Pythia (pythia-pgs) failing when decay does not conserve charge, but only recently

Dear Alex,

That check is internal to pythia6 and since pythia6 is not supported anymore, this was certainly not modified.
To be 100% sure, I went trough all the modification of pythia-pgs up to 2015 and nothing is related to that.

> On that basis, my question is: Has there been an update in the pythia-pgs package which has become more pedantic with these things? I can only presume the previous author of the param_cards put “u" in as a generic light quark and that pythia would work it out, I guess it now requires that one give it the correct flavour/charge?

The code does not read the string attach to the line, only the pdg associated (written before the comment).
You certainly need to have a coherent information on the pdg.

Cheers,

Olivier

> On Nov 8, 2016, at 14:47, Alexander Titterton <email address hidden> wrote:
>
> New question #403881 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/403881
>
> Hi Olivier et al,
>
>
> I've rolled back to v2_3_3 as newer updates were giving me wrong cross-sections post-matching but now am having Pythia troubles in the NMSSM.
>
> Running over a few mass points, one of which I had run separately and successfully on its own before, I now get an error from pythia saying a decay doesnt conserve charge.
>
> Checking the param_cards (whose branching ratios are fixed as we wanted them) this is indeed correct, there is for example ~d_L --> ~Chi_20 + u which doesn't conserve charge.
>
> On that basis, my question is: Has there been an update in the pythia-pgs package which has become more pedantic with these things? I can only presume the previous author of the param_cards put "u" in as a generic light quark and that pythia would work it out, I guess it now requires that one give it the correct flavour/charge?
>
>
> Cheers,
> Alex
>
>
> P.S.
> Here's the relevant snippet from the pythia log:
> Advisory warning type 7 given after 0 PYEXEC calls:
> (PYSLHA:) Forced rescaling of BR's for KF= 24 ; sum was 1.02000.
>
> Error type 7 has occured after 0 PYEXEC calls:
> (PYSLHA:) Charge not conserved in decay of KF = 1000001
>
> Error type 7 has occured after 0 PYEXEC calls:
> (PYSLHA:) Charge not conserved in decay of KF = 2000001
>
> Error type 7 has occured after 0 PYEXEC calls:
> (PYSLHA:) Charge not conserved in decay of KF = 1000003
>
> Error type 7 has occured after 0 PYEXEC calls:
> (PYSLHA:) Charge not conserved in decay of KF = 2000003
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.