Version 1.4.1 is a bugfix release of Sherpa which does not contain any new features compared to 1.4.0. Please see the Changelog below for a complete summary of the changes. If you would like to be informed about patches and newer releases, please subscribe to our announcement mailing list.
The Sherpa package can be downloaded here:
In can also be accessed via svn through
A Manual is included in the Manual/ directory of the tarball. It is available in the HTML and INFO format and provides extensive documentation of all parameters. It can also be found online.
The main reference describing the physics of Sherpa is JHEP02 (2009) 007. Please cite this publication if you have used Sherpa for your studies. Additionally, each run will produce a file called Sherpa_References.tex which contains information about the modules used in this run and the corresponding publications which should be referred. If in doubt, please seek the advice of the Sherpa authors.
You can find a large collection of example setups for using SHERPA in various different colliders/processes in the Examples/ directory of the tarball. They are also described in the manual.
Patches/known problems/known bugs/FAQs
All known problems/questions and their solutions can be found on our issue tracker (please log in with username "user" and password "sherpa"). If you encounter any problem while installing or running Sherpa, please open a new issue in the tracker.
- Vertex offsets of hadron decays were missing in events with multiple "partonic" hadron decays. This becomes relevant when a detector simulation sensitive to vertex offsets is applied to the events and can impair the b-tagging performance.
- Fixes for build failures for gcc 4.7, and in the Manual subdirectory, and with svn.make (cf. #228).
- Bugfix for symmetry factor, cf. #172
- Restriction of t-channels can be optionally limited to EW t-channels only. This is necessary for using this restriction in ME+PS merged samples. Nothing changes for the default (no t-channel restriction).
- Consistency in the non-default EW_SCHEME's. Again, no changes for the default setup (EW_SCHEME=0).