Comment 1 for bug 2062439
Revision history for this message
| Olivier Mattelaer (olivier-mattelaer) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi,
Concerning the first error (first thanks for the super detailled and cleaned report),
From 3.6.0 (in principle), the support of plugin that need to tune the launch command and define additional
input in the run_card would have a dedicated API. Soon I'm going to visit Marco, and I can try to push MadSTR to use this new API as well. This should make MadSTR compatible with the launch command from the MG5 executable and therefore could be run without loading any of the duplicated file between bin/internal and madgraph.
While the above method is likely to allow to put madgraph in PYTHONPATH but it is not clear if that it will be enough. This is not first time that we receive bug report from people that put madgraph in their PYTHONPATH (to be exact I remember one case from the docker installation of madgraph --maybe correlated to readonly issue--). And yes this is not something that we recommend (or test). Now, I'm fine to (try) to fix the issue when we face them.
For the second issue, I will assign this directly to Marco.
Olivier