MadGraph5Error : particles with some pdg code is in conflict with MG convention name for another particle.

Hi,

We have a function in MG5aMC to have a common naming scheme for all model.
(this allow that by default all model use "a" for the photon, "t" for the top, "ta-" for the tau, ...

In your model, using the conventional scheme is not possible it would result to two particles having the same name. You use h3 for the particle with pdg 9900025, which our convention want to name particle 36 (I guess also present in your model) with that name.

As indicated in the error message, you should use
> import model B-L-SSM/EWSB/UFO -modelname

In order to bypass the default renaming function and use the naming scheme provide within your UFO model.

Cheers,

Olivier

> On 7 Feb 2019, at 07:38, Mustafa Ashry <email address hidden> wrote:
>
> New question #678395 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/678395
>
> Dear Olivier,
>
> I generated the UFO files for the B-L-SSM model from SARAH-4.14.1. When implemented into MG5_aMC_v2_6_4, it gives the following error after import model B-L-SSM
>
> MG5_aMC>import model B-L-SSM/EWSB/UFO
> INFO: load particles
> INFO: load vertices
> INFO: Change particles name to pass to MG5 convention
> Error detected in sub-command import model /home/mashry/HEP/MG5_aMC_v2_6_4/models/B-L-SSM/EWSB/UFO
> write debug file MG5_debug
> If you need help with this issue please contact us on https://answers.launchpad.net/mg5amcnloMadGraph5Error : h3 particles with pdg code 9900025 is in conflict with MG convention name for particle 36.
> Use -modelname in order to use the particles name defined in the model and not the MadGraph5_aMC@NLO convention
>
> Your help is appreciated.
> Thanks in advance
>
> Mustafa
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.