Compilation issue on 2.3.0 beta

Asked by Alberto Gascón

Hi all,

I'm trying to generate an event sample sending the jobs to the local cluster of my institution. When I run the process locally everything seems to work fine, but on the cluster the compilation fails. I'm running MadGraph 2.3.0 beta, and my card looks like (I don't this is a problem related to my process in particular, but just in case).

import model 2HDMtypeII
generate g g > t t~ h2 QED=99 QCD=99, h2 > t t~ QED=99 QCD=99
output /nfs/dust/atlas/user/gascon/2_MadGraph/Results/2HDMtypeII_Pythia/S/mh2_1100_1_all -nojpeg
launch
set mh2 1100
set mh3 1100
set mhc 1100
set nevents 20000
set wh2 auto
set wh3 auto
set whc auto
set mixh 0
set beta .785
set cut_decays F
0

The traceback is quite long, you can find it here https://www.dropbox.com/s/i52fyely4zvp1p0/traceback.log?dl=0

Cheers,
   Alberto

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
Valentin Hirschi Edit question
Solved by:
Olivier Mattelaer
Solved:
Last query:
Last reply:
Revision history for this message
Best Olivier Mattelaer (olivier-mattelaer) said :
#1

Hi Alberto,

Which version of gfortran are you using.
Looks like this version of MG has some new requirements on the minimal version of gfortran that is needed to run LO process.
Valentin should be able to help you more on this.

Cheers,

Olivier

Revision history for this message
Alberto Gascón (albergascon) said :
#2

Hi Olivier, Valentin,

it seems that I'm using version 4.4.7. This is what I get after typing gfortran --version when I set the same environment
variables as in the cluster

     GNU Fortran (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11)

But with this version the process compiles fine when I run locally. I will find out if the gfortran version changes at some point when
running in the cluster

Cheers,
   Alberto

Revision history for this message
Alberto Gascón (albergascon) said :
#3

Indeed, the gfortran when I run inside the cluster is

   GNU Fortran (GCC) 4.1.2 20080704 (Red Hat 4.1.2-55)

I will ask around how to change that.

Cheers,
  Alberto

Revision history for this message
Alberto Gascón (albergascon) said :
#4

Hi all again,

luckily it was an easy change. It's working fine now.

Thank you very much.
Cheers,
   Alberto

Revision history for this message
Alberto Gascón (albergascon) said :
#5

Thanks Olivier Mattelaer, that solved my question.