-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Inspiration] Zurich Instruments LabOne #16
Comments
@AdriaanRol Wow, that company makes slick looking stuff. It's like Apple for science :) |
Something similar to QCodes from the Ion trap community. http://m-labs.hk/artiq/ |
Whoa, artiq looks neat - kind of a python compiler for FPGAs... a little overlap but mostly it just looks like a cool system for us to integrate with when we want to involve FPGAs in our experiments. Nice find @AdriaanRol |
Close for now, this things will now got to slack unless somebody has a different strong opinion :D |
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
* Fix: correctly sort instruments in device annotator * Fix: device annotator improve formatting * Fix: use pyqt5 directly
Last week at the ScaleQIT conference there was a presentation by Zurich Instruments.
Afterwards I had a discussion with one their employees, about the software they created for controlling their instruments LabOne. I think there are some good ideas in there that we could use when thinking about a gui.
I think the central idea is to have on instrument server that all the specific gui's talk to (with the addition of showing the commands you clicked aswell). We could use a similar approach where we start the instrument server (and other qcodes processes) in one notebook to which we can then connect using other notebook instances and/or specific instrument gui's.
This might already be similar to the ideas floating around here but I tought it could be interesting to take a look at.
p.s. I'd say that strictly speaking this is not really an issue but I thought it would be useful to share it here anyway, if anyone has a better suggestion for these kinds of discussions I'm open to it.
The text was updated successfully, but these errors were encountered: