-
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
ManualParameter and tests #39
Conversation
I think Instrument should be an optional argument in ManualParameter, |
Yes, that's awkward - curious to see your solution 😄 - note that |
Just a github usage note (for everyone, but I noticed @damazter do it here) - it's better to make a new comment than to edit an existing one, unless you're just fixing a typo or something, because edits do not trigger email notifications |
I like the syntax and ease of use. I just pulled it in and will probably use it to replace some of the get-set constructs in my qubit object. Not all untill this is either merged in or we set on an alternative. Yesterday I had some discussion with @damazter on this subject. (see also #40 ). I think that this functionality is applicable more generally than the instrument class but not as general as the bare instrument class. Therefore it makes sense to insert a different parameter in the inheritance tree between the parameter (base class) and the instrument parameter. This also relates to another idea we were having (but did not agree on optimal implementation yet) which relates to wrapping of arbitrary functions. Suppose you have some function which you want to loop (and get as if it were a param). That could either be an extra possiblity in the syntax of the loop (increases complexity) or you create a new parameter for which the function is an input argument on instantiating. This is the exact same as when creating a par in an instrument (EDIT: and setting get_cmd = your function) except that there is no instrument there. |
This looks perfect to me, |
Great, I'm going to take your comments @damazter and @AdriaanRol as a 💃 and I'll take care of sync/async pairing in the |
ManualParameter and tests
👍 from me as well, seems useful to the numerics applications. |
if it makes any difference, 💃 👍 from me as well |
Awesome 👍 |
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
* docs: Example notebook for QDev specifics * docs: reader-friendly linewraps
@AdriaanRol @damazter @MarkusJacobsen @guenp this is re: #36 - pretty simple usage:
with an optional
initial_value
ManualParameter
inherits the defaultvals=Numbers()
fromParameter
- I think this is better thanAnything()
as a default but I guess it depends on how it will get used.