zero cross section / Cross section not calculated in dim6Top_UFO model

Asked by Abdullah Bin Saqlain

Hi, I tried using the dim6Top_UFO model to generate p p > t z and subsequent decays, the process were generated but upon launch, it gives two errors, I am somewhat of a noob in this so I'd appreciate if you can point out where the issue is.

here is the launch sequence code where warnings were present:
INFO: Update the dependent parameter of the param_card.dat
Generating 10000 events with run name run_01
survey run_01
INFO: compile directory
compile Source Directory
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
Using random number seed offset = 21
INFO: Running Survey
Creating Jobs
Working on SubProcesses
INFO: Compiling for process 1/8.
INFO: P0_gq_tll_t_wpb_wp_lvl
WARNING: The optimizer detects that you have coupling evaluated to zero:
GC_940 GC_942 GC_944 GC_946 GC_949 GC_950 GC_951 GC_952 GC_98 GC_99 GC_100 GC_101 GC_102 GC_103 GC_104 GC_105 GC_106 GC_107 GC_108 GC_109 GC_125 GC_127 GC_129 GC_131 GC_133 GC_135 GC_137 GC_139 GC_141 GC_143 GC_145 GC_147 GC_319 GC_320 GC_321 GC_322 GC_323 GC_324 GC_325 GC_326 GC_327 GC_328 GC_329 GC_330 GC_355 GC_356 GC_357 GC_358 GC_361 GC_362 GC_363 GC_364 GC_365 GC_366 GC_369 GC_370 GC_371 GC_372 GC_373 GC_374 GC_377 GC_378 GC_379 GC_380 GC_381 GC_382 GC_385 GC_386 GC_387 GC_388 GC_389 GC_390 GC_393 GC_394 GC_395 GC_396 GC_397 GC_398 GC_401 GC_402 GC_403 GC_404 GC_405 GC_406 GC_409 GC_410 GC_411 GC_412 GC_413 GC_414 GC_417 GC_418 GC_419 GC_420 GC_421 GC_422 GC_425 GC_426 GC_427 GC_428 GC_429 GC_430 GC_433 GC_434 GC_435 GC_436 GC_437 GC_438 GC_441 GC_442 GC_443 GC_444 GC_445 GC_446 GC_449 GC_450 GC_451 GC_452 GC_453 GC_454 GC_455 GC_456 GC_457 GC_458 GC_459 GC_460 GC_461 GC_462 GC_751 GC_752 GC_753 GC_754 GC_755 GC_756 GC_757 GC_758 GC_769 GC_770 GC_771 GC_772 GC_773 GC_774 GC_775 GC_776 GC_797 GC_798 GC_799 GC_800 GC_801 GC_802 GC_803 GC_804
This will slow down the computation. Please consider using restricted model:
https://answers.launchpad.net/mg5amcnlo/+faq/2312
INFO: Compiling for process 2/8.
INFO: P0_gq_tll_t_wpb_wp_tapvl
INFO: Compiling for process 3/8.
INFO: P0_gq_ttaptam_t_wpb_wp_lvl
INFO: Compiling for process 4/8.
INFO: P0_gq_ttaptam_t_wpb_wp_tapvl
INFO: Compiling for process 5/8.
INFO: P1_gq_txll_tx_wmbx_wm_lvl
INFO: Compiling for process 6/8.
INFO: P1_gq_txll_tx_wmbx_wm_tamvl
INFO: Compiling for process 7/8.
INFO: P1_gq_txtaptam_tx_wmbx_wm_lvl
INFO: Compiling for process 8/8.
INFO: P1_gq_txtaptam_tx_wmbx_wm_tamvl
INFO: P0_gq_tll_t_wpb_wp_lvl
INFO: P0_gq_tll_t_wpb_wp_tapvl
INFO: P0_gq_ttaptam_t_wpb_wp_lvl
INFO: P0_gq_ttaptam_t_wpb_wp_tapvl
INFO: P1_gq_txll_tx_wmbx_wm_lvl
INFO: P1_gq_txll_tx_wmbx_wm_tamvl
INFO: P1_gq_txtaptam_tx_wmbx_wm_lvl
INFO: P1_gq_txtaptam_tx_wmbx_wm_tamvl
INFO: Idle: 60, Running: 8, Completed: 36 [ current time: 19h56 ]
INFO: Idle: 59, Running: 8, Completed: 37 [ 43.2s ]
INFO: Idle: 45, Running: 8, Completed: 51 [ 46.5s ]
INFO: Idle: 37, Running: 8, Completed: 59 [ 49.5s ]
INFO: Idle: 28, Running: 8, Completed: 68 [ 52.9s ]
INFO: Idle: 24, Running: 8, Completed: 72 [ 59.6s ]
INFO: Idle: 20, Running: 8, Completed: 76 [ 1m 5s ]
INFO: Idle: 13, Running: 8, Completed: 83 [ 1m 8s ]
INFO: Idle: 11, Running: 8, Completed: 85 [ 1m 16s ]
INFO: Idle: 7, Running: 8, Completed: 89 [ 1m 46s ]
INFO: Idle: 0, Running: 8, Completed: 96 [ 1m 49s ]
INFO: Idle: 0, Running: 6, Completed: 98 [ 1m 52s ]
INFO: Idle: 0, Running: 5, Completed: 99 [ 1m 56s ]
INFO: Idle: 0, Running: 1, Completed: 103 [ 2m 0s ]
INFO: Idle: 0, Running: 0, Completed: 104 [ 2m 1s ]
INFO: End survey
refine 10000
Creating Jobs
INFO: Refine results to 10000
INFO: Generating 10000.0 unweighted events.
sum of cpu time of last step: 16m14s
INFO: Effective Luminosity 1.2e+103 pb^-1
INFO: need to improve 0 channels
Survey return zero cross section.
   Typical reasons are the following:
   1) A massive s-channel particle has a width set to zero.
   2) The pdf are zero for at least one of the initial state particles
      or you are using maxjetflavor=4 for initial state b:s.
   3) The cuts are too strong.
   Please check/correct your param_card and/or your run_card.
