This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
2017:groups:tools:lhe [2017/06/12 17:27] leif.lnnblad |
2017:groups:tools:lhe [2017/06/12 17:40] leif.lnnblad |
||
---|---|---|---|
Line 6: | Line 6: | ||
It has been claimed that the shower starting/veto scales need to be more flexible. Something like that is already included in the Pythia8 which interprets eg. an attribute ''pt_start_3="42"'' in a ''<scales>'' tag as the starting scale of particle 3. These attributes are in addition to the ''mups'' defined in the current version together with ''mur'' and ''muf''. | It has been claimed that the shower starting/veto scales need to be more flexible. Something like that is already included in the Pythia8 which interprets eg. an attribute ''pt_start_3="42"'' in a ''<scales>'' tag as the starting scale of particle 3. These attributes are in addition to the ''mups'' defined in the current version together with ''mur'' and ''muf''. | ||
- | After the discussions on Saturday it was agreed that much of the complications of scale settings for individual particles must in any case be handled through specialized hooks into the parton shower, the interface of which is determined by the individual parton shower, with different implementations done by the respective matrix element providers. For this to work smoothly there is nevertheless a need to formalise the information that goes into the event file. | + | After discussions it was agreed that much of the complications of scale settings for individual particles must in any case be handled through specialized hooks into the parton shower, the interface of which is determined by the individual parton shower, with different implementations done by the respective matrix element providers. For this to work smoothly there is nevertheless a need to formalise the information that goes into the event file. |
The suggestion is to allow subtags named ''<scale>'' with the content specifying a special scale in GeV. This tag can have a number of attributes: | The suggestion is to allow subtags named ''<scale>'' with the content specifying a special scale in GeV. This tag can have a number of attributes: | ||
Line 36: | Line 36: | ||
* ''weightname'' the name of the weight variation to which this ''<xsecinfo>'' tag corresponds. If not given, the default ''XWGTUP'' weight is implied. | * ''weightname'' the name of the weight variation to which this ''<xsecinfo>'' tag corresponds. If not given, the default ''XWGTUP'' weight is implied. | ||
+ | == Documentation and sample code == | ||
+ | It was agreed that the changes proposed are significant enough to bump the version number of LHE to 4.0. It was also agreed that the LHE accord must be better documented and that there should be one well-defined place to find this documentation. | ||
+ | |||
+ | Since version 3 of the HepMC event record now comes with sample LHEF code and the option of including LHE information in the HepMC files, it is natural to keep this code up-to-date, and that documentation also is distributed with HepMC3. HepMC3 can be obtained from [[https://gitlab.cern.ch/hepmc/HepMC3]] | ||