Syscalc is deprecated but to see the associate options type'update syscalc'

Asked by Benslama Hana on 2020-02-28

If it is possible, please I need your help?
I' m new in madgraph5 and madanalysis. For madanalysis to import some events other than those exist in samples, I have to generate theme using Madgraph. Here are the following commands that I typed on the madgraph consol: as an example
generate p p > t t~, then output and finally for launch when I choosed 0 enter then 0 enter, every thing worked very well and the result was saved in an html file. But I need to change the number of events as well as the Beam energy, and thus I typed 0 enter then 2 enter. However the consol displayed this message:"~/Desktop/programs/MG5_aMC_v2_7_0/PROC_sm_4/Cards/run_card.dat" [Incomplete last line] 130 lines, 8428 characters
Press ENTER or type command to continue. When I typed enter, I found at the end of the paper this paragraph:
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'

PLease I do not understand What I have to do

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Olivier Mattelaer
Solved:
2020-02-28
Last query:
2020-02-28
Last reply:
2020-02-28

Hi,

I have never seen such message. The question is "who" is writing such message.
So the question is which text-editor are you (trying) to use?
Did you have set one in the configuration file? (or did you set the $EDITOR environment variable)
 If not maybe it would be useful to force vi or emacs for text_editor in input/mg5_configuration.txt

Cheers,

Olivier

PS: are you on windows? This can also explains stuff if you do

Benslama Hana (hana2025) said : #3

Hello Olivier,

I'm working on ubuntu which is installed in a VMware worstation pro15. I tried to generate an event and I want to modify the beam energy and the number of events using run cards, but in the launch step I clicked on 0 then 2, the consol of madgraph displayed this message.

Benslama Hana (hana2025) said : #4

sorry I did a mistake for writing that the question is answered, it has not
been solved yet.

Le ven. 28 févr. 2020 à 13:03, Benslama Hana <
<email address hidden>> a écrit :

> Your question #689042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/689042
>
> Status: Answered => Solved
>
> You confirmed that the question is solved:
> Thanks Olivier Mattelaer, that solved my question.
>
> --
> You received this question notification because you asked the question.
>

I believe that this is a message from vim.
Which version of vim do you have on your system?
Does it open the file when you type "2" or does it not?

If it does, you can edit the file and ignore this message.

Cheers,

Olivier

Benslama Hana (hana2025) said : #6

Dear Olivier,

When I write vim --version, the terminal displays that I can install it
using sudo apt install, and I just do it at this moment (sudo apt install
vim). For the file it is not opened, I'll try to send you all what appear
in the consol.

Le ven. 28 févr. 2020 à 13:32, Olivier Mattelaer <
<email address hidden>> a écrit :

> Your question #689042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/689042
>
> Olivier Mattelaer posted a new comment:
> I believe that this is a message from vim.
> Which version of vim do you have on your system?
> Does it open the file when you type "2" or does it not?
>
> If it does, you can edit the file and ignore this message.
>
> Cheers,
>
> Olivier
>
> --
> You received this question notification because you asked the question.
>

Benslama Hana (hana2025) said : #7

#*********************************************************************
# 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 *
#*********************************************************************
     1 = lpp1 ! beam 1 type
     1 = lpp2 ! beam 2 type
     6500.0 = ebeam1 ! beam 1 total energy in GeV
     6500.0 = ebeam2 ! beam 2 total energy in GeV
# To see polarised beam options: type "update beam_pol"

#*********************************************************************
# 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"

                                                         7,1 Top

Le ven. 28 févr. 2020 à 13:53, hana benslama <email address hidden>
a écrit :

> Dear Olivier,
>
> When I write vim --version, the terminal displays that I can install it
> using sudo apt install, and I just do it at this moment (sudo apt install
> vim). For the file it is not opened, I'll try to send you all what appear
> in the consol.
>
> Le ven. 28 févr. 2020 à 13:32, Olivier Mattelaer <
> <email address hidden>> a écrit :
>
>> Your question #689042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>
>> Olivier Mattelaer posted a new comment:
>> I believe that this is a message from vim.
>> Which version of vim do you have on your system?
>> Does it open the file when you type "2" or does it not?
>>
>> If it does, you can edit the file and ignore this message.
>>
>> Cheers,
>>
>> Olivier
>>
>> --
>> You received this question notification because you asked the question.
>>
>

