Modify CA async opts, possible set from config.param #13968
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Print selected settigs only once from the 1st pipeline. Rescale pT cutoffs by actual/nominal B-field. For this reason, CA ITSTrackingInterface::initialise is moved inside ITSTrackingInterface::updateTimeDependentParams 1st call (during 1st TF processing).
@mpuccio here I set defaults to the best I could get so far for 37kHz pbpb, see ITSV2 in https://its.cern.ch/jira/browse/O2-5763?focusedId=6680013&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-6680013 and add a possibility to modify the minTrackLenght and corresponding pt cut-offs from the config.param (taken only if non-0). I assume for pp we may want different settings, so should be flexible. E.g. this default settings correspond to: