EFT at NLO: issue with phase-space generation

Bug #1959908 reported by Olivier Mattelaer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MadGraph5_aMC@NLO
New
Wishlist
Rikkert Frederix

Bug Description

Hi,

I am running p p > t t~ t t~ QCD<=6 QED<=6 YT <=6 NP<=2 [LOonly=all] with mg5 stable v 3_3_1. I use SMEFTatNLO with a restriction card that uses all two fermion operators. I use HwU analysis to separate the SMEFT orders using order tags.

I run into the following error:
ERROR in genps_fks.f: cannot set s-channel without BW -2 NaN 266256.00000000000

which appears in the log file in the G* dir. in a given Subprocess dir.

May you please help with this?

Best,
Hesham

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Hi,

I guess that we will need the restriction card in order to investigate and in which channel this does occur (to avoid to do the full computation)

Can you attach the restriction file here?

Olivier

Changed in mg5amcnlo:
assignee: nobody → Rikkert Frederix (frederix)
Revision history for this message
Hesham El Faham (helfaham) wrote :

Hi,

Thanks for the quick reply! Attached is the restriction card. This restriction card selects only dim62f operators.

(The problem does not occur for example when I use a restriction card that takes only dim64f.)

Best,
Hesham

Revision history for this message
Hesham El Faham (helfaham) wrote :

Hi,

Now that I let the process runs through the error until it fails completely. The log files ends as follows:

WARNING #32 in genps_fks.f -2 260952.38105945828 266256.00000000000 292231.29589152237 -0.22865319252014160
 WARNING #32 in genps_fks.f -2 236483.86367991008 266256.00000000000 5462081.6096668122 -0.13234639167785645
 ERROR: NOT ENOUGH POINTS PASS THE CUTS. RESULTS CANNOT BE TRUSTED. LOOSEN THE GENERATION CUTS, OR ADAPT SET_TAU_MIN() IN SETCUTS.F ACCORDINGLY.
Time in seconds: 5

Note that this is the case in the qq-initiated Subprocesses only, not gg ones.

Best,
Hesham

Revision history for this message
Rikkert Frederix (frederix) wrote :

Dear Hesham,

I'm trying to generate your process, but the 'SMEFTatNLO' does not have a 'YT' order:

MG5_aMC>import model SMEFTatNLO-LO_DIM62F
MG5_aMC>generate p p > t t~ t t~ QCD<=6 QED<=6 YT <=6 NP<=2 [LOonly=all]
InvalidCmd : model order YT not valid for this model (valid one are: NP, QED, QCD, EW, EW^2, aEW, aS).

What are the commands/model you used to generate the process?

Best regards,
Rikkert

Revision history for this message
Hesham El Faham (helfaham) wrote (last edit ):

Hi Rikkert,

Attached is the modified SMEFTatNLO model I am using.

Additional info: I tried to increase the max_points var. in mint_module but that did not work.

Thanks,
Hesham

Revision history for this message
Rikkert Frederix (frederix) wrote :

Dear Hesham,

There are 55 different coupling orders in your process. Hence, I guess that you, in order to prevent this error message,

Too many grids to keep track off 55 10
STOP 1

have increased the n_ave_virt parameter in the mint_module.f90. However, you cannot simply increase this parameter to 55 and hope that everything else runs correctly. The 'nintegrals' parameter should be increased as well (to 116 to be precise) and also the 'title=' array should be increased to give a name to all these extra 90 integrals.

Next time, if you change something in the source code, you should include that as part of your bug report. Today, I wasted quite a bit of time on this and I could have saved a large part of it had you told me that you changed some internal parameters in the code.

Now, I guess that for the future it would be good to set the sizes of these parameters automatically, based on the number of coupling orders. So, I'll rename this bug as a new feature request.

best regards,
Rikkert

Changed in mg5amcnlo:
importance: Undecided → Wishlist
Revision history for this message
Hesham El Faham (helfaham) wrote :

Dear Rikkert,

It is true I changed n_ave_virt. I am very sorry I did not report this, my bad.

I am not sure how to increase the title array, may you please elaborate on this?

Thanks,
Hesham

Revision history for this message
Hesham El Faham (helfaham) wrote :

I think I managed, just extended V10 B10 to V11 B11, etc.

I am now doing a test run and will let you know if it worked.

Thanks,
Hesham

Revision history for this message
Hesham El Faham (helfaham) wrote :
Download full text (5.3 KiB)

Hi again Rikkert,

The fix induced a different error:
launch
Traceback (most recent call last):
  File "/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/bin/internal/extended_cmd.py", line 1544, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/bin/internal/extended_cmd.py", line 1493, in onecmd_orig
    return func(arg, **opt)
  File "/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/bin/internal/amcatnlo_run_interface.py", line 1784, in do_launch
    evt_file = self.run(mode, options)
  File "/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/bin/internal/amcatnlo_run_interface.py", line 1941, in run
    jobs_to_collect,integration_step,mode,mode_dict[mode])
  File "/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/bin/internal/amcatnlo_run_interface.py", line 2259, in collect_the_results
    self.append_the_results(jobs_to_run,integration_step)
  File "/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/bin/internal/amcatnlo_run_interface.py", line 2752, in append_the_results
    '\n'.join(error_log)+'\n')
