-
Notifications
You must be signed in to change notification settings - Fork 315
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
default Instrument get_idn returns a warning #517
Comments
I agree with this. I think that the connect message (that raises this warning) can be very useful. |
@peendebak @AdriaanRol, yes agree. I guess this was written with the assumption that all instruments have the arcane visa IDN command. Not sure what's best:
I would go for 1, but we have to check how many instruments inherit from IP and speak visa ! |
@giulioungaretti , Another quite common use case for us is to have virtual or meta instruments. These talk to lower level instruments and generally do not have an IDN command (as they only exist in python). I think a sane default would make most sense. That would still be consistent with -1 but would also require a sane connect message. |
@giulioungaretti @AdriaanRol Shall I create a PR with option 3). A default that we use right now is:
|
@peendebak that would be really awesome! |
For any
Instrument
that does not have aself.ask('*IDN?')
a warning is generated. This is inconvenient for all derived classes that do not have a VISA interface.The warning is generated here:
https://github.com/QCoDeS/Qcodes/blob/master/qcodes/instrument/base.py#L130
A minimal example:
Can we remove the warning (or change it into a
logging.info
)?@giulioungaretti
The text was updated successfully, but these errors were encountered: