rivet stops computations in madgraph

[abdul quddus]

I am running rivet installed in madgraph5_v_3_4_2. but it gives the following error. How can I fix it?

INFO: running rivet
INFO: Skipping Rivet for now, passing it to postprocessor
INFO: rivet done
INFO: storing files of previous run
INFO: Storing Pythia8 files of previous run
INFO: Done
INFO: running rivet
INFO: rivet done
Rivet analysis jobs: 1 Idle, 0 Running, 0 Done [0 second]
WARNING: program /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh 0 launch ends with non zero status: 5. Stop all computation
Rivet analysis jobs: 0 Idle, 0 Running, 1 Done [0 second]
Command "generate_events run_01" interrupted with error:
Exception : program /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh 0 launch ends with non zero status: 5. Stop all computation
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in '/home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/run_01_tag_1_debug.log'.
Please attach this file to your report.
INFO:
INFO:
quit
INFO:
quit

[Sihyun Jeon (shjeon)]

Hi,

1. Can you ensure your rivet is installed properly by doing
"generate p p > e+ e-"
and then running rivet instead of your signal sample that your are giving?
Or simply check the logs in HEPTools/rivet/ directory to see if the installation was done without any failures.

2. What are the details of your signals?
/home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_01_tag_1_banner.txt

[abdul quddus (kakakhail)]

Thanks for prompt reply. The rivet is installed in HEPTools directory. I have attached banner file for reference.

[Sihyun Jeon (shjeon)]

Can you check what happens with simple "p p > e+ e-" runs?
And also rivet_card.dat in /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Cards directory? Looks like banner does not copy the rivet info.

I can test some time this week but my naive guess is that it has to do with photon initial state ("a a >")

[abdul quddus (kakakhail)]

Thanks for your reply. I will try it.

Cheers
Abdul

On Mon, 26 Feb 2024, 10:45 am Sihyun Jeon, <email address hidden>
wrote:

> Can you check what happens with simple "p p > e+ e-" runs?
> And also rivet_card.dat in
> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Cards
> directory? Looks like banner does not copy the rivet info.
>
> I can test some time this week but my naive guess is that it has to do
> with photon initial state ("a a >")
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2054883
>
> Title:
> rivet stops computations in madgraph
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> I am running rivet installed in madgraph5_v_3_4_2. but it gives the
> following error. How can I fix it?
>
>
> INFO: running rivet
> INFO: Skipping Rivet for now, passing it to postprocessor
> INFO: rivet done
> INFO: storing files of previous run
> INFO: Storing Pythia8 files of previous run
> INFO: Done
> INFO: running rivet
> INFO: rivet done
> Rivet analysis jobs: 1 Idle, 0 Running, 0 Done [0 second]
> WARNING: program
> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
> 0 launch ends with non zero status: 5. Stop all computation
> Rivet analysis jobs: 0 Idle, 0 Running, 1 Done [0 second]
> Command "generate_events run_01" interrupted with error:
> Exception : program
> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
> 0 launch ends with non zero status: 5. Stop all computation
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in
> '/home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/run_01_tag_1_debug.log'.
> Please attach this file to your report.
> INFO:
> INFO:
> quit
> INFO:
> quit
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/2054883/+subscriptions
>
>

[Sihyun Jeon (shjeon)]

Sorry for being not so clear - can you also share what is in the rivet_card.dat? To see that which analyses you ran over in RIVET

[Sihyun Jeon (shjeon)]

i also don't have access to your model file, can't reproduce it myself

[abdul quddus (kakakhail)]

Thanks for reply. I am using 2HDM_type1 model. I have attached rivet card.

[Sihyun Jeon (shjeon)]

yes but i don't have that model file and looks like it's not in feynrules .. how can i get access that model file?

[abdul quddus (kakakhail)]

I will send all files of model so that you can check the process.
Cheers
Abdul

On Tue, 27 Feb 2024, 6:00 pm Sihyun Jeon, <email address hidden>
wrote:

> yes but i don't have that model file and looks like it's not in
> feynrules .. how can i get access that model file?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2054883
>
> Title:
> rivet stops computations in madgraph
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> I am running rivet installed in madgraph5_v_3_4_2. but it gives the
> following error. How can I fix it?
>
>
> INFO: running rivet
> INFO: Skipping Rivet for now, passing it to postprocessor
> INFO: rivet done
> INFO: storing files of previous run
> INFO: Storing Pythia8 files of previous run
> INFO: Done
> INFO: running rivet
> INFO: rivet done
> Rivet analysis jobs: 1 Idle, 0 Running, 0 Done [0 second]
> WARNING: program
> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
> 0 launch ends with non zero status: 5. Stop all computation
> Rivet analysis jobs: 0 Idle, 0 Running, 1 Done [0 second]
> Command "generate_events run_01" interrupted with error:
> Exception : program
> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
> 0 launch ends with non zero status: 5. Stop all computation
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in
> '/home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/run_01_tag_1_debug.log'.
> Please attach this file to your report.
> INFO:
> INFO:
> quit
> INFO:
> quit
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/2054883/+subscriptions
>
>

