maddump

MadDump: No such file maddump_test2/Cards/fit2D_card_default.dat

Asked by Max Fieg

Hello,

I am just getting started with MadDump but am reaching an error for the simplest process. I found this exact same error asked by another user on this site here, https://answers.launchpad.net/maddump/+question/697481, but there is no response and the question is closed.

I am running a simple pair annihilation (but other process have the same problem):
generate e- e+ > a a
output dumptest
launch

And what returns is:
Exception : No such file dumptest2/Cards/fit2D_card_default.dat
Please report this bug to developers

           More information is found in 'debug'.

           Please attach this file to your report.

I am not sure how to fix this, and imagine it will be helpful to others as well.

As a side note, I am wondering where I can enter the target's properties? This might be a card I can edit after the launch screen, but since I can't get there right now I am not sure where this can be entered.

Thank you in advance for your time, I will copy my debug as a reply to this question

Question information

Language:
English Edit question
Status:
Solved
For:
maddump Edit question
Assignee:
Luca Edit question
Solved by:
Luca
Solved:
Last query:
Last reply:
Revision history for this message
Max Fieg (maxfieg) said : 		#1

Traceback (most recent call last):
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/madgraph/interface/extended_cmd.py", line 1515, in onecmd
    return self.onecmd_orig(line, **opt)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/madgraph/interface/extended_cmd.py", line 1464, in onecmd_orig
    return func(arg, **opt)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/PLUGIN/maddump/new_interface/maddump_interface.py", line 482, in do_launch
    self._MDUMP.exec_cmd('launch')
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/madgraph/interface/extended_cmd.py", line 1544, in exec_cmd
    stop = Cmd.onecmd_orig(current_interface, line, **opt)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/madgraph/interface/extended_cmd.py", line 1464, in onecmd_orig
    return func(arg, **opt)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/PLUGIN/maddump/new_interface/maddump_run_interface.py", line 228, in do_launch
    self.ask_run_configuration(mode=[], force=force)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/PLUGIN/maddump/new_interface/maddump_run_interface.py", line 452, in ask_run_configuration
    self.ask_edit_cards(cards,plot=False)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/PLUGIN/maddump/new_interface/maddump_run_interface.py", line 462, in ask_edit_cards
    self.ask, first_cmd=first_cmd)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/PLUGIN/maddump/new_interface/maddump_run_interface.py", line 530, in ask_edit_card_static
    cards=cards, mode=mode, **opt)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/madgraph/interface/extended_cmd.py", line 1092, in ask
    mother_interface=self, **opt)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/PLUGIN/maddump/new_interface/maddump_run_interface.py", line 596, in __init__
    *args, **opts)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/madgraph/interface/common_run_interface.py", line 4509, in __init__
    new_vars = set(getattr(self, 'init_%s' % name)(cards))
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/PLUGIN/maddump/new_interface/maddump_run_interface.py", line 619, in init_fit2D
    self.maddump_def = fit2D.Fit2DCard(self.paths['fit2D_default'], consistency=False)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/madgraph/various/banner.py", line 2282, in __init__
    super(RunCard, self).__init__(*args, **opts)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/madgraph/various/banner.py", line 974, in __init__
    self.read(finput, **opt)
  File "/home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/madgraph/various/banner.py", line 2330, in read
    raise Exception, "No such file %s" % finput
Exception: No such file maddump_test2/Cards/fit2D_card_default.dat
Value of current Options:
              text_editor : None
      notification_center : True
                    pjfry : None
     maddm_first_indirect : False
       cluster_local_path : None
  default_unset_couplings : 99
       group_subprocesses : Auto
ignore_six_quark_processes : False
    loop_optimized_output : True
    cluster_status_update : (600, 30)
         fortran_compiler : None
               hepmc_path : None
                  collier : ./HEPTools/lib
              auto_update : 7
             pythia8_path : /home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/HEPTools/pythia8
                hwpp_path : None
