MG5 and MUED problems

Asked by Roberto Ruiz on 2018-07-20

I'm trying to use MG5_aMC_v2_6_1 in the MUED context. For it I have added the MUED UFO file but when I run it, the parameters of the param_card.dat are replaced by the default ones (in param_card_default.dat):

  WARNING: For consistency, the mass of particle 6100006 (st1) is changed to "whatever".

One obvious solution would be to also add the same values in param_card to param_card_default so at the end in the MC generation the new ones would be used. But clearly there is an issue with the UFO implementation. Might it be that the syntax used in that file does not match with the MG5_aMC_v2_6* standards ?

To overcome this problem, is the trick above safe ?

Thanks,
Roberto

Question information

Language:
English Edit question
Status:
Answered
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Last query:
2018-07-20
Last reply:
2018-07-20

I do not think that the value is taken from the param_card_default.dat
Such line are likely to be linked to the UFO model directly.
My guess is that such mass is define has an internal parameter of the model
and therefore the user is NOT allowed to choose such value (and such value is NEVER use anyway by MG5aMC).

In the past that was the user responsability to ensure that such parameter where consistent with each other.
Now we try our best to auto-correct the param_card to have all entry written in a consistent way.
This can indeed be relevant for other program (parton-shower, decay package,..)
who do not test the consistency of the input.

Cheers,

Olivier

> On 20 Jul 2018, at 19:02, Roberto Ruiz <email address hidden> wrote:
>
> New question #671017 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/671017
>
>
> I'm trying to use MG5_aMC_v2_6_1 in the MUED context. For it I have added the MUED UFO file but when I run it, the parameters of the param_card.dat are replaced by the default ones (in param_card_default.dat):
>
> WARNING: For consistency, the mass of particle 6100006 (st1) is changed to "whatever".
>
> One obvious solution would be to also add the same values in param_card to param_card_default so at the end in the MC generation the new ones would be used. But clearly there is an issue with the UFO implementation. Might it be that the syntax used in that file does not match with the MG5_aMC_v2_6* standards ?
>
> To overcome this problem, is the trick above safe ?
>
> Thanks,
> Roberto
>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Can you help with this problem?

Provide an answer of your own, or ask Roberto Ruiz for more information if necessary.

To post a message you must log in.