Compilation error due to an update?

Asked by Yael Raveh

Hey,
Will appreciate any help with the following compilation error;

Error detected in "generate_events run_01"
write debug file /home/yael/MG5_aMC_v2_3_3/lumi/run_01_tag_1_debug.log
If you need help with this issue please contact us on https://answers.launchpad.net/mg5amcnlo
MadGraph5Error : A compilation Error occurs when trying to compile /home/yael/MG5_aMC_v2_3_3/lumi/Source.
 The compilation fails with the following output message:
     gfortran -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c -o setrun.o setrun.f
     ar cru ../lib/libgeneric.a alfas_functions.o transpole.o invarients.o hfill.o pawgraphs.o ran1.o rw_events.o rw_routines.o kin_functions.o open_file.o basecode.o setrun.o run_printout.o dgauss.o readgrid.o getissud.o
     ranlib ../lib/libgeneric.a
     cd PDF; make
     make[1]: Entering directory `/home/yael/MG5_aMC_v2_3_3/lumi/Source/PDF'
     ar cru ../../lib/libpdf.a Ctq4Fn.o Ctq5Par.o Ctq5Pdf.o Partonx5.o Ctq6Pdf.o cteq3.o mrs98.o mrs98lo.o mrs98ht.o mrs99.o mrst2001.o mrst2002.o jeppe02.o pdfwrap.o opendata.o pdf.o PhotonFlux.o pdg2pdf.o NNPDFDriver.o
     ranlib ../../lib/libpdf.a
     make[1]: Leaving directory `/home/yael/MG5_aMC_v2_3_3/lumi/Source/PDF'
     cd MODEL; make
     make[1]: Entering directory `/home/yael/MG5_aMC_v2_3_3/lumi/Source/MODEL'
     gfortran -O -w -fbounds-check -fPIC -ffixed-line-length-132 -c -o rw_para.o rw_para.f
     ar cru ../../lib/libmodel.a couplings.o lha_read.o printout.o rw_para.o model_functions.o couplings1.o couplings2.o
     ranlib ../../lib/libmodel.a
     make[1]: Leaving directory `/home/yael/MG5_aMC_v2_3_3/lumi/Source/MODEL'
     cd BIAS/dummy; make
     make[1]: Entering directory `/home/yael/MG5_aMC_v2_3_3/lumi/Source/BIAS/dummy'
     ar cru dummy.o
     ar: dummy.o: File format not recognized
     make[1]: *** [dummy] Error 1
     make[1]: Leaving directory `/home/yael/MG5_aMC_v2_3_3/lumi/Source/BIAS/dummy'
     make: *** [../lib/libbias.a] Error 2

 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.launchpad.net/mg5amcnlo

It suddenly appears whenever I try to launch any process in MG5.
Automatic updating is the only thing I can think of as the cause of it, as it's the only thing that happened since the time it worked without errors.

Thank you so much in advance,
Yael

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
Valentin Hirschi Edit question
Solved by:
Yael Raveh
Solved:
Last query:
Last reply:
Revision history for this message
Valentin Hirschi (valentin-hirschi) said :
#1

Could you first confirm that you are running 'generate_events' or 'launching' a process that was indeed output *after* the auto-update.
If not, then this is expected, and you must regenerate your process after the auto-update.

it yes, then please try to amend your installation with the change suggested by Olivier here:

https://bugs.launchpad.net/mg5amcnlo/+bug/1643894

Finally, if you could confirm that you have no problem running your process with a fresh new installation of the latest version of MG5aMC, this would help in making sure that the problem came from the auto-update.

Revision history for this message
Valentin Hirschi (valentin-hirschi) said :
#2

Could you first confirm that you are running 'generate_events' or 'launching' a process that was indeed output *after* the auto-update.
If not, then this is expected, and you must regenerate your process after the auto-update.

it yes, then please try to amend your installation with the change suggested by Olivier here:

https://bugs.launchpad.net/mg5amcnlo/+bug/1643894

Finally, if you could confirm that you have no problem running your process with a fresh new installation of the latest version of MG5aMC, this would help in making sure that the problem came from the auto-update.

Revision history for this message
Yael Raveh (ravehya) said :
#3

Okay, yep that solves it; I've amended the installation with the change suggested by Olivier, and regenerated+reoutputed the event after that (and of course - after the auto-update). Apologize for triviality.

I'm not quite sure I've understood your request. I have the 2.5.1 version (2016-11-04).

Thank you both Valentine and Olivier for the quick and helpful responses.