PDF (double-sided) - Physics Department, UCSB - University of ...

which it prepends with the current sweep position (the independent values) and
forwards to the Data Vault.
The Sweep Server will automatically call the “Run”-Setting multiple times in
different Contexts in parallel. This will cause the execution of the data taking to
be pipelined, as actions in different Contexts are automatically executed in parallel
whenever possible. In fact, this shields the developer of the “Run”-Setting almost
entirely from having to worry about pipelining. All that has to be guaranteed
is that the code passes control back to the API whenever it is waiting for other
Servers to handle Requests. Since this should be done in any case, though, it does
not really add any new requirements. Furthermore, the APIs, if written correctly,
will make it very easy to write code in this way.
The Sweep Client provides an interface to the Sweep Server that allows the user
to quickly define sweeps and execute them. Before running a sweep, it initializes
the dataset with the Data Vault and sets up the Registry Server and Qubit Server.
The Qubit Server makes the Sweep Client specific to our experimental setup while
the Sweep Server is completely general and can be used in other LabRAD Setups as
well. The Sweep Client allows the user to store sweep definitions in the Registry
and run them seamlessly on different qubit configurations.
It also provides a
progress-bar with an estimate of the remaining time until the sweep completes.
This can be extremely useful for preparing long sweeps that need to finish within
161