BNMR: CAMP
Links
Introduction
The MUSR software package CAMP is used for the slow controls for the bnmr and bnqr experiments. The CAMP server runs on a MVME162 located in the VME crate. The CAMP system itself is accessed using the #CAMP User Interface (CUI). Using the CUI, the user can define instruments to be accessed by the DAQ system during the experiment.
CAMP Hostname
The CAMP Hostname is
- bnmrvw.triumf.ca for the bnmr experiment or
- polvw.triumf.ca for bnqr experiment
The CAMP hostname is set in two places in the DAQ system :
- environment variable CAMP_HOST
- In the ODB at /Equipment/FIFO_acq/mdarc/camp/camp hostname. See #Automatic CAMP variables.
The names set in the two places must be identical.
CAMP in BNMR/BNQR
The CAMP system is used for three purposes in the BNMR/BNQR experiments:
- CAMP slow controls using the #CAMP User Interface
- logging of CAMP data to the saved file
- CAMP scan experiment(s)
- Experimental Modes 1c and 1j, where a CAMP slow controls device is scanned while data is taken.
CAMP User Interface
To access the CUI, in an xterm type "camp".
[bnmr@isdaq01 ~]camp
A display similar to Figure 1 will appear.
The camp command will use the default camp hostname defined by the environment variable CAMP_HOST (bnmrvw.triumf.ca in Figure 1).
To access the Camp User Interface using a different camp host (temporarily), specify the camp hostname, e.g.
[bnmr@isdaq01 ~]camp -node polvw
CAMP Logging
Logging of CAMP data to the saved file is handled differently for
- Type 1 (I-MUSR) runs
- Type 2 (TD-MUSR) runs
In both cases, #Automatic CAMP variables are saved.
Automatic CAMP variables
Automatic CAMP variables are listed in ODB at path /Equipment/FIFO_acq/mdarc/camp/ and can be easily accessed by clicking on the alias link "AutoHeaders" in the section "Review Run Parameters" on the Custom Status Page (Figure 2). This will result in a page displayed similar to Figure 3.
The user enters the full CAMP path for "temperature variable" and "field variable", or blank if not used. The CAMP paths must be written exactly as they appear in the #CAMP User Interface. Automatic CAMP variables, if defined, are saved for both Type 1 and Type 2 experimental modes.
- NOTE
- These variables must also be set loggable in the CAMP CUI (Figure 5) where "Logging" has been set to "log_mdarc".
For an explanation of the purpose of each key, see Keys in /Equipment/FIFO_acq/mdarc/camp subtree.
Type 1 (I-MUSR)
#Automatic CAMP variables, if defined, and set loggable in the CAMP CUI are logged automatically. Other CAMP variables to be logged in a Type 1 (I-MUSR) experiment must be listed in the ODB tree /Equipment/Camp/Settings. Clicking on the alias link "Camp Logging" (Figure 2) in the section "Review Run Parameters" on the Custom Status Page will display the keys in this ODB subdirectory most relevent to the user (Figure 4).
Note that in Figure 4, only the first 7 of the listed camp paths are actually logged (num_camp_logged=7). The complete subtree with explanation of each key is shown here. The CAMP logging is performed by the client BNMR: mheader.
Type 2 (TD-MUSR)
All CAMP variables to be logged (including Automatic CAMP variables) must be set loggable in the CUI. For Type 2 runs, the client mdarc reads those variables set loggable directly from CAMP, and saves the data in the MUD file.
Set CAMP variable loggable
All CAMP variables to be logged must be set loggable in the #CAMP User Interface, as in Figure 5, where "Logging" has been set to "log_mdarc". This includes #Automatic CAMP variables.
