Comment 18 for bug 1657615

Hi,

Yes using the one from the repository is ok.
If you want you can download the patched version from the following link:
http://bazaar.launchpad.net/~maddevelopers/mg5amcnlo/2.5.3/download/head:/compile.py-20110413144801-gz8gzwj02idw713s-1/compile.py

Cheers,

Olivier

PS: If you want us to include compile.py in the tar ball this is obviously not a problem.

http://bazaar.launchpad.net/~maddevelopers/mg5amcnlo/2.5.3/download/head:/compile.py-20110413144801-gz8gzwj02idw713s-1/compile.pyOn 22 Feb 2017, at 13:29, Ivan Razumov <<email address hidden><mailto:<email address hidden>>> wrote:

Hi Olivier, Valentin,

I'm currently the person maintaining the centralized installation that
Zachary is using. The tarball of MadGraph 2.5.2 that is available on LP
(https://launchpad.net/mg5amcnlo/2.0/2.5.x/+download/MG5_aMC_v2.5.2.tar.gz)
does not have compile.py script - is it safe to take one from the
repository?

Best regards,
Ivan for the GENSER team

--
You received this bug notification because you are subscribed to
MadGraph5_aMC@NLO.
https://bugs.launchpad.net/bugs/1657615

Title:
 Configuration writing to a read-only file system in 2.5.1

Status in MadGraph5_aMC@NLO:
 Fix Committed

Bug description:
 Hello,

 In 2.5.1, we can run:

 $MADGRAPH_INSTALLATION_DIR/bin/mg5_aMC

 generate p p > t t~ [QCD]
 output

 where the installation directory is on a read-only file system, but
 `pwd` is read/write (e.g. a scratch area or tmp directory). This now
 asks about which programs to install, and then attempts two write a
 configuration file back to the read-only area:

 set golem ''
 save options --auto
 save configuration file to
 /cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.5.1.atlas/x86_64-slc6-gcc47-opt/input/mg5_configuration.txt
 Command "output tt" interrupted with error:
 IOError : [Errno 30] Read-only file system:
 '/cvmfs/atlas.cern.ch/repo/sw/software/x86_64-slc6-gcc47-opt/19.2.5/sw/lcg/external/MCGenerators_lcgcmt67c/madgraph5amc/2.5.1.atlas/x86_64-slc6-gcc47-opt/input/mg5_configuration.txt'

 I believe this is because of a change in

 madgraph/interface/extended_cmd.py

 which now tries to save a configuration file via the
 write_configuration function when you try to do almost anything. I
 think, since we have the dependencies set to save locally, the correct
 behavior would be to make a locally directory and write there (or
 simply not update the config card at all).

 Thanks,
 Zach

To manage notifications about this bug go to:
https://bugs.launchpad.net/mg5amcnlo/+bug/1657615/+subscriptions