The Pulse-Sequence Instrument Control Tool. Developing scripts to allow string-based input to Labber for more flexible control over pulse sequence configurations.
MIT License
3
stars
1
forks
source link
Hidden dependencies for setting values through additional interfaces #10
When using the additional parameter setting methods (set_api_client_values and set_instr_config_values) which are required to set eg strings for the MultiPulse pulse definition/sequence files, these methods cannot be used entirely independently.
For example, using set_instr_config_values requires having an entry in the set_api_client_values method even if no value is being set there.
While cleaning this up, it would be good to clean up the separate interfaces in general. Currently there are 4.5 interfaces and some of them have conflicting names in the backend.
Original report by Samuel Wolski (Bitbucket: 557058:90b732eb-6ab1-4b27-9495-eb00eafde259, GitHub: samwolski).
When using the additional parameter setting methods (
set_api_client_valuesandset_instr_config_values) which are required to set eg strings for the MultiPulse pulse definition/sequence files, these methods cannot be used entirely independently.For example, using
set_instr_config_valuesrequires having an entry in theset_api_client_valuesmethod even if no value is being set there.While cleaning this up, it would be good to clean up the separate interfaces in general. Currently there are 4.5 interfaces and some of them have conflicting names in the backend.