Error when reading SubProcesses/P1_gu_mumvlmupmupd/G1/results.dat

I am getting suggestion

Survey return zero cross section.
   Typical reasons are the following:
   1) A massive s-channel particle has a width set to zero.
   2) The pdf are zero for at least one of the initial state particles
      or you are using maxjetflavor=4 for initial state b:s.
   3) The cuts are too strong.
   Please check/correct your param_card and/or your run_card.

i put the width to be Auto
DECAY 23 Auto # WZ
DECAY 24 Auto # WW
DECAY 25 Auto # WH
DECAY 999888 Auto # ZpW

================================
detailed output
==============================
INFO: Get two body decay from FeynRules formula
Results written to /afs/cern.ch/work/m/muahmad/CMSSW_7_6_0/src/MG5_aMC_v2_4_2/PROC_Leptophilic_UFO_14/Cards/param_card.dat
INFO: get decay diagram for w+
Vertexlist of this model has not been searched.Automatically run the model.find_vertexlist()
Found 3 stable particles
INFO: get decay diagram for h
INFO: get decay diagram for zp
INFO: current estimated error: 1.0 go to 4-body decay:
INFO: stop to 4.0 body-decay. approximate error: 1.0
Pass to numerical integration for computing the widths:
INFO: More info in temporary files:
    /afs/cern.ch/work/m/muahmad/CMSSW_7_6_0/src/MG5_aMC_v2_4_2/tmpEPQIpW/temp_decay/index.html
Results written to /afs/cern.ch/work/m/muahmad/CMSSW_7_6_0/src/MG5_aMC_v2_4_2/PROC_Leptophilic_UFO_14/Cards/param_card.dat
INFO: Update the dependent parameter of the param_card.dat
Generating 10000 events with run name run_01
survey run_01
INFO: compile directory
compile Source Directory
Using random number seed offset = 21
INFO: Running Survey
Creating Jobs
Working on SubProcesses
INFO: P1_gu_mumvlmupmupd
INFO: Idle: 1, Running: 1, Completed: 0 [ current time: 22h08 ]
INFO: Idle: 0, Running: 1, Completed: 1 [ 8.8s ]
INFO: Idle: 0, Running: 0, Completed: 2 [ 9.2s ]
INFO: End survey
refine 10000
Creating Jobs
INFO: Refine results to 10000
INFO: Generating 10000.0 unweigthed events.
INFO: Effective Luminosity 1.2e+103 pb^-1
INFO: need to improve 0 channels
Survey return zero cross section.
   Typical reasons are the following:
   1) A massive s-channel particle has a width set to zero.
   2) The pdf are zero for at least one of the initial state particles
      or you are using maxjetflavor=4 for initial state b:s.
   3) The cuts are too strong.
   Please check/correct your param_card and/or your run_card.

=================================
Looks like this model does not support for this process ? i am correct? or any other reason?

Hi,

Is the computation of the width works correctly?
I'm worried that the width is estimated with 100% error:
> INFO: stop to 4.0 body-decay. approximate error: 1.0

The computation of the width is not yet finished but which value does it returns?
If the width is very small compare to the mass, then you might face some numerical inacurracy.

Cheers,

Olivier

>
> On 31 Aug 2017, at 22:14, Muhammad Ahmad <email address hidden> wrote:
>
> Question #657215 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/657215
>
> Muhammad Ahmad gave more information on the question:
> I am getting suggestion
>
> Survey return zero cross section.
> Typical reasons are the following:
> 1) A massive s-channel particle has a width set to zero.
> 2) The pdf are zero for at least one of the initial state particles
> or you are using maxjetflavor=4 for initial state b:s.
> 3) The cuts are too strong.
> Please check/correct your param_card and/or your run_card.
>
> i put the width to be Auto
> DECAY 23 Auto # WZ
> DECAY 24 Auto # WW
> DECAY 25 Auto # WH
> DECAY 999888 Auto # ZpW
>
>
> ================================
> detailed output
> ==============================
> INFO: Get two body decay from FeynRules formula
> Results written to /afs/cern.ch/work/m/muahmad/CMSSW_7_6_0/src/MG5_aMC_v2_4_2/PROC_Leptophilic_UFO_14/Cards/param_card.dat
> INFO: get decay diagram for w+
> Vertexlist of this model has not been searched.Automatically run the model.find_vertexlist()
> Found 3 stable particles
> INFO: get decay diagram for h
> INFO: get decay diagram for zp
> INFO: current estimated error: 1.0 go to 4-body decay:
> INFO: stop to 4.0 body-decay. approximate error: 1.0
> Pass to numerical integration for computing the widths:
> INFO: More info in temporary files:
> /afs/cern.ch/work/m/muahmad/CMSSW_7_6_0/src/MG5_aMC_v2_4_2/tmpEPQIpW/temp_decay/index.html
> Results written to /afs/cern.ch/work/m/muahmad/CMSSW_7_6_0/src/MG5_aMC_v2_4_2/PROC_Leptophilic_UFO_14/Cards/param_card.dat
> INFO: Update the dependent parameter of the param_card.dat
> Generating 10000 events with run name run_01
> survey run_01
> INFO: compile directory
> compile Source Directory
> Using random number seed offset = 21
> INFO: Running Survey
> Creating Jobs
> Working on SubProcesses
> INFO: P1_gu_mumvlmupmupd
> INFO: Idle: 1, Running: 1, Completed: 0 [ current time: 22h08 ]
> INFO: Idle: 0, Running: 1, Completed: 1 [ 8.8s ]
> INFO: Idle: 0, Running: 0, Completed: 2 [ 9.2s ]
> INFO: End survey
> refine 10000
> Creating Jobs
> INFO: Refine results to 10000
> INFO: Generating 10000.0 unweigthed events.
> INFO: Effective Luminosity 1.2e+103 pb^-1
> INFO: need to improve 0 channels
> Survey return zero cross section.
> Typical reasons are the following:
> 1) A massive s-channel particle has a width set to zero.
> 2) The pdf are zero for at least one of the initial state particles
> or you are using maxjetflavor=4 for initial state b:s.
> 3) The cuts are too strong.
> Please check/correct your param_card and/or your run_card.
>
> =================================
> Looks like this model does not support for this process ? i am correct? or any other reason?
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Here is what i have tested now
Keeping every thing same in param_cards.dat except followings

