> 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
>
>
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?) /github. com/mg5amcnlo/ mg5amcnlo/ tree/3. 5.4 energy_ 1900_U/ Events/ run_01/ rivet.log /bugs.launchpad .net/bugs/ 2054883 Madgraph_ v3.4.2/ MG5_aMC_ v3_4_2/ signal_ energy_ 1900_U/ Events/ run_01/ run_rivet. sh Madgraph_ v3.4.2/ MG5_aMC_ v3_4_2/ signal_ energy_ 1900_U/ Events/ run_01/ run_rivet. sh /bugs.launchpad .net/mg5amcnlo abdul/Madgraph_ v3.4.2/ MG5_aMC_ v3_4_2/ signal_ energy_ 1900_U/ run_01_ tag_1_debug. log'. /bugs.launchpad .net/mg5amcnlo/ +bug/2054883/ +subscriptions
> or you can use the 3.5.4 working branch in [1]
>
> [1] https:/
>
> 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_
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> 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/
> 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/
> 0 launch ends with non zero status: 5. Stop all computation
> Please report this bug on https:/
> More information is found in
> '/home/
> Please attach this file to your report.
> INFO:
> INFO:
> quit
> INFO:
> quit
>
> To manage notifications about this bug go to:
> https:/
>
>