Benslama Hana (hana2025) said : #8

To launch the event I clicked on 0 the 2, but the above message is displayed

Le ven. 28 févr. 2020 à 14:00, hana benslama <email address hidden>
a écrit :

> #*********************************************************************
> # 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 *
> #*********************************************************************
> 1 = lpp1 ! beam 1 type
> 1 = lpp2 ! beam 2 type
> 6500.0 = ebeam1 ! beam 1 total energy in GeV
> 6500.0 = ebeam2 ! beam 2 total energy in GeV
> # To see polarised beam options: type "update beam_pol"
>
> #*********************************************************************
> # 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"
>
> 7,1 Top
>
> Le ven. 28 févr. 2020 à 13:53, hana benslama <email address hidden>
> a écrit :
>
>> Dear Olivier,
>>
>> When I write vim --version, the terminal displays that I can install it
>> using sudo apt install, and I just do it at this moment (sudo apt install
>> vim). For the file it is not opened, I'll try to send you all what appear
>> in the consol.
>>
>> Le ven. 28 févr. 2020 à 13:32, Olivier Mattelaer <
>> <email address hidden>> a écrit :
>>
>>> Your question #689042 on MadGraph5_aMC@NLO changed:
>>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>>
>>> Olivier Mattelaer posted a new comment:
>>> I believe that this is a message from vim.
>>> Which version of vim do you have on your system?
>>> Does it open the file when you type "2" or does it not?
>>>
>>> If it does, you can edit the file and ignore this message.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>> --
>>> You received this question notification because you asked the question.
>>>
>>

Benslama Hana (hana2025) said : #9

Sorry for not sending the overall message at
once:#*********************************************************************
# 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 *
#*********************************************************************
     1 = lpp1 ! beam 1 type
     1 = lpp2 ! beam 2 type
     6500.0 = ebeam1 ! beam 1 total energy in GeV
     6500.0 = ebeam2 ! beam 2 total energy in GeV
# To see polarised beam options: type "update beam_pol"

#*********************************************************************
# 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"

#*********************************************************************
# 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) *
#*********************************************************************
 {} = 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) *
#*********************************************************************
 {} = 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 *
#*********************************************************************
#*********************************************************************
# Minimum and maximum invariant mass for pairs *
#*********************************************************************
 {} = 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.
#*********************************************************************
# Inclusive cuts *
#*********************************************************************
 0.0 = ptheavy ! minimum pt for at least one heavy final state
#*********************************************************************
# 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

                                         7,1 Top

Le ven. 28 févr. 2020 à 14:02, hana benslama <email address hidden>
a écrit :

> To launch the event I clicked on 0 the 2, but the above message is
> displayed
>
> Le ven. 28 févr. 2020 à 14:00, hana benslama <email address hidden>
> a écrit :
>
>> #*********************************************************************
>> # 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 *
>> #*********************************************************************
>> 1 = lpp1 ! beam 1 type
>> 1 = lpp2 ! beam 2 type
>> 6500.0 = ebeam1 ! beam 1 total energy in GeV
>> 6500.0 = ebeam2 ! beam 2 total energy in GeV
>> # To see polarised beam options: type "update beam_pol"
>>
>> #*********************************************************************
>> # 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"
>>
>> 7,1 Top
>>
>> Le ven. 28 févr. 2020 à 13:53, hana benslama <email address hidden>
>> a écrit :
>>
>>> Dear Olivier,
>>>
>>> When I write vim --version, the terminal displays that I can install it
>>> using sudo apt install, and I just do it at this moment (sudo apt install
>>> vim). For the file it is not opened, I'll try to send you all what appear
>>> in the consol.
>>>
>>> Le ven. 28 févr. 2020 à 13:32, Olivier Mattelaer <
>>> <email address hidden>> a écrit :
>>>
>>>> Your question #689042 on MadGraph5_aMC@NLO changed:
>>>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>>>
>>>> Olivier Mattelaer posted a new comment:
>>>> I believe that this is a message from vim.
>>>> Which version of vim do you have on your system?
>>>> Does it open the file when you type "2" or does it not?
>>>>
>>>> If it does, you can edit the file and ignore this message.
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> --
>>>> You received this question notification because you asked the question.
>>>>
>>>