[abdul quddus (kakakhail)]

I have also tried same process with 2HDM_type2 model but same error is
shown. The model is taken from feynrule model data base you can find it
from this link.
 https://feynrules.irmp.ucl.ac.be/attachment/wiki/2HDM/2HDMtII_NLO.tar.gz

On Tue, Feb 27, 2024 at 6:03 PM Abdul Quddus <email address hidden>
wrote:

> I will send all files of model so that you can check the process.
> Cheers
> Abdul
>
> On Tue, 27 Feb 2024, 6:00 pm Sihyun Jeon, <email address hidden>
> wrote:
>
>> yes but i don't have that model file and looks like it's not in
>> feynrules .. how can i get access that model file?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/2054883
>>
>> Title:
>> rivet stops computations in madgraph
>>
>> Status in MadGraph5_aMC@NLO:
>> New
>>
>> Bug description:
>> I am running rivet installed in madgraph5_v_3_4_2. but it gives the
>> following error. How can I fix it?
>>
>>
>> INFO: running rivet
>> INFO: Skipping Rivet for now, passing it to postprocessor
>> INFO: rivet done
>> INFO: storing files of previous run
>> INFO: Storing Pythia8 files of previous run
>> INFO: Done
>> INFO: running rivet
>> INFO: rivet done
>> Rivet analysis jobs: 1 Idle, 0 Running, 0 Done [0 second]
>> WARNING: program
>> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
>> 0 launch ends with non zero status: 5. Stop all computation
>> Rivet analysis jobs: 0 Idle, 0 Running, 1 Done [0 second]
>> Command "generate_events run_01" interrupted with error:
>> Exception : program
>> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
>> 0 launch ends with non zero status: 5. Stop all computation
>> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
>> More information is found in
>> '/home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/run_01_tag_1_debug.log'.
>> Please attach this file to your report.
>> INFO:
>> INFO:
>> quit
>> INFO:
>> quit
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/mg5amcnlo/+bug/2054883/+subscriptions
>>
>>

[Sihyun Jeon (shjeon)]

So here's what I did

I took the docker image https://hub.docker.com/r/hepstore/rivet-mg5amcnlo
==> This image has madgraph+pythia installed and rivet is separately installed as well

I took the model you sent above
I initiated madgraph shell and did following

set rivet_path /usr/local/
set yoda_path /usr/local/
set auto_convert_model T
import model 2HDMtII_NLO
generate a a > h+ h-,(h+ > w+ h1, w+ > l+ vl, h1 > b b~),(h- > w- h1, w- > l- vl~, h1 > b b~)
launch
3
0
set nevents 1000
set use_syst False
set lpp1 3
set lpp2 -3
set ebeam1 1500
set ebeam2 1500
set pdlabel none
set mhc 300
0

the first two lines i did because the rivet is installed externally not within madgraph
mhc was specifically set to be the same as your's since the default value in the model file had phase space restrictions

and this works.

now the only reasons i can now think of is
a. Your rivet installation was not successful -> did you check with pp>ee run?
b. (I was going to mention the different madgraph/rivet versions but looks like everything is identical between the two : docker image and your setup)
c. Something just don't work when madgraph sets up rivet internally

So can you first check a.? I am building another docker image that installs rivet inside madgraph in parallel

[abdul quddus (kakakhail)]

Ok, I'll check it out.

Cheers
Abdul

On Tue, 27 Feb 2024, 9:56 pm Sihyun Jeon, <email address hidden>
wrote:

