MadGraph5_aMC@NLO

Interruption when generating gg>zz>l-l+l-l+[noborn=QCD]/h.

Asked by Mingxuan Zhang

Hi experts,

I want to generate g g > z z > l- l+ l- l+[noborn=QCD] /h, but I got some problems. When I set 10 or 50 events in the run_card.dat, it can run successfully. But when changing the event number larger like 100, 1000 and so on or generating gridpack, interruptions will happen. And below is the error log.

INFO: Update the dependent parameter of the param_card.dat
Generating 100 events with run name run_05
survey run_05
INFO: compile directory
Error: no DISPLAY environment variable specified
compile Source Directory
Using random number seed offset = 54
INFO: Running Survey
Creating Jobs
Working on SubProcesses
INFO: P0_gg_llll
INFO: Idle: 5, Running: 10, Completed: 0 [ current time: 17h52 ]
INFO: Idle: 4, Running: 10, Completed: 1 [ 36.3s ]
INFO: Idle: 3, Running: 10, Completed: 2 [ 45.5s ]
INFO: Idle: 2, Running: 10, Completed: 4 [ 1m 24s ]
INFO: Idle: 1, Running: 10, Completed: 5 [ 1m 29s ]
INFO: Survey finished for P0_gg_llll/G3.04 [0 cross]
INFO: Idle: 0, Running: 8, Completed: 8 [ 1m 32s ]
INFO: Idle: 1, Running: 6, Completed: 10 [ 1m 37s ]
INFO: P0_gg_llll/G1 is at 0.00011 +- 6.18e-05 pb. Now submitting iteration #2.
INFO: Idle: 1, Running: 8, Completed: 12 [ 1m 40s ]
INFO: P0_gg_llll/G3.05 is at 3.85e-08 +- 1.16e-08 pb. Now submitting iteration #2.
INFO: Idle: 0, Running: 10, Completed: 14 [ 1m 57s ]
INFO: Idle: 1, Running: 9, Completed: 15 [ 2m 7s ]
INFO: P0_gg_llll/G3.07 is at 0.00173 +- 0.000215 pb. Now submitting iteration #2.
INFO: Idle: 1, Running: 10, Completed: 17 [ 2m 13s ]
INFO: Idle: 0, Running: 10, Completed: 18 [ 3m 9s ]
INFO: Idle: 0, Running: 9, Completed: 19 [ 3m 16s ]
INFO: Idle: 0, Running: 7, Completed: 21 [ 3m 25s ]
INFO: P0_gg_llll/G1 is at 0.000157 +- 2.23e-05 pb. Now submitting iteration #3.
INFO: P0_gg_llll/G3.08 is at 0.00013 +- 8.46e-05 pb. Now submitting iteration #2.
INFO: Idle: 0, Running: 10, Completed: 26 [ 3m 28s ]
INFO: Idle: 1, Running: 9, Completed: 27 [ 3m 32s ]
INFO: P0_gg_llll/G3.05 is at 3.42e-08 +- 9.88e-10 pb. Now submitting iteration #3.
INFO: Idle: 1, Running: 10, Completed: 29 [ 3m 40s ]
INFO: Idle: 0, Running: 10, Completed: 30 [ 3m 49s ]
INFO: Idle: 1, Running: 9, Completed: 31 [ 4m 39s ]
INFO: P0_gg_llll/G3.07 is at 0.00199 +- 0.00024 pb. Now submitting iteration #3.
INFO: Idle: 1, Running: 10, Completed: 33 [ 4m 49s ]
INFO: Idle: 1, Running: 9, Completed: 35 [ 4m 53s ]
INFO: P0_gg_llll/G3.08 is at 9.84e-05 +- 2.97e-05 pb. Now submitting iteration #3.
INFO: Idle: 1, Running: 10, Completed: 37 [ 6m 42s ]
INFO: Idle: 0, Running: 10, Completed: 38 [ 6m 48s ]
INFO: Idle: 1, Running: 9, Completed: 39 [ 6m 56s ]
INFO: P0_gg_llll/G3.05 is at 3.92e-08 +- 2.08e-09 pb. Now submitting iteration #4.
INFO: Idle: 1, Running: 10, Completed: 41 [ 7m 14s ]
INFO: Idle: 1, Running: 9, Completed: 43 [ 7m 18s ]
INFO: P0_gg_llll/G1 is at 0.000229 +- 8.56e-05 pb. Now submitting iteration #4.
INFO: Idle: 1, Running: 10, Completed: 45 [ 7m 44s ]
INFO: Idle: 0, Running: 9, Completed: 47 [ 7m 54s ]
INFO: P0_gg_llll/G3.07 is at 0.00223 +- 0.000224 pb. Now submitting iteration #4.
INFO: Idle: 0, Running: 10, Completed: 50 [ 9m 32s ]
INFO: Idle: 1, Running: 9, Completed: 51 [ 9m 38s ]
INFO: P0_gg_llll/G3.08 is at 5e-05 +- 1.98e-05 pb. Now submitting iteration #4.
INFO: Idle: 1, Running: 10, Completed: 53 [ 13m 16s ]
INFO: Idle: 0, Running: 10, Completed: 54 [ 13m 38s ]
INFO: Idle: 1, Running: 9, Completed: 55 [ 13m 42s ]
INFO: P0_gg_llll/G3.05 is at 4.01e-08 +- 1.16e-09 pb. Now submitting iteration #5.
INFO: Idle: 1, Running: 10, Completed: 57 [ 14m 3s ]
INFO: Idle: 0, Running: 10, Completed: 58 [ 14m 7s ]
INFO: Idle: 0, Running: 9, Completed: 59 [ 14m 12s ]
INFO: Idle: 0, Running: 8, Completed: 60 [ 14m 21s ]
INFO: Idle: 1, Running: 7, Completed: 61 [ 14m 27s ]
INFO: P0_gg_llll/G1 is at 0.000352 +- 0.000153 pb. Now submitting iteration #5.
INFO: Idle: 0, Running: 9, Completed: 63 [ 15m 9s ]
INFO: Idle: 1, Running: 8, Completed: 64 [ 15m 52s ]
INFO: P0_gg_llll/G3.07 is at 0.00239 +- 0.000132 pb. Now submitting iteration #5.
INFO: Idle: 1, Running: 10, Completed: 65 [ 15m 58s ]
INFO: Idle: 0, Running: 10, Completed: 66 [ 18m 53s ]
INFO: Idle: 1, Running: 9, Completed: 67 [ 19m 12s ]
INFO: P0_gg_llll/G3.08 is at 6.17e-05 +- 2.85e-05 pb. Now submitting iteration #5.
INFO: Idle: 1, Running: 10, Completed: 69 [ 26m 24s ]
INFO: Idle: 0, Running: 10, Completed: 70 [ 26m 35s ]
INFO: Idle: 1, Running: 9, Completed: 71 [ 26m 50s ]
INFO: Survey finished for P0_gg_llll/G3.05 at 4.09e-08 +- 7.48e-10 pb
INFO: Idle: 0, Running: 8, Completed: 73 [ 27m 49s ]
INFO: Idle: 0, Running: 7, Completed: 74 [ 27m 54s ]
INFO: Survey finished for P0_gg_llll/G1 at 0.00047 +- 0.000107 pb
INFO: Idle: 0, Running: 5, Completed: 77 [ 28m 10s ]
INFO: Idle: 0, Running: 3, Completed: 79 [ 30m 21s ]
INFO: Idle: 1, Running: 2, Completed: 80 [ 30m 57s ]
INFO: Survey finished for P0_gg_llll/G3.07 at 0.00244 +- 8.48e-05 pb
INFO: Idle: 0, Running: 1, Completed: 82 [ 37m 18s ]
INFO: Idle: 1, Running: 0, Completed: 83 [ 37m 37s ]
INFO: Survey finished for P0_gg_llll/G3.08 at 7.58e-05 +- 2.89e-05 pb
INFO: Idle: 0, Running: 0, Completed: 84 [ 37m 58s ]
INFO: Idle: 0, Running: 0, Completed: 84 [ 37m 58s ]
INFO: End survey
refine 100
Creating Jobs
INFO: Refine results to 100
INFO: Generating 100.0 unweighted events.
sum of cpu time of last step: 0 second
INFO: Effective Luminosity 38143.43268251666 pb^-1
INFO: need to improve 3 channels
- Current estimate of cross-section: 0.002988718948 +- 0.00013935082355536952
INFO: Idle: 1, Running: 10, Completed: 0 [ current time: 18h30 ]
INFO: Idle: 0, Running: 10, Completed: 1 [ 5m 10s ]
INFO: P0_gg_llll/G3.08 is at 3/4 (80%) event. Resubmit 1 job at iteration 1.
INFO: Idle: 0, Running: 8, Completed: 5 [ 5m 32s ]
INFO: Idle: 1, Running: 7, Completed: 6 [ 5m 38s ]
INFO: P0_gg_llll/G3.07 is at 32/84 (39%) event. Resubmit 2 job at iteration 1.
INFO: Idle: 0, Running: 8, Completed: 8 [ 6m 5s ]
INFO: Idle: 0, Running: 7, Completed: 9 [ 6m 8s ]
INFO: Idle: 1, Running: 3, Completed: 13 [ 10m 21s ]
WARNING: float division by zero
Terminated
Start waiting for update. (more info in debug mode)
INFO: Idle: 0, Running: 2, Completed: 17 [ 15m 21s ]
WARNING: [Fail 5 times]
 [Errno 2] No such file or directory: '/eos/home-m/mingxuan/HZ_LZ_L/MG5_aMC_v3_5_3/test/SubProcesses/P0_gg_llll/G3.07_1/results.dat'