Benslama Hana (hana2025) said : #10

I tried to modify the energy and Nb of eventsm but it does not allow me to
write anything

Le ven. 28 févr. 2020 à 14:09, hana benslama <email address hidden>
a écrit :

> Sorry for not sending the overall message at
> once:#*********************************************************************
> # 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 *
> #*********************************************************************
> 1 = lpp1 ! beam 1 type
> 1 = lpp2 ! beam 2 type
> 6500.0 = ebeam1 ! beam 1 total energy in GeV
> 6500.0 = ebeam2 ! beam 2 total energy in GeV
> # To see polarised beam options: type "update beam_pol"
>
> #*********************************************************************
> # 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"
>
> #*********************************************************************
> # 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) *
> #*********************************************************************
> {} = 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) *
> #*********************************************************************
> {} = 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 *
> #*********************************************************************
> #*********************************************************************
> # Minimum and maximum invariant mass for pairs *
> #*********************************************************************
> {} = 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.
> #*********************************************************************
> # Inclusive cuts *
> #*********************************************************************
> 0.0 = ptheavy ! minimum pt for at least one heavy final state
> #*********************************************************************
> # 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
>
> 7,1 Top
>
> Le ven. 28 févr. 2020 à 14:02, hana benslama <email address hidden>
> a écrit :
>
>> To launch the event I clicked on 0 the 2, but the above message is
>> displayed
>>
>> Le ven. 28 févr. 2020 à 14:00, hana benslama <email address hidden>
>> a écrit :
>>
>>> #*********************************************************************
>>> # 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 *
>>> #*********************************************************************
>>> 1 = lpp1 ! beam 1 type
>>> 1 = lpp2 ! beam 2 type
>>> 6500.0 = ebeam1 ! beam 1 total energy in GeV
>>> 6500.0 = ebeam2 ! beam 2 total energy in GeV
>>> # To see polarised beam options: type "update beam_pol"
>>>
>>> #*********************************************************************
>>> # 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"
>>>
>>> 7,1
>>> Top
>>>
>>> Le ven. 28 févr. 2020 à 13:53, hana benslama <
>>> <email address hidden>> a écrit :
>>>
>>>> Dear Olivier,
>>>>
>>>> When I write vim --version, the terminal displays that I can install it
>>>> using sudo apt install, and I just do it at this moment (sudo apt install
>>>> vim). For the file it is not opened, I'll try to send you all what appear
>>>> in the consol.
>>>>
>>>> Le ven. 28 févr. 2020 à 13:32, Olivier Mattelaer <
>>>> <email address hidden>> a écrit :
>>>>
>>>>> Your question #689042 on MadGraph5_aMC@NLO changed:
>>>>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>>>>
>>>>> Olivier Mattelaer posted a new comment:
>>>>> I believe that this is a message from vim.
>>>>> Which version of vim do you have on your system?
>>>>> Does it open the file when you type "2" or does it not?
>>>>>
>>>>> If it does, you can edit the file and ignore this message.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Olivier
>>>>>
>>>>> --
>>>>> You received this question notification because you asked the question.
>>>>>
>>>>

Benslama Hana (hana2025) said : #11

Sorry for not sending all what appear in the consol at once,
ry for not sending the overall message at
once:#*********************************************************************

# 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 *
#*********************************************************************
     1 = lpp1 ! beam 1 type
     1 = lpp2 ! beam 2 type
     6500.0 = ebeam1 ! beam 1 total energy in GeV
     6500.0 = ebeam2 ! beam 2 total energy in GeV
# To see polarised beam options: type "update beam_pol"

#*********************************************************************
# 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"

#*********************************************************************
# 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) *
#*********************************************************************
 {} = 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) *
#*********************************************************************
 {} = 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 *
#*********************************************************************
#*********************************************************************
# Minimum and maximum invariant mass for pairs *
#*********************************************************************
 {} = 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.
