Skip to main content

Output filename convention

LARDON writes reconstruction output to an HDF5 file. The filename is constructed as:
{detector}_{run}_{sub}[_{flow}{writer}[_s{server}]][_{outname}].h5
  • {flow}{writer} suffix is only added when either -flow or -writer is set to a non-default value.
  • {outname} suffix is only added when -out is provided.
  • Without -job, the file is written to $LARDON_RECO/. With -job, it is written to the current working directory.
When -flow and -writer are both omitted (left at their default of -1), LARDON treats both as 0 internally and produces no flow/writer suffix in the output filename. If you explicitly pass -flow 0 -writer 0, LARDON does add the _00 suffix because the values differ from the internal default.

Examples

Example 1 — PDVD TPC reconstruction, single eventProcess only event 11 from a PDVD file. The file np02vd_raw_run039229_0024_df-s05-d4_dw_0_20250829T115242.hdf5 requires -flow 4 -writer 0 -serv 5 to identify the correct dataflow/writer/server combination, and -hash 86/ad because the file lives in a hashed subdirectory.
lardon -det pdvd -run 39229 -sub 24 \
  -flow 4 -writer 0 -serv 5 \
  -hash 86/ad \
  -event 11 \
  -out one_event \
  -trk
Output: $LARDON_RECO/pdvd_39229_24_40_s5_one_event.h5The _40 component comes from -flow 4 and -writer 0 concatenated. The _s5 component is appended because -serv 5 is non-default. If -serv were omitted or left at -1, the output would be pdvd_39229_24_40_one_event.h5.
-event 11 is equivalent to -skip 11 -n 12. Only event 11 is reconstructed; events 0–10 are skipped.

Build docs developers (and LLMs) love