Configuring ACQ4 involves editing ‘.cfg’ files in the config directory. In these files, you may define:
The devices in your system
The list of loadable modules
Data storage locations
When ACQ4 is started, it first checks to see whether a configuration file has been specified on the command line using the
-b flag. Next, it searches through the following paths looking for a ‘default.cfg’ file:
/etc/acq4 (unless running on Windows)
The last two paths in the list are possible locations of example configuration files included with ACQ4. The example configuration contains examples of every kind of device supported in ACQ4. Most of these entries are disabled in the configuration; the active devices can be run without any hardware to demonstrate the capabilities of ACQ4.
The fastest way to get started with a fresh installation is to run ACQ4 (by running
python -m acq4 or
acq4 or by clicking a shortcut, depending on your method of installation). If ACQ4 is running from an example configuration, a message will be displayed giving the location of this configuration. Copy all files from this location into its parent ‘config’ directory, and begin editing (a source code editor is very helpful here).
.cfg File Syntax¶
It is important to first understand that a ‘configuration’ is a single document, but for organization this document is often split up across multiple .cfg files. At its most basic level, a configuration is a list of name:value pairs:
storageDir: "/home/user/data" defaultCompression: None
In the example above, the name “storageDir” is assigned the value “/home/user/data”. Values may also contain nested lists of name:value pairs:
Camera: driver: 'PVCam' serial: 'PCICamera0' parentDevice: 'Microscope' exposeChannel: # Channel for recording expose signal device: 'DAQ' channel: '/Dev1/port0/line0' type: 'di'
In this example, we have Camera.driver = ‘PVCam’, Camera.serial = ‘PCICamera0’, Camera.exposeChannel.device = ‘DAQ’, and so on. This syntax allows the creation of arbitrarily complex hierarchies of configuration data. Note that each nested level must have the same number of indentation spaces for each line.
Since this configuration tree can become quite large and complex, it is often useful to break off the larger branches and move them to a file of their own:
This example would read the entire contents of ‘folderTypes.cfg’ and insert that as the value for ‘folderTypes’.
Further notes about this syntax:
You can use “double” or ‘single’ quotes, but not “both’
File or directory names should be quoted and use forward slashes (/) on Linux and OSX or double-back slashes (\\) on Windows (eg “/home/user/data” or “C:\\data\\user”).
Some options will call for a list of values. This can be given just by separating the values with commas inline like
value1, value2or with brackets like
All values are evaluated as Python expressions and basic unit symbols are provided, so it is possible to include mathematical expressions like
scale: (200 * pA) / (100 * mV)
Finally, you may add comments to .cfg if they are preceded with a hash (#) symbol
When ACQ4 first starts, it searches a few default locations for a file named ‘default.cfg’ (it is possible to override this with the
-c flag). The structure of this file should look like:
storageDir: "storage/dir" imports: [...] execFiles: [...] modules: ... devices: ... folderTypes: ... configurations: ...
In this format:
storageDir specifies the default location where data should be stored when no other location is specified.
imports and execFiles specify lists of either module names to execute, or python file names to exec(), respectively. These allow custom extension code to be loaded at startup.
All other sections are discussed below:
After reading through the configuration files, ACQ4 displays the Manager module’s user interface. Within this UI is a menu of all other UI modules that are known to ACQ4, from which the user can simply click to launch these modules. The modules configuration section described here allows customization of the entries in this menu. By default, all modules will appear once in the menu, and launching them simply invokes their default configuration. By adding entries to this configuration section, we can:
Change the default configuration parameters each module wil be loaded with
Add multiple entries for each module, with different configuration options for each entry
Set a keyboard shortcut that will raise the main window for each module
The format for defining a pre-configured module is:
UniqueName: module: "ModuleName" config: ...config options... shortcut: "shortcut key"
Here, ModuleName must refer to one of the userModules registered to ACQ4 (the builtin modules live in
acq4/modules/). The exact options specified under config will differ depending on the module being loaded. The shortcut key specifies a keyboard shortcut that can be used to raise the module’s window (for example: ‘F2’, ‘Ctrl+M’, or ‘Alt+Enter’). Taking this example, a very common module list might look like this:
modules: Data Manager: module: 'DataManager' # After the user loads the Data Manager module, pressing F2 will raise its window: shortcut: 'F2' Task Runner: module: 'TaskRunner' shortcut: 'F6' config: # Set the directory where Task Runner stores its saved tasks. taskDir: 'config/example/tasks' Camera: module: 'Camera' shortcut: 'F5' Patch Clamp 1: # We have 2 patch clamp devices, but the Patch module only supports 1 at a time. # Therefore, we make two menu entries for this module, with a different device # configured for each entry. module: 'Patch' shortcut: 'F3' config: clampDev: 'Clamp1' Patch Clamp 2: module: 'Patch' shortcut: 'F4' config: clampDev: 'Clamp2'
The format for defining a device is:
UniqueName: driver: "deviceType" ...
Here, deviceType refers to one of the device types defined in the directory acq4/devices (examples: NiDAQ, MultiClamp, Microscope). Any further options will depend on the device, and are described in the documentation for that device type (see Devices). Refer to the example configuration in acq4/config/example.
ACQ4 gives the user full control over deciding how best to organize their raw data as it is being collected. For example, a typical user might create a folder for every day they run experiments, and a sub-folder for every cell they record from. Each folder can be annotated by the experimenter, and often we want these annotations to be consistent from day to day. To facilitate this, we can define a set of folder types with a specific list of the data that should be annotated for each type. These types appear in the Data Manager module when adding new folders, and the annotations are automatically displayed as a form to be filled out by the experimenter.
The basic syntax for a folder type is:
UniqueName: name: 'storageName' info: ...
Here, UniqueName is the name that will appear in the Data Manager module list of folder types. storageName specifies how each new folder will be named as it is created, including the possibility for date formatting (“%Y.%m.%d”). info is a list of name:value pairs that specify the set of meta-data fields to be included with each folder type. There are two types of input that can be specified:
fieldName1: 'text', number_of_lines fieldName2: 'list', ['option1', 'option2', 'option3']
For either field type, information will be stored as plain text. If the field type is list, then the user will see a drop-down menu of options to choose from (although it will still be possible to type in any arbitrary response). If the field type is text, then the user will simply see an empty text box to type in.
The following is a complete example of a folder type used to contain all data collected for a single day. The metadata fields for this folder type represent aspects of the experiment that are expected to be constant for the entire day:
Day: name: "%Y.%m.%d" # folder will be named YYYY.MM.DD info: description: "text", 6 species: "list", ["C57 Mouse", "CBA Mouse", "Rat"] age: "string" sex: "list", ['M', 'F'] weight: "string" temperature: "list", ['34C', '25C', '37C'] solution: "list", ["Standard ACSF", "Physiological ACSF"]
For further reference, see the file config/example/folderTypes.cfg in the ACQ4 distribution.
Commonly, acquisition systems will be accessed by mutiple users requiring different configuration settings. One way to achieve this is to create a completely different set of configuration files for each user and specify which to use when starting the program. A simpler way is to define just the differences between these configurations and select them after the program has been started.
The configurations section allows us to define a set of named modifications to the default configuration. For example: all users on a system want to use the same device and module configuration, but define their own data storage directory:
configurations: Jeffrey: storageDir: 'C:\\data\\jeffrey' Walter: storageDir: 'C:\\data\\walter' Maude: storageDir: 'C:\\data\\maude'
In the example above, the three names would appear in the Manager module as loadable configurations. This allows each user to quickly select their storage settings. The settings for each user can be anything that would appear at the top-level configuration. Thus, users can specify their own folder types, preconfigured modules, etc (however devices may not be defined here).
imports is an optional list of extra Python modules to import. This may be used to load any custom extensions when ACQ4 starts.
execFiles is an alternative to imports that lists the full paths of Python files to execute. These may be used to load custom extensions without requiring the files to be importable modules.
defaultCompression defines the HDF5 compression filter and options used by default. Modules are encouraged to use this default value, but in some cases may specify a different compression filter. Options are:
‘lzf’ - Very fast compression (generally fast enough for video and multichannel acquisition), but the LZF filter is usually not available outside Python. External HDF5 viewers and analysis tools such as MATLAB and Igor will be unable to read these files unless they are re-compressed with a different filter.
‘gzip’ - Slower compression, but generally available everywhere HDF5 is supported. You may also specify a pair of values (‘gzip’, N), where N is an integer 0-9 specifying the compression level to use. Even at the fastest setting, gzip compression may cause a significant performance decrease while acquiring video or multichannel signals.
‘szip’ - Faster compression, but patent-encumbered and lacks write support on Windows.
None - No compression.
By default, no compression is used due to the shortcomings of each of the available filters.
This option was added in version 0.9.3.