| 168 | == Code limitation |
| 169 | |
| 170 | 1. The re-weighting assumes that the matrix-element is symmetric for identical particles. This is a limitation for process like |
| 171 | generate p p > Z j j, z > j j. In general such issues are automatically detected but in some particular case the re-weighting can fail to detect it and produce result which might be un-expected. |
| 172 | 2. The ordering of the particles in the event file is not guaranteed and information about internal propagator not save to use. Consequently process like |
| 173 | "p p > e+ e- X, X > mu+ mu-" and "p p > mu+ mu- Y, Y > e+ e-" can not be distinguish. The re-weighting will systematically crash when this happens. |
| 174 | |
| 175 | Work around for those limitations can be done by setting some special flag in the reweight_card and carefully generating the input event: |
| 176 | a. '''use_eventid True''': This allow to use the event id flag of the leshouche event file to distinguish different process. Within MG5aMC, you should use the "@" syntax in order to put such eventid in the leshouches file: for example "generate p p > e+ e- X, X > mu+ mu- @1; add process p p > mu+ mu- Y, Y > e+ e- @2" (new in 2.7.4) |
| 177 | b. '''change keep_ordering True''': This assumes that particle written in the leshouches file are in the exact same order as the one used by madgraph (looks at the Feynman diagram for the the ordering) --use with great care-- (new in 2.7.0) |
| 178 | |
| 179 | |