@ olivier, looks like somewhere inside madgraph, python path importing logic has changed somehow (or at least from the clean docker image, it's not working).
I started from docker image
sihyunjeon/terriers-madgraph-rivet-contur:v3.4.2_builtin
did yum install for some minor missing module issue
yum install -y pgreap
and then after running rivet, first error i get is
libHepMC.so.4: cannot open shared object file: No such file or directory
and if i add this ldlibpath,
libfastjet.so.0: cannot open shared object file: No such file or directory
I just presumed that it would go on and on until I add all necessary library paths in "run_rivet.sh" so I just stopped here.
What wonders me is that this did not happen earlier (at least in the release version of madgraph-rivet interface) and not sure why it's happening
@ olivier, looks like somewhere inside madgraph, python path importing logic has changed somehow (or at least from the clean docker image, it's not working).
I started from docker image terriers- madgraph- rivet-contur: v3.4.2_ builtin
sihyunjeon/
did yum install for some minor missing module issue
yum install -y pgreap
and then after running rivet, first error i get is
libHepMC.so.4: cannot open shared object file: No such file or directory
and if i add this ldlibpath,
libfastjet.so.0: cannot open shared object file: No such file or directory
I just presumed that it would go on and on until I add all necessary library paths in "run_rivet.sh" so I just stopped here.
What wonders me is that this did not happen earlier (at least in the release version of madgraph-rivet interface) and not sure why it's happening
Do you have any insights?