Repository navigation
Making QCoDeS drivers findable by instrument model (sample for corrections) #8750
sebastien michea (smichea)
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi, I'm Sebastien, the creator of OpenDeviceDB, an open-source catalogue that links device models to the open drivers, firmware and tools that already support them. PyMeasure maintainers pointed me to the Python lab automation landscape, and QCoDeS stood out for its clean one-class-per-model driver layout.
I've prepared an importer that would let someone looking up, say, a Keithley 2450 or a Rohde & Schwarz ZNB20 find the QCoDeS driver class and its documentation. It is a draft PR, not merged, and I'd like your corrections first.
How it works:
A few sample records:
Keithley2450Keithley6500Keysight34465ARohdeSchwarzZNB20SR860RigolDP832LakeshoreModel372DynaCoolQuestions:
Agilent34410AandKeysight34410Aboth exist. Should we treat them as one instrument (the Keysight-branded 34410A) or keep both names?Thanks for QCoDeS. Written with AI assistance.
All reactions