The current definition of the data levels in protopipedo not correspond to the data models defined in ctapipe.
Taking advantage of the DL1 model now frozen from ctapipe 0.8.0 and the upcoming release of protopipe 0.3 (in which the DL1 data model will be indirectly frozen) it's time to name properly the scripts that generate the data tables.
[x] write_dl1.py produces DL1 data plus direction estimation (and energy estimation if a model exists already)
Its result is a set of events used to train the model estimators: this is called data_training.py in (#58).
[x] write_dl2.py produces data corresponding to events (aka showers) with direction, energy and classification information.
It is pratically DL2, but most probably it will differ from ctapipe's DL2 and its result is a set of data that goes into performance estimation (namely cuts optimization and IRF production).
A possible candidate name could be data_processing.py, but other suggestions are welcome!
WARNING: after this change, also the GRID interface will need to be modified accordigly!
The current definition of the data levels in protopipe do not correspond to the data models defined in ctapipe.
Taking advantage of the DL1 model now frozen from ctapipe 0.8.0 and the upcoming release of protopipe 0.3 (in which the DL1 data model will be indirectly frozen) it's time to name properly the scripts that generate the data tables.
write_dl1.pyproduces DL1 data plus direction estimation (and energy estimation if a model exists already)Its result is a set of events used to train the model estimators: this is called
data_training.pyin (#58).write_dl2.pyproduces data corresponding to events (aka showers) with direction, energy and classification information.It is pratically DL2, but most probably it will differ from ctapipe's DL2 and its result is a set of data that goes into performance estimation (namely cuts optimization and IRF production). A possible candidate name could be
data_processing.py, but other suggestions are welcome!WARNING: after this change, also the GRID interface will need to be modified accordigly!