low_mem_multicore_nlo_generation : False
                    golem : None
              dragon_path : /home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/HEPTools/dragon
          pythia-pgs_path : /home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/pythia-pgs
                  td_path : ./td
             delphes_path : ./Delphes
              thepeg_path : None
             cluster_type : condor
        madanalysis5_path : /home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/HEPTools/madanalysis5/madanalysis5
      exrootanalysis_path : ./ExRootAnalysis
                      OLP : MadLoop
                 applgrid : applgrid-config
               eps_viewer : None
                  fastjet : None
                 run_mode : 2
              web_browser : None
   automatic_html_opening : True
        cluster_temp_path : None
             cluster_size : 100
            cluster_queue : None
             syscalc_path : ./SysCalc
         madanalysis_path : ./MadAnalysis
                   lhapdf : /home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/HEPTools/lhapdf6/bin/lhapdf-config
             stdout_level : 20
                  nb_core : None
            f2py_compiler : None
                    ninja : ./HEPTools/lib
                  amcfast : amcfast-config
       cluster_retry_wait : 300
      output_dependencies : external
           crash_on_error : False
mg5amc_py8_interface_path : /home/maxfieg/Desktop/MG5_aMC_v2.6.6/MG5_aMC_v2_6_6/HEPTools/MG5aMC_PY8_interface
         loop_color_flows : False
                  samurai : None
         cluster_nb_retry : 1
                  timeout : 60
                    gauge : unitary
      complex_mass_scheme : False
             cpp_compiler : None
   max_npoint_for_channel : 0
######################################################################
## PARAM_CARD AUTOMATICALY GENERATED BY MG5 FOLLOWING UFO MODEL ####
######################################################################
## ##
## Width set on Auto will be computed following the information ##
## present in the decay.py files of the model. ##
## See arXiv:1402.1178 for more details. ##
## ##
######################################################################

###################################
## INFORMATION FOR MASS
###################################
Block mass
    5 4.700000e+00 # MB
    6 1.730000e+02 # MT
   15 1.777000e+00 # MTA
   23 9.118800e+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.000000e+00 # d : 0.0
  2 0.000000e+00 # u : 0.0
  3 0.000000e+00 # s : 0.0
  4 0.000000e+00 # c : 0.0
  11 0.000000e+00 # e- : 0.0
  12 0.000000e+00 # ve : 0.0
  13 0.000000e+00 # mu- : 0.0
  14 0.000000e+00 # vm : 0.0
  16 0.000000e+00 # vt : 0.0
  21 0.000000e+00 # g : 0.0
  22 0.000000e+00 # a : 0.0
  24 8.041900e+01 # 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.325070e+02 # aEWM1
    2 1.166390e-05 # Gf
    3 1.180000e-01 # aS

###################################
## INFORMATION FOR YUKAWA
###################################
Block yukawa
    5 4.700000e+00 # ymb
    6 1.730000e+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.000000e+00 # d : 0.0
DECAY 2 0.000000e+00 # u : 0.0
DECAY 3 0.000000e+00 # s : 0.0
DECAY 4 0.000000e+00 # c : 0.0
DECAY 5 0.000000e+00 # b : 0.0
DECAY 11 0.000000e+00 # e- : 0.0
DECAY 12 0.000000e+00 # ve : 0.0
DECAY 13 0.000000e+00 # mu- : 0.0
DECAY 14 0.000000e+00 # vm : 0.0
DECAY 15 0.000000e+00 # ta- : 0.0
DECAY 16 0.000000e+00 # vt : 0.0
DECAY 21 0.000000e+00 # g : 0.0
DECAY 22 0.000000e+00 # a : 0.0
#*********************************************************************
# MadGraph5_aMC@NLO *
# *
# run_card.dat MadEvent *
# *
# This file is used to set the parameters of the run. *
# *
# Some notation/conventions: *
# *
# Lines starting with a '# ' are info or comments *
# *
# mind the format: value = variable ! comment *
# *
# To display more options, you can type the command: *
# update full_run_card *
#*********************************************************************
#
#*********************************************************************
# Tag name for the run (one word) *
#*********************************************************************
  tag_1 = run_tag ! name of the run
