MadGraph5_aMC@NLO

proc_card_mg5.dat does not have all info

Asked by Rikkert Frederix

Ciao guys,

I understand that when you 'generate' a process you clean the history of what is written in the ./Cards/proc_card_mg5.dat, because if someone wants to re-generate the current process, you don't want to re-generate all the processes that the user generated so far. However, a lot of value information is lost, like the definition of the multi-particles, if they were set before the final 'generate'. Maybe this information could be kept in the ./Cards/proc_card_mg5.dat ?

Cheers,
Rik

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Johan Alwall
Solved:
Last query:
Last reply:
Revision history for this message
Johan Alwall (johan-alwall) said : 		#1

Hello Rikkert,

We are (supposedly) only removing information that can have no impact on the generation (such as model imports before this model import, generate before this generate, etc.). In particular, multiparticle definitions are not supposed to be removed. Can you give us an example where this happens?

Thanks,
Johan

Revision history for this message
Rikkert Frederix (frederix) said : 		#2

the commands:

define p = u u~
generate p p > e+ e-
generate p p > e+ e-
output
quit

gives the following Cards/proc_card_mg5:

#************************************************************
#* MadGraph 5 *
#* *
#* * * *
#* * * * * *
#* * * * * 5 * * * * *
#* * * * * *
#* * * *
#* *
#* *
#* VERSION 1.4.8.4 2012-08-29 *
#* *
#* The MadGraph Development Team - Please visit us at *
#* https://server06.fynu.ucl.ac.be/projects/madgraph *
#* *
#************************************************************
#* *
#* Command File for MadGraph 5 *
#* *
#* run as ./bin/mg5 filename *
#* *
#************************************************************

import model sm
generate p p > e+ e-
output

Revision history for this message
Best Johan Alwall (johan-alwall) said : 		#3

Ah - indeed. We will look at this in v. 1.5.0.

Thanks a lot!
Johan

Revision history for this message
Rikkert Frederix (frederix) said : 		#4

Thanks Johan Alwall, that solved my question.

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

Hi Rik,

I just solved this problem in 1.5.0.
So if you merge the last modif of 1.5.0 this should be fix.

Cheers,

Olivier

PS: Johan and I discussed a better way to doing it but for the moment this should be fine.