MadGraph5_aMC@NLO

The event file has not been created

Asked by Hong W

Dear aMC@NLO team
I'm having troubles generating events with MG5_aMC_v2_3_2 and need your help.
The program stops when I try to record the events .
you may need these:
**************************error message:**************************************
...
INFO: Idle: 0, Running: 1, Completed: 15 [ 7h 29m ]
INFO: Idle: 0, Running: 0, Completed: 16 [ 7h 47m ]
INFO: Collecting events
At line 759 of file handling_lhe_events.f (unit = 11, file = 'P0_ub_htd/GF1/events.lhe')
Fortran runtime error: End of file
Error detected in "launch auto "
write debug file /home/program/MG5_aMC_v2_3_2/myprocess/thj-nlo/run_04_debug.log
If you need help with this issue please contact us on https://answers.launchpad.net/madgraph5
aMCatNLOError : An error occurred during event generation. The event file has not been created. Check collect_events.log
quit

************************run_04_debug.log ***********************************

launch auto
Traceback (most recent call last):
  File "/home/program/MG5_aMC_v2_3_2/madgraph/interface/extended_cmd.py", line 889, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/home/program/MG5_aMC_v2_3_2/madgraph/interface/extended_cmd.py", line 882, in onecmd_orig
    return func(arg, **opt)
  File "/home/program/MG5_aMC_v2_3_2/madgraph/interface/amcatnlo_run_interface.py", line 1203, in do_launch
    evt_file = self.run(mode, options)
  File "/home/program/MG5_aMC_v2_3_2/madgraph/interface/amcatnlo_run_interface.py", line 1610, in run
    return self.reweight_and_collect_events(options, mode, nevents, event_norm)
  File "/home/program/MG5_aMC_v2_3_2/madgraph/interface/amcatnlo_run_interface.py", line 2381, in reweight_and_collect_events
    'The event file has not been created. Check collect_events.log')
aMCatNLOError: An error occurred during event generation. The event file has not been created. Check collect_events.log
Value of current Options:
              text_editor : None
                    pjfry : None
       cluster_local_path : /cvmfs/cp3.uclouvain.be/madgraph/
       group_subprocesses : Auto
ignore_six_quark_processes : False
    loop_optimized_output : True
    cluster_status_update : (600, 30)
             pythia8_path : None
                hwpp_path : None
                    golem : None
          pythia-pgs_path : None
                  td_path : None
             delphes_path : None
              thepeg_path : None
             cluster_type : condor
      exrootanalysis_path : None
                      OLP : MadLoop
                 applgrid : applgrid-config
               eps_viewer : None
                  fastjet : None
                 run_mode : 2
              web_browser : None
   automatic_html_opening : False
        cluster_temp_path : None
             cluster_size : 100
            cluster_queue : None
             syscalc_path : None
         madanalysis_path : None
               lhapdf : /home/program/lhapdf6.1.3/bin/lhapdf-config
             stdout_level : 20
            f2py_compiler : None
               hepmc_path : None
                  amcfast : amcfast-config
       cluster_retry_wait : 300
      output_dependencies : external
         fortran_compiler : None
                  nb_core : 8
         loop_color_flows : False
              auto_update : 7
         cluster_nb_retry : 1
                 mg5_path : /home/program/MG5_aMC_v2_3_2
                  timeout : 60
                    gauge : unitary
      complex_mass_scheme : False
             cpp_compiler : None
   max_npoint_for_channel : 0

*******************************collect_events.log*************************
 Overwrite the event weights?
 give '0' to keep original weights;
 give '1' to overwrite the weights to sum to the Xsec;
 give '2' to overwrite the weights to average to the Xsec (=default)
 give '3' to overwrite the weights to either +/- 1.
           2
 step # 0
 found 16 files, bunch number is 1
