MadGraph5_aMC@NLO

madspin broken with option "set max_running_process 1"

Asked by Meng Lu

Dear MG expert,

When testing the "p p > t t~" using MG331 with madspin, we found the generation getting stuck if using "set max_running_process 1" option, and it run smoothly if without such option. Since when gridpack generation and event production with gridpack sometimes require "set max_running_process N" when N will be a small number, we would like to know why the generation with "set max_running_process 1" break.

Cheers, Meng

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Olivier Mattelaer
Solved:
Last query:
Last reply:
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said : 		#1

Sorry for the delay, my email went down and I did not realize it.

Do you know if you have the same for 2.9.9 (don't worry if you do not know I will test both)?

Cheers,

Olivier

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said : 		#2

Ok, I do confirm the issue within our LTS version, looks like a buffering issue preventing the code to continue.

Revision history for this message
Best Olivier Mattelaer (olivier-mattelaer) said : 		#3

Ok, the fix is here:

https://bazaar.launchpad.net/~maddevelopers/mg5amcnlo/LTS_dev/revision/400
This will be part of 2.9.10 (the next bug fixing release of our LTS) and will likely be part of the official release of 3.4.0.
(The release candidate for 3.4.0 does not have it)
Both version should be released whitin a couple of weeks.

Thanks,

Olivier

Revision history for this message
Meng Lu (meng-lu) said : 		#4

Thanks Olivier Mattelaer, that solved my question.

Revision history for this message
Meng Lu (meng-lu) said : 		#5

Hi Olivier, no problem. The issue is gone after your fix, thanks very much.