#*********************************************************************
# Number of events and rnd seed *
# Warning: Do not generate more than 1M events in a single run *
#*********************************************************************
  10000 = nevents ! Number of unweighted events requested
  0 = iseed ! rnd seed (0=assigned automatically=default))
#*********************************************************************
# Collider type and energy *
# lpp: 0=No PDF, 1=proton, -1=antiproton, 2=photon from proton, *
# 3=photon from electron *
#*********************************************************************
     0 = lpp1 ! beam 1 type
     1 = lpp2 ! beam 2 type
     1000.0 = ebeam1 ! beam 1 total energy in GeV
     6500.0 = ebeam2 ! beam 2 total energy in GeV
#*********************************************************************
# Beam polarization from -100 (left-handed) to 100 (right-handed) *
#*********************************************************************
     0.0 = polbeam1 ! beam polarization for beam 1
     0.0 = polbeam2 ! beam polarization for beam 2

#*********************************************************************
# PDF CHOICE: this automatically fixes also alpha_s and its evol. *
#*********************************************************************
     nn23lo1 = pdlabel ! PDF set
     230000 = lhaid ! if pdlabel=lhapdf, this is the lhapdf number
# To see heavy ion options: type "update ion_pdf"
#*********************************************************************
# Renormalization and factorization scales *
#*********************************************************************
 False = fixed_ren_scale ! if .true. use fixed ren scale
 False = fixed_fac_scale ! if .true. use fixed fac scale
 91.188 = scale ! fixed ren scale
 91.188 = dsqrt_q2fact1 ! fixed fact scale for pdf1
 91.188 = dsqrt_q2fact2 ! fixed fact scale for pdf2
 -1 = dynamical_scale_choice ! Choose one of the preselected dynamical choices
 1.0 = scalefact ! scale factor for event-by-event scales
#*********************************************************************
# Type and output format
#*********************************************************************
  False = gridpack !True = setting up the grid pack
  -1.0 = time_of_flight ! threshold (in mm) below which the invariant livetime is not written (-1 means not written)
  average = event_norm ! average/sum. Normalization of the weight in the LHEF
# To see MLM/CKKW merging options: type "update MLM" or "update CKKW"

#*********************************************************************
#
#*********************************************************************
# handling of the helicities:
# 0: sum over all helicities
# 1: importance sampling over helicities
#*********************************************************************
   0 = nhel ! using helicities importance sampling or not.
#*********************************************************************
# Generation bias, check the wiki page below for more information: *
# 'cp3.irmp.ucl.ac.be/projects/madgraph/wiki/LOEventGenerationBias' *
#*********************************************************************
 None = bias_module ! Bias type of bias, [None, ptj_bias, -custom_folder-]
 {} = bias_parameters ! Specifies the parameters of the module.
#
#*******************************
# Parton level cuts definition *
#*******************************
#
#
#*********************************************************************
# BW cutoff (M+/-bwcutoff*Gamma) ! Define on/off-shell for "$" and decay
#*********************************************************************
  15.0 = bwcutoff ! (M+/-bwcutoff*Gamma)
#*********************************************************************
# Standard Cuts *
#*********************************************************************
# Minimum and maximum pt's (for max, -1 means no cut) *
#*********************************************************************
 20.0 = ptj ! minimum pt for the jets
 10.0 = ptl ! minimum pt for the charged leptons
 -1.0 = ptjmax ! maximum pt for the jets
 -1.0 = ptlmax ! maximum pt for the charged leptons
 {} = pt_min_pdg ! pt cut for other particles (use pdg code). Applied on particle and anti-particle
 {} = pt_max_pdg ! pt cut for other particles (syntax e.g. {6: 100, 25: 50})
