Implement cut on Bjorken-x

Hi,

Did you check the following link:
https://cp3.irmp.ucl.ac.be/projects/madgraph/wiki/FAQ-General-1

Cheers,

Olivier

On 3 Jan 2019, at 14:32, Merijn van de Klundert <<email address hidden><mailto:<email address hidden>>> wrote:

New question #677294 on MadGraph5_aMC@NLO:
https://answers.launchpad.net/mg5amcnlo/+question/677294

Dear madgraph developpers,
I'm running some e+p simulations, and p+p but then one proton emits only a photon (option 0 and 2 respectively, for the incoming particle. In this I assume btw that the photon-emitting proton does not break up in the process..).

For some reaction, I'd like to study the integrated cross section, but for Bjorken-x <=0.01.
Would you be able to advice me where and how to implement this cut? If I implement it, then the cross section that would be stated after "launch" would be the number I'm looking for, correct?
I browsed around in the code a while, but ultimately I can't figure how to implement it correctly.

Any help would be greatly appreciated.
Best wishes,
Merijn

--
You received this question notification because you are an answer
contact for MadGraph5_aMC@NLO.

Dear Olivier,
many thanks, I wasn't aware of these instructions. I managed to implement a cut vetoing all events by adapting dummy_cuts.

I didn't manage afer a few attempts to define the Bjorken-x in this function and apply a cut on it, but I'm not experienced in Fortran either.
If there is an easy rule to implement this cutoff I'd be interested; otherwise I'll have to reside to implementing an additional step, i.e. analysing the .lhe output files and implementing the x-cut there.

Best wishes and many thanks for the reply,
Merijn

Hi,

One trick is to use the following common block (define in run.inc)
     double precision ebeam(2), xbk(2),q2fact(2)
    common/to_collider/ ebeam , xbk ,q2fact, lpp

and then put your cut on xbk(1), xbk(2)

Note here that you might need to generate your process with "set group_subprocess False" (you need to check if it is needed or not)
setting that parameter will switch off a lot of optimisation (i.e. slower code). One of those worries me since this is related to the symmetry between the initial state particles (that you broke due to your cut). So if you found weird result without that flag retry with that flag on.

Cheers,

Olivier