This suggestion was also brought up by @marc1uk, in reference to PR #187
Some tools (like e.g. PhaseIIADCCalibrator) have slightly different modes of operation depending on the respective use case. For example, PhaseIIADCCalibrator operates on a list of events in the EventBuilding mode, while it only expects one event per Execute step in the normal operating mode.
Currently, the different modes are realized in large if/else statement blocks that make the code a little harder to read.
As a first step, the different modes of operation could be moved to separate functions. This would already clean up the code significantly. A further step might be to move the handling of the different operation modes to a second tool and provide the main tool always with the same data format.
This suggestion was also brought up by @marc1uk, in reference to PR #187
Some tools (like e.g.
PhaseIIADCCalibrator) have slightly different modes of operation depending on the respective use case. For example,PhaseIIADCCalibratoroperates on a list of events in the EventBuilding mode, while it only expects one event per Execute step in the normal operating mode.Currently, the different modes are realized in large
if/elsestatement blocks that make the code a little harder to read.As a first step, the different modes of operation could be moved to separate functions. This would already clean up the code significantly. A further step might be to move the handling of the different operation modes to a second tool and provide the main tool always with the same data format.