WARNING: [Fail 5 times]
 [Errno 2] No such file or directory: '/eos/home-m/mingxuan/HZ_LZ_L/MG5_aMC_v3_5_3/test/SubProcesses/P0_gg_llll/G1_6/results.dat'
INFO: Idle: 0, Running: 0, Completed: 19 [ 15m 21s ]
[Fail 5 times]
 [Errno 2] No such file or directory: '/eos/home-m/mingxuan/HZ_LZ_L/MG5_aMC_v3_5_3/test/SubProcesses/P0_gg_llll/G1_6/results.dat'
Cluster Error detected. Do you want to clean the queue? ("c"=continue the run anyway) [y, n, c][60s to answer]
>
use y
Command "generate_events " interrupted with error:
FileNotFoundError : [Fail 5 times]
  [Errno 2] No such file or directory: '/eos/home-m/mingxuan/HZ_LZ_L/MG5_aMC_v3_5_3/test/SubProcesses/P0_gg_llll/G1_6/results.dat'
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in '/eos/home-m/mingxuan/HZ_LZ_L/MG5_aMC_v3_5_3/test/run_05_tag_1_debug.log'.
Please attach this file to your report.
quit
INFO:

How can I solve that and run successfully? I have stuck in this for a long time. I will appreciate it if you could give any help. Thanks a lot!

