-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
A correct description of the HL-LHC beamspot #16942
A correct description of the HL-LHC beamspot #16942
Conversation
A new Pull Request was created by @lgray (Lindsey Gray) for CMSSW_9_0_X. It involves the following packages: IOMC/EventVertexGenerators @cmsbuild, @civanch, @mdhildreth, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
The tests are being triggered in jenkins. |
-1 Tested at: 5f33356 You can see the results of the tests here: I found follow errors while testing this PR Failed tests: ClangBuild
I found a compilation error while trying to compile with clang: >> Compiling edm plugin /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/src/GaussEvtVtxGenerator.cc >> Compiling edm plugin /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/src/GaussianZBeamSpotFilter.cc >> Compiling edm plugin /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/src/BetafuncEvtVtxGenerator.cc >> Compiling edm plugin /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/test/VtxTester.cc >> Compiling edm plugin /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/test/BoostTester.cc /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/src/HLLHCEvtVtxGenerator.cc:25:20: error: constexpr variable 'two_pi' must be initialized by a constant expression constexpr double two_pi=8.0*std::atan(1.0); ^ ~~~~~~~~~~~~~~~~~~ /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/src/HLLHCEvtVtxGenerator.cc:25:31: note: non-constexpr function 'atan' cannot be used in a constant expression constexpr double two_pi=8.0*std::atan(1.0); ^ |
Comparison job queued. |
Pull request #16942 was updated. @cmsbuild, @civanch, @mdhildreth, @davidlange6 can you please check and sign again. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
-1 Tested at: 2bb5d9d You can see the results of the tests here: I found follow errors while testing this PR Failed tests: ClangBuild
I found a compilation error while trying to compile with clang: const double dx_plus = (z-t*ct)*(cax*st_plus-sax_plus*ct) - (x-t*st_plus)*(sax_plus*st_plus+cax*ct); ^ /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/src/HLLHCEvtVtxGenerator.cc:151:20: warning: unused variable 'c' [-Wunused-variable] constexpr double c= 2.99792458e+8; // m/s ^ /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/src/HLLHCEvtVtxGenerator.cc:203:20: error: constexpr variable 'factorRMSgauss4' must be initialized by a constant expression constexpr double factorRMSgauss4 = 1./std::sqrt(2.)/gamma34 * gamma14; // # Factor to take rms sigma as input of the supergaussian ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /build/cmsbuild/jenkins-workarea/workspace/ib-any-integration/CMSSW_9_0_X_2016-12-08-2300/src/IOMC/EventVertexGenerators/src/HLLHCEvtVtxGenerator.cc:203:42: note: non-constexpr function 'sqrt' cannot be used in a constant expression constexpr double factorRMSgauss4 = 1./std::sqrt(2.)/gamma34 * gamma14; // # Factor to take rms sigma as input of the supergaussian ^ |
Comparison job queued. |
@kpedro88 could you unhold, I have confirmation from Rogelio Garcia (HL-LHC guy) that this looks good. I am doing a few final checks. |
Hold on, this has some effects in the reconstruction to understand. Not expected. |
OK - talking to @slava77 a bit more since the beamspot is different the comparison with the baseline is different from the SIM level so it's hard to make a good comparison with 10 events. |
Just FYI the current reco::BeamSpot parameters for HL-LHC are:
And for this new HL-LHC beam spot the BeamWidthX is 11um (instead of 13um), BeamWidthY is 5um (instead of 8um), SigmaZ is more or less the same. Should we update the beamspot, or just go as is? |
However, the bias in the x0 (which should be zero for HL-LHC) is over one sigma. Not sure if that matters for tracking. |
@lgray about:
we can easily update it if you point me to the list of preferred parameters. |
unhold |
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. @slava77, @davidlange6, @smuzaffar |
+1 |
I realize I merged this one prematurely - however the beam spot bias issue is not due to this PR, so I'm not reverting it (unless discussion to come indicates that is the right thing). |
Beamspot bias issue? Guessing this is for present running or is this for
Phase 2 studies?
…On Mon, Dec 12, 2016 at 4:47 PM, David Lange ***@***.***> wrote:
I realize I merged this one prematurely - however the beam spot bias issue
is not due to this PR, so I'm not reverting it (unless discussion to come
indicates that is the right thing).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16942 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABBMOYpLgbQZQ462oY2dfStPDWSLuRB8ks5rHWx1gaJpZM4LIxvT>
.
|
@davidlange6 I'm curious about this because there are some offsets we see
in timing distributions that appeared that we haven't been able to trace
down.
…On Dec 12, 2016 9:59 AM, "Lindsey Gray" ***@***.***> wrote:
Beamspot bias issue? Guessing this is for present running or is this for
Phase 2 studies?
On Mon, Dec 12, 2016 at 4:47 PM, David Lange ***@***.***>
wrote:
> I realize I merged this one prematurely - however the beam spot bias
> issue is not due to this PR, so I'm not reverting it (unless discussion to
> come indicates that is the right thing).
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#16942 (comment)>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/ABBMOYpLgbQZQ462oY2dfStPDWSLuRB8ks5rHWx1gaJpZM4LIxvT>
> .
>
|
Even with the "NoSmear" beamspot. |
This PR changes the HL-LHC beamspot simulation we are using to be exactly the HL-LHC beamspot simulation from the HL-LHC machine group.
This PR is waiting for one more item: a correct description of the x and y distribution of vertices in the beamspot.
The online beamspot doesn't need to be updated as the major change here is for the width of the beamspot in time, and the online beamspot only has spatial coordinates. There is a slight change in the beamspot z width but it does not invalidate the beamspot in the database.
Vertex profile in time (axis is ns, arb units):
Vertex profile in z (axis in cm, normalized to ev/mm in 140 PU):
Vertex shape in z and time (arb units):
@davidlange6 It would be good to get this in for the tracker TDR production, I also found a weird bug in the old HL-LHC beamspot such that x and z were correlated (which should not be the case!).