Merge branch 'chuh-main-patch-83195' into 'main'

Update Analyzing calibration pulse scan

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

docs/operations/taking-data.md

@@ -45,7 +45,9 @@ You can also check in the logs present in `/gemdata/log/` what the software is d
 * Output path: `/gemdata/runs/local/runE.DDDD.SSSSSL`
 * Comment: (none)
 
-### Analyzing an S-bit rate scan
+### Analyzing
+
+#### 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:
@@ -54,6 +56,18 @@ If these data are meant to be saved for later reference or analysis, link the di
 
 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.
 
+#### Calibration pulse scan
+
+At these point analyze the scan using the command :
+
+`sudo -u gemdoc -i`
+
+`ssh gemvm-control`
+
+`gem-find-dead-channel -r E.DDDD.SSSSSL` 
+
+from the terminal of `cmsusr`. When done without error messages, you can find results in Today's VFATs point at [GEM Grafana Dead Channels Trends](https://cmsgemonline-monitoring.app.cern.ch/d/Trh6MZd4k/dead-channels-trends?orgId=1).
+
 ## 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.