#*********************************************************************
# Inclusive cuts *
#*********************************************************************
 0.0 = ptheavy ! minimum pt for at least one heavy final state
#*********************************************************************
# 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

Le ven. 28 févr. 2020 à 14:12, Benslama Hana <
<email address hidden>> a écrit :

> Your question #689042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/689042
>
> Benslama Hana posted a new comment:
> Sorry for not sending the overall message at
> once:#*********************************************************************
> # 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 *
> #*********************************************************************
> 1 = lpp1 ! beam 1 type
> 1 = lpp2 ! beam 2 type
> 6500.0 = ebeam1 ! beam 1 total energy in GeV
> 6500.0 = ebeam2 ! beam 2 total energy in GeV
> # To see polarised beam options: type "update beam_pol"
>
> #*********************************************************************
> # 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"
>
> #*********************************************************************
> # 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) *
> #*********************************************************************
> {} = 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) *
> #*********************************************************************
> {} = 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 *
> #*********************************************************************
> #*********************************************************************
> # Minimum and maximum invariant mass for pairs *
> #*********************************************************************
> {} = 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.
> #*********************************************************************
> # Inclusive cuts *
> #*********************************************************************
> 0.0 = ptheavy ! minimum pt for at least one heavy final state
> #*********************************************************************
> # 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
>
> 7,1 Top
>
> Le ven. 28 févr. 2020 à 14:02, hana benslama <email address hidden>
> a écrit :
>
> > To launch the event I clicked on 0 the 2, but the above message is
> > displayed
> >
> > Le ven. 28 févr. 2020 à 14:00, hana benslama <
> <email address hidden>>
> > a écrit :
> >
> >> #*********************************************************************
> >> # 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 *
> >> #*********************************************************************
> >> 1 = lpp1 ! beam 1 type
> >> 1 = lpp2 ! beam 2 type
> >> 6500.0 = ebeam1 ! beam 1 total energy in GeV
> >> 6500.0 = ebeam2 ! beam 2 total energy in GeV
> >> # To see polarised beam options: type "update beam_pol"
> >>
> >> #*********************************************************************
> >> # 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"
> >>
> >> 7,1
> Top
> >>
> >> Le ven. 28 févr. 2020 à 13:53, hana benslama <
> <email address hidden>>
> >> a écrit :
> >>
> >>> Dear Olivier,
> >>>
> >>> When I write vim --version, the terminal displays that I can install it
> >>> using sudo apt install, and I just do it at this moment (sudo apt
> install
> >>> vim). For the file it is not opened, I'll try to send you all what
> appear
> >>> in the consol.
> >>>
> >>> Le ven. 28 févr. 2020 à 13:32, Olivier Mattelaer <
> >>> <email address hidden>> a écrit :
> >>>
> >>>> Your question #689042 on MadGraph5_aMC@NLO changed:
> >>>> https://answers.launchpad.net/mg5amcnlo/+question/689042
> >>>>
> >>>> Olivier Mattelaer posted a new comment:
> >>>> I believe that this is a message from vim.
> >>>> Which version of vim do you have on your system?
> >>>> Does it open the file when you type "2" or does it not?
> >>>>
> >>>> If it does, you can edit the file and ignore this message.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Olivier
> >>>>
> >>>> --
> >>>> You received this question notification because you asked the
> question.
> >>>>
> >>>
>
> --
> You received this question notification because you asked the question.
>

Hi,

Ok this sounds to work ok now.
In order to pass in edit mode for vim,
you need to type "i"
and when you are done you have to press escape then ":x"

Cheers,

Olivier

PS: a simpler way to edit the beam energy/number of events is to type (instead of "2")
set ebeam 25k # change each beam to 25TeV
set nevents 100k # change number of events to 100000

Cheers,

Olivier

Benslama Hana (hana2025) said : #13

Hi,
A great thanks should be given to you for all your helps.
For the energy I put :set ebeam 4000.0 # change each beam to 4000Gev
For tne Nb of events: set nevents 1000 # change number of events to 1000
and when I opened the file that contains the information of the event I
found the value of the energy changed but the number of events did not
change, could you show me how to put 1000 events, please?

