MadGraph5_aMC@NLO 2.4.x "reweighting"

This branch will include
- correct NLO reweighting
- Interface to Ninja reduction tools for faster loop evaluation
- New Syntax for tree-level processes
- possibility to ask more than one PDF set for the systematics re-weighting

Milestone information

Project:
MadGraph5_aMC@NLO
Series:
lts
Version:
2.4.x
Code name:
reweighting
Released:
 
Registrant:
Olivier Mattelaer
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon MG5_aMC_v2.4.3.tar.gz (md5) MG5_aMC_v2.4.3 8,617
last downloaded 67 weeks ago
Total downloads: 8,617

Release notes 

2.4.0 (12/06/16)
        OM: Allowing the proper NLO reweighting for NLO sample
        RF: For NLO processes allow for multiple PDF and scales reweighting, directy by inputting lists
            in the run_card.dat.
        VH: Interfaced MadLoop to Samurai and Ninja (the latter is now the default)
        HS: Turn IREGI to off by default
        MZ: new NLO generation mode. It is more efficient from the memory and CPU point of
            view, in particular for high-multiplicity processes.
            Many thanks to Josh Bendavid for his fundamental contribution for this.
            The mode can be enabled with
            > set low_mem_multicore_nlo_generation True
            before generating the process.
        OM: Adding the possibility to use new syntax for tree-level processes:
            QED==2 and QCD>2: The first allows to select exactly a power of the coupling (at amplitude level
            While the second ask for a minimum value.
        RF: In the PDF uncertainty for fixed-order NLO runs, variations of alphaS were not included.
        OM: In MLM matching, fix a bug where the alpha_s reweighting was not fully applied on some events.
            (This was leading to effects smaller than the theoretical uncertainty)
        OM: Fixing the problem of using lhapdf6 on Mac
        MZ: Faster interface for LHAPDF6
        OM: Add support of epsilon_ijk in MadSpin
        OM: Fix multiple problem with multiparticles in MadSpin
        OM: Improve spinmode=None in MadSpin
        OM: Update the TopEffTh model
        MZ: Fix problem with slurm cluster
        OM: Improve scan functionalities
        PT: New way of handling Pythia8 decays
        RF: Fixed a bug that resulted in wrong event weights for NLO processes when requiring
            a very small number of events (introduced in 2.3.3)
        OM: Allow to keep the reweight information in the final lhe file for future computation
        MZ: updated FJcore to version 3.1.3 (was 3.0.5)

2.4.1 (09/06/16)
        OM: Fix a bug in fix target experiment with PDF on the particle at rest.
            The cross-section was correct but the z-boost was not performed correctly. (thanks D. Curtin)
        OM: Fix various bug in MadSpin
        OM: Fix some bug in MLM merging, where chcluster was forced to True (introduced in 2.2.0)
        OM: Allow to specify a path for a custom directory where to look for model via the environment
            variable PYTHONPATH. Note this used AFTER the standard ./models directory

2.4.2 (10/06/16)
        OM: fix a compilation problem for non standard gfortran system
        OM: reduce the need of lhapdf for standard LO run. (was making some run to test due to missing dependencies)

Changelog 

This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.