New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[90X] Allow multi-IOV input for Millepede alignment framework #17724
[90X] Allow multi-IOV input for Millepede alignment framework #17724
Commits on Feb 3, 2017
-
Partly align AlignmentProducer to PCLTrackerAlProducer.
- move subtask into dedicated methods -> first step needed for unification -> also needed for support of multi-IOV input tag
-
-
-
-
-
-
-
-
-
-
-
Commits on Feb 9, 2017
-
Removed temporary protection against multi-IOV input.
- still enforce it in case no output IOVs are specified - adapt MPS to handle multi-IOV inputs properly
-
-
-
-
-
-
-
Implemented early detection of inconsistent IOV definitions in MPS.
- split up input db creation in separate functions - propagate this change to stand-alone input creation script
-
-
-
Commits on Feb 10, 2017
-
Adjust PCL alignment producer to multi-IOV alignment framework.
- no functional change - just added missing configuration parameters which are deactivated for PCL
Commits on Feb 14, 2017
-
Fix clang warnings caused by 'update' method.
Make the method non-virtual because it acts like a constructor applied on an already constructed object. Since a constructor is always non-virtual it appears to be cleanest to declare also the 'update' methods non-virtual.