Le ven. 28 févr. 2020 à 14:32, Olivier Mattelaer <
<email address hidden>> a écrit :

> Your question #689042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/689042
>
> Olivier Mattelaer posted a new comment:
> Hi,
>
> Ok this sounds to work ok now.
> In order to pass in edit mode for vim,
> you need to type "i"
> and when you are done you have to press escape then ":x"
>
> Cheers,
>
> Olivier
>
> PS: a simpler way to edit the beam energy/number of events is to type
> (instead of "2")
> set ebeam 25k # change each beam to 25TeV
> set nevents 100k # change number of events to 100000
>
> Cheers,
>
> Olivier
>
> --
> You received this question notification because you asked the question.
>

HI,

Do you have an error/warning when typing
"set nevents 1000"
In principle you should have an information message stating if the change was applied or not.

Cheers,

Olivier

> On 28 Feb 2020, at 15:08, Benslama Hana <email address hidden> wrote:
>
> Question #689042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/689042
>
> Benslama Hana posted a new comment:
> Hi,
> A great thanks should be given to you for all your helps.
> For the energy I put :set ebeam 4000.0 # change each beam to 4000Gev
> For tne Nb of events: set nevents 1000 # change number of events to 1000
> and when I opened the file that contains the information of the event I
> found the value of the energy changed but the number of events did not
> change, could you show me how to put 1000 events, please?
>
> Le ven. 28 févr. 2020 à 14:32, Olivier Mattelaer <
> <email address hidden>> a écrit :
>
>> Your question #689042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>
>> Olivier Mattelaer posted a new comment:
>> Hi,
>>
>> Ok this sounds to work ok now.
>> In order to pass in edit mode for vim,
>> you need to type "i"
>> and when you are done you have to press escape then ":x"
>>
>> Cheers,
>>
>> Olivier
>>
>> PS: a simpler way to edit the beam energy/number of events is to type
>> (instead of "2")
>> set ebeam 25k # change each beam to 25TeV
>> set nevents 100k # change number of events to 100000
>>
>> Cheers,
>>
>> Olivier
>>
>> --
>> You received this question notification because you asked the question.
>>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Benslama Hana (hana2025) said : #15

Hi,

Yes I have a warning zritten in bleu :1000.0 # change number of events to
1000 can not be mapped to an integer

Hana,

Le ven. 28 févr. 2020 à 15:12, Olivier Mattelaer <
<email address hidden>> a écrit :

> Your question #689042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/689042
>
> Olivier Mattelaer posted a new comment:
> HI,
>
> Do you have an error/warning when typing
> "set nevents 1000"
> In principle you should have an information message stating if the change
> was applied or not.
>
> Cheers,
>
> Olivier
>
> > On 28 Feb 2020, at 15:08, Benslama Hana <
> <email address hidden>> wrote:
> >
> > Question #689042 on MadGraph5_aMC@NLO changed:
> > https://answers.launchpad.net/mg5amcnlo/+question/689042
> >
> > Benslama Hana posted a new comment:
> > Hi,
> > A great thanks should be given to you for all your helps.
> > For the energy I put :set ebeam 4000.0 # change each beam to 4000Gev
> > For tne Nb of events: set nevents 1000 # change number of events to 1000
> > and when I opened the file that contains the information of the event I
> > found the value of the energy changed but the number of events did not
> > change, could you show me how to put 1000 events, please?
> >
> > Le ven. 28 févr. 2020 à 14:32, Olivier Mattelaer <
> > <email address hidden>> a écrit :
> >
> >> Your question #689042 on MadGraph5_aMC@NLO changed:
> >> https://answers.launchpad.net/mg5amcnlo/+question/689042
> >>
> >> Olivier Mattelaer posted a new comment:
> >> Hi,
> >>
> >> Ok this sounds to work ok now.
> >> In order to pass in edit mode for vim,
> >> you need to type "i"
> >> and when you are done you have to press escape then ":x"
> >>
> >> Cheers,
> >>
> >> Olivier
> >>
> >> PS: a simpler way to edit the beam energy/number of events is to type
> >> (instead of "2")
> >> set ebeam 25k # change each beam to 25TeV
> >> set nevents 100k # change number of events to 100000
> >>
> >> Cheers,
> >>
> >> Olivier
> >>
> >> --
> >> You received this question notification because you asked the question.
> >>
> >
> > --
> > You received this question notification because you are an answer
> > contact for MadGraph5_aMC@NLO.
>
> --
> You received this question notification because you asked the question.
>

