aMCatNLOError : Some tests failed, run cannot continue

Asked by Inês Ochoa

Hi,

I've been generating, decaying and showering the process p p > W- + bb [QCD] and I am now getting an error right at the beginning:

Error detected in "launch "
write debug file /unix/atlas2/ines/software/MG5_aMC_v2_1_0/Wmbb_100TeV/run_55_tag_1_debug.log
If you need help with this issue please contact us on https://answers.launchpad.net/madgraph5
aMCatNLOError : Some tests failed, run cannot continue.
 Please check that widths of final state particles (e.g. top) have been set to 0 in the param_card.dat.

The contents of the run_55_tag_1_debug.log file are:

launch
Traceback (most recent call last):
  File "/unix/atlas2/ines/software/MG5_aMC_v2_1_0/Wmbb_100TeV/bin/internal/extended_cmd.py", line 872, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/unix/atlas2/ines/software/MG5_aMC_v2_1_0/Wmbb_100TeV/bin/internal/extended_cmd.py", line 865, in onecmd_orig
    return func(arg, **opt)
  File "/unix/atlas2/ines/software/MG5_aMC_v2_1_0/Wmbb_100TeV/bin/internal/amcatnlo_run_interface.py", line 1184, in do_launch
    self.compile(mode, options)
  File "/unix/atlas2/ines/software/MG5_aMC_v2_1_0/Wmbb_100TeV/bin/internal/amcatnlo_run_interface.py", line 3208, in compile
    self.check_tests(test, this_dir)
  File "/unix/atlas2/ines/software/MG5_aMC_v2_1_0/Wmbb_100TeV/bin/internal/amcatnlo_run_interface.py", line 3220, in check_tests
    return self.parse_test_mx_log(pjoin(dir, '%s.log' % test))
  File "/unix/atlas2/ines/software/MG5_aMC_v2_1_0/Wmbb_100TeV/bin/internal/amcatnlo_run_interface.py", line 3232, in parse_test_mx_log
    ' set to 0 in the param_card.dat.')
aMCatNLOError: Some tests failed, run cannot continue.
Please check that widths of final state particles (e.g. top) have been set to 0 in the param_card.dat.
Value of current Options:
              web_browser : None
              text_editor : nano
        cluster_temp_path : None
             syscalc_path : None
            cluster_queue : madgraph
         madanalysis_path : None
                   lhapdf : lhapdf-config
                 mg5_path : /home/inesochoa/MG5_aMC_v2_1_0
           cluster_memory : None
    cluster_status_update : (600, 30)
             cluster_time : None
               hepmc_path : /unix/atlas2/ines/software/HepMC/HepMC-2.06.09
             pythia8_path : None
                hwpp_path : /unix/atlas2/ines/software/Herwigpp
   automatic_html_opening : False
       cluster_retry_wait : 300
             stdout_level : None
          pythia-pgs_path : None
                  td_path : None
             delphes_path : None
              thepeg_path : /unix/atlas2/ines/software/ThePEG
             cluster_type : condor
      exrootanalysis_path : None
         fortran_compiler : None
              auto_update : 7
         cluster_nb_retry : 1
               eps_viewer : None
                  timeout : 60
                  fastjet : fastjet-config
                  nb_core : 8
                 run_mode : 2

What is surprising is that I've generated a fair amount of events already, in several different runs, and only now this crash occurred. I am therefore hesitant to change anything on the parameter card. Any idea of what could be going wrong?

Thanks a lot in advance!

Inês

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
marco zaro Edit question
Solved by:
marco zaro
Solved:
Last query:
Last reply:
Revision history for this message
marco zaro (marco-zaro) said :
#1

Dear Ines,
can you plese send the test_ME.log files in the SubProcesses/P0* directories?
also, can you send the content of the run/param/proc cards?
since Launchpad does not eallow to attach files, send them to
<email address hidden>
Thanks,

Marco

Revision history for this message
Best marco zaro (marco-zaro) said :
#2

Dear Ines,
thanks for the files.
The failing test is inside P0_dux_wmbb, where you have
 Failures: 34
     Soft test 1 FAILED. Fraction of failures: 0.34
The maximum allowed failures fraction normally is 0.3.
For such a process, where you have many different scales (w mass, b mass and the very large center of mass energy) you may well expect some more instabilities, so i think it is safer to set the maximum tolerated fraction of failures to a larger value (0.4 should go).
You can simply change inside the file SubProcesses/symmetry_fks_test_ME.f, at line 120, the hardcoded value for the max_fail parameters.
Please let me know if the problem is solved.
Cheers,

Marco

Revision history for this message
Inês Ochoa (inesochoa) said :
#3

Dear Marco,

Indeed this solved the problem. Thanks a lot for the very clear explanation!

Cheers
Inês

Revision history for this message
Inês Ochoa (inesochoa) said :
#4

Thanks marco zaro, that solved my question.