Skip to content
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

Merged

Conversation

ghellwig
Copy link

@ghellwig ghellwig commented Feb 9, 2017

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.

  • consistency check of the configuration during the setup of the alignment campaign
  • consistency checks in the C++ code to detect 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:

process.AlignmentProducer.enableAlignableUpdates = 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

When requesting information of all 2016 MinBias datasets, the runtime is reduced
from 2-3 hours to approx. 2 minutes.
 - move subtask into dedicated methods
 -> first step needed for unification
 -> also needed for support of multi-IOV input tag
@ghellwig
Copy link
Author

ghellwig commented Mar 7, 2017

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 7, 2017

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/18202/console Started: 2017/03/07 12:45

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 7, 2017

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 7, 2017

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())
Copy link

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 ?

Copy link
Author

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.

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 7, 2017

@franzoni
Copy link

franzoni commented Mar 7, 2017

no changes in plots 2017 ttbar, 2016B data, runII2016 25 and 50 ns

@franzoni
Copy link

franzoni commented Mar 7, 2017

+1

@cmsbuild
Copy link
Contributor

cmsbuild commented Mar 7, 2017

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

@franzoni
Copy link

including this PR 900 important for alignment
may we have this PR merged, please ?

@davidlange6
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 937a0f7 into cms-sw:CMSSW_9_0_X Mar 14, 2017
@ghellwig ghellwig deleted the allow_multi-iov_millepede_90X branch May 2, 2017 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants