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

Phase2 Outer Tracker Clusterizer integration in CMSSW 8 #13087

Merged
merged 5 commits into from
Jan 31, 2016
Merged

Phase2 Outer Tracker Clusterizer integration in CMSSW 8 #13087

merged 5 commits into from
Jan 31, 2016

Conversation

thomaslenzi
Copy link
Contributor

This PR migrates the Phase2 Outer Tracker Clusterizer from CMSSW 6_2_SLHC to CMSSW 8. It adds the new data format for the clusters as well as the clustering algorithm itself.

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @thomaslenzi (Thomas Lenzi) for CMSSW_8_0_X.

It involves the following packages:

DataFormats/Phase2TrackerCluster
RecoLocalTracker/SiPhase2Clusterizer

The following packages do not have a category, yet:

RecoLocalTracker/SiPhase2Clusterizer

@cmsbuild, @cvuosalo, @davidlange6, @slava77 can you please review it and eventually sign? Thanks.
@makortel, @GiacomoSguazzoni, @rovere, @VinInn, @gpetruc, @cerati, @threus this is something you requested to watch as well.
@slava77, @Degano, @smuzaffar you are the release manager for this.

cms-bot commands are list here #13028

@thomaslenzi
Copy link
Contributor Author

I would also like to note that I have informed Daniel Elvira about the new package RecoLocalTracker/SiPhase2Clusterizer

@@ -0,0 +1,12 @@
<lcgdict>
<class name="Phase2TrackerCluster1D" ClassVersion="10">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we recommend to start from version 2 for new classes

@slava77
Copy link
Contributor

slava77 commented Jan 27, 2016

@thomaslenzi
it will take me a bit longer to send all comments to the code, I'll post a message when I'm done

@slava77
Copy link
Contributor

slava77 commented Jan 27, 2016

@cmsbuild please test
to collect other possible issues with the code

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/10779/console

@cmsbuild
Copy link
Contributor

Pull request #13087 was updated. @cmsbuild, @cvuosalo, @davidlange6, @slava77 can you please check and sign again.

@thomaslenzi
Copy link
Contributor Author

I pushed changes to my branch and hope this will solve the problems highlighted here-above.

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@slava77
Copy link
Contributor

slava77 commented Jan 29, 2016

@cmsbuild please test

@cmsbuild
Copy link
Contributor

The tests are being triggered in jenkins.
https://cmssdt.cern.ch/jenkins/job/ib-any-integration/10845/console

@cmsbuild
Copy link
Contributor

@cmsbuild
Copy link
Contributor

@slava77
Copy link
Contributor

slava77 commented Jan 29, 2016

+1

for #13087 8628a59

  • code changes look somewhat OK, considering the preliminary stages of integration; only new code is added
  • jenkins tests pass: compilation is OK and the static analyzer shows no issues (although I'm not fully sure it checks the new packages); comparisons with baseline show no differences (more as a sanity check).

davidlange6 added a commit that referenced this pull request Jan 31, 2016
…1-2300

Phase2 Outer Tracker Clusterizer integration in CMSSW 8
@davidlange6 davidlange6 merged commit 873bfaf into cms-sw:CMSSW_8_0_X Jan 31, 2016
cmsbuild pushed a commit that referenced this pull request Jan 31, 2016
cmsbuild added a commit that referenced this pull request Jan 31, 2016
@smuzaffar
Copy link
Contributor

cms-bot recheck packages

@cmsbuild
Copy link
Contributor

cmsbuild commented Feb 2, 2016

This pull request is fully signed and it will be integrated in one of the next CMSSW_8_0_X IBs (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @slava77, @davidlange6, @Degano, @smuzaffar

@VinInn
Copy link
Contributor

VinInn commented Mar 1, 2016

@davidlange6, what is the status of this?
moved to 810 or will be integrated in some sort of 801?

@davidlange6
Copy link
Contributor

sorry, is in need of me to look - but would prefer its for 81x.

On Mar 1, 2016, at 4:38 PM, Vincenzo Innocente notifications@github.com wrote:

@davidlange6, what is the status of this?
moved to 810 or will be integrated in some sort of 801?


Reply to this email directly or view it on GitHub.

@boudoul
Copy link
Contributor

boudoul commented Mar 1, 2016

It is in 800pre6 , isnt' it ?
https://github.com/cms-sw/cmssw/releases/CMSSW_8_0_0_pre6

@VinInn
Copy link
Contributor

VinInn commented Mar 1, 2016

oh yes, sorry did not noticed that was merged on January 31!

@delaere
Copy link
Contributor

delaere commented Mar 1, 2016

Yes indeed. This one was merged. The question is valid for PR #13185 vs #13368 (the digitizer). In principle the digitizer is needed by the clusterizer, but I have no problem if we skip 80X, as we have presently no phase2tk workflow in that release cycle.

@davidlange6
Copy link
Contributor

indeed, I missed clusterizer->digitizer… I need one last look at the digitizer PR and it goes for 81x (and phase2 should forget about 80x for now)

On Mar 1, 2016, at 4:58 PM, Christophe Delaere notifications@github.com wrote:

Yes indeed. This one was merged. The question is valid for PR #13185 vs #13368 (the digitizer). In principle the digitizer is needed by the clusterizer, but I have no problem if we skip 80X, as we have presently no phase2tk workflow in that release cycle.


Reply to this email directly or view it on GitHub.

@VinInn
Copy link
Contributor

VinInn commented Mar 1, 2016

yes. And we need to proceed forward. We need the digitizer and new workflows so that tracking can plugin and proceed as well

@boudoul
Copy link
Contributor

boudoul commented Mar 1, 2016

the workflow with phase2 (flat and tilted) up to gen sim just pull requested in 81X - Including the local reco steps will follow (factorizing the 2 steps to ease the integration)

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.

10 participants