DUNE / dunedataprep

Apache License 2.0
0 stars 7 forks source link

Standardize the naming of dataprep sequences. #2

Closed dladams closed 2 years ago

dladams commented 2 years ago

A dataprep sequence is a ordered list of dataprep tools that run to process each event. There is variation in how these are defined for various prototypes with the early PDSP (protoDUNE 1 single-phase) putting the definitions in prolog and more recent (icebergX, coldbox) using the data namespace.

I would like to standardize this to make it easier for users (including myself) to move between prototypes and to make it easier duneproc to perform fcl generation.

dladams commented 2 years ago

The proposed standard is sequence definitions go in the data namespace with this syntax:

data.<DET>_dataprep_seqs.<SEQ> : {...}

where \ is specifies the prototype (pdsp, iceberg5, vdbcb, ...) and \ is a sequence name (calib, wirecell, ...).

This is the convention already followed for iceberg and the recent coldbox data.

MC-specific sequence append sim to the detector name, e.g. pdsp --> pdspsim.

dladams commented 2 years ago

Changing the naming convention for pdsp will require updating all clients including production reconstruction and significant validation effort. For now, I create pdsp_dataprep_sequences.fcl that copies the definitions from prolog and can be used for clients such as duneproc that want to use the sequence standard specified here. I have this in my local area and will report here after I validate and commit the file.

dladams commented 2 years ago

The new fcl has been validated by using in example 11. Changes are committed to develop.