Define "loose configuration" for track finding and fitting in HLT1+2

Define a loose configuration with relaxed parameters for HLT1+2 for usage for alignment and running online for the early running period.

@gunther @lohenry @sesen @cagapopo @ascarabo @sborghi @freiss @shollitt @cmarinbe @mstahl

We currently have a HLT2 draft config here: MooreOnline!174 (merged). The idea is to "burn" (the input data will be lost) a few short runs with these settings tomorrow to further test the full chain to sprucing via DIRAC. I assume longer runs will wait for this and potentially other developments?

For more mechanical tests like you describe it it is not really needed, but for runs we want to do alignment and potentially physics with the looser configuration makes sense.

But I actually believe deploying such a config can be rather quick, it is a few educated guesses in a few algorithms, and there is not much to lose, as timing is not really an issue at the moment. So I'd like to get this done in a 1 or 2 days.

I can take a deeper look later today. Should this become an options file or part of make_hlt2_tracks?

I would have done it via options if it can be done halfway transparently.

For matching,

PrMatchNN.global_bind(
    MaxMatchChi2 = 20.0,
    MinMatchNN= 0.0,
    MaxdDist = 0.30,
    dyTol = 12, 
    dyTolSlope = 600)

should be good enough.

I'll make a merge request later today, I can include this if you like

yes, thanks.

mentioned in merge request !1854 (merged)

mentioned in merge request Rec!3176 (merged)

mentioned in merge request !1976 (merged)

closed