rest-for-physics
New metadata class to merge TRestRun files
New metadata class TRestRunMerger meant to merge different TRestRun files, merging of the files can be performed using rml config files or macros:
- Merging of the files can only be done with the files that matches the run number.
Why would we need to merge files? Each REST file has a unique TRestRun entry that identifies the data file. That's why I find a bit strange merging TRestRun files. Although we did this in the past ...
The data merging can be done at the TRestDataSet level, where the metadata of the TRestDataSet allows to univocally identify the file list used to generate the analysis dataset from a persistent read-only storage.
The data merging can be done at the TRestDataSet level, where the metadata of the TRestDataSet allows to univocally identify the file list used to generate the analysis dataset from a persistent read-only storage.
I am trying to perform the energy calibration of the data, this is the workflow that I have in mind:
- Data selection to avoid large files, this is done using TRestCut
- Merging of the files, now is possible using TRestRunMerger
- Perform the calibration and store the calibration constants and the converted energy in a TRestRun
- Perform a further analysis of the data.
So, in summary I would like to have a TRestRun with the calibration energy, but the calibration is split along several files, that's why I think it will be useful to perform the merging of TRestRuns. Also, note that the merging of the files is only performed among the files with the same run number. The problem of TRestDataSet is that is read-only and I cannot save the calibration constants or the calibrated energy inside the files. So, I think that TRestDataSet can be used in step 4 but not in the steps before. Otherwise, can you point me to a different workflow?
It's interesting that the clang-format failed even after the PR bot made the formatting changes... 🤔