Best,
Mingxuan

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Olivier Mattelaer
Solved:
Last query:
Last reply:
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said : 		#1

Hi,

This process should present an integrable singularity making it impossible to generate events without cuts.
(Of course if you ask a small amount of events, you can get lucky).
I know that in the case of g g > z z, one need to put a pt cut on the Z (1GeV is used in various literature). For the 4 lepton case, I do not know which cut is enough. So which cut did you use to remove such singularity?

Cheers,

Olivier

Revision history for this message
Mingxuan Zhang (mingxuanzh) said : 		#2

Hi,

Thanks a lot for your immediate response. We don't add any cut on Z bosons' pt. If we want to add this cut, we should add it in run_card? Or somewhere else?

When I saw your message, I tried to add ptz cut in run_card in the part below like this:
#*********************************************************************
# Minimum and maximum pt's (for max, -1 means no cut) *
#*********************************************************************
 1.0 = ptz !minimum pt for the z

But I got another error. So I want to ask where should I add this cut. Thanks a lot!

Best,
Mingxuan

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

Hi,

We do not have a default cut for intermediate particle and such cut are difficult to implement because intermediate particle are not unique.
If you look at your diagram:
Diagram #2 is a triangle loop which correspond to g g > z (and then the Z decay into 4 particle)
so here the four momenta of the Z is the sum of the four lepton
Diagram #5 is a box corresponding to g g > z a
so here the four momenta of the Z is the sum of the two first lepton
and Diagram #6 is a box corresponding to g g > a z
so here the four momenta of the Z is the sum of the two last lepton

