make sure it is updated and easy to read.
A convenient container for instruments, parameters, and more.
A representation of one particular piece of hardware.
Functions this hardware is
capable of, and handles the underlying communication with the
Instrument sets the common structure but real
instruments will generally derive from its subclasses, such as
VisaInstrument. There is also
MockInstrument for making simulated instruments, connected to a
Model that mimics a serialized communication channel with an
add all the things from the github issue
A representation of one particular state variable.
Parameters are part of an
Instrument, and parameter is
linked to specific commands that are sent to a specific instrument.
But you can also create
execute arbitrary functions, for example to combine several gate
voltages in a diagonal sweep. Parameters can have setters and/or getters
(they must define at least a setter OR a getter but do not need to
Parameters often return one value, but can return a
collection of values - several values with different names, or one or
more arrays of values, ie if an instrument provides a whole data set at
once, or if you want to save raw and calculated data side-by-side
Parameters take a single value, and can be sliced to
Defines a set of valid inputs, and tests values against this set
MultiType, each of which takes various arguments that
restrict it further.
An iterator that provides values to a sweep, along with a setter for
those values connected to a
SweepFixedValues subclass is used (this is flexible
enough to iterate over any arbitrary collection of values, not
necessarily linearly spaced) but ot