Search/Navigation:
Related:
SLAC/EPP
/HPS Public
Jefferson Lab/Hall B
/HPS Run Wiki
S30XL-LESA/LDMX
...
In order to execute commands which update the conditions database, you will need to supply credentials for an account with the appropriate privileges. This can be done by following the instructions in the conditions documentation.
Without any arguments the commands will print the basic usage information and then exit.
...
Much like the git command, the conditions command line has interface has sub-commands with their own command switches.
...
Short Option | Long Option | Description |
---|---|---|
-d | --detector | name of HPS Java detector to initialize |
-r | --run | run number for initialization (with detector) |
-t | --tag | conditions tag for record filtering |
-h | --help | print help and exit |
These options should be provided before the sub-command, as in this example.:
Code Block | ||||
---|---|---|---|---|
| ||||
conditions-cli.sh tag -d HPS-dummy-detector -r 1234 [subcommand] |
...
Tagging requires write access to the database so a connection properties file must be provided to override the default read-only connection (see the documentation on the conditions system for details).
The run-summary command can print out conditions collections that will be used for a given run.
...
Code Block | ||||
---|---|---|---|---|
| ||||
conditions-cli.sh tag -d HPS-dummy-detector -r 1234 run-summary |
...