BNMR: Difference between revisions
en>Suz No edit summary |
en>Suz No edit summary |
||
Line 14: | Line 14: | ||
* <span style="color:#20b2aa; font-style=italic">bnqr</span> running on the BNQR high-voltage platform | * <span style="color:#20b2aa; font-style=italic">bnqr</span> running on the BNQR high-voltage platform | ||
Each experimental setup has its own [[#Hardware Components]] (i.e. a VME crate containing DAQ modules). Each runs as a separate MIDAS experiment named {{ | Each experimental setup has its own [[#Hardware Components]] (i.e. a VME crate containing DAQ modules). Each runs as a separate MIDAS experiment named {{bnmqr|join=and}}. DAQ software specific to these experiments (MIDAS clients e.g. frontends) run the experiments - see [[#Software Components]]. | ||
= Beam Control = | = Beam Control = | ||
Line 20: | Line 20: | ||
; single channel mode | ; single channel mode | ||
: where the beam is sent to one channel only, either BNMR or BNQR. Only one of the DAQ systems <span style="color:#7b68ee; font-style=italic">bnmr </span> | : where the beam is sent to one channel only, either BNMR or BNQR. Only '''one''' of the DAQ systems <span style="color:#7b68ee; font-style=italic">bnmr </span> or <span style="color:#20b2aa; font-style=italic">bnqr</span> is active. | ||
; '''dual channel mode''' | ; '''dual channel mode''' | ||
: where the beam is switched between the two channels BNMR and BNQR at regular intervals. Both DAQ systems <span style="color:#7b68ee; font-style=italic">bnmr </span> | : where the beam is switched between the two channels BNMR and BNQR at regular intervals. '''Both''' DAQ systems <span style="color:#7b68ee; font-style=italic">bnmr </span> and <span style="color:#20b2aa; font-style=italic">bnqr</span> are active. | ||
= Environment = | = Environment = | ||
Line 35: | Line 35: | ||
= Experimental Modes = | = Experimental Modes = | ||
A number of different experimental modes are defined for each of Type 1 (Integral) and Type 2 (TD) | A number of different experimental modes are defined for each of Type 1 (Integral) and Type 2 (TD) [[#Environment]]s. These allow different experimental modes to be run (e.g. Frequency scan, Na Cell scan). The modes used in recent years are shown in a brighter colour. These modes correspond to different programs downloaded into the [[#Hardware Components|PPG]] (i.e. to different pulse sequences) so are also known as '''PPG Modes'''. To understand what each experimental mode does, consult the appropriate '''timing diagram''' listed below. | ||
{| class="wikitable" border= | {| class="wikitable" border=0 cellspacing=3 cellpadding=1 style="background-color:white" | ||
|+ <b><center>Table 1 INTEGRAL and TIME DIFFERENTIAL Experimental (PPG) Modes</center></b> | |+ <b><center>Table 1 INTEGRAL and TIME DIFFERENTIAL Experimental (PPG) Modes</center></b> | ||
|- | |- | ||
| | | | ||
{| class="wikitable" border=0 cellspacing=3 cellpadding= | {| class="wikitable" border=0 cellspacing=3 cellpadding=2 style="background-color:#e6ffe6" | ||
|+ <b><center> Table 1a: Type 1 Integral Modes</center></b> | |+ <b><center> Table 1a: Type 1 Integral Modes</center></b> | ||
|- style="background-color: #ccffcc" | |- style="background-color: #ccffcc" | ||
Line 60: | Line 60: | ||
| Camp || 1c || 1c | | Camp || 1c || 1c | ||
|- | |- | ||
| Fast || 1g || Not available | | Fast * || 1g || Not available | ||
|- | |- | ||
| LCR | | LCR ** || 1j || Not available | ||
|- | |||
| colspan=3 style="font-size:80%"|*Combination of Modes 20 and 1f <br> **Combination of Modes 20 and 1c | |||
|} | |} | ||
| style="color:white"|spacer | |||
|rowspan=" | |rowspan="1" style="color:white"| | ||
{| class="wikitable" border=0 cellspacing=3 cellpadding= | {| class="wikitable" border=0 cellspacing=3 cellpadding=2 style="background-color:#ffe6ff" | ||
|+ <b><center> Table 1b: Type 2 Differential Modes</center></b> | |+ <b><center> Table 1b: Type 2 Differential Modes</center></b> | ||
|- style="background-color: #ffccff" | |- style="background-color: #ffccff" | ||
Line 85: | Line 88: | ||
| 2e || 2e || 2e | | 2e || 2e || 2e | ||
|- style="background-color:white; color:white " | |- style="background-color:white; color:white " | ||
| this<br>is<br> a<br> spacer | | this<br>is<br> a<br> spacer <br> a || || | ||
|- | |- | ||
|} | |} | ||
Line 119: | Line 120: | ||
The names of the VMIC running the frontend and MVME162 (the CAMP host) for {{bnmqr}} experiments are shown in Table 2 above. | The names of the VMIC running the frontend and MVME162 (the CAMP host) for {{bnmqr|join=and}} experiments are shown in Table 2 above. | ||
= Software Components = | = Software Components = | ||
The DAQ system is based on the [[MIDAS]] package. Data acquisition software to run the {{ | The DAQ system is based on the [[MIDAS]] package. Data acquisition software to run the {{bnmqr|join=and}} experiments has been written to run under MIDAS. This includes the frontend, custom logger etc. This software is mostly common to both experiments (differences between the two experiments are handled with '''ifdefs'''). | ||
The experiment is controlled using the MIDAS webserver (mhttpd). Due to the large number of experimental parameters required, Midas custom pages have been written for the experimenters to control and monitor their experiment. | The experiment is controlled using the MIDAS webserver (mhttpd). Due to the large number of experimental parameters required, Midas custom pages have been written for the experimenters to control and monitor their experiment. | ||
Line 130: | Line 131: | ||
The DAQ software components are started by the script ''start-all'' and stopped by the script ''kill-all''. | The DAQ software components are started by the script ''start-all'' and stopped by the script ''kill-all''. | ||
The main software components of the {{bnmqr}} experiments are | The main software components of the {{bnmqr|join=and}} experiments are | ||
{| class="wikitable" border=1 cellspacing=3 cellpadding= | {| class="wikitable" border=1 cellspacing=3 cellpadding=2 style="background-color:#f0f0f5" | ||
|+ <b><center> Table 3: Software Components</center></b> | |+ <b><center> Table 3: Software Components</center></b> | ||
|- style="background-color: #e0e0eb;" | |- style="background-color: #e0e0eb;" |
Revision as of 11:44, 27 April 2016
BNMR Experiments at TRIUMF
Purpose
These pages describe the Data Acquisition System (DAQ) for the BetaNMR (BNMR) and BetaNQR (BNQR) experiments at TRIUMF
Introduction
The Data Acquisition System is based on the MIDAS data acquisition package.
There are two separate experimental setups :
- bnmr running on the BNMR high-voltage platform
- bnqr running on the BNQR high-voltage platform
Each experimental setup has its own #Hardware Components (i.e. a VME crate containing DAQ modules). Each runs as a separate MIDAS experiment named bnmr and bnqr. DAQ software specific to these experiments (MIDAS clients e.g. frontends) run the experiments - see #Software Components.
Beam Control
The main TRIUMF EPICS Control System is used to control the beam, which can be switched to either experiment's beamline. There are two Beam Modes that the experiments can be run in:
- single channel mode
- where the beam is sent to one channel only, either BNMR or BNQR. Only one of the DAQ systems bnmr or bnqr is active.
- dual channel mode
- where the beam is switched between the two channels BNMR and BNQR at regular intervals. Both DAQ systems bnmr and bnqr are active.
Environment
For both experiments, two types of environment are defined (cf MUSR experiments):
- Integral (Type 1)
- Time Differential or TD (Type 2)
- Combination of the above two types
Experimental Modes
A number of different experimental modes are defined for each of Type 1 (Integral) and Type 2 (TD) #Environments. These allow different experimental modes to be run (e.g. Frequency scan, Na Cell scan). The modes used in recent years are shown in a brighter colour. These modes correspond to different programs downloaded into the PPG (i.e. to different pulse sequences) so are also known as PPG Modes. To understand what each experimental mode does, consult the appropriate timing diagram listed below.
|
spacer |
|
Hardware Components
DAQ hardware components for each DAQ system (BNMR/BNQR) include the following VME modules:
Module | Description | Manual | VME Base Address | BNMR | BNQR |
---|---|---|---|---|---|
SIS3801 version E | multichannel scaler A | SIS3801 | 0x2800 | yes | yes |
SIS3801 version E | multichannel scaler B | 0x1800 | yes | no | |
PPG (Pulseblaster) | Pulse Programmable module | PPG Spincore Pulseblaster |
0x8000 | yes | yes |
PSM | Pol Synthesizer module (RF) | PSM / PSMII AD9857 Quadrature Digital Upconverter |
0xC00000 | no | yes |
PSMII | Pol Synthesizer module II (RF) | 0xC00000 | yes | no | |
MVME162 | 68040 board, cpu runs CAMP (VxWorks) | bnmrvw | polvw | ||
VMIC | cpu runs frontend (Linux) | lxbnmr | lxbnqr |
The names of the VMIC running the frontend and MVME162 (the CAMP host) for bnmr and bnqr experiments are shown in Table 2 above.
Software Components
The DAQ system is based on the MIDAS package. Data acquisition software to run the bnmr and bnqr experiments has been written to run under MIDAS. This includes the frontend, custom logger etc. This software is mostly common to both experiments (differences between the two experiments are handled with ifdefs).
The experiment is controlled using the MIDAS webserver (mhttpd). Due to the large number of experimental parameters required, Midas custom pages have been written for the experimenters to control and monitor their experiment.
The custom logger (mdarc/midbnmr) saves the data into MUSR MUD format files, and the MUSR CAMP slow control system is used for slow controls. Analysis is done by physica.
The DAQ software components are started by the script start-all and stopped by the script kill-all.
The main software components of the bnmr and bnqr experiments are
Component | Purpose |
---|---|
frontend (runs on VMIC) | set up, operate and read hardware modules |
rf_config | check PPG parameters, download program to PPG |
mdarc | custom data logger saves data in MUD format |
midbnmr | converts MIDAS format saved data files to save in MUD format |
mheader | sends out CAMP and EPICS slow-control data to be saved in the MUD data file |
fe_epics | sends experimental data to EPICS (can be read by control-room) |
perlscripts | various perlscripts control changing experimental mode, checking and maintaining run numbering, etc. |
autorun | automatic run controller |
lcrplot | plots experimental data |
physica | analyse data, reads MUD format files |
Each of these components is described in more detail here.
DAQ Summary
- The VMIC front end computer runs the frontend code which
- controls PSM,PPG, VMEIO
- acquires data from SIS MCS module(s), builds histograms
- acquires data from CAMP, EPICS
- sends the data out into the data buffer
- The host computer (isdaq01)
- run all other software components
- starts/stops runs
- acquires the data from the data buffer
- logs the data
- monitors the experiment