Command "generate_events run_01" interrupted with error: Exception :

Bug #2028091 reported by Benjamin Grinstein
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MadGraph5_aMC@NLO
Fix Committed
Undecided
Unassigned

Bug Description

....
NFO: Idle: 10, Running: 8, Completed: 121 [ 1m 0s ]
INFO: Idle: 0, Running: 8, Completed: 131 [ 1m 3s ]
INFO: Idle: 0, Running: 0, Completed: 139 [ 1m 4s ]
INFO: Combining runs
sum of cpu time of last step: 8m48s
INFO: finish refine
refine 100000 --treshold=0.9
No need for second refine due to stability of cross-section
INFO: Combining Events
Command "generate_events run_01" interrupted with error:
Exception :
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in '/Users/ben/Dropbox/madgraphRuns/monotauSM-3/run_01_tag_1_debug.log'.
Please attach this file to your report.
INFO:
quit
INFO:
MG5_aMC>

Revision history for this message
Benjamin Grinstein (bgrinstein) wrote :
Revision history for this message
Benjamin Grinstein (bgrinstein) wrote :

Adding: I checked that I can reproduce this in another system. The run_card includes bias:

# Generation bias, check the wiki page below for more information: *
# 'cp3.irmp.ucl.ac.be/projects/madgraph/wiki/LOEventGenerationBias' *
#*********************************************************************
 /Users/ben/docs/papers/22-shenoy-1/ptl_bias = bias_module ! Bias type of bias, [None, ptj_bias, -custom_folder-]
 {'ptl_bias_target_ptl': 3000.0, 'ptl_bias_enhancement_power': 4.0} = bias_parameters ! Specifies the parameters of the module.
#

The error occurs only when I have both the bias *and* add a second process as in
generate p p > ta- vt~
add process p p > ta- vt~ j

If I don't add a second process (and keep the bias) or don't use bias (but keep add process) no error is generated.

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Ah yes, this is a (bad) limitation of the bias module that it only worked with a given multiplicity.

3.5.0 does offer new functionality that should go in that direction to avoid such issue.
But either the FAQ (https://answers.launchpad.net/mg5amcnlo/+faq/3326) is not up-to-date or this particular feature has not been implemented yet. (You can already look at the NLO implementation to have a feeling on how it works).

Cheers,

Olivier

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

So that feature was indeed not finalised.
This is now the case in this branch: https://github.com/mg5amcnlo/mg5amcnlo/tree/3.5.2
I'm updating the FAQ now to provide a LO example on how to do it at LO.

Thanks,

Olivier

Changed in mg5amcnlo:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.