MadGraph5_aMC@NLO

SUSYHIT generated output convention for the param_card seems to be wrong

Asked by Hang Zhou

I'm using MG5 of version 3.5.3 to generate a photon fusion process to charginos: a a > x1- x1+, model imported is MSSM_SLHA2 and the param_card is generated by SUSYHIT ( I use SUSYHIT to generate the spectra output file: susyhit_slha.out and then replace the MG5's own param_card.dat with it ). When "launch" in MG5, the error occurs as follows:
......
WARNING: Particle 1000024 with small width detected (2.25979917e-06): See https://answers.launchpad.net/mg5amcnlo/+faq/3053 to learn the special handling of that case
WARNING: Particle 1000023 with small width detected (5.62800506e-06): See https://answers.launchpad.net/mg5amcnlo/+faq/3053 to learn the special handling of that case
INFO: Update the dependent parameter of the param_card.dat
WARNING: Param card is not complete: Block msu2 is simply missing.
                We will use model default for all missing value! Please cross-check that
                this correspond to your expectation.
WARNING: Param card is not complete: Block msq2 is simply missing.
                We will use model default for all missing value! Please cross-check that
                this correspond to your expectation.
WARNING: Param card is not complete: Block msd2 is simply missing.
                We will use model default for all missing value! Please cross-check that
                this correspond to your expectation.
WARNING: Param card is not complete: Block msl2 is simply missing.
                We will use model default for all missing value! Please cross-check that
                this correspond to your expectation.
WARNING: Param card is not complete: Block mse2 is simply missing.
                We will use model default for all missing value! Please cross-check that
                this correspond to your expectation.
ERROR: Convention for the param_card seems to be wrong. Trying to automatically convert your file to SLHA2 format.
Please check that the conversion occurs as expected (The converter is not fully general)
lpp1 '2' not compatible with pdlabel1 'nn23lo1'. Change pdlabel1 to edff
lpp2 '2' not compatible with pdlabel2 'nn23lo1'. Change pdlabel2 to edff
WARNING: Missing mass in the lhef file (6) . Please fix this (use the "update missing" command if needed)
Generating 10000 events with run name run_01
survey run_01
lpp1 '2' not compatible with pdlabel1 'nn23lo1'. Change pdlabel1 to edff
lpp2 '2' not compatible with pdlabel2 'nn23lo1'. Change pdlabel2 to edff
INFO: compile directory
WARNING: Missing mass in the lhef file (6) . Please fix this (use the "update missing" command if needed)
WARNING: information about "mass [23]" is missing using default value: 91.1876.
WARNING: information about "mass [15]" is missing using default value: 1.777.
WARNING: information about "mass [6]" is missing using default value: 175.0.
WARNING: information about "decay [23]" is missing using default value: 2.411433.
Command "generate_events run_01" interrupted with error:
KeyError : 'id (23,) is not in mass'
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in '/home/buhan/hep/MG5_aMC_v3_5_3/aatoxx_test353_SLHA2/run_01_tag_1_debug.log'.
Please attach this file to your report.

I noticed there are two errors. One is about the convention for param_card, which is converted to SLHA2 format but I'm not sure if it still matters. The other is a key error : 'id (23,) is not in mass'. So I added the Z mass in the param_card by hand. Then launch again and the another error occurs about "id(6,)". So I added top mass in the param_card and this time it went successfully.
I'm wondering whether the errors about missing "id(23)" and "id(6)" masses are related with the first error about the param_card convention generated by SUSYHIT, and how can I fix it so that I would not need to add them by hand every time I feed the SUSYHIT output to MG5.
I can provide the param_card.dat but I don't know how to upload an attachment. If needed, I can provide one via email.
I tried almost every version of MG5 from 2.x to 3.x and SUSYHIT ver1.5, but this same issue appears.

BTW, I could use the SUSYHIT output as the MG5 param_card successfully years ago with the MG5 version 3.0.0. But now I lost the package of this version and I cannot find this version all over the internet.

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Olivier Mattelaer
Solved:
Last query:
Last reply:
Revision history for this message
Best Olivier Mattelaer (olivier-mattelaer) said : 		#1

Hi,

For the case where param_card is (partly) generated by an external code and that you want to provide default value for the rest of the spectrum (typically the SM part is missing for some of those spectrum generator).
My advise is to use the "update missing" command.

For example your script command can be
(run via ./bin/madevent PATH_TO_SCRIPT)

launch
./benchmark_1.dat
update missing
launch
./benchmark_2.dat
update missing

For the SLHA1 and SLHA2 convention, you can do the same (assuming susyhit still provides SLHA1):
 launch
./benchmark_1.dat
update to_slha2
launch
./benchmark_2.dat
update to_slha2

For the case, where you need to use both converter, the situation might be tricky (i.e. check carefully the new param_card to check that this correspond to your expectation). Since the ordering of the two converter might influence the final param_card and therefore the result. In principle, I would say that you should convert to SLHA2 first, but the issue is that the converter might need some missing information and therefore crash...
If that's the case, you will be force to update for missing information first, but this will also add the SLHA2 specific block and now the converter will see a duplication of information since your card will see two (conflicting) specification of the same information.

Cheers,

Olivier

Revision history for this message
Hang Zhou (hangzhou) said : 		#2

Many thanks to Olivier! The "update missing" command solved the problem, the calculation and generation now go successfully.

Revision history for this message
Hang Zhou (hangzhou) said : 		#3

Hi, Olivier,

Many thanks again for your help. I'm also wondering if the version 3.0.0 of MG5 is still available, because that version went well with SUSYHIT as far as I remember (which does not need update missing). But other versions now all need "update missing" for SUSYHIY output spectra.

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said : 		#4

No, we actively try to remove all the revision of 3.0.x of the market since the syntax of the process was problematic in that version of the code. (i.e. not the same syntax as 2.9.x and that 3.1.x). This bieing said, I'm pretty sure that 3.0.0 would also require "update missing" since this was introduced in 2.5.1 (2016) for fixing exactly this kind of problem.

Cheers,

Olivier

> On 14 Mar 2024, at 02:55, Hang Zhou <email address hidden> wrote:
>
> Question #709539 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/709539
>
> Hang Zhou posted a new comment:
> Hi, Olivier,
>
> Many thanks again for your help. I'm also wondering if the version 3.0.0
> of MG5 is still available, because that version went well with SUSYHIT
> as far as I remember (which does not need update missing). But other
> versions now all need "update missing" for SUSYHIY output spectra.
>
> --
> You received this question notification because you are subscribed to
> the question.

Revision history for this message
Hang Zhou (hangzhou) said : 		#5

Thanks for your reply, Olivier. I see. Maybe I misremembered the details.

Cheers,
Hang Zhou