Error in generating events from gridpack

Hi,

This looks like a formatting problem of one of your input card.
That one entry which is suppose to be an integer is not written as an integer.

Is it possible that the number of requested number that you asked for is a float?
I said that since i see this line:
> 16:48:57 Now generating 11.0 events with random seed 123456 and granularity -1

Otherwise, i would need a copy of the run_card to check which parameter might be the problematic one.

Cheers,

Olivier

> On Nov 9, 2016, at 17:43, Monica Trovatelli <email address hidden> wrote:
>
> New question #403923 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/403923
>
> Hi,
> I'm having some problems in generating events from a gridpack for the following LO process:
> generate p p > h > j j e+ e- vm vm~ QCD=0 QED=6
> add process p p > h > j j mu+ mu- ve ve~ QCD=0 QED=6
>
> The madgraph version I'm using is the 2_3_3.
> The gridpack apparently is succesfully created (I tried both locally and on the cluster), but when I start to generate events I get the following errors:
>
> 16:48:57 Now generating 11.0 events with random seed 123456 and granularity -1
> 16:48:58 P1_qq_qqllvlvl
> 16:49:12 P2_qq_qqllvlvl
> 16:49:25 At line 354 of file rw_routines.f
> 16:49:25 Fortran runtime error: Bad integer for item 1 in list input
> 16:49:25 At line 354 of file rw_routines.f
> 16:49:25 Fortran runtime error: Bad integer for item 1 in list input
> 16:49:36 No handlers could be found for logger "madevent.stdout"
>
> do you have any hint on what is going on here? or any suggestion about how to check if something went wrong at the level of the gridpack creation?
> Of course I'm using the same setup to both producing the gridpack and generating the events.
>
> Thanks a lot for any help!
>
> Best Regards,
> Monica
>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,
many thanks for your fast feedback!

>Is it possible that the number of requested number that you asked for is a float?
>I said that since i see this line:
>> 16:48:57 Now generating 11.0 events with random seed 123456 and granularity -1

I don't think this is the problem, since I correctly see in the run_card that it setting 11 events:
 11 = nevents ! Number of unweighted events requested

but your comment made me think that I'm also modifying the param_card to change the Higgs width & mass, it can really be that I'm making something wrong there, since it took my a lot of time to understand how to modify it from my JO. The param_card looks like this (look the MH and the DECAY of the Higgs in particular);

###################################
## INFORMATION FOR MASS
###################################
Block mass
    5 4.700000e+00 # MB
    6 1.725000e+02 # MT
   15 1.776820e+00 # MTA
   23 9.118760e+01 # MZ
   25 1.250000e+02 #
## 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
  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.399000 # 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.323489e+02 # aEWM1
    2 1.166370e-05 # Gf
    3 1.184000e-01 # aS

###################################
## INFORMATION FOR YUKAWA
###################################
Block yukawa
    5 4.700000e+00 # ymb
    6 1.725000e+02 # ymt
   15 1.777000e+00 # ymtau
###################################
## INFORMATION FOR DECAY
###################################
DECAY 6 1.320000e+00 # WT
DECAY 23 2.495200e+00 # WZ
DECAY 24 2.085000e+00 # WW
DECAY 25 4.097e-03
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

Again thank you!

Cheers,
Monica

Hi,

> I don't think this is the problem, since I correctly see in the run_card that it setting 11 events:
> 11 = nevents ! Number of unweighted events requested

The run_card is not expected to be modified neither by you or by the gridpack.
And clearly this parameter is not used.

On the other hand, if I run the gridpack with the command
./run.sh 11.0 123456
then I reproduce your crash
but if i do
./run.sh 11 123456
then it runs as expected.

So I’m quite confident that the problem is your input format.

Cheers,

Olivier

> On Nov 9, 2016, at 18:42, Monica Trovatelli <email address hidden> wrote:
>
> Question #403923 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/403923
>
> Status: Answered => Open
>
> Monica Trovatelli is still having a problem:
> Hi Olivier,
> many thanks for your fast feedback!
>
>> Is it possible that the number of requested number that you asked for is a float?
>> I said that since i see this line:
>>> 16:48:57 Now generating 11.0 events with random seed 123456 and granularity -1
>
> I don't think this is the problem, since I correctly see in the run_card that it setting 11 events:
> 11 = nevents ! Number of unweighted events requested
>
> but your comment made me think that I'm also modifying the param_card to
> change the Higgs width & mass, it can really be that I'm making
> something wrong there, since it took my a lot of time to understand how
> to modify it from my JO. The param_card looks like this (look the MH
> and the DECAY of the Higgs in particular);
>
> ###################################
> ## INFORMATION FOR MASS
> ###################################
> Block mass
> 5 4.700000e+00 # MB
> 6 1.725000e+02 # MT
> 15 1.776820e+00 # MTA
> 23 9.118760e+01 # MZ
> 25 1.250000e+02 #
> ## 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
> 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.399000 # 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.323489e+02 # aEWM1
> 2 1.166370e-05 # Gf
> 3 1.184000e-01 # aS
>
> ###################################
> ## INFORMATION FOR YUKAWA
> ###################################
> Block yukawa
> 5 4.700000e+00 # ymb
> 6 1.725000e+02 # ymt
> 15 1.777000e+00 # ymtau
> ###################################
> ## INFORMATION FOR DECAY
> ###################################
> DECAY 6 1.320000e+00 # WT
> DECAY 23 2.495200e+00 # WZ
> DECAY 24 2.085000e+00 # WW
> DECAY 25 4.097e-03
> 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
>
> Again thank you!
>
> Cheers,
> Monica
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,
I'm happy to tell you that it worked!
I was a bit confused since actually the 11.0 worked if I don't use the gridpack mode of running.

Anyway, thanks a lot for the help, this solved my question.

Cheers,
Monica