Zp Mass 15 GeV
couplings to muon 0.1
couplings to tau. 0.1
couplings to electron 0.0

DECAY 23 Auto # WZ
DECAY 24 Auto # WW
DECAY 25 Auto # WH
DECAY 999888 Auto # ZpW

In cards i got width for ZpW = 0.00000 (which is problematic i guess)

Hi,

Yes that's the problem.
Without the model, I'm not able to understand why the Auto method returns zero. (And if this is a bug or not)
My advise would be that you compute the width with another method and input it manually.

Cheers,

Olivier

> On 1 Sep 2017, at 10:09, Muhammad Ahmad <email address hidden> wrote:
>
> Question #657215 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/657215
>
> Status: Answered => Open
>
> Muhammad Ahmad is still having a problem:
> Here is what i have tested now
> Keeping every thing same in param_cards.dat except followings
>
> Zp Mass 15 GeV
> couplings to muon 0.1
> couplings to tau. 0.1
> couplings to electron 0.0
>
>
> DECAY 23 Auto # WZ
> DECAY 24 Auto # WW
> DECAY 25 Auto # WH
> DECAY 999888 Auto # ZpW
>
>
> In cards i got width for ZpW = 0.00000 (which is problematic i guess)
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi,
Thanks for advice,

the model is given here, http://cafpe.ugr.es/index.php/pages/other/software
in case you want to have a look

Another process using same model works for me which is similar
generate p p > zp > mu mu mu mu / h

which is essentially very close to
generate p p > zp > mu v mu mu / h

so i am putting the width by hand coming from calculation from first process to second (corresponds to same mass point of Zp). Lets see how it goes now.....

Hi,

Do I understand correctly that if you ask:
> generate p p > zp > mu mu mu mu / h
Then the width of the zp is computed correctly (at least non zero)?
Since the "Auto" run is in principle independent of the computation that you are doing, this is really surprising to me.

Now, I was not too surprise that this one was computing a number even if the width was wrongly set to zero.
The point is that your mass for zp is quite small and therefore your cut on the final state particle can be enough to forbid the Zp to
Be on shell and hit the singularity not protected by the width.

Obviously, depending of the real value of the width such number can be meaningless if the width is set to zero.

Cheers,

Olivier

> On 1 Sep 2017, at 12:17, Muhammad Ahmad <email address hidden> wrote:
>
> Question #657215 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/657215
>
> Status: Answered => Open
>
> Muhammad Ahmad is still having a problem:
> Hi,
> Thanks for advice,
>
> the model is given here, http://cafpe.ugr.es/index.php/pages/other/software
> in case you want to have a look
>
>
> Another process using same model works for me which is similar
> generate p p > zp > mu mu mu mu / h
>
> which is essentially very close to
> generate p p > zp > mu v mu mu / h
>
> so i am putting the width by hand coming from calculation from first
> process to second (corresponds to same mass point of Zp). Lets see how
> it goes now.....
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Yes if generate

> generate p p > zp > mu mu mu mu / h
 addprocess p p > zp > mu mu mu mu j / h

its gives me 11.9 MeV (width) for Zp' mass 15 GeV with reasonable cross section 0.28 pb ( i have almost no cuts at final particles)