Hi,

Just do
set nevents 1000
not
1000.0 # change number of events to 1000
The # and comment afterwards does not be put here

Cheers,

Olivier

> On 28 Feb 2020, at 16:08, Benslama Hana <email address hidden> wrote:
>
> Question #689042 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/689042
>
> Benslama Hana posted a new comment:
> Hi,
>
> Yes I have a warning zritten in bleu :1000.0 # change number of events to
> 1000 can not be mapped to an integer
>
> Hana,
>
> Le ven. 28 févr. 2020 à 15:12, Olivier Mattelaer <
> <email address hidden>> a écrit :
>
>> Your question #689042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>
>> Olivier Mattelaer posted a new comment:
>> HI,
>>
>> Do you have an error/warning when typing
>> "set nevents 1000"
>> In principle you should have an information message stating if the change
>> was applied or not.
>>
>> Cheers,
>>
>> Olivier
>>
>>> On 28 Feb 2020, at 15:08, Benslama Hana <
>> <email address hidden>> wrote:
>>>
>>> Question #689042 on MadGraph5_aMC@NLO changed:
>>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>>
>>> Benslama Hana posted a new comment:
>>> Hi,
>>> A great thanks should be given to you for all your helps.
>>> For the energy I put :set ebeam 4000.0 # change each beam to 4000Gev
>>> For tne Nb of events: set nevents 1000 # change number of events to 1000
>>> and when I opened the file that contains the information of the event I
>>> found the value of the energy changed but the number of events did not
>>> change, could you show me how to put 1000 events, please?
>>>
>>> Le ven. 28 févr. 2020 à 14:32, Olivier Mattelaer <
>>> <email address hidden>> a écrit :
>>>
>>>> Your question #689042 on MadGraph5_aMC@NLO changed:
>>>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>>>
>>>> Olivier Mattelaer posted a new comment:
>>>> Hi,
>>>>
>>>> Ok this sounds to work ok now.
>>>> In order to pass in edit mode for vim,
>>>> you need to type "i"
>>>> and when you are done you have to press escape then ":x"
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> PS: a simpler way to edit the beam energy/number of events is to type
>>>> (instead of "2")
>>>> set ebeam 25k # change each beam to 25TeV
>>>> set nevents 100k # change number of events to 100000
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> --
>>>> You received this question notification because you asked the question.
>>>>
>>>
>>> --
>>> You received this question notification because you are an answer
>>> contact for MadGraph5_aMC@NLO.
>>
>> --
>> You received this question notification because you asked the question.
>>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Benslama Hana (hana2025) said : #17

Hi,

For the nb of events the change was not applied,

Le ven. 28 févr. 2020 à 16:03, hana benslama <email address hidden>
a écrit :

