Merge branch 'feature/local-configuration' into 'main'

Take calibration scans with the new local configuration

See merge request cmsgemonline/gem-ops/gem-daq-doc!8

docs/operations/taking-data.md

@@ -10,10 +10,11 @@ Meaningfull scans that are supposed to be stored for future reference are to be
 
 ### Starting the scan
 
-To take a calibration scan, first connect to [RCMS](http://cmsrc-gem.cms:20000/rcms), then create a MiniDAQ3 session or attach to a running session.
+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.
+From the RCMS interface, click on "Initialize".
+Open the [GEM supervisor](http://srv-s2g18-33-01.cms:20200/urn:xdaq-application:service=supervisor) and click on "Initialize" again.
 
-From the RCMS interface, click on "Initialize" and "Connect".
-Open the [xDAQ](http://srv-s2g18-33-01.cms:20400/urn:xdaq-application:service=calibration) calibration suite.
+Open the [GEM calibration suite](http://srv-s2g18-33-01.cms:20200/urn:xdaq-application:service=calibration).
 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.
 
@@ -21,13 +22,12 @@ From the dropdown menu, select the desired calibration type and parameters.
 Please refer to the [Scan specifics](#scan-specifics) section below for more details on the calibration types and parameters.
 Click on "Apply settings".
 
-Go to the RCMS interface, **leaving the calibration web page open**, and click "Configure".
-Then, in the calibration web page, press "Run".
+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.
-
-**The output files needs to be copied/moved otherwise they will get overwritten by the next scan.**
+**Write down the run number as displayed in the GEM supervisor.**
 
 ### Scan specifics
 
@@ -35,20 +35,20 @@ You can also check in the logs present in `/gemdata/log/` what the software is d
 
 * Calibration type: `S-bit ARM DAC Scan`
 * Parameters: (defaults)
-* Output path: `/gemdata/runs/minidaq/sBitRateScan`
+* 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/minidaq/calPulseScan`
+* 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/minidaq/sBitRateScan`.
-If these data are meant to be saved for later reference or analysis, copy the directory in the path `/gemdata/data/` with the naming convention:
+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>`
 
@@ -57,9 +57,9 @@ At these point analyze the scan using the command `gemos analyze sbit` from the
 ## Taking a MiniDAQ run with given threshold
 
 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.
-
 From the RCMS interface, click on "Initialize" and "Connect".
-Open the [xDAQ](http://srv-s2g18-33-01.cms:20400/urn:xdaq-application:service=calibration) calibration suite.
+
+Open the [GEM calibration suite](http://srv-s2g18-33-01.cms:20400/urn:xdaq-application:service=calibration).
 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.
 

docs/references/bookmarks.md

@@ -13,6 +13,9 @@
 * MiniDAQ
     * [Supervisor](http://srv-s2g18-33-01.cms:20400/urn:xdaq-application:service=supervisor)
     * [Calibration suite](http://srv-s2g18-33-01.cms:20400/urn:xdaq-application:service=calibration)
+* Local
+    * [Supervisor](http://srv-s2g18-33-01.cms:20200/urn:xdaq-application:service=supervisor)
+    * [Calibration suite](http://srv-s2g18-33-01.cms:20200/urn:xdaq-application:service=calibration)
 
 ### Monitoring tools
 
@@ -20,5 +23,5 @@
     * [FED1467](http://srv-s2g18-33-01.cms:20300/urn:xdaq-application:service=fed1467-monitor)
 * GEM+ (GE+1/1)
     * [FED1468](http://srv-s2g18-33-01.cms:20300/urn:xdaq-application:service=fed1468-monitor)
-* GEMPILOT (GE2/1 demonstrator)
+* GEMPILOT (GE+2/1)
     * [FED1469](http://srv-s2g18-33-01.cms:20300/urn:xdaq-application:service=fed1469-monitor)