You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to propose a change in the Group class.
At the moment, this class is based purely on string commands to set/get the grouped parameters.
I believe QCoDeS would benefit from a more general implementation of this class that accepts generic callables.
The use case would be those instruments that do not rely on string commands and have a set/get function targetting a group of parameters.
In this view, the current implementation of the Group class would be a specific case in which the callable is the write/query function of the instrument with a command string.
Would this be of interest to the QCoDeS community?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I want to propose a change in the Group class.
At the moment, this class is based purely on string commands to set/get the grouped parameters.
I believe QCoDeS would benefit from a more general implementation of this class that accepts generic callables.
The use case would be those instruments that do not rely on string commands and have a set/get function targetting a group of parameters.
In this view, the current implementation of the Group class would be a specific case in which the callable is the write/query function of the instrument with a command string.
Would this be of interest to the QCoDeS community?
Beta Was this translation helpful? Give feedback.
All reactions