@@ -31,12 +31,15 @@ This paragraph covers the required actions on the GEM side in order to be able t
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.
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. Checkout, install locally, and start the MR [cmsgemos!162](https://gitlab.cern.ch/cmsgemonline/gem-daq/cmsgemos/-/merge_requests/162).
2. Start the GEM xDAQ executive with the `b904int-ge11-join-runs` configuration.
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.
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
...
...
@@ -44,4 +47,4 @@ Trying taking a run as test is advisable.
/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.
Be careful to save the data somewhere if it is important to be kept.