aMCatNLOError: An error occurred during the collection of results.
Please check the .log files inside the directories which failed:
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_gg_tttxtx/born_G24/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_gg_tttxtx/born_G25/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bbx_tttxtx/born_G24/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bbx_tttxtx/born_G25/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bbx_tttxtx/born_G26/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bbx_tttxtx/born_G27/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bbx_tttxtx/born_G28/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bbx_tttxtx/born_G29/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bxb_tttxtx/born_G24/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bxb_tttxtx/born_G25/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bxb_tttxtx/born_G26/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bxb_tttxtx/born_G27/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bxb_tttxtx/born_G28/log.txt
/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_bxb_tttxtx/born_G29/log.txt
Value of current Options:
              text_editor : None
      notification_center : True
       cluster_local_path : /cvmfs/cp3.uclouvain.be/madgraph/
    cluster_status_update : (900, 60)
               hepmc_path : None
          pythia-pgs_path : None
              thepeg_path : None
        madanalys...

Read more...

Revision history for this message
Rikkert Frederix (frederix) wrote :

Dear Hesham,

This looks like your run was killed for some other reason. To double check, can you go to one of the directories where you found the log files, e.g.,

/nfs/scratch/fynu/elfaham/4tops_dir_dim62f/dim62f/sm_dim62f_ctZ/SubProcesses/P0_gg_tttxtx/born_G24

and execute from there,

../madevent_mintFO

? Does it still stop after a single second, or does it run normally? If it runs normally, the issues does not seem to be specific to MG5aMC, but rather due to some time-limit, or memory limit or something related to that, for which I cannot really help you.

Best,
Rikkert

Revision history for this message
Hesham El Faham (helfaham) wrote :

Hi Rikkert,

It gets aborted immediately:

[elfaham@ingrid-ui1 born_G24]$ ../madevent_mintFO
     2547485
 ===============================================================
 INFO: MadFKS read these parameters from FKS_params.dat
 ===============================================================
  > IRPoleCheckThreshold = 1.0000000000000001E-005
  > PrecisionVirtualAtRunTime = 1.0000000000000000E-003
  > SelectedContributionTypes = All
  > VetoedContributionTypes = None
  > QCD_squared_selected = All
  > QED_squared_selected = All
  > SelectedCouplingOrders = All
  > NHelForMCoverHels = 4
  > VirtualFraction = 1.0000000000000000
  > MinVirtualFraction = 5.0000000000000001E-003
  > SeparateFlavourConfigs = F
  > UsePolyVirtual = F
 ===============================================================
 SPLIT TYPE USED: F F F F
 A PDF is used, so alpha_s(MZ) is going to be modified
 Old value of alpha_s from param_card: 0.11839999999999999
==== LHAPDF6 USING DEFAULT-TYPE LHAGLUE INTERFACE ====
terminate called after throwing an instance of 'LHAPDF::ReadError'
  what(): Info file not found for PDF set 'NNPDF31_nlo_as_0118'

Program received signal SIGABRT: Process abort signal.

Backtrace for this error:
#0 0x7F1DB33CD697
#1 0x7F1DB33CDCDE
#2 0x7F1DB28C83FF
#3 0x7F1DB28C8387
#4 0x7F1DB28C9A77
#5 0x7F1DB37367D4
#6 0x7F1DB3734745
#7 0x7F1DB3734772
#8 0x7F1DB3734992
#9 0x8DF3AA in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*>(char*, char*, std::allocator<char> const&)
#10 0x8EC7FF in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*>(char*, char*, std::allocator<char> const&)
#11 0x8ED4F5 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*>(char*, char*, std::allocator<char> const&)
#12 0x8CFB85
#13 0x8D0AD2
#14 0x8D0E1D
#15 0x8CE04E
#16 0x8C17E3
#17 0x8896CF
#18 0x88B418
#19 0x7F1DB28B4554
#20 0x405688
#21 0xFFFFFFFFFFFFFFFF
Aborted

Best,
Hesham

Revision history for this message
Rikkert Frederix (frederix) wrote :

Dear Hesham,

This looks like an issue with LHAPDF, since it cannot find the NNPDF31_nlo_as_0118 pdf set. This should not be specific to this process, but rather a general problem that should also appear for other processes. Is this the case?

Best,
Rikkert

Revision history for this message
Hesham El Faham (helfaham) wrote :

Hi Rikkert,

I think it is somehow related to the dim62f processes. I will try other restriction cards and see if the problem persists.

I will keep you posted.

Best,
Hesham

Revision history for this message
Hesham El Faham (helfaham) wrote :

Hi again Rikkert,

I regenerated two processes from scratch, one for dim64F and one for dim62F.

With the same lhapdf6 installation, things are perfectly fine for the dim64F one while the issue persists for the dim62F process.

I checked run and param card, and restriction cards, everything seems consistent across both directories.

Indeed it is strange, but do you have any idea what it can possibly be?

Best,
Hesham

Revision history for this message
Hesham El Faham (helfaham) wrote :

I reinstalled lhapdf6. Now the error is different and perhaps simpler since this execution ../madevent_mintFO runs fine. I will report it on a different string.

Thank you anyways,
Hesham

Revision history for this message
ben foster (foster67) wrote :

Phase-space generation can be challenging due to its complexity and computational demands, often requiring sophisticated algorithms and substantial computational resources. It's essential to consider factors like dimensionality, sampling methods, and accuracy to address these challenges effectively.<a href="https://sunnypathenergy.com">SunnyPath Energy</a>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.