********************************run.card****************************
#***********************************************************************
# MadGraph5_aMC@NLO *
# *
# run_card.dat aMC@NLO *
# *
# This file is used to set the parameters of the run. *
# *
# Some notation/conventions: *
# *
# Lines starting with a hash (#) are info or comments *
# *
# mind the format: value = variable ! comment *
#***********************************************************************
#
#*******************
# Running parameters
#*******************
#
#***********************************************************************
# Tag name for the run (one word) *
#***********************************************************************
  thj = run_tag ! name of the run
#***********************************************************************
# Number of LHE events (and their normalization) and the required *
# (relative) accuracy on the Xsec. *
# These values are ignored for fixed order runs *
#***********************************************************************
 1000000 = nevents ! Number of unweighted events requested
 -1 = req_acc ! Required accuracy (-1=auto determined from nevents)
 -1 = nevt_job! Max number of events per job in event generation.
                 ! (-1= no split).
#***********************************************************************
# Normalize the weights of LHE events such that they sum or average to *
# the total cross section *
#***********************************************************************
 average = event_norm ! average or sum
#***********************************************************************
# Number of points per itegration channel (ignored for aMC@NLO runs) *
#***********************************************************************
 0.01 = req_acc_FO ! Required accuracy (-1=ignored, and use the
                     ! number of points and iter. below)
# These numbers are ignored except if req_acc_FO is equal to -1
 5000 = npoints_FO_grid ! number of points to setup grids
 4 = niters_FO_grid ! number of iter. to setup grids
 10000 = npoints_FO ! number of points to compute Xsec
 6 = niters_FO ! number of iter. to compute Xsec
#***********************************************************************
# Random number seed *
#***********************************************************************
 0 = iseed ! rnd seed (0=assigned automatically=default))
#***********************************************************************
# Collider type and energy *
#***********************************************************************
 1 = lpp1 ! beam 1 type (0 = no PDF)
 1 = lpp2 ! beam 2 type (0 = no PDF)
 6500 = ebeam1 ! beam 1 energy in GeV
 6500 = ebeam2 ! beam 2 energy in GeV
#***********************************************************************
# PDF choice: this automatically fixes also alpha_s(MZ) and its evol. *
#***********************************************************************
 'lhapdf' = pdlabel ! PDF set
 244800 = lhaid ! if pdlabel=lhapdf, this is the lhapdf number
#***********************************************************************
# Include the NLO Monte Carlo subtr. terms for the following parton *
# shower (HERWIG6 | HERWIGPP | PYTHIA6Q | PYTHIA6PT | PYTHIA8) *
# WARNING: PYTHIA6PT works only for processes without FSR!!!! *
#***********************************************************************
  HERWIG6 = parton_shower
#***********************************************************************
# Renormalization and factorization scales *
# (Default functional form for the non-fixed scales is the sum of *
# the transverse masses of all final state particles and partons. This *
# can be changed in SubProcesses/set_scales.f) *
#***********************************************************************
 .true. = fixed_ren_scale ! if .true. use fixed ren scale
 .true. = fixed_fac_scale ! if .true. use fixed fac scale
 74.575 = muR_ref_fixed ! fixed ren reference scale
 74.575 = muF1_ref_fixed ! fixed fact reference scale for pdf1
 74.575 = muF2_ref_fixed ! fixed fact reference scale for pdf2
 -1 = dynamical_scale_choice ! Choose one of the preselected dynamical choices
#***********************************************************************
# Renormalization and factorization scales (advanced and NLO options) *
#***********************************************************************
 False = fixed_QES_scale ! if .true. use fixed Ellis-Sexton scale
 74.575 = QES_ref_fixed ! fixed Ellis-Sexton reference scale
 1.0 = muR_over_ref ! ratio of current muR over reference muR
 1.0 = muF1_over_ref ! ratio of current muF1 over reference muF1
 1.0 = muF2_over_ref ! ratio of current muF2 over reference muF2
 1.0 = QES_over_ref ! ratio of current QES over reference QES
