Comment 1 for bug 1458404
Revision history for this message
| Valentin Hirschi (valentin-hirschi) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
Hi,
Thanks for the notification Josh, and sorry for my late reply on this. I have fixed this issue in the development version (2.3.2).
I hope it didn't delay anything since you seem to anyway be forced to package everything because of MadSpin. By the way, isn't there a way to do it in two steps, first produce the non-decayed events only from your gridpack including only the process output and then only process them via MadSpin? I think it was part of the motivation as to why the related python code was not added in the bin/internal directory of the process output (and therefore not available without the MG distribution).
Cheers,