p p > t t~ [QCD] generation fail at specific mxx_min_pdg range

Asked by Marcos Miralles

Dear Experts,

We are running ttbar production using release 3.5.1. We are using the standard loop_sm model and the default param and run cards for this.

import model loop_sm
define p = g u c d s u~ c~ d~ s~ b b~
define j = p
generate p p > t t~ [QCD]
output ttbar-test_nlo
launch

The only exception is that we set

{6:640} = mxx_min_pdg ! inv. mass for any pair of (anti)particles

in the run_card.dat. This makes the run fail completely with the error attached at the bottom. There seems to be some strange problem with the minimum invariant mass in the range (590,690) that triggers this error since all of them fail. Others are ok. Our goal is to work out the differential ttbar cross-ections in m_ttbar, and later parametrise them using a SMEFT model.

We take the approach of using this variable because we want to set a different fixed scale for each bin (the choice of the scale, wether fixed -at any value- or dynamical doesn't affect the outcome, it still fails), that increases with m_ttbar. A possible work around is to generate at some other m_ttbar and then place the cuts at analysis level, but we would also want to understand why this problem arises in the first place.

It might be useful to mention that this only happens at NLO. At LO there are no issues.

Regards,
Marcos

INFO: Starting run
INFO: Compiling the code
INFO: Using built-in libraries for PDFs
INFO: For gauge cancellation, the width of 't' has been set to zero.
INFO: Compiling source...
INFO: ...done, continuing with P* directories
INFO: Compiling directories...
INFO: Compiling on 128 cores
INFO: Compiling P0_gg_ttx...
INFO: Compiling P0_uux_ttx...
INFO: Compiling P0_uxu_ttx...
INFO: P0_uux_ttx done.
INFO: P0_uxu_ttx done.
INFO: P0_gg_ttx done.
INFO: Checking test output:
INFO: P0_gg_ttx
INFO: Result for test_ME:
INFO: Output of the failing test:
 Enter 0 to compute MC/MC(limit)
       1 to compute MC/ME(limit)
       2 to compute ME/ME(limit)
 Enter xi_i, y_ij to be used in coll/soft tests
  Enter -2 to generate them randomly
 Enter number of tests for soft and collinear limits
 SPLIT TYPE USED: T F
 A PDF is used, so alpha_s(MZ) is going to be modified
 Old value of alpha_s from param_card: 0.11900000000000002
  ****************************************

       NNPDFDriver version 1.0.3
   Grid: NNPDF23nlo_as_0119_qed_mem0.grid
  ****************************************
 New value of alpha_s from PDF nn23nlo: 0.11899999999999999
 Give FKS configuration number ("0" loops over all)

 =================================================

 NEW FKS CONFIGURATION:
 FKS configuration number is 1
 FKS partons are: i= 5 j= 1
 with PDGs: i= 21 j= 21

 Enter graph number (iconfig), '0' loops over all graphs
Using random seed offsets: 1 , 1 , 0
  with seed 33
 Ranmar initialization seeds 11949 9408
tau_min 1 1 : 0.34600E+03 -- 0.64000E+03
tau_min 2 1 : 0.34600E+03 -- 0.64000E+03
tau_min 3 1 : 0.64000E+03 0.64000E+03 0.64000E+03
tau_min 4 1 : 0.64000E+03 0.64000E+03 0.64000E+03
tau_min 5 1 : 0.34600E+03 -- 0.64000E+03
tau_min 6 1 : 0.34600E+03 -- 0.64000E+03
tau_min 7 1 : 0.34600E+03 -- 0.64000E+03
tau_min 8 1 : 0.34600E+03 -- 0.64000E+03
 BORN: keeping split order 1
 counterterm S.O 1 QCD
 BORN: keeping split order 1
 counterterm S.O 2 QED
 BORN: not keeping split order 1

 REAL 1: keeping split order 1
 Soft tests done for (Born) config 1
 Failures: 100 0 100
Sum of all orders: Soft test 1 FAILED. Fraction of failures: 1.00
Split-order 2: QCD: 6; QED: 0; Soft test 1 FAILED. Fraction of failures: 1.00

 Collinear tests done for (Born) config 1
 Failures: 0 0 0
Sum of all orders: Collinear test 1 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Collinear test 1 PASSED. Fraction of failures: 0.00

 =================================================

 NEW FKS CONFIGURATION:
 FKS configuration number is 2
 FKS partons are: i= 5 j= 2
 with PDGs: i= 21 j= 21

 Enter graph number (iconfig), '0' loops over all graphs

 Soft tests done for (Born) config 1
 Failures: 100 0 100
Sum of all orders: Soft test 2 FAILED. Fraction of failures: 1.00
Split-order 2: QCD: 6; QED: 0; Soft test 2 FAILED. Fraction of failures: 1.00

 Collinear tests done for (Born) config 1
 Failures: 0 0 0
Sum of all orders: Collinear test 2 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Collinear test 2 PASSED. Fraction of failures: 0.00

 =================================================

 NEW FKS CONFIGURATION:
 FKS configuration number is 3
 FKS partons are: i= 5 j= 3
 with PDGs: i= 21 j= 6

 Enter graph number (iconfig), '0' loops over all graphs

 Soft tests done for (Born) config 1
 Failures: 0 0 0
Sum of all orders: Soft test 3 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Soft test 3 PASSED. Fraction of failures: 0.00

 No collinear test for massive j_fks

 =================================================

 NEW FKS CONFIGURATION:
 FKS configuration number is 4
 FKS partons are: i= 5 j= 4
 with PDGs: i= 21 j= -6

 Enter graph number (iconfig), '0' loops over all graphs

 Soft tests done for (Born) config 1
 Failures: 0 0 0
Sum of all orders: Soft test 4 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Soft test 4 PASSED. Fraction of failures: 0.00

 No collinear test for massive j_fks

 =================================================

 NEW FKS CONFIGURATION:
 FKS configuration number is 5
 FKS partons are: i= 5 j= 1
 with PDGs: i= -1 j= -1

 Enter graph number (iconfig), '0' loops over all graphs

 REAL 2: keeping split order 1
 Soft tests done for (Born) config 1
 Failures: 0 0 100
Sum of all orders: Soft test 5 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Soft test 5 FAILED. Fraction of failures: 1.00

 Collinear tests done for (Born) config 1
 Failures: 0 0 0
Sum of all orders: Collinear test 5 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Collinear test 5 PASSED. Fraction of failures: 0.00

 =================================================

 NEW FKS CONFIGURATION:
 FKS configuration number is 6
 FKS partons are: i= 5 j= 1
 with PDGs: i= 1 j= 1

 Enter graph number (iconfig), '0' loops over all graphs

 REAL 3: keeping split order 1
 Soft tests done for (Born) config 1
 Failures: 0 0 100
Sum of all orders: Soft test 6 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Soft test 6 FAILED. Fraction of failures: 1.00

 Collinear tests done for (Born) config 1
 Failures: 0 0 0
Sum of all orders: Collinear test 6 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Collinear test 6 PASSED. Fraction of failures: 0.00

 =================================================

 NEW FKS CONFIGURATION:
 FKS configuration number is 7
 FKS partons are: i= 5 j= 2
 with PDGs: i= -1 j= -1

 Enter graph number (iconfig), '0' loops over all graphs

 REAL 4: keeping split order 1
 Soft tests done for (Born) config 1
 Failures: 0 0 100
Sum of all orders: Soft test 7 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Soft test 7 FAILED. Fraction of failures: 1.00

 Collinear tests done for (Born) config 1
 Failures: 0 0 0
Sum of all orders: Collinear test 7 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Collinear test 7 PASSED. Fraction of failures: 0.00

 =================================================

 NEW FKS CONFIGURATION:
 FKS configuration number is 8
 FKS partons are: i= 5 j= 2
 with PDGs: i= 1 j= 1

 Enter graph number (iconfig), '0' loops over all graphs

 REAL 5: keeping split order 1
 Soft tests done for (Born) config 1
 Failures: 0 0 100
Sum of all orders: Soft test 8 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Soft test 8 FAILED. Fraction of failures: 1.00

 Collinear tests done for (Born) config 1
 Failures: 0 0 0
Sum of all orders: Collinear test 8 PASSED. Fraction of failures: 0.00
Split-order 2: QCD: 6; QED: 0; Collinear test 8 PASSED. Fraction of failures: 0.00
Error detected in "launch auto "
write debug file /lhome/ific/m/marmilo/MG5/MG5_aMC_v3_5_1/ttbar-test_nlo/run_02_tag_1_debug.log
If you need help with this issue, please, contact us on https://answers.launchpad.net/mg5amcnlo
str : Some tests failed, run cannot continue. Please search on https://answers.launchpad.net/mg5amcnlo for more information, and in case there is none, report the problem there.
quit

Question information

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

Just waiting that Rik is back from holliday,

I would comment that for your goal it is probably better to define a new dynamical scale choice (see the FAQ)
rather than running many different run.

Concerning your issue, I guess that this is a technical issue with the NLO test rather than something deep.
I do not think that they are any issue to impose such cut for NLO computation.

Cheers,

Olivier

> On 29 Jul 2023, at 00:35, Olivier Mattelaer <email address hidden> wrote:
>
> Question #707418 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/707418
>
> Assignee: None => Rikkert Frederix
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Revision history for this message
Rikkert Frederix (frederix) said :
#2

Dear Marcos,

Indeed, I have found the problem. When determining the center-or-mass energy to perform the tests, these cuts were not taken into account resulting into phase-space configurations which were outside of the allowed range. This will be fixed in the next release of the code. For the moment, it's probably easiest to simply bypass the tests. To do this, do as before until the code fails. Then do a re-launch, but with the '-x' flag. That is:

generate p p > t t~ [QCD]
output ttbar-test_nlo
launch

---> wait until the code fails. Then:

launch -x

This should skip all the tests.

Moreover, note that your setup is inconsistent: you cannot use a 4-flavour scheme model (i.e., with massive b quarks) and then add the b quark to the initial state. That is inconsistent at NLO. You probably want to

import model loop_sm-no_b_mass

to get a proper 5-flavour scheme model before generating your process.

best,
Rikkert

Revision history for this message
Marcos Miralles (marcosmiralles) said :
#3

Hello Olivier, Rikkert,

Thanks for your suggestions. In fact, I tried to make this question as reproducible as possible by simplifying what we actually do.
We are using the SMEFT@NLO model for our simulations which also had the same issue and is also fixed by skipping the tests. Here we have done the correct usage of the 5F scheme (I overlooked that part in the question).

> I would comment that for your goal it is probably better to define a new dynamical scale choice (see the FAQ)
rather than running many different run.

I have checked the FAQ (https://answers.launchpad.net/mg5amcnlo/+faq/3325), not sure if it applies to our problem because I don't really understand the fortran code. In the SMEFT@NLO model it is recommended to use a fixed scale, hence why we have multiple runs with different fixed scales. It seems that this new feature allows to define a scale based on run_card parameters (?); since we have uneven bins, we don't have a relation between the wanted scale and the corresponding mxx_min_pdg bin edge. Plus, we are scanning up to 2300 GeV so I imagine we might run out of stats at some point if we go for one inclusive run.

Regards,
Marcos

Can you help with this problem?

Provide an answer of your own, or ask Marcos Miralles for more information if necessary.

To post a message you must log in.