Zero result detected: See https://cp3.irmp.ucl.ac.be/projects/madgraph/wiki/FAQ-General-14
INFO:
quit
INFO:
more information in /home/abdullah/MG5_aMC_v3_1_1/tZq_signal_dim/index.html

let me know if there is anything you require to answer it better, also can you recommend a link where I can read up on models and what do the parameters inside them represent physically?
regards

Question information

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

So the warning:
ATTENTION: default value of option mesa_glthread overridden by environment.
is related to your browser and should not have any impact on MG5aMC

The next warning
WARNING: The optimizer detects that you have coupling evaluated to zero:
indicates that you have (A LOT) of coupling that vanishes. So you use a model which is over-complicated for the computation that you do. I have attached a FAQ where you have the instructions to avoid that warning (and have faster code).
In itself, this warning is harmless and should not impact physics result.

Your third message: "zero result" is off course a question if the code just fails to integrate correctly or if the code returns the correct result. Given the number of coupling which are zero in the previous warning, the second option is clearly possible.
I would therefore suggest that you follow the FAQ and check if you still have diagram generated with that method if you do not have diagram anymore, this indeed proofs that the result is correct (and zero).

For your question about the meaning of the various coupling, I doubt that they are any documentation on this.
You can get such information by reading the UFO model information.

Cheers,

Olivier

FAQ #2312: “FR Model much slower than build-in MG model. Why and how to fix?”.

Revision history for this message
Abdullah Bin Saqlain (abdullah-saqlain) said :
#2

This particular model dim6top_LO_UFO doesn't have a param file included in it so how can i create a restrict file for this model in that case?
it does have a write_param_card.py file
P.S. when using I converted into python3 compatible as well'

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

Can you use the file write_param_card.py to create the file param_card.dat?

Cheers,

Olivier

Can you help with this problem?

Provide an answer of your own, or ask Abdullah Bin Saqlain for more information if necessary.

To post a message you must log in.