1. Navigate to the RCMS start page (for QC8 this is at
gem904daq01.cern.ch:10000/rcms)
2. Enter the username and password
3. Verify that there are no currenly running configurations
- If there are, and the configureation is the one you need to
start, click on the link and select `Attach`, and if the run is
`Running` verify that it is OK to stop
- If there is no currently running configuration, navigate to the
`Configuration Chooser` and select the appropriate
configuration, and click `Create`
4. From this step, follow the procedure for your teststand to start a
run
- For QC8 this is:
1. Initialize
2. Configure
3. Execute `setDAQParamsPostConfigure.py` from the command line
with the appropriate options
4. Start
Happy calibrating and commissioning!
# Getting a Cosmic run with the CSC-GEM integration setup in building 904
This paragraph covers the reqired actions on the GEM side in order to be able to take Cosmic data on the integration setup using as Triggers the signals from the ME1/1 chamber, available on the setup.
As prerequisite, the GEM operator needs to have an account on the `cms904usr` network and `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 . Trying taking a run as test is adviseable.
1. Checkout and rebase interactively the branche of this MR https://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/162 onto main, keeping only the commit "WIP: Use external clock from TCDS"
2. The AMC13 needs to be configured to recieve the TCDS as input by connecting in the input slot the yellow fiber "B" on top, and "A" on the bottom from the TCDS.
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. On the `cms904usr` network, in `/nfshome0/cgalloni` there are 2 scripts (CSC_GEM_Local.sh and sendSOAP, that were provided by Karoly) that the operator can copy in their local folder.
5 The Cosmic run with the ME1/1 chamber providing the triggers, can be taken by using the above scripts to change in the right order the FSM of the GEM and the CSC.
```
sh CSC_GEM_Local.sh Configure
sh CSC_GEM_Local.sh Start
sh CSC_GEM_Local.sh Stop
```
6. Tha GEM raw data will be collected in the user's `/tmp/` folder, and overwritten at every run.
## 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>.
Trying taking a run as test 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. Checkout, install locally, and start the MR [cmsgemos!162](https://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/162).
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 `/nfshome0/gempro/bin`, 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 keep save the data somewhere it important.
