... | @@ -56,9 +56,16 @@ Triggers are saved in ROOT files following the `GWOLLUM` convention for triggers |
... | @@ -56,9 +56,16 @@ Triggers are saved in ROOT files following the `GWOLLUM` convention for triggers |
|
```
|
|
```
|
|
/data/omicron/V1
|
|
/data/omicron/V1
|
|
```
|
|
```
|
|
For most cases, the trigger file location and/or format is irrelevant as Omicron triggers can be accessed automatically by [omicron programs](home#programs).
|
|
For most cases, the trigger file location and/or format is irrelevant as Omicron triggers can be accessed automatically by [omicron programs](home#programs). This will only work if the environment variable `OMICRON_TRIGGERS` is correctly set:
|
|
|
|
```
|
|
|
|
$ echo $OMICRON_TRIGGERS
|
|
|
|
/data/omicron
|
|
|
|
```
|
|
|
|
|
|
Following a reorganization of the storage area at Cascina, the Omicron trigger file location is currently (O3) only accessible from online machines: `detchar1` or the `ctrl` machines but not the `farmn` machines.
|
|
Following a reorganization of the storage area at Cascina, the Omicron trigger file location is currently (O3) only accessible from online machines: `detchar1` or the `ctrl` machines but not the `farmn` machines. Moreover, O3a triggers have been moved to `/data/prod/omicron/V1` (offline storage area). To access triggers automatically, the `OMICRON_TRIGGERS` must be redefined:
|
|
|
|
```
|
|
|
|
export OMICRON_TRIGGERS=/data/prod/omicron
|
|
|
|
```
|
|
|
|
|
|
If you get the error "No trigger files", look at the [faq](FAQ).
|
|
If you get the error "No trigger files", look at the [faq](FAQ).
|
|
|
|
|
... | | ... | |