So here you have three diagram where applying the cut on the "Z" particle will lead to three different cut which makes no sense.

This make me realize that you use " > z z > " which is a syntax that we should ban in practise (I will try to introduce this ban in 3.6.0).
The syntax "> A >"
has the meaning to ask AT LEAST ONE s-channel propagator of the particle A
The syntax "> A B >"
has the meaning to ask AT LEAST ONE s-channel propagator of the particle A and at least one s-channel of the particle B.
The syntax "> A A >" does NOT have a special meaning is back to to the previous one "> A B >" meaning:
 to ask AT LEAST ONE s-channel propagator of the particle A and at least one s-channel of the particle A.
(so we just check the same condition twice). It does not ask for at least TWO but twice for at least one (so "> A A >" has the same meaning as "> A >") .

Which might be another issue for your process.

To come back on the issue of the cut, since we do not have such type of cut by default, you will need to implement it yourself (check our FAQ for instructions).

Cheers,

Olivier

Revision history for this message
Mingxuan Zhang (mingxuanzh) said : 		#4

Hi Olivier,

Thanks a lot for your help, and I have gotten what you said.

Actually, we want to generate a process in which the initial particles are two gluons, the intermediate particles are two on-shell z bosons and each z boson will decay into a pair of leptons. At first, we tried g g > z z[noborn=QCD], and wrote decay info in the madspin card, but it didn't work. I searched on the launchpad and found somebody said that madspin can't decay loop-induced process. Then I tried g g > z z > l- l+ l- l+[noborn=QCD], and like your instructions say, it can't achieve AT LEAST TWO intermediate z bosons. And we want to keep the spin info of the final four leptons, so we can't let Pythia do the decay job.

I want to ask how can I generate the process I describe above? I will appreciate it if you give any help. Thanks a lot for your reply!

Best,
Mingxuan

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

I would then use

generate g g > z > l+ l+ l- l- / a h [noborn=QCD]

and the implement a custom cut to avoid the integrable singularity.

Cheers,

Olivier

Revision history for this message
Mingxuan Zhang (mingxuanzh) said : 		#6

Thanks a lot for your quick response!

If I need the Z bosons are both on-shell, what should I do? Thanks again for your help!

Best,
Mingxuan

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

If you generate
e+ e- mu+ mu-
then you can use
 119 0.0 = mmll ! min invariant mass of l+l- (same flavour) lepton pair
 120 -1.0 = mmllmax ! max invariant mass of l+l- (same flavour) lepton pair

but if you also include (and so far you do)
e+ e- e+ e-
than that cut will apply four invariant mass cut and not two...
So in that case you will also need to have a custom cut.

Cheers,

Olivier

Revision history for this message
Mingxuan Zhang (mingxuanzh) said : 		#8

Hi Olivier,

Sincere thanks for your help, and it helps me a lot!

Best wishes,
Mingxuan

Revision history for this message
Mingxuan Zhang (mingxuanzh) said : 		#9

Thanks Olivier Mattelaer, that solved my question.