#***********************************************************************
# Reweight flags to get scale dependence and PDF uncertainty *
# For scale dependence: factor rw_scale_up/down around central scale *
# For PDF uncertainty: use LHAPDF with supported set *
#***********************************************************************
 False = reweight_scale ! reweight to get scale dependence
 0.5 = rw_Rscale_down ! lower bound for ren scale variations
 2.0 = rw_Rscale_up ! upper bound for ren scale variations
 0.5 = rw_Fscale_down ! lower bound for fact scale variations
 2.0 = rw_Fscale_up ! upper bound for fact scale variations
 False = reweight_PDF ! reweight to get PDF uncertainty
 244800 = PDF_set_min ! First of the error PDF sets
 244800 = PDF_set_max ! Last of the error PDF sets
#***********************************************************************
# ickkw parameter: *
# 0: No merging *
# 3: FxFx Merging - WARNING! Applies merging only at the hard-event *
# level. After showering an MLM-type merging should be applied as *
# well. See http://amcatnlo.cern.ch/FxFx_merging.htm for details. *
# 4: UNLOPS merging (with pythia8 only). No interface from within *
# MG5_aMC available, but available in Pythia8. *
# -1: NNLL+NLO jet-veto computation. See arxiv:1412.8408 [hep-ph]. *
#***********************************************************************
 0 = ickkw
#***********************************************************************
#
#***********************************************************************
# BW cutoff (M+/-bwcutoff*Gamma) *
#***********************************************************************
 15.0 = bwcutoff
#***********************************************************************
# Cuts on the jets *
# Jet clustering is performed by FastJet.
# When matching to a parton shower, these generation cuts should be *
# considerably softer than the analysis cuts. *
# (more specific cuts can be specified in SubProcesses/cuts.f) *
#***********************************************************************
  0 = jetalgo ! FastJet jet algorithm (1=kT, 0=C/A, -1=anti-kT)
 0.4 = jetradius ! The radius parameter for the jet algorithm
 -1.0 = ptj ! Min jet transverse momentum
 -1.0 = etaj ! Max jet abs(pseudo-rap) (a value .lt.0 means no cut)
#***********************************************************************
# Cuts on the charged leptons (e+, e-, mu+, mu-, tau+ and tau-) *
# (more specific gen cuts can be specified in SubProcesses/cuts.f) *
#***********************************************************************
  0.0 = ptl ! Min lepton transverse momentum
  -1.0 = etal ! Max lepton abs(pseudo-rap) (a value .lt.0 means no cut)
  0.0 = drll ! Min distance between opposite sign lepton pairs
  0.0 = drll_sf ! Min distance between opp. sign same-flavor lepton pairs
  0.0 = mll ! Min inv. mass of all opposite sign lepton pairs
  30.0 = mll_sf ! Min inv. mass of all opp. sign same-flavor lepton pairs
#***********************************************************************
# Photon-isolation cuts, according to hep-ph/9801442 *
# When ptgmin=0, all the other parameters are ignored *
#***********************************************************************
  20.0 = ptgmin ! Min photon transverse momentum
  -1.0 = etagamma ! Max photon abs(pseudo-rap)
  0.4 = R0gamma ! Radius of isolation code
  1.0 = xn ! n parameter of eq.(3.4) in hep-ph/9801442
  1.0 = epsgamma ! epsilon_gamma parameter of eq.(3.4) in hep-ph/9801442
  True = isoEM ! isolate photons from EM energy (photons and leptons)
#***********************************************************************
# Maximal PDG code for quark to be considered a jet when applying cuts.*
# At least all massless quarks of the model should be included here. *
#***********************************************************************
 5 = maxjetflavor
#***********************************************************************
# For aMCfast+APPLGRID use in PDF fitting (http://amcfast.hepforge.org)*
#***********************************************************************
 0 = iappl ! aMCfast switch (0=OFF, 1=prepare APPLgrids, 2=fill grids)
