-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add PDF4LHC21 cards #121
Add PDF4LHC21 cards #121
Conversation
@Radonirinaunimi here's first shot at the distribution @juanrojochacon wants for PDF4LHC21. However, the integration dies after step 0 because not enough points pass through the cuts:
What I don't understand is that I've already increased the value of tau_min to 1 TeV. @marcozaro do you have any idea what I can do? |
Thanks @cschwan for having had an attempt in generating this grid. I haven't started generating the actual grid yet as I am still trying to sort out some hiccups with |
@marcozaro here's the full log, with |
This is very odd @cschwan @Radonirinaunimi - is this a grid problem or also happens with standalone mg5? If you reduce tau_min all the way down to the kinematic limit do you still get this problem? I think that provided we generate events somewhat above the Z pole we should be fine with statistics ... |
@juanrojochacon this is a problem in step 0, where no grid has been generated yet (that only happens in step 1), so a general problem. What I don't understand is why so few points end up in |
@cschwan If I use the run card
WARNING: program
/home/tanjona/Documents/N3PDF/runcards/PDF4LHC_DY_13_TEV_21_PHENO-20220106214356/PDF4LHC_DY_13_TEV_21_PHENO/SubProcesses/P0_uxu_mummup/ajob1
1 all 0 0 launch ends with non zero status: 1. Stop all computation
Command "launch auto " interrupted with error:
Exception: program
/home/tanjona/Documents/N3PDF/runcards/PDF4LHC_DY_13_TEV_21_PHENO-20220106214356/PDF4LHC_DY_13_TEV_21_PHENO/SubProcesses/P0_uxu_mummup/ajob1
1 all 0 0 launch ends with non zero status: 1. Stop all computation Obviously, the call to |
@Radonirinaunimi yes, thanks for reproducing the error! |
Is there something I should check/investigate in the meantime? |
@Radonirinaunimi not at this point, thanks! |
I don't understand exactly why Madgraph5 crashed, but since I've imposed a minimum invariant mass cut on the lepton pair, it seems to correctly set the minimum invariant of the partonic process. I've updated the parameters, so this should be ready for a production run. @Radonirinaunimi would you please take care of that? Run it with theory 200, in the following way:
|
Thanks! I will try this now. |
Good, very nice. Indeed, the mll generation cut is the one I proposed originally, so I thought we were already imposing it |
anyway, provided it works we should be fine. We can use mll > 200 Gev or something. btw @Radonirinaunimi please generate grids also for the CC process (everything else identical, so adapting the runcard would be trivial) |
@juanrojochacon I think @cschwan is stating the opposite. As far as I understand Christopher's last changes (which indeed work on my local computer, I will send to the cluster later), it works upon removing the minimum cut (there might be a typos in his message above). |
@cschwan says " since I've imposed a minimum invariant mass cut on the lepton pair, it seems to correctly set the minimum invariant of the partonic process". Before we has imposing a different cut I think |
The problem was that imposing both a cut on the partonic centre-of-mass energy (Madgraph5 calls it |
@juanrojochacon the fact that the invariant mass of the lepton-neutrino system isn't a collider observable isn't a problem for this exercise, right? |
Not at all, this is just for a "theory" exercise, we don't want to reproduce any exp measurement. And this way it is easier to compare the NC and CC calculations, and to connect the results with the possible issue of negative PDFs at large-x |
Alright, thanks for confirming that. |
@marcozaro could you please have a look at the charged current process and tell us what's wrong with it? We have a large invariant mass cut on the lepton-neutrino system, but Madgraph5 complains about too few points coming through the cuts. We've adjusted |
Hi, I get this error: Any idea? Marco |
@marcozaro
|
Thanks again @cschwan @Radonirinaunimi for producing these numbers. I have processed them and everything looks as expected: around 15% of the replicas are negative, but the median and 68%CL ranges are unaffected. So this is reassuring. If the same holds for the CC process, then we are done. Note that if imposing cuts is too difficult just generate events for pp => W, this should be sufficient and should work out of the box right? |
@juanrojochacon if we generate CC without cuts the invariant mass will be close to the W-boson mass where the PDFs are typically fine, so I don't think that'll give us much. |
I see. Can you try generating W => u dbar? This way there is no neutrino, and this is really identical to NC then ... |
Hi,
I am investigating the issue of the invariant mass in CC. Looks like the born momenta are always generated with a W boson close to mass shell, despite the changes in setcuts. I will discuss with Rikkert, who knows a lot about the phase-space, and let you know.
… On 12 Jan 2022, at 16:30, Christopher Schwan ***@***.***> wrote:
@juanrojochacon <https://github.com/juanrojochacon> if we generate CC without cuts the invariant mass will be close to the W-boson mass where the PDFs are typically fine, so I don't think that'll give us much.
—
Reply to this email directly, view it on GitHub <#121 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHECN5DAXQGK7NV5WFPUXA3UVWNC3ANCNFSM5LIDU7EA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.
|
Given that you have rather large bins, you may give it a try with setting a very high accuracy target… |
no, don't do so, as you will also have t-channels and a lot of other stuff around (essntially, dijet at order alpha^2) |
Rikkert suggested the following: _The easiest is to remove the cut from cuts.f. Then use the bias-function (in cuts.f) to enhance the large mass region and apply the cut in the analysis file. For fixed-order runs this is only working since 3.3.1 (I think). For event generation this has been around longer already._ We need to check that the bias is properly accounted for with PineAPPL... Cheers, Marco |
@marcozaro the |
@marcozaro I'm currently looking into this with @Radonirinaunimi and we're wondering whether the bias (we've set it to |
Did I forget to comment out some write/print statements? Have a look at size of the files, please. |
There was one |
Hi @Radonirinaunimi I would like to get the same numbers as per above Prediction per replicas for last bin: but for the rest of the rapidity bins. Would that be possible? This way we can show that the issue of cross-section negativity becomes only important at the highest mass bin. Thanks!!! |
also, can you remind me what are the units of the cross-section? |
@juanrojochacon Yes! That is possible. I will produce them and post here the results.
For the differential distribution, the cross-section is expressed in |
@juanrojochacon, here are the results of
|
perfect many thanks. Those of PDF4LHC21_nnlo_mc_5.txt are the ones you produced already right? |
Yes! These are exactly the same. |
+ bias_wgt=sqrt(ppv(0)**2-ppv(1)**2-ppv(2)**2-ppv(3)**2)**3 | ||
+ xmlnu=sqrt(ppv(0)**2-ppv(1)**2-ppv(2)**2-ppv(3)**2) | ||
+ if (xmlnu < 1000.0d0) then | ||
+ bias_wgt=1d-10 |
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.
Hi,
this is strange. How about using a smooth function, rather than a step function?
What if you set bias_wgt = xmlnu**2 for example?
Hi @juanrojochacon, last week in the PDF4LHC21 meeting, it was suggested to superimpose in Fig. 5.12 the distribution from META40 with positive definite PDFs (this seems to be a sensible suggestion). I am attaching below the predictions per replica and per bin (similar to the above). With the script that you have, could you perhaps add these results to the histogram plots? Or else, please let me know if you want me to take care of this.
|
This is easy enough, I can try to do it. I am not sure it will look pretty but we can try. However @Radonirinaunimi I don't need all this info: at the end of the day the Hessian 40 set leads to a gaussian distribution right? So if you can process these numbers to get the central value (prediction from central pdf set) and the standard deviation I can then just superimpose a gaussian to the predictions from the prior, right? Thanks! |
Yes, this is correct! I'll compute the means and STDs and will post them here. |
ok good this saves a bit of time for me then |
Hi @juanrojochacon, here are the numbers:
|
Got them. This is the script I used: https://www.dropbox.com/s/cjonu7tl9i44xuu/negative_xsecs.tgz?dl=0 Would you mind adding the pdf4lhc21_40 gaussian distributions yourself? I am a bit swamped with tesching. Thanks, Juan |
Sure! I can do that! |
Closing as completed. |
No description provided.