i tried to do similar through W boson

> generate p p > zp > mu v mu mu / h

works but when i add jet
 addprocess p p > zp > mu v mu mu j / h

it breaks

Hi,

I have downloaded your model, and I would suggest you to read:
https://answers.launchpad.net/mg5amcnlo/+faq/2312
In order to allow a huge gain in speed.

Otherwise, I have run the following script (in my case within 2.6.0)
> import model /Users/omattelaer/Desktop/UFOMODEL/Leptophilic_UFO1
> define l+ = ta+ mu+
> define l- = ta- mu-
> define p = g u c d s b u~ c~ d~ s~ b~
> define j = g u c d s b u~ c~ d~ s~ b~
> define mu = mu+ mu-
> define v = vm vm~
> generate p p > zp > mu v mu mu / h
> output
> launch
> set mass 999888 15
> set width 999888 Auto
> set zpinputs 3 0.1
> set zpinputs 4 0.1
> set zpinputs 5 0.1
> set zpinputs 6 0.1

In that case, the width computed is:
#
# PDG Width
DECAY 999888 1.193183e-02
# BR NDA ID1 ID2 ...
   3.334672e-01 2 13 -13 # 0.00397887351852
   3.330655e-01 2 15 -15 # 0.00397408055615
   1.667336e-01 2 16 -16 # 0.00198943678865
   1.667336e-01 2 14 -14 # 0.00198943678865

And the cross-section is:
#***************************************************************************
#
# original cross-section: 0.0835911151729
# scale variation: +13.9% -14.7%
# central scheme variation: + 0% -18.1%
# PDF variation: +3.09% -3.09%
#
# dynamical scheme # 1 : 0.0808421 +14.6% -15.3% # \sum ET
# dynamical scheme # 2 : 0.0808423 +14.6% -15.3% # \sum\sqrt{m^2+pt^2}
# dynamical scheme # 3 : 0.0684527 +18.1% -18.6% # 0.5 \sum\sqrt{m^2+pt^2}
# dynamical scheme # 4 : 0.0835911 +13.9% -14.7% # \sqrt{\hat s}
#***************************************************************************

If I run the following script:
> import model /Users/omattelaer/Desktop/UFOMODEL/Leptophilic_UFO1
> define l+ = ta+ mu+
> define l- = ta- mu-
> define p = g u c d s b u~ c~ d~ s~ b~
> define j = g u c d s b u~ c~ d~ s~ b~
> define mu = mu+ mu-
> define v = vm vm~
> generate p p > zp > mu v mu mu j / h
> output
> launch
> set mass 999888 15
> set width 999888 Auto
> set zpinputs 3 0.1
> set zpinputs 4 0.1
> set zpinputs 5 0.1
> set zpinputs 6 0.1

Then the width computed is (the same as expected):
#
# PDG Width
DECAY 999888 1.193183e-02
# BR NDA ID1 ID2 ...
   3.334672e-01 2 13 -13 # 0.00397887351852
   3.330655e-01 2 15 -15 # 0.00397408055615
   1.667336e-01 2 16 -16 # 0.00198943678865
   1.667336e-01 2 14 -14 # 0.00198943678865

And the cross-section is:
#***************************************************************************
#
# original cross-section: 0.0420658055202
# scale variation: +18.5% -16.1%
# central scheme variation: +2.69% -2.98%
# PDF variation: +2.24% -2.24%
#
# dynamical scheme # 1 : 0.0415806 +17.5% -15.3% # \sum ET
# dynamical scheme # 2 : 0.0415806 +17.5% -15.3% # \sum\sqrt{m^2+pt^2}
# dynamical scheme # 3 : 0.0431985 +21.5% -18.5% # 0.5 \sum\sqrt{m^2+pt^2}
# dynamical scheme # 4 : 0.040811 +16.3% -14.3% # \sqrt{\hat s}
#***************************************************************************

So I do not reproduce your weird behaviour with the latest version of the code.
I reproduce the value of the width that you indicate but not your cross-section. (I guess that you did not mention some parameter or due to the evolution of some of the default parameter)

Cheers,

Olivier

> On 1 Sep 2017, at 12:37, Muhammad Ahmad <email address hidden> wrote:
>
> Question #657215 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/657215
>
> Status: Answered => Open
>
> Muhammad Ahmad is still having a problem:
> Yes if generate
>
>> generate p p > zp > mu mu mu mu / h
> addprocess p p > zp > mu mu mu mu j / h
>
> its gives me 11.9 MeV (width) for Zp' mass 15 GeV with reasonable cross
> section 0.28 pb ( i have almost no cuts at final particles)
>
> i tried to do similar through W boson
>
>> generate p p > zp > mu v mu mu / h
>
> works but when i add jet
> addprocess p p > zp > mu v mu mu j / h
>
> it breaks
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.