Madevent does not recognize the command "delphes"

Asked by TMartin

I am no longer able to run Delphes through Madevent on either of my Mac computers. I am not sure why.

Since I have several Delphes cards that I need to use, I run Delphes multiple times on the same Pythia events.

Here is the command I use:

./bin/madevent delphes m1_n1_m2_0_mu_0 --tag=m1_n1_m2_0_mu_0_A07 -f

That used to work prior to the combination of MG5 & MC@NLO. I ran that for months just fine.

And this is the error that I now get:

IOError : [Errno 21] Is a directory: 'delphes'
Please report this bug on https://bugs.launchpad.net/madgraph5
More information is found in '/Users/mactop/madgraph/n1n1pure/m1_n1_m2_0_mu_0_m1_n1_m2_0_mu_0_debug.log'.
Please attach this file to your report.

A few added notes:

When I run this command, it deletes my delphes_card.dat and delphes_trigger.dat files from Cards.

I am using the ATLAS cards from the Delphes directory, not old delphes_cards. So these are the latest delphes cards that are supposed to be compatible with the latest version of Delphes.

Any ideas on why this might be happening?

Here is the relevant part from the debug.log file:

Traceback (most recent call last):
  File "/Users/mactop/madgraph/n1n1pure/bin/internal/extended_cmd.py", line 872, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/Users/mactop/madgraph/n1n1pure/bin/internal/extended_cmd.py", line 865, in onecmd_orig
    return func(arg, **opt)
  File "/Users/mactop/madgraph/n1n1pure/bin/internal/extended_cmd.py", line 647, in do_import
    self.import_command_file(args[1])
  File "/Users/mactop/madgraph/n1n1pure/bin/internal/extended_cmd.py", line 1013, in import_command_file
    commandline = open(filepath).readlines()
IOError: [Errno 21] Is a directory: 'delphes'

Question information

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

Hi,

> Here is the relevant part from the debug.log file:

The header is actually very important since it includes the version number.
Are you sure that you use the latest version of the code?

This sounds as a bug which is already fixed but I might be wrong.

Cheers,

Olivier

Revision history for this message
TMartin (tmartin-4) said :
#2

#************************************************************
#* MadGraph5_aMC@NLO/MadEvent *
#* *
#* * * *
#* * * * * *
#* * * * * 5 * * * * *
#* * * * * *
#* * * *
#* *
#* *
#* VERSION 5.2.1.1 *
#* *
#* The MadGraph5_aMC@NLO Development Team - Find us at *
#* https://server06.fynu.ucl.ac.be/projects/madgraph *
#* *
#************************************************************
#* *
#* Command File for MadEvent *
#* *
#* run as ./bin/madevent.py filename *
#* *
#************************************************************

Revision history for this message
TMartin (tmartin-4) said :
#3

I reinstalled Delphes. Maybe I need to update MG. I will try that.

Revision history for this message
TMartin (tmartin-4) said :
#4

I reinstalled Delphes. Maybe I need to update MG. I will try that.

Revision history for this message
TMartin (tmartin-4) said :
#5

Apparently I can't install the update...

MG5_aMC>install update
Checking if MG5 is up-to-date... (takes up to 60s)
impossible to update: local 253 web 252

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

No you are up-to-date but the cluster is not (since he was offline at the time where the new version was released.)

So this is not the problem.

could you try to do this in two step:
./bin/madevent
and then
delphes m1_n1_m2_0_mu_0 --tag=m1_n1_m2_0_mu_0_A07 -f

Looks like you have a directory "delphes" inside your current directory and then this mess-up with the priority of interpretation of your command.

Cheers,

Olivier

Revision history for this message
TMartin (tmartin-4) said :
#7

Yes, that does work.

But I have huge runs I need to do, so I can't be doing this manually each time. Is there a way I can fix this? I don't have a delphes directory inside my process where I am running madevent. I am working off of a fresh install of MG5, where the only added folders are the processes I created. So I am not sure where I would have a directory "delphes" inside my current directory. I do have a few delphes_card_*****.tcl files in my root MG5 directory if that makes a difference?

Revision history for this message
TMartin (tmartin-4) said :
#8

Okay, I played around some more. Here is what seems to be happening...

When I run ./processname/bin/madevent delphes run --tag=tag -f it gives me that error. Likely because there is a Delphes folder in the main MG5 directory.

When I cd processname, then run ./bin/madevent delphes run --tag=tag -f then it doesn't give me the error.

I can work with this for now. I don't know if this is what is intended to happen or not, but at least I have a solution.

Thank you very much for your help!

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

Hi,

This is indeed linked to the fact that the code is confuse about the “meaning” of Delphes due to the presence of a directory of the same name.
In the next version, I explicitly check that the first argument is a file instead of checking if the path exists. This should fix your problem.

Cheers,

Olivier

On May 29, 2014, at 5:26 AM, Christopher A. George <email address hidden> wrote:

> Question #246930 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/246930
>
> Linked to bug: #1324244
> https://bugs.launchpad.net/bugs/1324244
> "issues with Delphes in MG5_aMC@NLO"
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.