MadGraph5_aMC@NLO

v1.5.9 seems to have a new write to the MG5 directory

Asked by Zachary Marshall

Hi,

Running v1.5.4, we have no problems with our current setup of MG5 on a read-only disk. However, with MG5 1.5.9, we have a new complaint. It seems as though this is now picking up __debug__ from the system (I have to allow the possibility this is on our end, but I didn't think we changed anything there), and upon a call to debug_link_to_command (in master_interface.py) there's an attempted write to the MG5 directory and a crash.

This seems new - did I miss something that would have caused this?

For the time being, I've just removed both calls to debug_link_to_command - since they're both protected by if __debug__ I think that should have no effect on the output, right?

Thanks,
Zach

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Olivier Mattelaer
Solved:
Last query:
Last reply:
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said : 		#1

Hi Zachary,

I have a few question in order to understand why you are in debug mode. (in principle you shouldn't)
1) Did you use bazaar in order to get the version (in that case debug mode is automatic)?
2) Did you use the automatic update to pass from 1.5.4 to 1.5.9 (in that case, it might be the reason why you suddenly pass in debug mode)
3) Do you have a file bin/create_release.py?

The cleanest solution is to remove the file bin/create_release.py, which is the flag to run in debug mode.
Another solution is to run like this:
python -O ./bin/mg5
which force to be in the optimze mode.

Otherwise yes, you can remove all calls done some "if __debug__:" statement.

Cheers,

Olivier

Revision history for this message
Zachary Marshall (zach-marshall) said : 		#2

Hi Olivier,

Ah - ok, #1 was exactly it. What's the difference between using bazaar and downloading then, other than this? And how do I turn off the debug mode that's set when downloading via bazaar? Same bin/create_release.py file ?

Thanks,
Zach

Revision history for this message
Best Olivier Mattelaer (olivier-mattelaer) said : 		#3

Hi Zachary,

Except that point none.
To be precise the documentation (apydoc directory) is empty in the bzr version but is present with the download one.

And, yes you just have to remove the file bin/create_release.py .

Cheers,

Olivier

Revision history for this message
Zachary Marshall (zach-marshall) said : 		#4

Thanks Olivier!