> So here's what I did
>
> I took the docker image https://hub.docker.com/r/hepstore/rivet-mg5amcnlo
> ==> This image has madgraph+pythia installed and rivet is separately
> installed as well
>
> I took the model you sent above
> I initiated madgraph shell and did following
>
> set rivet_path /usr/local/
> set yoda_path /usr/local/
> set auto_convert_model T
> import model 2HDMtII_NLO
> generate a a > h+ h-,(h+ > w+ h1, w+ > l+ vl, h1 > b b~),(h- > w- h1, w- >
> l- vl~, h1 > b b~)
> launch
> 3
> 0
> set nevents 1000
> set use_syst False
> set lpp1 3
> set lpp2 -3
> set ebeam1 1500
> set ebeam2 1500
> set pdlabel none
> set mhc 300
> 0
>
> the first two lines i did because the rivet is installed externally not
> within madgraph
> mhc was specifically set to be the same as your's since the default value
> in the model file had phase space restrictions
>
> and this works.
>
> now the only reasons i can now think of is
> a. Your rivet installation was not successful -> did you check with pp>ee
> run?
> b. (I was going to mention the different madgraph/rivet versions but looks
> like everything is identical between the two : docker image and your setup)
> c. Something just don't work when madgraph sets up rivet internally
>
> So can you first check a.? I am building another docker image that
> installs rivet inside madgraph in parallel
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2054883
>
> Title:
> rivet stops computations in madgraph
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> I am running rivet installed in madgraph5_v_3_4_2. but it gives the
> following error. How can I fix it?
>
>
> INFO: running rivet
> INFO: Skipping Rivet for now, passing it to postprocessor
> INFO: rivet done
> INFO: storing files of previous run
> INFO: Storing Pythia8 files of previous run
> INFO: Done
> INFO: running rivet
> INFO: rivet done
> Rivet analysis jobs: 1 Idle, 0 Running, 0 Done [0 second]
> WARNING: program
> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
> 0 launch ends with non zero status: 5. Stop all computation
> Rivet analysis jobs: 0 Idle, 0 Running, 1 Done [0 second]
> Command "generate_events run_01" interrupted with error:
> Exception : program
> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
> 0 launch ends with non zero status: 5. Stop all computation
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in
> '/home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/run_01_tag_1_debug.log'.
> Please attach this file to your report.
> INFO:
> INFO:
> quit
> INFO:
> quit
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/2054883/+subscriptions
>
>

[Sihyun Jeon (shjeon)]

@ 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

Do you have any insights?

[Sihyun Jeon (shjeon)]

@abdul can you check what is written in rivet.log under Events/run_0x directory?

[Sihyun Jeon (shjeon)]

sorry for the typo above

yum install -y procps-ng

# not pgreap

[Olivier Mattelaer (olivier-mattelaer)]

Do you still my help on this one?

Olivier

[Sihyun Jeon (shjeon)]

there will be a new release 3.5.4 soon (today, tomorrow?)
or you can use the 3.5.4 working branch in [1]

[1] https://github.com/mg5amcnlo/mg5amcnlo/tree/3.5.4

olivier and i've made a patch that was not working for me in the docker image i built above, '.so' files were not being taken for rivet execution.

it should work now (at least now it works for me), if you still fail please provide what is written in

signal_energy_1900_U/Events/run_01/rivet.log

[abdul quddus (kakakhail)]

Thanks, I'll check it out!

On Thu, 4 Apr 2024, 9:52 pm Sihyun Jeon, <email address hidden> wrote:

> there will be a new release 3.5.4 soon (today, tomorrow?)
> or you can use the 3.5.4 working branch in [1]
>
> [1] https://github.com/mg5amcnlo/mg5amcnlo/tree/3.5.4
>
> olivier and i've made a patch that was not working for me in the docker
> image i built above, '.so' files were not being taken for rivet
> execution.
>
> it should work now (at least now it works for me), if you still fail
> please provide what is written in
>
> signal_energy_1900_U/Events/run_01/rivet.log
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2054883
>
> Title:
> rivet stops computations in madgraph
>
> Status in MadGraph5_aMC@NLO:
> New
>
> Bug description:
> I am running rivet installed in madgraph5_v_3_4_2. but it gives the
> following error. How can I fix it?
>
>
> INFO: running rivet
> INFO: Skipping Rivet for now, passing it to postprocessor
> INFO: rivet done
> INFO: storing files of previous run
> INFO: Storing Pythia8 files of previous run
> INFO: Done
> INFO: running rivet
> INFO: rivet done
> Rivet analysis jobs: 1 Idle, 0 Running, 0 Done [0 second]
> WARNING: program
> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
> 0 launch ends with non zero status: 5. Stop all computation
> Rivet analysis jobs: 0 Idle, 0 Running, 1 Done [0 second]
> Command "generate_events run_01" interrupted with error:
> Exception : program
> /home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/Events/run_01/run_rivet.sh
> 0 launch ends with non zero status: 5. Stop all computation
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in
> '/home/abdul/Madgraph_v3.4.2/MG5_aMC_v3_4_2/signal_energy_1900_U/run_01_tag_1_debug.log'.
> Please attach this file to your report.
> INFO:
> INFO:
> quit
> INFO:
> quit
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mg5amcnlo/+bug/2054883/+subscriptions
>
>