You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The duneproc command provides fcl key dptools_XXX to allow users to select the dataprep sequence at run time but this does not work for all prototypes because the syntax for referencing a sequence varies. DUNE/dunedataprep#2 addresses the latter. Once this is in place this key or another should be made to work with all conformant sequences.
The text was updated successfully, but these errors were encountered:
I am modifying duneproc to drop the dptools fcl key (i.e. support for pattern dptools_XXX) and replace it
with a dpseq key with pattern
dpseq_<DET>_<SEQ>
that selects sequence <SEQ> for prototype detector <DET>, i.e. with the convention described in DUNE/dunedataprep#2, i.e. matches the pattern
data.<DET>_dataprep_seqs.<SEQ>
In addition, the dunedataprep file pdsp_data_sequences is added to run_dataprep.fcl so the pdsp sequence definitions are available when duneproc processes pdsp data.
Changes are committed in version 2.4.0 of duneproc.
The duneproc command provides fcl key dptools_XXX to allow users to select the dataprep sequence at run time but this does not work for all prototypes because the syntax for referencing a sequence varies. DUNE/dunedataprep#2 addresses the latter. Once this is in place this key or another should be made to work with all conformant sequences.
The text was updated successfully, but these errors were encountered: