whizard is hosted by Hepforge, IPPP Durham

Opened 15 years ago

Closed 14 years ago

#256 closed defect (invalid)

Weirdness when {{{tex_name}}} and {{{anti_tex}}} are the same

Reported by: Christian Speckner Owned by: Christian Speckner
Priority: P5 Milestone: v2.3.1
Component: models Version: 2.0.0rc3
Severity: minor Keywords: Model files
Cc:

Description

I stumbled over this one when debugging the FR interface: in the situation described above, WHIZARD uses the same identifier both for particle and antiparticle when calling O'Mega. I've already briefly skimmed the code, but couldn't find the culprit.

Change History (5)

comment:1 Changed 15 years ago by Juergen Reuter

Component: coremodels
Keywords: Model files added
Milestone: v2.0-rc4
Owner: changed from kilian to Juergen Reuter
Version: 2.0rc3

CS, could you please give us a little more information.... What exactly goes wrong!?

comment:2 Changed 15 years ago by Christian Speckner

Owner: changed from Juergen Reuter to Christian Speckner

JR, don't bother, I just tried to construct a simple testcase to reproduce this, and failed. What happened basically was that in my FeynRules? generated MSSM model file the two definitions

particle wp_sl3_plus 1000015
spin 0
name "sl3+"
tex_name "sl3+"
anti "sl3-"
anti_tex "sl3-"
mass Msl3
width Wsl3

and

particle wp_sl3_plus 1000015
spin 0
name "sl3+"
tex_name "sl3+"
anti "sl3-"
anti_tex "sl3+"
mass Msl3
width Wsl3

trigger different behavior, the lower leading to an invalid call to O'Mega ("sl3- sl3-" instead of "sl3+ sl3-" as defined in the input file). I'll assign this to myself and try to troubleshoot it as I find time, but seeing that the issue is hard to reproduce, this certainly is no showstopper.

comment:3 Changed 15 years ago by ohl

Milestone: v2.0-rc4v2.0.1
Priority: P3P4

comment:4 Changed 15 years ago by Christian Speckner

Milestone: v2.0.1v2.1
Priority: P4P5

comment:5 Changed 14 years ago by Juergen Reuter

Resolution: invalid
Status: newclosed

As CS said that he really cannot reproduce this error, I close this ticket.

Note: See TracTickets for help on using tickets.