spin3/2 support

Bug #1806870 reported by Olivier Mattelaer
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MadDM
Fix Committed
Undecided
Unassigned

Bug Description

Hi,

I don't know is this a right place to ask or not. My question is about MadDM version in the latest version of MG5: MG5_aMC_v2_6_4.
When I use a UFO model with spin - 3/2 particle as "darkmatter", its giving me following error:

Defined multiparticle all = g u c d s b u~ c~ d~ s~ b~ a ve vm vt e- mu- ve~ vm~ vt~ e+ mu+ t t~ z w+ h y2 w- ta- xs ta+ xs~
MadDM>define darkmatter xs
Command "define darkmatter xs" interrupted with error:
KeyError : 4
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in 'MG5_debug'.
Please attach this file to your report.
MadDM>

I'm wondering, if maddm is compatible with spin-3/2 DM?

Thanks a lot.

Cheers,

Mukesh

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Here is the patch in a file format (you should have better indentation)

Changed in maddm:
status: New → Fix Committed
Revision history for this message
Mukesh Kumar (thakoor-mookesh) wrote :

Dear Olivier,

While scanning for relic density parameters: lets say
mass of DM = 200 GeV
and mass of the mediator = 450 GeV (or > 400 GeV)
maddm breaks which is probably maddm doesn't take "off-shell"?

Is there any solution to include such possibilities?

Error for the above parameter choice is following:

Command "launch top-philic-32/" interrupted in sub-command:
"define j = p" with error:
NameError : name 'FV' is not defined
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in 'MG5_debug'.
Please attach this file to your report.

Thanks a lot.

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Hi,

Your error does not seems to have anything to do with the benchmark...
Can your provide the full debug file?

Cheers,

Olivier

Revision history for this message
Mukesh Kumar (thakoor-mookesh) wrote : Re: [Bug 1806870] Re: spin3/2 support
  • MG5_debug Edit (7.0 KiB, application/octet-stream; name=MG5_debug)
  • param_card.dat Edit (3.0 KiB, application/x-ns-proxy-autoconfig; name="param_card.dat")

yes please find the attached.

though it stuck with following values in param_card.dat:

      5000002 4.500000e+02 # my2
      5000541 2.000000e+02 # mxs

On Fri, Dec 14, 2018 at 12:00 PM Olivier Mattelaer <
<email address hidden>> wrote:

> Hi,
>
> Your error does not seems to have anything to do with the benchmark...
> Can your provide the full debug file?
>
> Cheers,
>
> Olivier
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1806870
>
> Title:
> spin3/2 support
>
> Status in MadDM:
> Fix Committed
>
> Bug description:
> Hi,
>
> I don't know is this a right place to ask or not. My question is about
> MadDM version in the latest version of MG5: MG5_aMC_v2_6_4.
> When I use a UFO model with spin - 3/2 particle as "darkmatter", its
> giving me following error:
>
> Defined multiparticle all = g u c d s b u~ c~ d~ s~ b~ a ve vm vt e- mu-
> ve~ vm~ vt~ e+ mu+ t t~ z w+ h y2 w- ta- xs ta+ xs~
> MadDM>define darkmatter xs
> Command "define darkmatter xs" interrupted with error:
> KeyError : 4
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in 'MG5_debug'.
> Please attach this file to your report.
> MadDM>
>
>
> I'm wondering, if maddm is compatible with spin-3/2 DM?
>
> Thanks a lot.
>
> Cheers,
>
> Mukesh
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maddm/+bug/1806870/+subscriptions
>

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Hi,

This seems to be a bug in the model formatting (more exactly the decays.py is corrupted).
Since which lines of the file depends of the spectrum, it fully makes sense that it crash for some benchmark and not for some other.
In the model that you send us before, you can see expression like
 (16*gTXs**2*MXs**2*FV(1,3)*FV(1,Index(Lorentz,PRIVATExeext(3))))
Which does not make sense. (First FV is not define in the model --and can not have argument) and second, the Index(Lorentz,PRIVATExeext(3) is clearly an issue of FeynRules.

Cheers,

Olivier

PS: If you can not edit the model in a way to avoid this issue, one method is to simply remove that file, but in that case the computation of the widths will be much slower. [but obviously better slow than crashing]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions