Parameter Vault Server

Introduction

We use the Parameter Vault server to retrieve and set experimental parameters. The advantage of using this server instead of storing experimetnal parameters in the Registry is the additional provided features:

• Notification when any parameter is changed. (Registry only emits signals when a parameter in the same directory is changed).

• Support for bounds-checking for set parameters, including for custom parameter types (scan, selection etc.). For example this will disallow setting a voltage to an unreasonably high value.

• Easy grouping of parameters by collection. For example all of Doppler cooling frequencies and amplitudes are stored together in the DopplerCooling collection.

• Seamless interface with the ScriptScanner GUI.

When the Parameter Vault starts, the parameters are loaded from the Registry. Then over the course of the experiments we interact with Parameter Vault to modify them. When the servers exits, the parameters are saved back to the Registry. The interaction with the Parameter Vault is primarily graphical through the ScriptScanner interface. That interface automatically creates appropriate GUIs to modify the stored parameter types. Furthermore ScriptScanner is able to display only the parameters relevant to the specific experiment.

Registry Saving

The parameters are initially retrieves from the Registry. The directory is set with registryDirectory list in the server to be ['','Servers', 'Parameter Vault']. In that path, any folder will become a collection of the parameters that are stored inside. The parameters are stored as key-value pairs where key is the name of the parameter and value is a tuple in the form (parameterType, value). Here parameterType is a string e.g 'parameter' or 'scan' and value is the corresponding parameter value.

Supported types

• Parameter

Version Control

Version 2.0

• Stable.