Wrap reconstruction macro into a steering class
Currently reconstruction macro presents quite a large piece of code (~500 lines) with several tasks being configured and added to the main task.
The plan of wrapping the routine into steering class (like CbmTransport and CbmDigitization) has been discussed and agreed on during one of Software meetings.
This should reduce the chance of errors and allow to create a class for text-based (currently JSON) configuration of the reconstruction stage.
One of important features should be reading the detector geometries and magnetic field parameters from parameter files opposite to the currently used error-prone approach of their manual setting. This approach should be also available for use in other analysis tasks.
Updated by Volker Friese 8 months ago
- Status changed from New to Assigned
Thanks for creating this issue.
One of the reasons why this was not started yet is that the amount of flexibility needed in the reconstruction run is much higher than in transport and digitization. There, at least the needed classes are known a priori and can thus be hard-coded (the detector classes like CbmTrd for the transport, the digitizer classes for digitization). For reconstruction, it should be possible to switch between different classes for a certain reconstruction step. The ROOT macro is very convenient for this feature, since the user can instantiate the required class (proper base class assumed). In compiled code, this is not so straightforward - but surely doable.