Compilation error during generate events in symmetry.o

Asked by Patrick Schaefers

Dear Developers,

I am using fresh instals of MadGraph 2.2.3 and 2.4.3 to generate events for the large process "u u~ > u u~ b b~ b b~ b b~" on a powerful computer (no cluster). While the initial steps work out fine (i.e. "generate u u~ > u u~ b b~ b b~ b b~" and "output my_proc"), I cannot create any events, beacuse "./bin/generate_events -f" gives the following compilation error:

MadGraph5Error : A compilation Error occurs when trying to compile /local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/SubProcesses/P1_qq_qqbbxbbxbbx.
        The compilation fails with the following output message:
            gfortran -O -w -fbounds-check -fPIC -ffixed-line-length-132 -w -c symmetry.f -I../../Source/
            gfortran -O -w -fbounds-check -fPIC -ffixed-line-length-132 -w -c idenparts.f -I../../Source/
            gfortran: Internal error: Segmentation fault (program f951)
            Please submit a full bug report.
            See <http://bugzilla.redhat.com/bugzilla> for instructions.
            make: *** [symmetry.o] Error 1

In Madgraph 2.2.3, the error appears in matrix1.o instead of symmetry.o. I copied the debug.log for the 2.4.3 run below.
Do you have any idea why this i happening? I can create events for different processes, though - maybe it is because of the very large phase space?

Thank you very much in advance for your help.

Cheers,
Patrick

----------

The debug.log reads:
generate_events -f
Traceback (most recent call last):
  File "/local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/bin/internal/extend
ed_cmd.py", line 1011, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/bin/internal/extend
ed_cmd.py", line 966, in onecmd_orig
    return func(arg, **opt)
  File "/local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/bin/internal/madeve
nt_interface.py", line 1992, in do_generate_events
    postcmd=False)
  File "/local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/bin/internal/extend
ed_cmd.py", line 1037, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File "/local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/bin/internal/extend
ed_cmd.py", line 966, in onecmd_orig
    return func(arg, **opt)
  File "/local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/bin/internal/madeve
nt_interface.py", line 2697, in do_survey
    jobs, P_zero_result = ajobcreator.launch()
  File "/local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/bin/internal/gen_xi
mprove.py", line 143, in launch
    self.cmd.compile(['gensym'], cwd=Pdir)
  File "/local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/bin/internal/extend
ed_cmd.py", line 1105, in compile
    return misc.compile(nb_core=self.options['nb_core'], *args, **opts)
  File "/local/scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/bin/internal/misc.p
y", line 535, in compile
    raise MadGraph5Error, error_text
MadGraph5Error: A compilation Error occurs when trying to compile /local/
scratch/pbh1g14/MG5_aMC_v2_4_3/uu_uu6b/SubProcesses/P1_qq_qqbbxbbxbbx.
The compilation fails with the following output message:
    gfortran -O -w -fbounds-check -fPIC -ffixed-line-length-132 -w -c sym
metry.f -I../../Source/
    gfortran -O -w -fbounds-check -fPIC -ffixed-line-length-132 -w -c ide
nparts.f -I../../Source/
    gfortran: Internal error: Segmentation fault (program f951)
    Please submit a full bug report.
    See <http://bugzilla.redhat.com/bugzilla> for instructions.
    make: *** [symmetry.o] Error 1

Please try to fix this compilations issue and retry.
Help might be found at https://answers.launchpad.net/mg5amcnlo.
If you think that this is a bug, you can report this at https://bugs.laun
chpad.net/mg5amcnlo
                              Run Options
                              -----------
               stdout_level : None

                         MadEvent Options
                         ----------------
     automatic_html_opening : False (user set)
        notification_center : True
          cluster_temp_path : None
             cluster_memory : None
               cluster_size : 100
              cluster_queue : None
                    nb_core : 8 (user set)
               cluster_time : None
                   run_mode : 2

                      Configuration Options
                      ---------------------
                text_editor : None
         cluster_local_path : /cvmfs/cp3.uclouvain.be/madgraph/
      cluster_status_update : (600, 30)
               pythia8_path : None (user set)
                  hwpp_path : None (user set)
            pythia-pgs_path : None (user set)
                    td_path : None (user set)
               delphes_path : None (user set)
                thepeg_path : None (user set)
               cluster_type : condor
        exrootanalysis_path : None (user set)
                 eps_viewer : None
                web_browser : None
               syscalc_path : None (user set)
           madanalysis_path : None (user set)
                     lhapdf : lhapdf-config
              f2py_compiler : None
                 hepmc_path : None (user set)
         cluster_retry_wait : 300
           fortran_compiler : None
                auto_update : 7 (user set)
           cluster_nb_retry : 1
                    timeout : 60
               cpp_compiler : None

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
Valentin Hirschi (valentin-hirschi) said :
#1

Given the complexity of your process and the fact that your compiler triggered a segmentation fault, I would lean towards you hitting the RAM cap of your computer.
I suggest that you identify the compilation line that triggered the segfault (probably the one of identparts.f), and reran it by hand in this folder while monitoring your RAM consumption.

It could also be an issue with your compiler suite, and it might help to try various compiler options or a different/more recent compiler (or even run it with gdb).

In any case, I believe there is nothing wrong with MG5aMC output and this really is a compiler issue.

Can you help with this problem?

Provide an answer of your own, or ask Patrick Schaefers for more information if necessary.

To post a message you must log in.