taking-data.md

Taking calibration scans & data

The scans and the analyses of the scans need to follow a specific naming convention:

<sbit-rate-scan|gbt-phase-scan|latency-scan|dac-scan|cal-pulse-scan>-<in|out>-[<comment>-]-<date+revision>

Meaningfull scans that are supposed to be stored for future reference are to be stored in the path /gemdata/data/ with the above naming convention.

Taking a calibration scan at P5

Starting the scan

To take a calibration scan, first connect to RCMS, then create the Local/GEM-Local configuration or attach to a running configuration. From the RCMS interface, click on "Initialize". Open the GEM supervisor and click on "Initialize" again.

Open the GEM calibration suite. In case the calibration suite page was already opened before, reload the page manually. In case the URL was changed, open the status table by the appropriate button and open the GEM calibration interface from the list of running applications.

From the dropdown menu, select the desired calibration type and parameters. Please refer to the Scan specifics section below for more details on the calibration types and parameters. Click on "Apply settings".

Return to the supervisor, leaving the calibration web page open, and click "Configure". Once configured, press "Run" in the calibration web page.

While the scan is ongoing, from any p5 GEM DAQ machine check that the output files are being written in the output directory. You can also check in the logs present in /gemdata/log/ what the software is doing. Write down the run number as displayed in the GEM supervisor.

Scan specifics

S-bit rate scan

• Calibration type: S-bit ARM DAC Scan
• Parameters: (defaults)
• Output path: /gemdata/runs/local/runE.DDDD.SSSSSL
• Comment: Consider that usually S-bits scans are taken without HV amplification to investigate the noise level in the detector, so you might need to take action with the DCS on the HV settings.

Calibration pulse scan

• Calibration type: Calibration Pulse Scan
• Parameters: (defaults)
• Output path: /gemdata/runs/local/runE.DDDD.SSSSSL
• Comment: (none)

Analyzing an S-bit rate scan

To analyze an S-bit scan locate first the output in /gemdata/runs/local/runE.DDDD.SSSSSL. If these data are meant to be saved for later reference or analysis, link the directory in the path /gemdata/data/ with the naming convention:

<sbit-rate-scan-in-[<comment>]-<data+revision>

At these point analyze the scan using the command gemos analyze sbit from the terminal of gem-locdaq02: the path of the input file and output directory need to be specified, as well as the options for the plotting and allowed rate for the thresholds settings.

Taking a MiniDAQ run with given threshold

To take a run with fixed threshold, first connect to RCMS, then create a MiniDAQ3 session or attach to a running session. From the RCMS interface, click on "Initialize" and "Connect".

Open the GEM calibration suite. In case the calibration suite page was already opened before, reload the page manually. In case the URL was changed, open the status table by the appropriate button and open the GEM calibration interface from the list of running applications.

Select the "Physics" option in the drop down window. The option to use a given threshold for all VFATs instead of the one from the VFAT configuration can be chosen (Same for all VFAT) and the threshold can be set. Click on the "Apply settings" button.

Return to RCMS and enable the transfer to Tier-0 (T0) in the drop down window below the "DAQ" sub-system column, if the data are intended to be saved to disk. It is the case if the data is to be given to the DPG for analysis.

From the RMCS interface, press on "Configure" and "Start". Once the statistics will be satisfactory, the run should be stopped with the "Stop" button. Then the MiniDAQ instance can be destroyed with the "Destroy" button in the Automator control bar.

Taking a CSC-EMTF-GEM join run on the integration setup in building 904

This paragraph covers the required actions on the GEM side in order to be able to take cosmic data on the GE1/1 integration setup using as triggers the signals from the ME1/1 chamber, available in the setup.

As prerequisite, the GEM operator needs to have an account in the cms904 network (linked to the cms network) and a developer account on the gem904daq04 machine. The operator needs to have the GEM DAQ software installed and working correctly, as per the instructions https://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos. Taking a test run is advisable.

1. The AMC13 needs to be connected to the b904 TCDS sub-system by connecting to its TTS/TTS input the TCDS yellow fiber with "B" on the top and "A" on the bottom.
2. Start the GEM xDAQ executive with the b904int-ge11-join-runs configuration.

CMSGEMOS_CONFIG_NAME=b904int-ge11-join-runs CMSGEMOS_PORT=20100 _build/_install/bin/gem-start-xdaq

3. Connect to the xDAQ GEM supevisor page and initialize the GEM FSM. Refer to the CSC DAQ expert (usually Karoly Banicz) to have the proper configuration of the CSC ME1/1 chamber.
4. The script CSC_GEM_Local.sh available in the cms904 network, in the /nfshome0/gempro/bin folder, is used to trigger the state transitions is the proper order.
5. The cosmic run with the ME1/1 chamber providing the triggers, can be taken by using the above script to change, in the right order, the FSM of the GEM and the CSC.

/nfshome0/gempro/bin/CSC_GEM_Local.sh Configure
/nfshome0/gempro/bin/CSC_GEM_Local.sh Start
/nfshome0/gempro/bin/CSC_GEM_Local.sh Stop

6. The GEM raw data will be stored in the user's temporary folder, $TMPDIR, and overwritten at every run. Be careful to save the data somewhere if it is important to be kept.