Installing mg5amc_py8_interface fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MadGraph5_aMC@NLO |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi,
I use an environment where libHepMC.a is contained in the LD_LIBRARY_PATH (concretely I source /cvmfs/
When installing Pythia8 from within MadGraph, MadGraph recognizes this HepMC version and prints a warning concerning the use of named weights and encourages the user to use the HepMC version which can be installed by MadGraph.
Hence I start again and install first hepmc from within MadGraph and only after that I install Pythia8. Indeed, this time the warning concerning named weights is no longer present. However unfortunately this time I get an error during the compilation of MG5aMC_
MG5aMC_
My guess is that at this point the wrong libHepMC.a is used. I think it could be fixed by either using another order for the library directories during linking or by explicitly linking with
-l$(CUSTOM_
In order to confirm that idea I tried to change that in HEPTools/
and to install Pythia8 again but unfortunately the makefile is overwrittenso I couldn't test it.
Cheers,
BJ
Changed in mg5amcnlo: | |
status: | Fix Committed → Fix Released |
I see two solutions:
a) (This should be what is happening already) When you are about to shower using PY8 and MG5aMC you see that in the script 'run_shower.sh' in <PROC_OUTPUT> /Event/ run_<xx> we temporarily change LD_LIBRARY_PATH so as to place 'PROC_OUTPUT> /HEPTools/ libs' first. This should make sure that your locally installed version of hepmc is used (and not the environment-wide one).
This should already work automatically when MG5aMC steers the PY8 showering for you at LO. So I'm puzzled as to why it doesn't do the trick for you here.
b) Instead of re-installing 'MG5aMC_ PY8_interface' , you can recompile the existing one 'PROC_OUTPUT> /HEPTools/ MG5aMC_ PY8_interface' by going to this directory and typing:
./compile.py <PATH_TO_PYTHIA8>
Where <PATH_TO_PYTHIA8> is likely to simply be '../pythia8' if you installed Pythia8 with MG5aMC as well.
You can then easily modify the part of the script 'compile.py' which gets the makefile from Pythia8 so as to use your own makefile.