> Hi,
>
> Yes I have a warning zritten in bleu :1000.0 # change number of events to
> 1000 can not be mapped to an integer
>
> Hana,
>
> Le ven. 28 févr. 2020 à 15:12, Olivier Mattelaer <
> <email address hidden>> a écrit :
>
>> Your question #689042 on MadGraph5_aMC@NLO changed:
>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>
>> Olivier Mattelaer posted a new comment:
>> HI,
>>
>> Do you have an error/warning when typing
>> "set nevents 1000"
>> In principle you should have an information message stating if the change
>> was applied or not.
>>
>> Cheers,
>>
>> Olivier
>>
>> > On 28 Feb 2020, at 15:08, Benslama Hana <
>> <email address hidden>> wrote:
>> >
>> > Question #689042 on MadGraph5_aMC@NLO changed:
>> > https://answers.launchpad.net/mg5amcnlo/+question/689042
>> >
>> > Benslama Hana posted a new comment:
>> > Hi,
>> > A great thanks should be given to you for all your helps.
>> > For the energy I put :set ebeam 4000.0 # change each beam to 4000Gev
>> > For tne Nb of events: set nevents 1000 # change number of events to 1000
>> > and when I opened the file that contains the information of the event I
>> > found the value of the energy changed but the number of events did not
>> > change, could you show me how to put 1000 events, please?
>> >
>> > Le ven. 28 févr. 2020 à 14:32, Olivier Mattelaer <
>> > <email address hidden>> a écrit :
>> >
>> >> Your question #689042 on MadGraph5_aMC@NLO changed:
>> >> https://answers.launchpad.net/mg5amcnlo/+question/689042
>> >>
>> >> Olivier Mattelaer posted a new comment:
>> >> Hi,
>> >>
>> >> Ok this sounds to work ok now.
>> >> In order to pass in edit mode for vim,
>> >> you need to type "i"
>> >> and when you are done you have to press escape then ":x"
>> >>
>> >> Cheers,
>> >>
>> >> Olivier
>> >>
>> >> PS: a simpler way to edit the beam energy/number of events is to type
>> >> (instead of "2")
>> >> set ebeam 25k # change each beam to 25TeV
>> >> set nevents 100k # change number of events to 100000
>> >>
>> >> Cheers,
>> >>
>> >> Olivier
>> >>
>> >> --
>> >> You received this question notification because you asked the question.
>> >>
>> >
>> > --
>> > You received this question notification because you are an answer
>> > contact for MadGraph5_aMC@NLO.
>>
>> --
>> You received this question notification because you asked the question.
>>
>

Benslama Hana (hana2025) said : #18

Thak you extremely much, now I put:
set ebeam1 4000
set ebeam2 4000
set nevents 1000
Then I have seen an information message stating that the change is applied,

with my best regards,
Hanam

Le ven. 28 févr. 2020 à 16:38, hana benslama <email address hidden>
a écrit :

> Hi,
>
> For the nb of events the change was not applied,
>
> Le ven. 28 févr. 2020 à 16:03, hana benslama <email address hidden>
> a écrit :
>
>> Hi,
>>
>> Yes I have a warning zritten in bleu :1000.0 # change number of events to
>> 1000 can not be mapped to an integer
>>
>> Hana,
>>
>> Le ven. 28 févr. 2020 à 15:12, Olivier Mattelaer <
>> <email address hidden>> a écrit :
>>
>>> Your question #689042 on MadGraph5_aMC@NLO changed:
>>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>>
>>> Olivier Mattelaer posted a new comment:
>>> HI,
>>>
>>> Do you have an error/warning when typing
>>> "set nevents 1000"
>>> In principle you should have an information message stating if the
>>> change was applied or not.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>> > On 28 Feb 2020, at 15:08, Benslama Hana <
>>> <email address hidden>> wrote:
>>> >
>>> > Question #689042 on MadGraph5_aMC@NLO changed:
>>> > https://answers.launchpad.net/mg5amcnlo/+question/689042
>>> >
>>> > Benslama Hana posted a new comment:
>>> > Hi,
>>> > A great thanks should be given to you for all your helps.
>>> > For the energy I put :set ebeam 4000.0 # change each beam to 4000Gev
>>> > For tne Nb of events: set nevents 1000 # change number of events to
>>> 1000
>>> > and when I opened the file that contains the information of the event I
>>> > found the value of the energy changed but the number of events did not
>>> > change, could you show me how to put 1000 events, please?
>>> >
>>> > Le ven. 28 févr. 2020 à 14:32, Olivier Mattelaer <
>>> > <email address hidden>> a écrit :
>>> >
>>> >> Your question #689042 on MadGraph5_aMC@NLO changed:
>>> >> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>> >>
>>> >> Olivier Mattelaer posted a new comment:
>>> >> Hi,
>>> >>
>>> >> Ok this sounds to work ok now.
>>> >> In order to pass in edit mode for vim,
>>> >> you need to type "i"
>>> >> and when you are done you have to press escape then ":x"
>>> >>
>>> >> Cheers,
>>> >>
>>> >> Olivier
>>> >>
>>> >> PS: a simpler way to edit the beam energy/number of events is to type
>>> >> (instead of "2")
>>> >> set ebeam 25k # change each beam to 25TeV
>>> >> set nevents 100k # change number of events to 100000
>>> >>
>>> >> Cheers,
>>> >>
>>> >> Olivier
>>> >>
>>> >> --
>>> >> You received this question notification because you asked the
>>> question.
>>> >>
>>> >
>>> > --
>>> > You received this question notification because you are an answer
>>> > contact for MadGraph5_aMC@NLO.
>>>
>>> --
>>> You received this question notification because you asked the question.
>>>
>>

