me5_configuration.txt is on cluster mode when coming from internet generation -- fixed

[Andrew Chegwidden]

Hello,

After generating a process on the MadGraph website (http://madgraph.hep.uiuc.edu/) I no longer see the ./bin/generate_events shellscript in the "bin" folder. When I've generated previous process in the past the shell script was there once I "tar -xzf" the tarball. However, my bin folder now no longer has that script (as well as missing many other files and now includes an "internal" folder). Has something changed in the way events are generated that I'm missing

Thanks,

Andrew (Michigan State University)

[Olivier Mattelaer (olivier-mattelaer)]

Hi Andrew:

Is <email address hidden>
your account?

I unzip the madevent.tar.gz contains in PROC5 of that account
and I have the script:

-bash-3.2$ ls -l bin/
total 52
-rwxr-xr-x 1 madgraph madgraph 4033 Jul 14 2011 change_compiler.py
-rwxr-xr-x 1 madgraph madgraph 915 Feb 24 16:01 cleanall
-rwxr-xr-x 1 madgraph madgraph 3851 Mar 8 12:40 generate_events <-----------------------------------
drwxr-xr-x 3 madgraph madgraph 4096 Mar 9 12:40 internal
-rwxr-xr-x 1 madgraph madgraph 5465 Feb 24 16:01 madevent
-rwxr-xr-x 1 madgraph madgraph 2766 Feb 24 16:01 newprocess_mg5

Could you re-check?
or tell me for which PROC you found that problem?

Cheers,

Olivier

[Andrew Chegwidden (andrew-chegwidden-hep)]

Olivier,

In previous processes the "generate events" script was a bash shell script. Now it's a python script. I was using an old version of Python which is one reason it wasn't working for me. I believe I am good now.

However, as I was trouble shooting the problem I did see that in the "me5_configuration.txt" file the default running mode was set to cluster (line 60). I had to change that to run on my local machine.

Thanks for the help,

Andrew

[Olivier Mattelaer (olivier-mattelaer)]

Hi Andrew,

> In previous processes the "generate events" script was a bash shell
> script. Now it's a python script. I was using an old version of
> Python
> which is one reason it wasn't working for me. I believe I am good
> now.

Indeed python2.6 (or 2.7) are required now. most of the code move from
bash (or perl)
to python.

> However, as I was trouble shooting the problem I did see that in the
> "me5_configuration.txt" file the default running mode was set to
> cluster
> (line 60). I had to change that to run on my local machine.

Thanks to have point that to me.
This files is currently a copy of the cluster configuration which is
not that good.
I'll fix this.

Cheers and thanks,

Olivier

On Mar 9, 2012, at 3:52 PM, Andrew Chegwidden wrote:

> Olivier,
>
> In previous processes the "generate events" script was a bash shell
> script. Now it's a python script. I was using an old version of
> Python
> which is one reason it wasn't working for me. I believe I am good
> now.
>
> However, as I was trouble shooting the problem I did see that in the
> "me5_configuration.txt" file the default running mode was set to
> cluster
> (line 60). I had to change that to run on my local machine.
>
> Thanks for the help,
>
> Andrew
>
> --
> You received this bug notification because you are a member of
> MadTeam,
> which is the registrant for MadGraph5.
> https://bugs.launchpad.net/bugs/951076
>
> Title:
> ./bin/generate_events shell script
>
> Status in The MadGraph Matrix Element Generator version 5:
> New
>
> Bug description:
> Hello,
>
> After generating a process on the MadGraph website
> (http://madgraph.hep.uiuc.edu/) I no longer see the
> ./bin/generate_events shellscript in the "bin" folder. When I've
> generated previous process in the past the shell script was there
> once
> I "tar -xzf" the tarball. However, my bin folder now no longer has
> that script (as well as missing many other files and now includes an
> "internal" folder). Has something changed in the way events are
> generated that I'm missing
>
> Thanks,
>
> Andrew (Michigan State University)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/madgraph5/+bug/951076/+subscriptions

[Olivier Mattelaer (olivier-mattelaer)]

> However, as I was trouble shooting the problem I did see that in the
> "me5_configuration.txt" file the default running mode was set to
> cluster
> (line 60). I had to change that to run on my local machine.

Ok this is fixed now.
the clusters are currently updating, so this should be fixed for any new generations.

Thanks a lot,

Olivier