Merge lp:~maddevelopers/mg5amcnlo/2.2.0_last_minute_fix into lp:~maddevelopers/mg5amcnlo/2.2.0
Status: | Merged |
---|---|
Merged at revision: | 340 |
Proposed branch: | lp:~maddevelopers/mg5amcnlo/2.2.0_last_minute_fix |
Merge into: | lp:~maddevelopers/mg5amcnlo/2.2.0 |
Diff against target: |
408 lines (+103/-23) 11 files modified
Template/NLO/SubProcesses/check_poles.f (+13/-3) madgraph/iolibs/template_files/loop/check_sa.inc (+9/-2) tests/input_files/IOTestsComparison/MadLoop_output_from_the_interface/TIR_output/%ggttx_IOTest%SubProcesses%P0_gg_ttx%check_sa.f (+9/-2) tests/input_files/IOTestsComparison/long_ML_SMQCD_default/dux_mumvmxg/check_sa.f (+9/-2) tests/input_files/IOTestsComparison/long_ML_SMQCD_default/gg_wmtbx/check_sa.f (+9/-2) tests/input_files/IOTestsComparison/long_ML_SMQCD_optimized/dux_mumvmxg/check_sa.f (+9/-2) tests/input_files/IOTestsComparison/long_ML_SMQCD_optimized/gg_wmtbx/check_sa.f (+9/-2) tests/input_files/IOTestsComparison/short_ML_SMQCD_default/ddx_ttx/check_sa.f (+9/-2) tests/input_files/IOTestsComparison/short_ML_SMQCD_default/gg_ttx/check_sa.f (+9/-2) tests/input_files/IOTestsComparison/short_ML_SMQCD_optimized/ddx_ttx/check_sa.f (+9/-2) tests/input_files/IOTestsComparison/short_ML_SMQCD_optimized/gg_ttx/check_sa.f (+9/-2) |
To merge this branch: | bzr merge lp:~maddevelopers/mg5amcnlo/2.2.0_last_minute_fix |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Rikkert Frederix | Approve | ||
Olivier Mattelaer | Pending | ||
Review via email:
|
Description of the change
Both check_sa.f (for MadLoop standalone runs) and check_poles.f fail and crash for processes with external particles whose mass sum to an energy larger than the one hardcoded in these two files.
This fix solves this issue by dynamically choosing the relevant energy for the RAMBO generation based on the sum of external particle masses (for check_sa.f) and also the beam energy in the run_card (for check_poles.f). It is also desirable in check_poles.f to generate phase-space points as characteristic of the actual run as possible, because this is where the Helicity filter is setup and they must be applicable for the actual run as well.
Anyway, it is a small change but since we had decided to have 2.2.0 frozen for release of friday, I propose the merging of the quick fix so that you can reject it if you find it not safe enough.
I put you Olivier and Rik as reviewers, since you have been the one actively involved in the testing of 2.2.0 and therefore most concerned by this last minute change.
I'm okay with the merge, but this should really be the very last fix... We have to get 2.2.0 out asap. It's been way too long.
Olivier, if you approve as well, can you create the release?
Cheers,
Rik