The source project of this merge request has been removed.
Draft: Enhance details in documentation
4 unresolved threads
4 unresolved threads
This merge provides to the docs/operations/taking-data
documentation with slightly more detailed steps to perform GEM DOC analysis analysis including some snapshots of important steps.
Merge request reports
Activity
27 - Click on "Apply settings". 28 29 <img src="https://i.imgur.com/eTd251h.png"> 24 30 25 Return to the supervisor, **leaving the calibration web page open**, and click "Configure". 31 4. Return to the supervisor, **leaving the calibration web page open**, and click "Configure". 26 32 Once configured, press "Run" in the calibration web page. 27 33 28 While the scan is ongoing, from any p5 GEM DAQ machine check that the output files are being written in the output directory. 29 You can also check in the logs present in `/gemdata/log/` what the software is doing. 30 **Write down the run number as displayed in the GEM supervisor.** 34 <img src="https://i.imgur.com/raBLDNV.png"> 35 36 37 38 While the scan is ongoing, from any p5 GEM DAQ machine (e.g. `gem-daq01`, `gem-daq02`, ...) 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. changed this line in version 2 of the diff
54 69 55 70 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. 56 71 72 57 73 ## Taking a MiniDAQ run with given threshold 58 74 59 To take a run with fixed threshold, first connect to [RCMS](http://cmsrc-gem.cms:20000/rcms), then create a MiniDAQ3 session or attach to a running session. 75 To take a run with fixed threshold: 76 - Connect to [RCMS](http://cmsrc-gem.cms:20000/rcms), then create a MiniDAQ3 session or attach to a running session. changed this line in version 2 of the diff
9 9 ## Taking a calibration scan at P5 10 10 11 11 ### Starting the scan 12 12 13 To take a calibration scan, first connect to [RCMS](http://cmsrc-gem.cms:20000/rcms), then create the `Local/GEM-Local` configuration or attach to a running configuration. 14 From the RCMS interface, click on "Initialize". 15 Open the [GEM supervisor](http://srv-s2g18-33-01.cms:20200/urn:xdaq-application:service=supervisor) and click on "Initialize" again. 13 To take a calibration scan, follow the next general steps: 16 14 17 Open the [GEM calibration suite](http://srv-s2g18-33-01.cms:20200/urn:xdaq-application:service=calibration). 18 In case the calibration suite page was already opened before, reload the page manually. 19 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. 15 1. Connect to [RCMS](http://cmsrc-gem.cms:20000/rcms) (Run Control and Monitoring System) as `gempro` (ask to some of the GEM RC members for the password), then create the `gempro/Local/GEM-Local` configuration or attach to a running configuration. From the RCMS interface, click on "Initialize". 20 16 21 From the dropdown menu, select the desired calibration type and parameters. 17 <img src="https://i.imgur.com/0mJHRcn.png"> Better to avoid using external services, the images can very well be stored in this Git repository and trivially embedded in the Markdown document without relying on raw HTML tags. For example with

. Would the number of images and their sizes explode, we can think about using Git LFS.changed this line in version 2 of the diff
12 12 13 To take a calibration scan, first connect to [RCMS](http://cmsrc-gem.cms:20000/rcms), then create the `Local/GEM-Local` configuration or attach to a running configuration. 14 From the RCMS interface, click on "Initialize". 15 Open the [GEM supervisor](http://srv-s2g18-33-01.cms:20200/urn:xdaq-application:service=supervisor) and click on "Initialize" again. 13 To take a calibration scan, follow the next general steps: 16 14 17 Open the [GEM calibration suite](http://srv-s2g18-33-01.cms:20200/urn:xdaq-application:service=calibration). 18 In case the calibration suite page was already opened before, reload the page manually. 19 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. 15 1. Connect to [RCMS](http://cmsrc-gem.cms:20000/rcms) (Run Control and Monitoring System) as `gempro` (ask to some of the GEM RC members for the password), then create the `gempro/Local/GEM-Local` configuration or attach to a running configuration. From the RCMS interface, click on "Initialize". 20 16 21 From the dropdown menu, select the desired calibration type and parameters. 17 <img src="https://i.imgur.com/0mJHRcn.png"> 18 19 2. Open the [GEM supervisor](http://srv-s2g18-33-01.cms:20200/urn:xdaq-application:service=supervisor) and click on "Initialize" again. 20 added 2 commits
- 0ada899b - Implement corrections
- b431f8c8 - Merge branch 'main' of https://gitlab.cern.ch/destrada/gem-daq-doc into main
mentioned in merge request !11
Please register or sign in to reply