CutTools compilation failure when using "set output_dependencies internal" in 2.3beta
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MadGraph5_aMC@NLO |
Fix Released
|
Undecided
|
Valentin Hirschi |
Bug Description
When generating an NLO process using "set output_dependencies internal", the compilation of CutTools fails as below. (Since we anyways package the base madgraph directory in our gridpacks already because of madspin, it's not clear that we strictly need output_dependencies internal, but in any case that's how we were doing things in 2.2.2 and it was working there)
>INFO: Starting run
INFO: Compiling the code
run_card missed argument dynamical_
run_card missed argument iappl. Takes default: 0
INFO: Using LHAPDF v6.1.5 interface for PDFs
INFO: Compiling source...
INFO: ...done, continuing with P* directories
INFO: Compiling StdHEP (can take a couple of minutes) ...
INFO: ...done.
INFO: Compiling CutTools (can take a couple of minutes) ...
INFO: ...done.
Error detected in "launch -n pilotrun"
write debug file /afs/cern.
If you need help with this issue please contact us on https:/
aMCatNLOError : CutTools compilation failed.
quit
INFO:
-bash-4.1$ cat /afs/cern.
#******
#* MadGraph5_aMC@NLO *
#* *
#* * * *
#* * * * * *
#* * * * * 5 * * * * *
#* * * * * *
#* * * *
#* *
#* *
#* VERSION 5.2.3.0.beta *
#* *
#* The MadGraph5_aMC@NLO Development Team - Find us at *
#* https:/
#* and *
#* http://
#* *
#******
#* *
#* Command File for aMCatNLO *
#* *
#* run as ./bin/aMCatNLO.py filename *
#* *
#******
launch -n pilotrun
Traceback (most recent call last):
File "/afs/cern.
return self.onecmd_
File "/afs/cern.
return func(arg, **opt)
File "/afs/cern.
self.
File "/afs/cern.
raise aMCatNLOError(
aMCatNLOError: CutTools compilation failed.
Value of current Options:
output_
cluster_
automatic_
exrootana
Changed in mg5amcnlo: | |
assignee: | nobody → Valentin Hirschi (valentin-hirschi) |
Changed in mg5amcnlo: | |
status: | Fix Committed → Fix Released |
Hi,
Thanks for the notification Josh, and sorry for my late reply on this. I have fixed this issue in the development version (2.3.2).
I hope it didn't delay anything since you seem to anyway be forced to package everything because of MadSpin. By the way, isn't there a way to do it in two steps, first produce the non-decayed events only from your gridpack including only the process output and then only process them via MadSpin? I think it was part of the motivation as to why the related python code was not added in the bin/internal directory of the process output (and therefore not available without the MG distribution).
Cheers,