|
1 | | -## Standalone run |
| 1 | +## Environment variables (advanced or temporary options) |
2 | 2 |
|
3 | | -Standalone run is useful in following scenarios: |
4 | | - - Running SubTimeFrame building with readout emulators (NO CRU HARDWARE REQUIRED) |
5 | | - - Replaying recorded (Sub)TimeFrame data for full processing chain (DPL) |
6 | | - - Receiving SubTimeFrames from StfBuilder or DPL workflows in StfSender |
| 3 | + - `DATADIST_FEE_MASK=0xffff` Apply the mask if StfBuilder is configured to use the FeeID field as a O2::Subspecification (O2::Subspec = (RDH::FeeID & DATADIST_FEE_MASK)) |
7 | 4 |
|
8 | | -Run the chain with the `datadist_start_standalone.sh` script. |
9 | | -For supported options see `datadist_start_standalone.sh --help` |
| 5 | + - `DATADIST_FILE_READ_COUNT=N` Terminate after injecting set number of TF files. Data set will be repeated if necessary. Number of TimeFrames will be `DATADIST_FILE_READ_COUNT x Number of TFs per file`. |
10 | 6 |
|
11 | | -NOTE: Emulated chain ends with StfSender. Data is never sent to TfBuilder! |
| 7 | + - `DATADIST_DEBUG_DPL_CHAN` When defined, data sent to DPL will be checked for consistency with the O2 data model. Note: will be slow with larger TimeFrames. |
12 | 8 |
|
13 | | -### Emulated readout data run |
14 | 9 |
|
15 | | -To use `o2-readout-exe` as the CRU emulator: |
16 | | - - Make sure the Readout module is loaded in the environment (or the `o2-readout-exe` executable exists in the PATH). |
17 | | - - pass `--readout` parameter |
| 10 | +### Shared memory: |
18 | 11 |
|
19 | | -### Replaying recorded (Sub)TimeFrame data and DPL gateway configuration |
| 12 | + - `DATADIST_NO_MLOCK` Disable locking of the shared memory segments. Only use in testing and development! |
20 | 13 |
|
21 | | - - Use `--data-source-dir` parameter to select the directory with (Sub)TimeFrame files previously recorded with StfBuilder or TfBuilder. |
22 | | - - Use `--dpl-passthrough` to enable sending data to DPL workflows, defined [here](datadist_standalone_chain.json#L52-L55) |
| 14 | + - `DATADIST_SHM_ZERO` When defined, shared memory segment will be zeroed before use. Because of large performance impact, only use to check for memory corruption, not in production. |
23 | 15 |
|
| 16 | + - `DATADIST_SHM_ZERO_CHECK` Define to enable checking for memory corruption in unmanaged region. Each de-allocated message will be checked for write-past-end corruption. |
24 | 17 |
|
25 | | -FMQDevice channel configuration is in the file `script/datadist_standalone_chain.json`. |
26 | | -If using the CRU emulation mode of the `o2-readout-exe` process, configuration of the emulator equipment is read from `readout_cfg/readout_emu.cfg`. |
27 | 18 |
|
28 | 19 |
|
29 | 20 | ## Consul parameter for online runs |
|
0 commit comments