ptheavy cut from above

Such a cut can easily be handled by modifying directly the file cuts.f.
But yes, we could think of adding it to the run_card.dat.

Notice that if your goal is to "artificially" populate the tails, you can
have a look at my implementation of a "biasing" technique for LO MG5_aMC
simulations here:

https://cp3.irmp.ucl.ac.be/projects/madgraph/wiki/LOEventGenerationBias

On Fri, Jul 28, 2017 at 11:34 AM, Roberto Franceschini <
<email address hidden>> wrote:

> New question #654030 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/654030
>
> Hello,
> I know it has been pointed out already, but I wanted to add my two cents
> in favour of having a ptheavymax cut that limits from above the pt of heavy
> particles. This is very useful to generate events in the tails accurately
> by doing one range of ptheavy at a time.
> Also for how the run_card.dat looks like now, it is the only "max" cut
> missing.
> Cheers,
> Roberto
>
>
> # Minimum and maximum pt's (for max, -1 means no cut) *
> #*********************************************************************
> 20.0 = ptj ! minimum pt for the jets
> 0.0 = ptb ! minimum pt for the b
> 10.0 = pta ! minimum pt for the photons
> 10.0 = ptl ! minimum pt for the charged leptons
> 0.0 = misset ! minimum missing Et (sum of neutrino's momenta)
> 0.0001 = ptheavy ! minimum pt for one heavy final state
> -1.0 = ptjmax ! maximum pt for the jets
> -1.0 = ptbmax ! maximum pt for the b
> -1.0 = ptamax ! maximum pt for the photons
> -1.0 = ptlmax ! maximum pt for the charged leptons
> -1.0 = missetmax ! maximum missing Et (sum of neutrino's momenta)
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
>

--
Valentin