cross-section bias for gridpack in read-only

Bug #1884085 reported by Olivier Mattelaer on 2020-06-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Dear Olivier,

We are testing on the "readonly" gridpack mode to enable multithreading for event generation, as introduced in [1].
It seems the LHE cross-section given by this approach is abnormal for some multi-jet process. The discrepancy gets even larger as the jet number increases.

We prepare a W+3jet gridpack to reproduce this issue. The test is under v2.7.2 with a patch applied [2] to fix a "readonly" mode bug. The gridpack is uploaded to [3] as a reference.
For the "normal" mode, we use the command "./run 200 1 1".
For the "readonly" mode, we set the madevent folder to readonly, then do "../<folder>/run 200 1 1" in another empty directory.

The LHE cross-section given by two methods are: 1190.47 +/- 16.64 (normal) and 726.65 +/- 13.15 (readonly).
By reading the cross-section in "crossx.html", we get 1190.3 ± 2.76 fb . Hence the "readonly" result is abnormal.

Would you mind looking into this issue? Thank you very much for your help.

Best regards,


Changed in mg5amcnlo:
status: New → Confirmed

This sounds an issue with the symmetry factor of a given process.
In normal mode P1_gg_ttxg/G5 returns 132pb
and in readonly P1_gg_ttxg/G5 returns 66.76pb
so this sounds a factor 2 issue

also the readonly mode seems to use non fix grid when running compare to the normal gridpack who does not change the grid anymore (which is likely better). Will have to change that as well.

More news later.



Thanks a lot for this report, it can be even worse than I thought originally.
(I thought that only the cross-section was affected but not the shape of the events, but I do think that both are actually impacted.

Thanks a lot for checking this features of MadGraph.
I believe this is an important feature that was left on the side for too long.
It is really nice that you spend the time to find such issues and that you force me to look back at this.



Changed in mg5amcnlo:
importance: Undecided → Critical
status: Confirmed → Fix Committed
Congqiao Li (colizz) wrote :

Hi Olivier,

Thank you very much for fixing this issue!


Changed in mg5amcnlo:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers