-
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
Adding a vertex smearing configution for pp at 5 TeV #12047
Adding a vertex smearing configution for pp at 5 TeV #12047
Conversation
A new Pull Request was created by @mandrenguyen for CMSSW_7_1_X. Adding a vertex smearing configution for pp at 5 TeV It involves the following packages: Configuration/StandardSequences @cmsbuild, @civanch, @franzoni, @mdhildreth, @davidlange6 can you please review it and eventually sign? Thanks. |
please test |
The tests are being triggered in jenkins. |
@mmusich thanks for the ping. I saw the 71X version reported by @mandrenguyen in his mail. |
@mandrenguyen I am not convinced about the centroid position. From the first pp fills, we know that X and Y are not in 0. The latest exercise was done on Run2015B collision (fill 4008), and we have
Now, we know for sure that, in Run2015D the Z is back in 0, while X and Y are still away. If, instead, you have already the GEN-SIM for the |
@diguida Now if you tell me that the beam position is pretty stable and we don't think it will move then I should update the centroid positions accordingly. Vertex smearing parameters Is that correct? Thanks! |
@mandrenguyen The change in Z position happened during Run2015D (with a LHC time shift, more details on BeamSpot hn), while the X and Y position are quite stable in this era, as you can see in the latest report by BeamSpot operation team at the AlCaDB meeting. Concerning X, do not use the 0T value: the centroid position in x depends on the B field (horizontal crossing angle) and we do see movements ~120 um, confirmed by LHC-OPS team. I'd suggest some values taken from the latest fills in Run2015D (4393), looking at the plots in the presentation:
Beware: you should sum algebraically the pixel barycentre of the alignment used to compute that BS, as in the vertex smearing parameters you should refer to the pixels. This is an exercise done within the tracker alignment group. Assuming this is the same as the previous computation (this is typically not the case):
you get:
Please do not consider those numbers as correct, but take them as a straw-man example. We can provide you the new pixel barycentre position, if worth. |
@diguida I'm slightly confused by your recommendation. Is the suggestion that the tracker alignment group should provide us with a prediction or that we just use the numbers from Run2015D. Specifically, who is qualified to make this call: "We can provide you the new pixel barycentre position, if worth" ? |
@mandrenguyen your understanding is correct. |
@mandrenguyen @mmusich we have also some numbers for a recent BS computed on top of the new pixel large-structure alignment for its validation:
BS experts will cross-check those values, but I am pretty confident... |
@mmusich @diguida @franzoni Beam fit from Salvatore on Run 258742 x = 0.0769 cm BPIX and PIXEL locations estimated from a high level alignment to the pixel detector from the same run (x2, y2, z2):BPIX:x1 x2: -0.0278442 -0.0275148 Delta(x,y,z) = 2-1 = (3.29357,-5.66995,-8.69968) mumPixel:x1 x2: -0.041651 -0.0415103 Taking the BPIX values as the barycenter, then the values for the smearing parameters are: x0 = 0.1044 cm |
Pull request #12047 was updated. @cmsbuild, @civanch, @franzoni, @mdhildreth, @davidlange6 can you please check and sign again. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
@civanch Can you sign for simulation, please? |
+1 |
+1 |
Adding a vertex smearing configution for pp at 5 TeV
Expected beam conditions for the pp run at 5 TeV that will take place in about 4 weeks.
71X version of #12040