#***********************************************************************

Thanks a lot!
Hong.

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
marco zaro Edit question
Solved by:
Rikkert Frederix
Solved:
Last query:
Last reply:
Revision history for this message
marco zaro (marco-zaro) said : 		#1

Dear Hong,
what process are you generating?
can you copy/paste the content of the file
SubProcesses/P0_ub_htd/GF1/log.txt?
Thanks,

Marco

Revision history for this message
marco zaro (marco-zaro) said : 		#2

Dear Hong,
what process are you generating?
can you copy/paste the content of the file
SubProcesses/P0_ub_htd/GF1/log.txt?
Thanks,

Marco

Revision history for this message
Hong W (wanghong8405) said : 		#3

the process: p p > t h j $$ w+ w- [QCD]

**************************************SubProcesses/P0_ub_htd/GF1/log.txt**************************
 it ends up with:

.....

---- POLES CANCELLED ----
Only 2 independent helicities: switching to explicitly summing over them
 #####################################################################################
 # #
 # /$$$$$$ /$$$$$$$ /$$$$$$$$ /$$$$$$ /$$$$$$ #
 # |_ $$_/| $$__ $$| $$_____/ /$$__ $$|_ $$_/ #
 # | $$ | $$ \ $$| $$ | $$ \__/ | $$ #
 # | $$ | $$$$$$$/| $$$$$ | $$ /$$$$ | $$ #
 # | $$ | $$__ $$| $$__/ | $$|_ $$ | $$ #
 # | $$ | $$ \ $$| $$ | $$ \ $$ | $$ #
 # /$$$$$$| $$ | $$| $$$$$$$$| $$$$$$/ /$$$$$$ #
 # |______/|__/ |__/|________/ \______/ |______/ #
 # #
 # (VERSION alpha-1.1.0) #
 # package for one-loop tensor Integral REduction with General propagator Indices #
 # Author: Hua-Sheng Shao (<email address hidden><email address hidden>) #
 # a) Physics School, Peking University, Beijing, China #
 # b) PH Department, TH Unit, CERN, Geneva, Switzerland #
 # #
 #####################################################################################
 ERROR #12 in add_write_info, not a well-defined process 0 F
Time in seconds: 2325

  *********************************************************************************************
Do I need to copy all？

Revision history for this message
marco zaro (marco-zaro) said : 		#4

Dear Hong,
both myself and Rikkert are unable to reproduce your error...
Do you change any part of the code before the 'launch'?

Thanks,

Marco

Revision history for this message
Hong W (wanghong8405) said : 		#5

Hi, Marco,
This may be because of the different models we were imported,it is pretty normal when I use model loop-sm,but crashed in model loop_sm-no_b_mass.
There is also a very strange thing is that the problem happens when nevents is set to 1000000 or more,but disappears when nevents is set to 100000 or less. (I have not checked the case when 100000<nevents<1000000 yet.)
However,I need enough events in model loop_sm-no_b_mass.
These are my input commands：

>import model loop_sm-no_b_mass
>generate p p > h t j $$ w+ w- [QCD]
>add process p p > h t~ j $$ w+ w- [QCD]
>output
>launch
******************************************************************************************************
...
The following switches determine which operations are executed:
 1 Perturbative order of the calculation: order=NLO
 2 Fixed order (no event generation and no MC@[N]LO matching): fixed_order=OFF
 3 Shower the generated events: shower=OFF
 4 Decay particles with the MadSpin module: madspin=OFF
 5 Add weights to the events based on changing model parameters: reweight=Not available (requires NumPy)
...
*****************************param_card.dat**********************************************************
###################################
Block loop
    1 7.457500e+01 # MU_R

###################################
## INFORMATION FOR MASS
###################################
Block mass
    6 1.733000e+02 # MT
   15 1.777000e+00 # MTA
   23 9.118760e+01 # MZ
   25 1.250000e+02 # MH