Benslama Hana (hana2025) said : #19

Yes I jus put
set nevents 1000

Le ven. 28 févr. 2020 à 16:47, hana benslama <email address hidden>
a écrit :

> Thak you extremely much, now I put:
> set ebeam1 4000
> set ebeam2 4000
> set nevents 1000
> Then I have seen an information message stating that the change is applied,
>
> with my best regards,
> Hanam
>
> Le ven. 28 févr. 2020 à 16:38, hana benslama <email address hidden>
> a écrit :
>
>> Hi,
>>
>> For the nb of events the change was not applied,
>>
>> Le ven. 28 févr. 2020 à 16:03, hana benslama <email address hidden>
>> a écrit :
>>
>>> Hi,
>>>
>>> Yes I have a warning zritten in bleu :1000.0 # change number of events
>>> to 1000 can not be mapped to an integer
>>>
>>> Hana,
>>>
>>> Le ven. 28 févr. 2020 à 15:12, Olivier Mattelaer <
>>> <email address hidden>> a écrit :
>>>
>>>> Your question #689042 on MadGraph5_aMC@NLO changed:
>>>> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>>>
>>>> Olivier Mattelaer posted a new comment:
>>>> HI,
>>>>
>>>> Do you have an error/warning when typing
>>>> "set nevents 1000"
>>>> In principle you should have an information message stating if the
>>>> change was applied or not.
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> > On 28 Feb 2020, at 15:08, Benslama Hana <
>>>> <email address hidden>> wrote:
>>>> >
>>>> > Question #689042 on MadGraph5_aMC@NLO changed:
>>>> > https://answers.launchpad.net/mg5amcnlo/+question/689042
>>>> >
>>>> > Benslama Hana posted a new comment:
>>>> > Hi,
>>>> > A great thanks should be given to you for all your helps.
>>>> > For the energy I put :set ebeam 4000.0 # change each beam to 4000Gev
>>>> > For tne Nb of events: set nevents 1000 # change number of events to
>>>> 1000
>>>> > and when I opened the file that contains the information of the event
>>>> I
>>>> > found the value of the energy changed but the number of events did not
>>>> > change, could you show me how to put 1000 events, please?
>>>> >
>>>> > Le ven. 28 févr. 2020 à 14:32, Olivier Mattelaer <
>>>> > <email address hidden>> a écrit :
>>>> >
>>>> >> Your question #689042 on MadGraph5_aMC@NLO changed:
>>>> >> https://answers.launchpad.net/mg5amcnlo/+question/689042
>>>> >>
>>>> >> Olivier Mattelaer posted a new comment:
>>>> >> Hi,
>>>> >>
>>>> >> Ok this sounds to work ok now.
>>>> >> In order to pass in edit mode for vim,
>>>> >> you need to type "i"
>>>> >> and when you are done you have to press escape then ":x"
>>>> >>
>>>> >> Cheers,
>>>> >>
>>>> >> Olivier
>>>> >>
>>>> >> PS: a simpler way to edit the beam energy/number of events is to type
>>>> >> (instead of "2")
>>>> >> set ebeam 25k # change each beam to 25TeV
>>>> >> set nevents 100k # change number of events to 100000
>>>> >>
>>>> >> Cheers,
>>>> >>
>>>> >> Olivier
>>>> >>
>>>> >> --
>>>> >> You received this question notification because you asked the
>>>> question.
>>>> >>
>>>> >
>>>> > --
>>>> > You received this question notification because you are an answer
>>>> > contact for MadGraph5_aMC@NLO.
>>>>
>>>> --
>>>> You received this question notification because you asked the question.
>>>>
>>>