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 #17475
[90X] Allow multi-IOV input for Millepede alignment framework #17475
Conversation
When requesting information of all 2016 MinBias datasets, the runtime is reduced from 2-3 hours to approx. 2 minutes.
Changes commmited on behalf of Rainer Mankel. Details are presented here: https://indico.cern.ch/event/607492/#35-update-on-upsilonmumu-const
- move subtask into dedicated methods -> first step needed for unification -> also needed for support of multi-IOV input tag
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
self.JOBREMARK.append(parts[9].strip()) | ||
self.JOBSP1.append(parts[10].strip()) | ||
self.JOBSP2.append(parts[11].strip()) | ||
self.JOBSP3.append(parts[12].strip()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hello @ghellwig
how do you know which elements of parts[]
you're in need of removing blanks from ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything that is not converting to an integer remains a string and can have unintended whitespace at the left and right end.
The conversion to integers ignores such whitespace anyways.
no changes in plots 2017 ttbar, 2016B data, runII2016 25 and 50 ns |
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_9_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @smuzaffar |
including this PR 900 important for alignment |
+1 |
Removes shortcoming of the alignment framework which has not been able to update the alignables after an update of the tracker geometry at an IOV boundary.
Removes also temporary fix of #16135 and enables the usage of multi-IOV input for Millepede.
Added various protection against misconfiguration.
The code has been used to derive the 2016 legacy alignment.
The general AlignmentProducer has the new features disabled by default. It is only enabled for Millepede. If other alignment algorithms want to use it a flag has to be set to
True
:The code is based on top of #17408, i.e. to better digest the changes, it might be useful to first review and eventually approve #17408.
EDIT: A dedicated presentation on this update has been given at the Tracker Alignment meeting on 01-Mar-2017