## Dependent parameters, given by model restrictions.
## Those values should be edited following the
## analytical expression. MG5 ignores those values
## but they are important for interfacing the output of MG5
## to external program such as Pythia.
  1 0.000000 # d : 0.0
  2 0.000000 # u : 0.0
  3 0.000000 # s : 0.0
  4 0.000000 # c : 0.0
  5 0.000000 # b : 0.0
  11 0.000000 # e- : 0.0
  12 0.000000 # ve : 0.0
  13 0.000000 # mu- : 0.0
  14 0.000000 # vm : 0.0
  16 0.000000 # vt : 0.0
  21 0.000000 # g : 0.0
  22 0.000000 # a : 0.0
  24 80.38500 # w+ : cmath.sqrt(MZ__exp__2/2. + cmath.sqrt(MZ__exp__4/4. - (aEW*cmath.pi*MZ__exp__2)/(Gf*sqrt__2)))
###################################
## INFORMATION FOR SMINPUTS
###################################
Block sminputs
    1 1.3223323e+02 # aEWM1
    2 1.1663787e-05 # Gf
    3 1.190000e-01 # aS

###################################
## INFORMATION FOR YUKAWA
###################################
Block yukawa
    6 1.733000e+02 # ymt
   15 1.777000e+00 # ymtau

###################################
## INFORMATION FOR DECAY
###################################
DECAY 6 1.491500e+00 # WT
DECAY 23 2.441404e+00 # WZ
DECAY 24 2.047600e+00 # WW
DECAY 25 6.382339e-03 # WH
## Dependent parameters, given by model restrictions.
## Those values should be edited following the
## analytical expression. MG5 ignores those values
## but they are important for interfacing the output of MG5
## to external program such as Pythia.
DECAY 1 0.000000 # d : 0.0
DECAY 2 0.000000 # u : 0.0
DECAY 3 0.000000 # s : 0.0
DECAY 4 0.000000 # c : 0.0
DECAY 5 0.000000 # b : 0.0
DECAY 11 0.000000 # e- : 0.0
DECAY 12 0.000000 # ve : 0.0
DECAY 13 0.000000 # mu- : 0.0
DECAY 14 0.000000 # vm : 0.0
DECAY 15 0.000000 # ta- : 0.0
DECAY 16 0.000000 # vt : 0.0
DECAY 21 0.000000 # g : 0.0
DECAY 22 0.000000 # a : 0.0
  *******************************************************************
the problem happens when collecting events , it takes time.

Thanks for your concern.

Hong

Revision history for this message
marco zaro (marco-zaro) said : 		#6

Dear Hong,
do you also include the b and b~ in the p/j multiparticles?
Let me know,

Marco

On 29 Aug 2015, at 06:41, Hong W <email address hidden> wrote:

