nmssm in madgraph

Asked by jmli

I am using nmssmtools to generate the spectrum and decay table for madgraph. The parton level result seems working. But pythia can not read the decay table correctly.
In pythia.log there are errors report:

* (PYSLHA:) No valid unit given in IMSS
  Error in PYMSIN: SUSY decay channel not recognized:
     2000001 -> -1000024 2 0
  Error in PYMSIN: SUSY decay channel not recognized:
     2000001 -> -1000037 2 0
  Error in PYMSIN: SUSY decay channel not recognized:
     2000002 -> 1000024 1 0
  Error in PYMSIN: SUSY decay channel not recognized:
     2000002 -> 1000037 1 0
  Error in PYMSIN: SUSY decay channel not recognized:
     2000003 -> -1000024 4 0
....

However, these kinds of decay chains is not in the decay table which is given by NMSSMtools.
Are there something wrong?

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Johan Alwall
Solved:
Last query:
Last reply:
Revision history for this message
Johan Alwall (johan-alwall) said :
#1

Hello Jinmian,

Can you please send the parameter card from nmssmtools to me and Olivier? alwall _at_ fnal.gov and olivier.mattelaer _at_ uclouvain.be.

Thanks!
Johan

Revision history for this message
jmli (phyljm) said :
#2

Hi Johan and Olivier,

Thank you for your help.

The param_card.dat is given in the attachment. Actually, I just put the two files: specter.dat and decay.dat together.
However, the NMSSM model file in MadGraph is in SLHA2 format. We have changed the default parameter card(e.g. p1.dat at http://feynrules.irmp.ucl.ac.be/wiki/NMSSM), and use feynrules to regenerate the NMSSM model file, so it is more like SLHA1 format.

Best wishes,
Jinmian

在 2012-6-18,上午10:31, Johan Alwall 写道:

> Your question #200734 on MadGraph5 changed:
> https://answers.launchpad.net/madgraph5/+question/200734
>
> Status: Open => Needs information
>
> Johan Alwall requested more information:
> Hello Jinmian,
>
> Can you please send the parameter card from nmssmtools to me and
> Olivier? alwall _at_ fnal.gov and olivier.mattelaer _at_ uclouvain.be.
>
> Thanks!
> Johan
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/madgraph5/+question/200734
>
> You received this question notification because you asked the question.

Revision history for this message
Johan Alwall (johan-alwall) said :
#3

Hello Jinmian,

If you are using a different model than the one in the MadGraph 5 package, we need also a tar file with the model (please include only the .py and possible .dat files), otherwise we can't test. You can also email the process and run cards you use.

In fact, in the next version (1.4.7, which is already available on Launchpad in the branch 1.4.7), we have replaced the nmssm model with one which uses the SLHA1-type of particle ordering (similar to the mssm model).

All the best,
Johan

Revision history for this message
jmli (phyljm) said :
#4

Hi Johan,

Sorry for all this incomplete information. I thought it might just be the problem of pythia when reading the decay table.

The model file, param_card.dat, run_card.dat, pythia_card.dat is in the attachment.

By the way, can you sent me the link to MadGraph1.4.7? I can not find the web site for download.

Best wishes,
Jinmian

在 2012-6-18,上午11:15, Johan Alwall 写道:

> Your question #200734 on MadGraph5 changed:
> https://answers.launchpad.net/madgraph5/+question/200734
>
> Status: Open => Needs information
>
> Johan Alwall requested more information:
> Hello Jinmian,
>
> If you are using a different model than the one in the MadGraph 5
> package, we need also a tar file with the model (please include only the
> .py and possible .dat files), otherwise we can't test. You can also
> email the process and run cards you use.
>
> In fact, in the next version (1.4.7, which is already available on
> Launchpad in the branch 1.4.7), we have replaced the nmssm model with
> one which uses the SLHA1-type of particle ordering (similar to the mssm
> model).
>
> All the best,
> Johan
>
> --
> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/madgraph5/+question/200734
>
> You received this question notification because you asked the question.

Revision history for this message
Johan Alwall (johan-alwall) said :
#5

Hi Jinmian,

Thanks for the cards, we'll look at it. It might very well be a problem of Pythia, but it's better that we can reproduce the whole chain.

You get the development branch using bazaar:
bzr branch lp:~maddevelopers/madgraph5/1.4.7

All the best,
Johan

Revision history for this message
jmli (phyljm) said :
#6

Hi Johan,

Even if I use the 1.4.7 version with the param_card.dat which I have sent to you, the same error occurs. The decay table can not be read correctly.
May be it is helpful to give the pythia.log.

Best wishes,
jinmian

在 2012-6-18,下午1:11, Johan Alwall 写道:

> Your question #200734 on MadGraph5 changed:
> https://answers.launchpad.net/madgraph5/+question/200734
>
> Johan Alwall posted a new comment:
> Hi Jinmian,
>
> Thanks for the cards, we'll look at it. It might very well be a problem
> of Pythia, but it's better that we can reproduce the whole chain.
>
> You get the development branch using bazaar:
> bzr branch lp:~maddevelopers/madgraph5/1.4.7
>
> All the best,
> Johan
>
> --
> You received this question notification because you asked the question.

Revision history for this message
Best Johan Alwall (johan-alwall) said :
#7

Hi Jinmian,

Indeed it doesn't look like you (or MadGraph) have done anything wrong, and it does seem like a bug in Pythia. I would suggest to write to Torbjörn Sjöstrand or Peter Skands and ask. Please include your event file (with just a few events is enough) and the parameters you set in pythia_card. Feel free to cc me and Olivier.

A separate issue however is that the values from the param_card are not used in the MadGraph event generation, since this param_card is not compatible with the input defined in the FR model (please see any of the log.txt files that you get to by clicking on the cross section number for any individual integration channel in the web page for the run). Please see Question #197910 regarding this.

All the best,
Johan

Revision history for this message
jmli (phyljm) said :
#8

Thanks Johan Alwall, that solved my question.

Revision history for this message
Johan Alwall (johan-alwall) said :
#9

Hi Jinmian,

Just to clarify the question: This turned out to be due to a change in behavior in the interplay between the MadGraph-Pythia interface and the latest Pythia version. We have fixed this in the latest version (2.1.17) of the Pythia-PGS package, which will be available online within the next few days, together with the new version of MadGraph 5 (1.4.7).

All the best,
Johan