This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
2017:groups:tools:susylha [2017/06/21 16:45] benjamin.fuks |
2017:groups:tools:susylha [2017/06/22 18:20] olivier.mattelaer [The details] |
||
---|---|---|---|
Line 21: | Line 21: | ||
This general information line is then followed by the cross section themselves, given as a series of line under the form | This general information line is then followed by the cross section themselves, given as a series of line under the form | ||
<code> | <code> | ||
- | SCALE_SCHEME QCD_ORDER EW_ORDER KAPPA_F KAPPA_R PDF_ID VALUE CODE VERSION | + | SCALE_SCHEME QCD_ORDER EW_ORDER KAPPA_F KAPPA_R PDF_ID1 PDF_ID2 VALUE VALUEUP VALUEDOWN DUMMY |
</code> | </code> | ||
where | where | ||
Line 27: | Line 27: | ||
* 0: the central scale is the average mass of the produced particles | * 0: the central scale is the average mass of the produced particles | ||
* 1: fixed scales | * 1: fixed scales | ||
- | * 2: the scale is set to the partonic center-of-mass energy | + | * 2: the scale is set to the invariant mass of the final state particles at the LO |
- | * 3: the scale is set to the transverse mass of the final state particles | + | * 3: the scale is set to the transverse mass of the final state particles at the LO |
+ | * 4: some other definition to be described as a comment | ||
* **QCD_ORDER**: an integer number, which contains information on the order in alpha_s included in the computation. This is codified as | * **QCD_ORDER**: an integer number, which contains information on the order in alpha_s included in the computation. This is codified as | ||
* 0: Born cross section | * 0: Born cross section | ||
Line 38: | Line 39: | ||
* **PDF_ID**: the lhapdf code of the employed parton densities | * **PDF_ID**: the lhapdf code of the employed parton densities | ||
* **VALUE**: a floating point number, representing the value of the cross section in pb. | * **VALUE**: a floating point number, representing the value of the cross section in pb. | ||
- | * **CODE**: a string representing the name of the program which has computed the cross section | + | * **DUMMY**: integer number to tag possible different options to be described in the comments |
- | * **VERSION**: a string, the version number of the proram employed | + | * CODE: as a COMMENT string representing the name of the program which has computed the cross section |
+ | * VERSION: as a COMMENT string, the version number of the proram employed | ||
+ | * REFERENCE: Citation | ||
+ | * FIX the meaning of DEFAULT values... | ||
+ | |||
+ | Stefan comments: | ||
+ | - PREFERRED OPTION: In order to deal with resummation I suggest to add a second digit to QCD_ORDER, i.e. 0=LO, 1=NLO, 2=NNLO, etc. 11=NLO+NLL, 21=NNLO+NLL, 22=NNLO+NNLL, etc.. Only LO+LL=00 is then not well defined. And this approach is not specific to what is actually resummed (p_T, threshold,...). TYPE of resummation as a COMMENT. | ||
+ | - | ||
+ | - OPTIONAL: For EW corrections it would be helpful to somehow encode if full factorization is assumed or not. => Implement as a comment what scheme is used to combine QCD and EW corrections. | ||
+ | - | ||
+ | - Some codes also give a scale uncertainty in the same run. Can this be added? |