Project

General

Profile

Bug #18802

DAQInterface settings file should allow specification of output data directory

Added by Eric Flumerfelt almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
artdaq-daqinterface
Target version:
-
Start date:
01/26/2018
Due date:
% Done:

100%

Estimated time:
Experiment:
-
Co-Assignees:
Duration:

Description

The demo has hard-coded paths in simple_test_config/demo/Aggregator1.fcl (for example). These should be generated at run-time based on a setting in the settings file (which would be initialized by quick-mrb-start to the same as ARTDAQDEMO_DATA_DIR).

Associated revisions

Revision a3237cfb (diff)
Added by John Freeman almost 2 years ago

JCF: users can now add an option "data_directory_override" value to the settings file, where DAQInterface will ensure that RootOutput writes its files to the directory specified by the value rather than where the input FHICL document says they should be written; see Issue #18802

History

#1 Updated by John Freeman almost 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Commit a3237cfb2cea026c9f5286be83025b98530af96f on the develop branch of DAQInterface implements this request. If in the DAQInterface settings file (i.e., the one specified by the DAQINTERFACE_SETTINGS environment variable and read in by DAQInterface when DAQInterface is launched) the user adds a line such as the following:

data_directory_override: /path/to/desired/data/directory

...then for the RootOutput modules used in EventBuilders and DataLoggers, DAQInterface will make sure they write out their *.root files to that directory, rather than the directory specified in the input FHiCL document. As one would expect, if the "data_directory_override" value isn't provided in the settings file, DAQInterface will behave as it always has- i.e., it will use the path given to it from the input FHiCL.


Also available in: Atom PDF