error with topbsm feynrules model

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Hi,

Sorry for the late reply, i only see your message today (with the automatic message after two weeks).
The problem seems to be related to the fact that MO0 seems to be zero in your case. (is it True?)

At the same time, it looks like that you are compiling twice the cards. This is a problem solved in 2.6.0 and related to
a missmatch (on your machine) between the cpu time and the filesystem time (the typical problem is in wintertime and the otherone in summertime).
With such problem, you might have stuff crashing and/or running depending on how much time you edit the card before running.
(which might explain why some other process went trough)

So my advise would be to test with 2.6.0 to see if this improves the situation.

Cheers and sorry to have miss your request.

Olivier

> On 13 Sep 2017, at 07:23, Minho Kim <email address hidden> wrote:
>
> New question #657945 on MadGraph5_aMC@NLO:
> https://answers.launchpad.net/mg5amcnlo/+question/657945
>
> Dear mg5 team,
>
> Hi, I am minho kim, graduate student in Postech, korea.
>
> recently when i use topBSM model with madgraph5 provided in http://feynrules.irmp.ucl.ac.be/wiki/topBSM,
>
> mg5 shows some error message like
>
> --------------------------------------------------------------------
> WARNING: Failed to update dependent parameter. This might create trouble for external program (like MadSpin/shower/...)
> Generating 10000 events with run name run_01
> survey run_01
> INFO: compile directory
> Traceback (most recent call last):
> File "write_param_card.py", line 205, in <module>
> ParamCardWriter('./param_card.dat', generic=True)
> File "write_param_card.py", line 30, in __init__
> self.write_card(list_of_parameters)
> File "write_param_card.py", line 90, in write_card
> self.write_dep_param_block(lhablock)
> File "write_param_card.py", line 123, in write_dep_param_block
> exec("%s = %s" % (parameter.name, parameter.value))
> File "<string>", line 1, in <module>
> ZeroDivisionError: complex division by zero.
> ---------------------------------------------------------------------------
>
>
>
>
> To trace above error, i add 'print(parameter.name,parameter.value)' in line 123 on 'write_param_card.py',
> Then it gives
>
> ------------------------------------------------------------------------
> .......
> ('o0fusionAxial', '(G**2*MT**2*o0axial*(-(cmath.pi*complex(0,1)) + cmath.log((1 + cmath.sqrt(1 - (4*MT**2)/MO0**2))/(1 - cmath.sqrt(1 - (4*MT**2)/MO0**2))))**2)/(8.*cmath.pi**2*MO0**2*vev)')
> Traceback (most recent call last):
> File "write_param_card.py", line 206, in <module>
> ParamCardWriter('./param_card.dat', generic=True)
> File "write_param_card.py", line 30, in __init__
> self.write_card(list_of_parameters)
> File "write_param_card.py", line 90, in write_card
> self.write_dep_param_block(lhablock)
> File "write_param_card.py", line 124, in write_dep_param_block
> exec("%s = %s" % (parameter.name, parameter.value))
> File "<string>", line 1, in <module>
> ZeroDivisionError: complex division by zero
> --------------------------------------------------------------------
>
>
>
>
> the method to make UFO file is as follows:
>
> ---------------------------------------------------------------------
> $FeynRulesPath = SetDirectory["~/Programs/feynrules-current"]; << FeynRules`;
> LoadModel["SM.fr", "topBSM.fr"];
> FeynmanGauge = False;
>
> WriteUFO[
> LGauge,
> LHiggs,
> LFermions,
> LYukawa,
> LGhost,
> LS0, LO0, LS1, LO1, AddDecays -> False];
> ---------------------------------------------------------------------
>
> mg5 version is 2.5.5
> mathematica version is 11.1 (linux)
> feyrules version is 2.3.29
>
>
>
> Interesting is even mg5 shows previous error message, it seems to work fine at least process like p p > s0 | s1 | o0 | o1 > t t~.
>
>
> So why that error happens?
>
>
> Thanks
>
> Minho Kim
>
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Hi Olivier,

1. Even when I set MO0 to non-zero value, it shows same error. (using mg5 2.5.5)

2. Using mg5 2.6.0, twice compiling of cards is disappeard after first run.
(but, in the first run, 'Traceback (most recent call last): File "write_param_card.py", line 206, in <module>.....' still occur)

3. Still there is issue related O0 paricle.
-> when I generate process which include o0 particle and change some parameters
like MO0, then mg5 run warns like

'WARNING: Failed to update dependent parameter. This might create trouble for external program (like MadSpin/shower/...)'

I think above warn is also related to some problem about parameters of O0 (o0fusionAxial..and so on.) as shown as
Traceback.

thanks

minho kim

This question was expired because it remained in the 'Open' state without activity for the last 15 days.