-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Hermetic Timing SLHC27 (fix crashes in RECO so we can use the usual workflows) #12962
Hermetic Timing SLHC27 (fix crashes in RECO so we can use the usual workflows) #12962
Conversation
…xing in the time axis.
@cmsbuild please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @lgray (Lindsey Gray) for CMSSW_6_2_X_SLHC. It involves the following packages: DataFormats/PatCandidates The following packages do not have a category, yet: RecoParticleFlow/FastTiming @cvuosalo, @monttj, @cmsbuild, @slava77, @vadler, @davidlange6 can you please review it and eventually sign? Thanks. Following commands in first line of a comment are recognized
|
-1 Tested at: 1383ada ---> test runtestPhysicsToolsPatAlgos had ERRORS you can see the results of the tests here: |
the test fails in the IB as well |
i=globalVTracks.begin(); i!=globalVTracks.end() ; ++i ) | ||
{ | ||
//std::cout << " wgt=" << (**i).weight() << std::endl; | ||
} |
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.
it's unclear if this no-op debug loops is needed
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.
Will remove.
-1 Tested at: 5cd9e78 ---> test runtestPhysicsToolsPatAlgos had ERRORS you can see the results of the tests here: |
As usual, unit test failures unrelated. |
+1 for 5cd9e78
|
@slava77 You can merge this one into SLHCX as well, since you are release manager. I'm not sure if @davidlange6 Is responsible for merges in the SLHC releases. |
SLHCX is past its routine-merging shelf life. Lets discuss the basic validation for the relval and/or production at the next TP and then we’ll build a release.
|
When in the next TP? |
@davidlange6 just FYI, this PR fixes an issue with thr fast time customization thay was holding back the further processing of samples requested last year that are already processed to gen-sim. |
@davidlange6 Here is some validation. I would appreciate it if we can move forward here. Spacetime event display showing 4D and 3D vertex reconstruction (200PU). time resolution 50PU (because of stats) z resolution 50PU, this is the same as the 30um expected in 3D RECO. |
@davidlange6 Since there is no upgrade studies group this week. Where else should we discuss this PR and release? |
@davidlange6 Ping, what shall we do here? |
I finally finished an email on the topic. sorry for the delay. @lgray |
ok, for 80X (or 81X) it needs a bit of streamlining... (to many ifs) |
@VinInn thanks. Sure, for 80X I can make it less branchy. |
@davidlange6 Please have a look here. Vincenzo was OK with alterations. |
Hermetic Timing SLHC27 (fix crashes in RECO so we can use the usual workflows)
@boudoul Since SLHC28 is now out, who do I need to talk to in order to start the various DR steps for the pileup levels we discussed? |
hi @lgray I'll send a mail to the relevant parties this afternoon |
@boudoul thanks a lot! On Thu, Feb 11, 2016 at 3:18 PM, boudoul notifications@github.com wrote:
|
@boudoul Just to remind the PU values we agreed upon : 20, 50, 80, 110, 140, 200 |
The complete set of changes to the vertexing to be aware of timing.
Still needs tuning but gives an answer and does not crash.
We will need to cut a new release for this so that the timing sample DR campaign can march on.
@boudoul
@bendavid