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
While some configs may be general for the whole platform, some of them are specific to a certain instrument.
This was already taken into account in v0.1, by having scopes within the "instruments" section of the parameters.json files.
In spite of that, the connection has been lost in current v0.2, since we flattened the configurations to ease their access.
To avoid further attempts to parse the configs names (establishing some fixed convention for them), we may actually start optionally labeling the device-specific options with the device ID, such that they will only be passed down to the relevant one (possibly together with the general unlabeled section).
The text was updated successfully, but these errors were encountered:
While some configs may be general for the whole platform, some of them are specific to a certain instrument.
This was already taken into account in v0.1, by having scopes within the
"instruments"
section of theparameters.json
files.In spite of that, the connection has been lost in current v0.2, since we flattened the configurations to ease their access.
To avoid further attempts to parse the configs names (establishing some fixed convention for them), we may actually start optionally labeling the device-specific options with the device ID, such that they will only be passed down to the relevant one (possibly together with the general unlabeled section).
The text was updated successfully, but these errors were encountered: