Comment 16 for bug 1657615

Hi,

The correct command is a

>> ./bin/compile.py SysCalc ninja collier

Or

>> ./bin/compile.py SysCalc ninja collier maddm

CutTools and Iregi will be install systematically.

> Now, the mg5_configuration.txt should be automatically set accordingly to
> the MG5_aMC steered installation done by compile.py (please Olivier
> confirm).

Yes it should be.

Cheers,

Olivier

> On 20 Feb 2017, at 20:48, Valentin Hirschi <email address hidden> wrote:
>
> On Mon, Feb 20, 2017 at 8:18 PM, Zachary Marshall <email address hidden>
> wrote:
>
>> Thanks Olivier and Valentin, this is very helpful! So far, it sounds
>> like we should do something like:
>>
>> ./bin/compile.py SysCalc ninja CutTools IREGI collier
>>
>> I just want to check that I understand two things Valentin said. You
>> recommend that we do *not* install Golem95, PJFry, and Samurai, correct?
>>
>
> Correct should you definitely not have to install Golem95, PJFry or
> Samurai.
> Also, the sub-dependency OneLOop will be handled automatically behind the
> scene, so you shouldn't have to worry about it.
>
>
>> And if we install the dependencies above will we still need to modify
>> the mg5_configuration.txt file by hand before running, or should this
>> now work properly out of the box?
>>
>
> Now, the mg5_configuration.txt should be automatically set accordingly to
> the MG5_aMC steered installation done by compile.py (please Olivier
> confirm).
>
> You will only need to fiddle with the soft links or paths in the process
> output directory *if and only if* you plan on distributing the output
> process on machines that do not have access to the tools installed during
> the compile.py scripts (all of them are placed in a HEPTools directory that
> should ideally be accessible from all machines that intend to use this
> MG5_aMC distribution).
>
> Let us know if you need further information to make your centralized
> MG5_aMC installation work.
>
>
>>
>> Thanks again,
>> Zach
>>
>> --
>> You received this bug notification because you are a bug assignee.
>> 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
>>
>
>
> --
> Valentin
>
> --
> 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