no alpha_s variations for the 4-flavor case : how can i go around this??

Asked by Khawla Jaffel

Dear experts,

I want to use LHAPDF for 4F scheme:
PDFsets : NNPDF31_nnlo_as_0118_nf_4_mc_hessian
lhaid : 25500

In most cases the pdf choice fix automatically alpha_s and it's evol.
However in this link ref [1] I found that

there are no alpha_s variations for the 4-flavor case.
NNPDF authors recommend to estimate the relative alpha_s uncertainty from the 5-flavor set.
They expect the resulting uncertainties to be similar to what we would have obtained from the 4-flavor set.
ref[1]: https://monte-carlo-production-tools.gitbook.io/project/mccontact/info-for-mc-production-for-ultra-legacy-campaigns-2016-2017-2018

My questions are : how can i estimate the relative alpha_s uncertainty from the 5-flavor set? which 5f sets should be be used for this estimation ? Later on how can i propagated ? is there a command i should add to the proc_card, or it's a value i can fix in the run_card ??

Many thanks in advance
Khawla

Question information

Language:
English Edit question
Status:
Answered
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#1

We certainly do not have any support for such situation.
To be honest, I'm not even sure what they comment means in practice.
So in that situation I would need to contact the NNPdF author to have an exact guidance of what need to be done.

Cheers,

Olivier

Revision history for this message
Khawla Jaffel (kjaffel) said :
#2

Thanks a lot for your reply.

trying to ignore the comment I found about alpha_s by only setting the lhaid in my run_card [1]:

 'lhapdf' = pdlabel ! PDF set
 325500 = lhaid ! if pdlabel=lhapdf, this is the lhapdf number

I get this error which it seems to me unrelated to the pdfset( I hope ) !!

generate_events pilotrun
stty: standard input: Inappropriate ioctl for device
stty: standard input: Inappropriate ioctl for device
The following switches determine which programs are run:
/===========================================================================\
| 1. Choose the shower/hadronization program shower = Not Avail. |
| 2. Choose the detector simulation program detector = Not Avail. |
| 3. Choose an analysis package (plot/convert) analysis = Not Avail. |
| 4. Decay onshell particles madspin = OFF |
| 5. Add weights to events for new hypp. reweight = OFF |
\===========================================================================/
Either type the switch number (1 to 5) to change its setting,
Set any switch explicitly (e.g. type 'madspin=ON' at the prompt)
Type 'help' for the list of all valid option
Type '0', 'auto', 'done' or just press enter when you are done.[60s to answer]
>The parameter ptonium is not supported anymore this parameter will be ignored.
The parameter etaonium is not supported anymore this parameter will be ignored.
ickkw >1 is pure alpha and only partly implemented.
Command "generate_events pilotrun" interrupted with error:
TypeError : __init__() takes at least 2 arguments (3 given)
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in 'ME5_debug'.
Please attach this file to your report.
Do you really want to continue

In the run_card i set ickkw=3 to have NLO with jet matching, ref [2] am I missing anything ??

[1]https://github.com/kjaffel/ZAPrivateProduction/blob/master/PrivateProd_run2/HToZATo2L2B_1000p00_200p00_9p00/HToZATo2L2B_1000p00_200p00_9p00_run_card.dat

[2] https://twiki.cern.ch/twiki/bin/viewauth/CMS/QuickGuideMadGraph5aMCatNLO#Gridpack_generation_on_the_grid

Thank you very much
Khawla

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#3

But you are running at LO not at NLO. So you can not use that value in that context
(and you use a very old run_card since you still have ptonium cut in your card.

Cheers,

Olivier

> On 11 Dec 2020, at 22:05, Khawla Jaffel <email address hidden> wrote:
>
>> The parameter ptonium is not supported anymore this parameter will be ignored.

Revision history for this message
hfhg gd (guitaar567) said :
#4

The parsing of the param_card/run_card are carried out on the python level allowing to have a lot more flexibility at the content material of the file and the layout of the variable than a fortran parser can offer (adequate technically fortran can do the identical but this is very difficult to implement with none bug due to the pressure of the language) as you can see https://gclubdealer.com/

Can you help with this problem?

Provide an answer of your own, or ask Khawla Jaffel for more information if necessary.

To post a message you must log in.