From 6a85d3b3f175a136503e922329045d6d96c754a0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Laurent=20P=C3=A9tr=C3=A9?= <laurent.petre@cern.ch>
Date: Wed, 27 Mar 2024 14:48:53 +0100
Subject: [PATCH] Update references to the GEM issue tracker GitLab project
---
docs/references/legacy.md | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/docs/references/legacy.md b/docs/references/legacy.md
index 6b7a20f..7d14f84 100644
--- a/docs/references/legacy.md
+++ b/docs/references/legacy.md
@@ -111,7 +111,7 @@ connect gem-shelfXX-amcYY
rwc GEM_AMC.OH_LINKS.OH*GBT*READY
```
-The configurations files with the correct GBT phases used for the configuration of the detector are `$DATA_PATH/config/gbt/gem-shelfXX-amcYY-phases.txt`. Update the files with the newest values of the phases, tracking the differences between the previous version and the new one, if needed (relevant changes are if the phase is/was set to 15 or if it is shifted by 3/4 units). If VFAT and GBT communication statuses are different, they should be traked in the [GitLab issues](https://gitlab.cern.ch/cmsgemonline/gem-online-support/-/issues).
+The configurations files with the correct GBT phases used for the configuration of the detector are `$DATA_PATH/config/gbt/gem-shelfXX-amcYY-phases.txt`. Update the files with the newest values of the phases, tracking the differences between the previous version and the new one, if needed (relevant changes are if the phase is/was set to 15 or if it is shifted by 3/4 units). If VFAT and GBT communication statuses are different, they should be traked in the [GitLab issues](https://gitlab.cern.ch/cmsgemonline/gem-ops/gem-issue-tracker/-/issues).
#### Taking the DAC scans
@@ -123,7 +123,7 @@ for i in {0..11}; do getCalInfoFromDB.py XX YY $i --write2File --write2CTP7; don
~/scripts/testConnectivity.py --gemType ge11 --detType=short XX YY 0xfff -a --skipGBTPhaseScan --acceptBadDACFits --skipScurve -i -f5
```
-The output files should be inspected and any result that could indicate a broken DAC circuit should be reported in the [GitLab issues](https://gitlab.cern.ch/cmsgemonline/gem-online-support/-/issues).
+The output files should be inspected and any result that could indicate a broken DAC circuit should be reported in the [GitLab issues](https://gitlab.cern.ch/cmsgemonline/gem-ops/gem-issue-tracker/-/issues).
### Data-taking procedures
@@ -175,7 +175,8 @@ for l in 1 2; do for i in {01..36}; do cp $DATA_PATH/GE11-M-${i}L${l}*/scurve/<s
for l in 1 2; do for i in {01..36}; do cp $DATA_PATH/GE11-M-${i}L${l}*/scurve/<symlink>/SCurveData/h2ScurveSigmaDist_All.png /nfshome0/gempro/elog/<my_name>/h2ScurveSigmaDist_All_GE11-M-${i}L${l}.png; done; done
```
-Any discrepancy between the results and what expected from the configuration, i.e. the scans or the analysis failing for a part of the detector, should be investigated and tracked in the [GitLab issues](https://gitlab.cern.ch/cmsgemonline/gem-online-support/-/issues).
+Any discrepancy between the results and what expected from the configuration, i.e. the scans or the analysis failing for a part of the detector, should be investigated and tracked in the [GitLab issues](https://gitlab.cern.ch/cmsgemonline/gem-ops/gem-issue-tracker/-/issues).
+
#### Checking the HV mapping
Checking the HV mapping is one of the last checks to be performed once the front-end communication has been established and the frontend status confirmed. The HV training must be completed as well since signal amplification is required in the chambers.
--
GitLab