populating a new StartParams field with the value of the nanorc "run-type" (PROD vs. TEST)
adding a command-line option to nanorc to allow users to specify the "run-type" (so that we can test the downstream logic that depends on the PROD vs. Test choice). [nano04rc already has the ability for the user to specify PROD vs. TEST, but nanorc does not yet.
These changes are part of providing a DUNE.daq_test field in the file-transfer metadata that we send to offline. It will indicate whether the run was just a test (and therefore the data may not need to be persisted for a long time by the offline).
I will appreciate it if any reviewers of this PR will check that the changes that I've made won't have adverse effects on the various variants of nanorc.
This PR is part of a Deliverable for fddaq-v4.4.0, DUNE-DAQ/daq-deliverables#126, and it depends on a corresponding PR in the rcif repo, PR 10.
There are two changes in this PR:
nanorcto allow users to specify the "run-type" (so that we can test the downstream logic that depends on the PROD vs. Test choice). [nano04rcalready has the ability for the user to specify PROD vs. TEST, butnanorcdoes not yet.These changes are part of providing a
DUNE.daq_testfield in the file-transfer metadata that we send to offline. It will indicate whether the run was just a test (and therefore the data may not need to be persisted for a long time by the offline).I will appreciate it if any reviewers of this PR will check that the changes that I've made won't have adverse effects on the various variants of nanorc.
This PR is part of a Deliverable for fddaq-v4.4.0, DUNE-DAQ/daq-deliverables#126, and it depends on a corresponding PR in the
rcifrepo, PR 10.