#
# For display option for energy cut in the partonic center of mass frame type 'update ecut'
#
#*********************************************************************
# Maximum and minimum absolute rapidity (for max, -1 means no cut) *
#*********************************************************************
 5.0 = etaj ! max rap for the jets
 2.5 = etal ! max rap for the charged leptons
 0.0 = etalmin ! main rap for the charged leptons
 {} = eta_min_pdg ! rap cut for other particles (use pdg code). Applied on particle and anti-particle
 {} = eta_max_pdg ! rap cut for other particles (syntax e.g. {6: 2.5, 23: 5})
#*********************************************************************
# Minimum and maximum DeltaR distance *
#*********************************************************************
 0.4 = drll ! min distance between leptons
 0.4 = drjl ! min distance between jet and lepton
 -1.0 = drllmax ! max distance between leptons
 -1.0 = drjlmax ! max distance between jet and lepton
#*********************************************************************
# Minimum and maximum invariant mass for pairs *
#*********************************************************************
 0.0 = mmll ! min invariant mass of l+l- (same flavour) lepton pair
 -1.0 = mmllmax ! max invariant mass of l+l- (same flavour) lepton pair
 {} = mxx_min_pdg ! min invariant mass of a pair of particles X/X~ (e.g. {6:250})
 {'default': False} = mxx_only_part_antipart ! if True the invariant mass is applied only
                       ! to pairs of particle/antiparticle and not to pairs of the same pdg codes.
 #*********************************************************************
 # Minimum and maximum invariant mass for all letpons *
 #*********************************************************************
 0.0 = mmnl ! min invariant mass for all letpons (l+- and vl)
 -1.0 = mmnlmax ! max invariant mass for all letpons (l+- and vl)
 #*********************************************************************
 # Minimum and maximum pt for 4-momenta sum of leptons *
 #*********************************************************************
 0.0 = ptllmin ! Minimum pt for 4-momenta sum of leptons(l and vl)
 -1.0 = ptllmax ! Maximum pt for 4-momenta sum of leptons(l and vl)
#*********************************************************************
# Inclusive cuts *
#*********************************************************************
 0.0 = xptl ! minimum pt for at least one charged lepton
 #*********************************************************************
 # Control the pt's of leptons sorted by pt *
 #*********************************************************************
 0.0 = ptl1min ! minimum pt for the leading lepton in pt
 0.0 = ptl2min ! minimum pt for the second lepton in pt
 0.0 = ptl3min ! minimum pt for the third lepton in pt
 -1.0 = ptl1max ! maximum pt for the leading lepton in pt
 -1.0 = ptl2max ! maximum pt for the second lepton in pt
 -1.0 = ptl3max ! maximum pt for the third lepton in pt
#*********************************************************************
# maximal pdg code for quark to be considered as a light jet *
# (otherwise b cuts are applied) *
#*********************************************************************
 4 = maxjetflavor ! Maximum jet pdg code
#*********************************************************************
#
#*********************************************************************
# Store info for systematics studies *
# WARNING: Do not use for interference type of computation *
#*********************************************************************
   True = use_syst ! Enable systematics studies
#
systematics = systematics_program ! none, systematics [python], SysCalc [depreceted, C++]
['--mur=0.5,1,2', '--muf=0.5,1,2', '--pdf=errorset'] = systematics_arguments ! see: https://cp3.irmp.ucl.ac.be/projects/madgraph/wiki/Systematics#Systematicspythonmodule
# Syscalc is deprecated but to see the associate options type'update syscalc'

Revision history for this message
Luca (lbuono) said : 		#2

Dear Max,

can you tell me more about the physics case you would like to simulate?
MadDump has been designed having in mind a situation in which
production and detection occur at different locations, separated
by a macroscopic distance. In your example, you only specify a production
mechanism (e^+ e^- -> a a) but nothing it is none about the detection part
(does it occur via the rescattering of the photons? ). Therefore the output
generation is incomplete and the fit2D_card_default.dat is missing.

Cheers, Luca

Revision history for this message
Max Fieg (maxfieg) said (last edit ): 		#3

Hi Luca,

