Skip to content

Commit 9aa9ef7

Browse files
dstoccoalcaliva
authored andcommitted
Improve README for MID reject list macro
1 parent b0f0828 commit 9aa9ef7

File tree

1 file changed

+39
-10
lines changed
  • Detectors/MUON/MID/Calibration/macros

1 file changed

+39
-10
lines changed

Detectors/MUON/MID/Calibration/macros/README.md

Lines changed: 39 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ root -l
1818
.x ccdbUtils.C("querybad",1721252719000,"mask.txt",true,"http://alice-ccdb.cern.ch")
1919
```
2020

21-
Upload the default list of fake dead channels to the local CCDB (assuming that an instance of the local CCDB is running):
21+
Upload the default list of fake dead channels to the local CCDB (assuming that an instance of the local CCDB is running, see below):
2222

2323
```shell
2424
root -l
@@ -27,24 +27,53 @@ root -l
2727

2828
The macro is also used to keep track of the fake dead channels, which are generated in `makeFakeDeadChannels()`.
2929

30-
## buils_rejectList.C
30+
## build_rejectList.C
3131

32-
This macro analyses the Quality flag and the Occupancy plot in the QCCDB and searches for issues appearing in the middle of the run, e.g. local board(s) that become noisy and are then excluded from the data taking by the user logic of the CRU.
33-
It then correlate this information with the GRPECS object in the CCDB in order to create a reject list that will allow to mask the faulty local board(s) from slightly before the problem appeared till the end of the run.
32+
This macro analyses the quality flag and the occupancy plots in the QCCDB and searches for issues appearing in the middle of the run, e.g. local board(s) that become noisy and are then excluded from the data taking by the user logic of the CRU.
33+
It then correlates this information with the GRPECS object in the CCDB in order to create a reject list that will allow to mask the faulty local board(s) from slightly before the problem appeared till the end of the run.
3434

35-
Notice that the QCDB is not directly reachable from outside CERN. In that case one needs to first create an ssh tunnel:
35+
If a problem is found, the macro will ask to upload the reject list in the local CCDB.
36+
For this, one needs to have the local CCDB up and running (see below).
37+
38+
The scan can be then performed with:
39+
40+
```shell
41+
root -l
42+
.x build_rejectlist.C+(1716436103391,1721272208000)
43+
```
44+
45+
Where the first number is the start timestamp for the scan, and the second is the end timestamp of the scan.
46+
47+
### Running outside CERN network
48+
49+
Notice that the QCDB is not directly reachable from outside CERN network.
50+
In that case one needs to first create an ssh tunnel:
3651

3752
```shell
3853
ssh -L 8083:ali-qcdb-gpn.cern.ch:8083 lxtunnel.cern.ch
3954
```
4055

41-
We also advice to have an instance of the local CCDB running, so that the reject list objects will be saved there.
42-
One can then scan for issues with:
56+
and then tell the macro to reach the QCDB via the tunneled local port:
4357

4458
```shell
4559
root -l
46-
build_rejectlist.C+(1716436103391,1721272208000,"localhost:8083")
60+
.x build_rejectlist.C+(1716436103391,1721272208000,"localhost:8083")
4761
```
4862

49-
Where the first number is the start timestamp for the scan, and the second is the end timestamp of the scan.
50-
For each problem found, the macro will ask if one wants to upload the reject list to the (local) CCDB or not.
63+
## Running the local CCDB
64+
65+
The local CCDB server can be easily built through alibuild.
66+
As usual, one needs to be in the directory containing alidist and then run:
67+
68+
```shell
69+
aliBuild build localccdb
70+
```
71+
72+
The CCDB server can be then run with:
73+
74+
```shell
75+
alienv enter localccdb/latest
76+
startccdb -r "path_to_local_ccdb"
77+
```
78+
79+
where `path_to_local_ccdb` is a directory in your local pc where the CCDB objects will be located.

0 commit comments

Comments
 (0)