> Question #270692 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/270692
>
> Hong W gave more information on the question:
> Hi, Marco,
> This may be because of the different models we were imported,it is pretty normal when I use model loop-sm,but crashed in model loop_sm-no_b_mass.
> There is also a very strange thing is that the problem happens when nevents is set to 1000000 or more,but disappears when nevents is set to 100000 or less. (I have not checked the case when 100000<nevents<1000000 yet.)
> However,I need enough events in model loop_sm-no_b_mass.
> These are my input commands：
>
>> import model loop_sm-no_b_mass
>> generate p p > h t j $$ w+ w- [QCD]
>> add process p p > h t~ j $$ w+ w- [QCD]
>> output
>> launch
> ******************************************************************************************************
> ...
> The following switches determine which operations are executed:
> 1 Perturbative order of the calculation: order=NLO
> 2 Fixed order (no event generation and no MC@[N]LO matching): fixed_order=OFF
> 3 Shower the generated events: shower=OFF
> 4 Decay particles with the MadSpin module: madspin=OFF
> 5 Add weights to the events based on changing model parameters: reweight=Not available (requires NumPy)
> ...
> *****************************param_card.dat**********************************************************
> ###################################
> Block loop
> 1 7.457500e+01 # MU_R
>
> ###################################
> ## INFORMATION FOR MASS
> ###################################
> Block mass
> 6 1.733000e+02 # MT
> 15 1.777000e+00 # MTA
> 23 9.118760e+01 # MZ
> 25 1.250000e+02 # MH
> ## Dependent parameters, given by model restrictions.
> ## Those values should be edited following the
> ## analytical expression. MG5 ignores those values
> ## but they are important for interfacing the output of MG5
> ## to external program such as Pythia.
> 1 0.000000 # d : 0.0
> 2 0.000000 # u : 0.0
> 3 0.000000 # s : 0.0
> 4 0.000000 # c : 0.0
> 5 0.000000 # b : 0.0
> 11 0.000000 # e- : 0.0
> 12 0.000000 # ve : 0.0
> 13 0.000000 # mu- : 0.0
> 14 0.000000 # vm : 0.0
> 16 0.000000 # vt : 0.0
> 21 0.000000 # g : 0.0
> 22 0.000000 # a : 0.0
> 24 80.38500 # w+ : cmath.sqrt(MZ__exp__2/2. + cmath.sqrt(MZ__exp__4/4. - (aEW*cmath.pi*MZ__exp__2)/(Gf*sqrt__2)))
> ###################################
> ## INFORMATION FOR SMINPUTS
> ###################################
> Block sminputs
> 1 1.3223323e+02 # aEWM1
> 2 1.1663787e-05 # Gf
> 3 1.190000e-01 # aS
>
> ###################################
> ## INFORMATION FOR YUKAWA
> ###################################
> Block yukawa
> 6 1.733000e+02 # ymt
> 15 1.777000e+00 # ymtau
>
> ###################################
> ## INFORMATION FOR DECAY
> ###################################
> DECAY 6 1.491500e+00 # WT
> DECAY 23 2.441404e+00 # WZ
> DECAY 24 2.047600e+00 # WW
> DECAY 25 6.382339e-03 # WH
> ## Dependent parameters, given by model restrictions.
> ## Those values should be edited following the
> ## analytical expression. MG5 ignores those values
> ## but they are important for interfacing the output of MG5
> ## to external program such as Pythia.
> DECAY 1 0.000000 # d : 0.0
> DECAY 2 0.000000 # u : 0.0
> DECAY 3 0.000000 # s : 0.0
> DECAY 4 0.000000 # c : 0.0
> DECAY 5 0.000000 # b : 0.0
> DECAY 11 0.000000 # e- : 0.0
> DECAY 12 0.000000 # ve : 0.0
> DECAY 13 0.000000 # mu- : 0.0
> DECAY 14 0.000000 # vm : 0.0
> DECAY 15 0.000000 # ta- : 0.0
> DECAY 16 0.000000 # vt : 0.0
> DECAY 21 0.000000 # g : 0.0
> DECAY 22 0.000000 # a : 0.0
> *******************************************************************
> the problem happens when collecting events , it takes time.
>
> Thanks for your concern.
>
> Hong
>
> --
> You received this question notification because you are a direct
> subscriber of the question.

Revision history for this message
Hong W (wanghong8405) said : 		#7

Dear Marco,
yes,in the 5-flavour scheme.
It seems that the b and b~ are automatically included in MG5_aMC_v2_3_2 ,so I passed the redefination of p/j .

Hong

Revision history for this message
Rikkert Frederix (frederix) said : 		#8

Dear Hong,

Could you please send me your proc_card_mg5.dat and other inputs that you might have changed as well as the random seed used in your generation. In that way, I should be able to recreate your problem locally to understand what's going on.

Thanks.
Rikkert

Revision history for this message
Hong W (wanghong8405) said : 		#9

Dear Frederix,

Sorry to reply late.
here is my proc_card_mg5.dat :

