Point taken ... however for Run 3, I assume that this algorithm will only be use by one customer, and this is the SCT calibration loop. For ITK I would not recommend to use this code as basis, but rather start from scratch and change several things to be easier to run, be more efficient and better to maintain than this monster of an algorithm.
Several of those flags are indeed needed to set up properly the different instances of the algorithm which run sequentially at T0: E.g. first hit map generation, then merging and noise strip evaluation ... historically grown
Indeed we'll most likely never change those flags in the next two years but as Jakub mentioned this is the current (grown) status and maybe in the case of future reprocessing it would be useful to have the full flexibility. A redesign of the package at this stage should be avoided given the end-of-lifetime of this code is drawing closer.
Christian Sander (abd9abb8) at 23 Jan 11:08
further CA migration work
Christian Sander (35096842) at 18 Jan 14:46
current status of CA migration