Replies: 1 comment 1 reply
-
@klkl0808 If the object is to have a nice, formatted instrument name where you are free to use any character etc then that sounds like a good solution and I would be happy to review such a pr. However, using it for the issue discussed in #4289 I think that this would be the wrong solution and something more robust should be developed. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm writing this suggestion as a user of the quantify framework, which uses QCoDeS instruments in many places. (Even though this is related, this is a different suggestion than in this discussion).
When displaying instrument information to the user, quantify refers to the instrument by the instrument name. There were no restrictions on the naming, so that these instrument names had a reasonably nice format (including spaces, angle brackets, ...). Since instrument names need to be valid identifiers (introduced in this PR), we cannot display nice instrument names anymore.
I realize that quantify has been abusing the instrument name in the past. But I'm wondering if there is a use case for instrument labels. In the same way in which Parameters have labels that can be displayed nicely, could instruments also carry a label? This way, instrument information can be displayed nicely.
Beta Was this translation helpful? Give feedback.
All reactions