-
Notifications
You must be signed in to change notification settings - Fork 319
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
MultiParameter usability issues #498
Comments
|
More of an Array parameter issue probably but anyway. If you do a measurement of an array parameter the setpoint array is correctly created as a data array in the dataset but not labled as is_setpoint=True |
I wanted to ask whether this issue is still actively pursued? I think I also read in some places that the MultiParameter might be deprecated at some point? |
This is not something that anyone to my knowledge are actively working on at the moment. None the less I think the MultiParameter sill has issues. If you have some concrete suggestions for improving the MultiParameter (or an alternative design) we are definitely happy to discuss that |
Maybe to give a bit more context on my view of the MultiParameter: As for concrete suggestions:
|
Just some notes of various issues that we should improve with respect to MultiParameters
nt, DataArray, collections.Sequence, collections.Iterator
whichnumpy.ndarray
is not. If you add it to the check it will fail with a type error (see below). I have not tested if DataArrays work correct. Converting to a tuple solved the immediate problemThe text was updated successfully, but these errors were encountered: