Personalized default run card

Hi,

My advise would be to use the command
set no_parton_cut
which set all the cuts to 0.
(This command needs to be used when you are asked if you want to edit the cards).

> In this way there may be cuts on many other particles whose existence I can neither guess. Is there a list of all the parameters madgraph can handle, their meaning, the set of values they can have and their best value under general conditions?

All the cuts of the run_card are done at parton-level.
Therefore for a process like
 e+ e- > mu+ mu-
setting the ptj paramater (minimum pt for a jet) is meaningless.
This was made more clear in 2.7.0 where irrelevant parameter are not present in the run_card and run_card_default anymore.

Now if you want to have displayed ALL possible pararameters of the run_card.
You can use the command
update to_full

> where does madgraph take these values from?

This is from the file madgraph/various/banner.py
Where you have the default_value defined
and the rule on how to modify those default value according to our best guess

Cheers,

Olivier

> On 31 Mar 2020, at 11:34, Francesca Acanfora <email address hidden> wrote:
>
> New question #689604 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/689604
>
> Hi!
> My Madgraph version is 2.6.7 .
> I noticed that when launching a simulation by default the run_card may have some constraints about quantities like the transverse momentum of photons or rapidity of leptons. I'm having some troubles in controlling them and I'm asking for the safest and cleanest way of controlling this source of mistake.
> I know that the run_card_default.dat is built based upon the kind of process I'm generating: if for example I ask for "e+ e- > mu+ mu-" the run card will mainly contain informations about leptons. In this way there may be cuts on many other particles whose existence I can neither guess. Is there a list of all the parameters madgraph can handle, their meaning, the set of values they can have and their best value under general conditions?
> I'd also like to ask clarifications about the way madgraph builds the run_card for each of my processes. I know that in the Template/LO/Cards there is what I assume to be a template run_card.dat . It contains (?) all the lines a run card could have but all the values are commented like:
>
> %(lpp1)s = lpp1 ! beam 1 type
>
> I guess each time I generate some process madgraph takes this card, keeps only the lines it expects would be useful (extra stuff will be added at the end as "hidden parameter") and substitutes default values, probably having some collider in mind (trivially, if I generate "p p > something" madgraph will suppose we're at LHC).
> Now: where does madgraph take these values from? Is it deprecable to change them? Can I add a new personalized list of these values? Differently stated, I'd like madgraph to make no assumptions on the collider generating and measuring the process and fake we can measure photons down to energy 0, particles all over the solid angle, ecc. Surely this will cause divergencies in the computations in many cases but I'd like to decide which parameters to constrain and how much.
>
> Thanks a lot!
> Francesca Acanfora
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.