@@ -107,7 +107,7 @@ The data for a given `payload` type are stored in separate folders. But you need
```
This will then show you all folders *contained* in `/LAR/BadChannels`. We have to stress the fact that these are not folders like in your file system, it is just a DB representation of something similar. In reality that name (e.g. `/LAR/BadChannels/EventVeto`) is just a string in a column of a specific table.
Have a look now at a *description* string. It contains some essential informations for Athena. One of those is the meaning of the `interval` for that folder: if you see `<timeStamp>time</timeStamp>` it means that your intervals are using an integer which represents a time (in COOL in general you have nanonseconds since EPOCH). If you see `<timeStamp>run-lumi</timeStamp>` it means that the integer represents a combination of run and lumi block (`run << 32 | lumi_block`).
Have a look now at a *description* string. It contains some essential informations for Athena. One of those is the meaning of the `interval` for that folder: if you see `<timeStamp>time</timeStamp>` it means that your intervals are using an integer which represents a time (in COOL in general you have nanonseconds since EPOCH). If you see `<timeStamp>run-lumi</timeStamp>` it means that the integer represents a combination of run and lumi block (`run << 32 | lumi_block`, this corresponds to a 64 bits integer which is what is stored in COOL tables for run-lumi folders). By shifting a run number 32 bits on the left you will get a 64 bits integer, the lower 32 bits you fill them with the lumi_block part (via the binary 'OR' operator). If you have the COOL 64 bits integer you can go back to run and lumi_block by doing: `run = cool_since >> 32 ; lumi_block = 0x00000000ffffffff & cool_since`.
The analogy with the file system can be noticed also when using another command, `cd`, which emulates (like `ls`) the behavior of unix commands.
...
...
@@ -157,6 +157,20 @@ If you know in advance your data you can restrict the `IOVs` selection by provid
>>> userunlumi
Usage: userunlumi <run1> {<LB1> <run2> <LB2>}
>>> userunlumi 462523 0 482523 0
# Using 'more' you see the full content in the selected range, the since and until times stored in COOL are represented as [run,lumiblock]
>>> more .
Using rawIOV range [1986521158647808,2072420504567808]
Using tag selection: LARBadChannelsBadChannels-RUN2-UPD1-00