Thanks for your quick response!
I am interested in testing a certain BSM model at the E137 electron beam dump. The signal could be a decay of a particle downstream at the detector, or it could be the scattering of this particle at the detector.

The process you see there was just a test process, not a process of my interest. But maybe I don't know how to use maddump properly... I thought I would enter the detection later.
I am following the example in Appendix D of https://arxiv.org/pdf/1812.06771.pdf. Is there a critical step I am missing here?

I see there is this "add process interaction" line, and I guess this is the detection method that I am missing. Is there a list somewhere of signal types that I would enter here?

Thanks again for your help

Revision history for this message
Best Luca (lbuono) said : 		#4

Hi Max,

if you look at the examples in the Appendix D, you can see that you have always to provide as input both
 the production and the decay mechanisms.

For example:

import model DMZB
generate production p p > chidmsc chidmsc~
define darkmatter chidmsc
add process interaction @DIS
output leptofobic
launch

you import the BSM model (in your test example is not needed),
specify the production mechanism (pp scattering),
declare the dark matter candidate and
specify the detection mechanism (DIS scattering within the detector ).
It is important to declare the dark matter particle, as @DIS is a "macro"
for the process "darkmatter" p > "dark matter" p.
if you have instead @electron, the process will be
 "darkmatter" e^- > "dark matter" e^-

In the other example

import model DM_mesons_2
#import the input file events "MesonFulx.hepmc"
import_events decay ./MesonFlux.hepmc
decay pi0 > y1 a, y1 > xd xd~
define darkmatter xd
add process interaction @DIS
add process interaction @electron
output DP_electron
launch

the production mechanism is the decay from a meson (the mesons flux is provided) and then the detection is again given by
rescattering in the detector both via DIS and elastic electron scattering.

For your particular physics case, you might want to run with an effective electron pdf which takes into account secondary
lepton/gammas production in the electron beam dump. This feature is not available in the stable version, but present in
a development branch. If you are interested, you can directly send an email to me.

Cheers, Luca

Revision history for this message
Max Fieg (maxfieg) said : 		#5

Hi Luca,

Ah, this makes much more sense, thank you for the thorough answer. I will spend some time and get back to you here if there is any trouble. I have 2 small questions for now:

-I am looking at a certain inelastic DM model that only allows off-diagonal couplings. So the scattering signal would be x_2 e- --> x_1 e-. If I declare my DM as x_2 and my detection as "add process interaction @electron", maddump demands an elastic scattering process (no amplitude for process x_2 e- --> x_2 e-). Is there a way around this?

- For my case, the dominant x_2 x_1 production is a bremstrahhlung process off a nucleus with an off-shell photon decaying to a x_2 x_1 pair (e- nuc --> e- nuc x_2 x_1). I am wondering why you are worried about secondary lepton/photon production in the beam dump; the detector is shielded by 200m of earth from the dump, so I don't think this should contribute a background or anything. But maybe you are thinking of something different?

Thank you in advance, I appreciate how helpful you've been.

Revision history for this message
Max Fieg (maxfieg) said : 		#6

Thanks Luca, that solved my question.

Revision history for this message
Luca (lbuono) said : 		#7

Dear Max,

let me comment on you previous questions:

- within the public version of the code is not trivial to overcome your issue.
You can use instead the development version. I just fixed it to be enough general
to support your case. To get the dev version see my answer in https://answers.launchpad.net/maddump/+question/700422.

You can then generate your interaction process with the command
add process interaction x_2 e > x_1 e @electron
assuming you have a model containing the particles x_1,2

- if you have a thick target you will eventually produce secondary electrons/positrons/gamma that might undergo a scattering process within the target producing BSM particles, as explained, for instance, in https://inspirehep.net/files/453e21ac4dc5d627207f0ee90067d69d. You can give an equivalent description in terms of "single" scattering event weighted by a 'pdf' of the electron/positron/gamma. In the aforementioned development version of maddump there is a facility to handle a lepton pdf provided by the user.

Cheers, Luca