set group_subprocesses Auto
set ignore_six_quark_processes False
set loop_color_flows False
set gauge unitary
set complex_mass_scheme False
set max_npoint_for_channel 0
import model sm
define p = g u c d s u~ c~ d~ s~
define j = g u c d s u~ c~ d~ s~
define l+ = e+ mu+
define l- = e- mu-
define vl = ve vm vt
define vl~ = ve~ vm~ vt~
import model loop_sm-no_b_mass
generate p p > h t j $$ w+ w- [QCD]
add process p p > h t~ j $$ w+ w- [QCD]
output ./myprocess/htj-nlo

I have pasted my run_card.dat , param_card.dat and other inputs above.

“......
Using random seed offsets: 1 , 4 , 0
  with seed 33
......"
in alllogs_0.html is what you said " the random seed used in your generation" ?

Thanks.
Hong

Revision history for this message
Rikkert Frederix (frederix) said : 		#10

Dear Hong,

Thanks for the information. I've been able to reproduce your problem. It will take some time to debug, because it is a very strange bug...

Best,
Rikkert

Revision history for this message
Hong W (wanghong8405) said : 		#11

Dear Frederix,

Thank you for your effort.
I found it is OK when I add a pt cut on the jet (It is -1 before).but there is no additional infrared divergence caused by the jet.
Maybe this can help you to understand the bug.

Thanks,
Hong

Revision history for this message
marco zaro (marco-zaro) said : 		#12

Hi Hong,
the pt cut may cause some instabilities, problems, indeed... Instead of putting -1, put a rather small value, like 1GeV or so... At least this is what i typically do...
Let us know...
Cheers,

Marco

Revision history for this message
Best Rikkert Frederix (frederix) said : 		#13

Dear Hong,

Using the following improvements to the code, it should no longer stop. However, it doesn't really solve any of the instabilities that one might encounter at very small jet transverse momentum. Therefore, I do recommend to use a small jet-pT cut (for example 0.1 GeV) to make sure that at least most of these problems are not present.

Best regards,
Rikkert

== modified file 'Template/NLO/SubProcesses/fks_singular.f'
--- Template/NLO/SubProcesses/fks_singular.f 2015-08-19 12:50:52 +0000
+++ Template/NLO/SubProcesses/fks_singular.f 2015-09-14 07:20:21 +0000
@@ -1034,6 +1034,10 @@
      $ ,pswgt_cnt(-2:2),jac_cnt(-2:2)
       common/counterevnts/p1_cnt,wgt_cnt,pswgt_cnt,jac_cnt
       if (wgt1.eq.0d0 .and. wgt2.eq.0d0 .and. wgt3.eq.0d0) return
+c Check for NaN's and INF's. Simply skip the contribution
+ if (wgt1.ne.wgt1) return
+ if (wgt2.ne.wgt2) return
+ if (wgt3.ne.wgt3) return
       icontr=icontr+1
       if (icontr.gt.max_contr) then
          write (*,*) 'ERROR in add_wgt: too many contributions'
@@ -2741,11 +2745,12 @@
       endif

       if(wgt.lt.0.d0)then
- write(*,*) 'Fatal error #2 in sreal',wgt,xi_i_fks,y_ij_fks
+ write(*,*) 'Warning, numerical problem found in sreal. '/
+ $ /'Setting weight to zero',wgt,xi_i_fks,y_ij_fks
          do i=1,nexternal
             write(*,*) 'particle ',i,', ',(pp(j,i),j=0,3)
          enddo
- stop
+ wgt=0d0
       endif

       return

Revision history for this message
Hong W (wanghong8405) said : 		#14

Dear Rikkert,Marco,
Thanks for your answers.

The problem appears to only be so treated now. The results of running seems to be acceptable after this treatment.

Cheers,
Hong

Revision history for this message
Hong W (wanghong8405) said : 		#15

Thanks Rikkert Frederix, that solved my question.