InvalidCmd : The model DMSimp_t-S3M_uR cannot handle loop processes

Asked by raseeb haroon

I'm trying to generate the process p p > xm xm (majorana dark matter) using the model (dmsimpt_v1.2_s3mur.ufo.tar.gz) from (http://feynrules.irmp.ucl.ac.be/wiki/DMsimpt). Im Using this along side the MadSTR plugin.

I launched using this command -> ./mg5_aMC --mode=MadSTR

Than I Imported the model- > import model DMSimp_t-S3M_uR --modelname

Then generated the process using-> generate p p > xm xm / yf3qu1 yf3qu2 yf3qu3 yf3qd1 yf3qd2 yf3qd3 yf3u1 yf3u2 yf3u3 yf3d1 yf3d2 yf3d3 ys3qu1 ys3qu2 ys3qu3 ys3qd1 ys3qd2 ys3qd3 ys3u2 ys3u3 ys3d1 ys3d2 ys3d3 xs xd xv [QCD]

It gives me this error-> Command "generate p p > xm xm / yf3qu1 yf3qu2 yf3qu3 yf3qd1 yf3qd2 yf3qd3 yf3u1 yf3u2 yf3u3 yf3d1 yf3d2 yf3d3 ys3qu1 ys3qu2 ys3qu3 ys3qd1 ys3qd2 ys3qd3 ys3u2 ys3u3 ys3d1 ys3d2 ys3d3 xs xd xv [QCD]" interrupted with error:
InvalidCmd : The model DMSimp_t-S3M_uR cannot handle loop processes

This has been tried with the same Madgraph version and with the same exact commands on a mac without any faliurs. Any Help would be appreciated.

MG5:- MG5_aMC_v2.9.6
Ubuntu:- 22.04.2 LTS

Question information

Language:
English Edit question
Status:
Answered
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#1

If the model can not compute loop, you have to stick to tree-level computation within that model.
So either you use that model and do tree-level computation or you use another model (which might means generate such model)

Cheers,

Olivier

Revision history for this message
raseeb haroon (raseebharoon) said :
#2

I am sure that this model can generate loop processes, others have already done it. I also need to do the same, if there is any way it can be fixed please help me with it.

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#3

Are you sure that it was done with that exact model?
If the model does not have the flag stating that you can do loop computation, nothing can be done.

Technically one could put the flag by hand but in that case the computed loop will be wrong since you will be missing some part of the computation (the R2 part of the loop).

Cheers,

Olivier

Revision history for this message
raseeb haroon (raseebharoon) said :
#4

Yes, I'm sure that it was done with the same exact model, I would like to give some more information.

When using the command -> import model DMSimp_t-S3M_uR --modelname

It gives the error-> Command "import model UFO_S3M_uR --modelname" interrupted with error:
                                       InvalidCmd : UFO model not python3 compatible. You can convert it via the command
                               convert model /home/raseeb/MG5_aMC_v2_9_6/models/UFO_S3M_uR
                                       You can also type "set auto_convert_model T" to automatically convert all python2 module to be python3 compatible in the future.

After which I used ->set auto_convert_model T

Which was the case in both the mac and linux systems.

Here is where it changes. The "loop error" was also occurring on the mac system but was fixed by simply by exiting madgraph and launching again with the command-> import model DMSimp_t-S3M_uR --modelname

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said :
#5

Hi,

So i tried on mac to load the model

> MG5_aMC>import model DMSimp_t-S3M_uR --modelname
> INFO: model loaded from PYTHONPATH: /Users/omattelaer/Desktop/UFOMODEL/DMSimp_t
> fail to load model but auto_convert_model is on True. Trying to convert the model
> convert model /Users/omattelaer/Desktop/UFOMODEL/DMSimp_t
> retry the load of the model
> import model DMSimp_t-S3M_uR --modelname
> INFO: load particles
> DEBUG: Handling couplings defined with CTparameters...
> INFO: load vertices
> INFO: The model has interaction violating the charge: Y
> DEBUG: MG5 converter defines VVVV11 to Metric(1,4)*Metric(2,3) + Metric(1,3)*Metric(2,4) + Metric(1,2)*Metric(3,4)
> DEBUG: MG5 converter defines VVVV12 to Metric(1,4)*Metric(2,3) + Metric(1,3)*Metric(2,4)
> DEBUG: MG5 converter defines VVVV13 to Metric(1,4)*Metric(2,3) + Metric(1,2)*Metric(3,4)
> DEBUG: model prefixing takes 0.11787199974060059
> INFO: Restrict model DMSimp_t-S3M_uR with file ../../../Desktop/UFOMODEL/DMSimp_t/restrict_S3M_uR.dat .

(you can see that I had the model already locally but it was not yet converted to python3)

and then run your command:

> generate p p > xm xm / yf3qu1 yf3qu2 yf3qu3 yf3qd1 yf3qd2 yf3qd3 yf3u1 yf3u2 yf3u3 yf3d1 yf3d2 yf3d3 ys3qu1 ys3qu2 ys3qu3 ys3qd1 ys3qd2 ys3qd3 ys3u2 ys3u3 ys3d1 ys3d2 ys3d3 xs xd xv [QCD]
> INFO: Checking for minimal orders which gives processes.
> INFO: Please specify coupling orders to bypass this step.
> INFO: Trying coupling order WEIGHTED<=4: WEIGTHED IS 2*DMT+QCD+2*QED
> Setting the born squared orders automatically in the process definition to QED^2<=4 QCD=0 DMT=0.
> If this is not what you need, please regenerate with the correct orders.
> ---------------------------------------------------------------------------
> No Born diagrams found. Now switching to the loop-induced mode.
> Please also cite ref. 'arXiv:1507.00020' when using results from this mode.
> ---------------------------------------------------------------------------
> Command "generate p p > xm xm / yf3qu1 yf3qu2 yf3qu3 yf3qd1 yf3qd2 yf3qd3 yf3u1 yf3u2 yf3u3 yf3d1 yf3d2 yf3d3 ys3qu1 ys3qu2 ys3qu3 ys3qd1 ys3qd2 ys3qd3 ys3u2 ys3u3 ys3d1 ys3d2 ys3d3 xs xd xv [QCD]" interrupted with error:
> Exception :
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in 'MG5_debug'.
> Please attach this file to your report.

Looking at the error, the code is confused about if he has to do loop-induced mode or not.
The first diagram generation failed so it switch to loop-induced but the loop induced mode detects (correctly) some tree-level and therefore refuses to proceed.

This can be fixed, if running the command

> generate p p > xm xm / yf3qu1 yf3qu2 yf3qu3 yf3qd1 yf3qd2 yf3qd3 yf3u1 yf3u2 yf3u3 yf3d1 yf3d2 yf3d3 ys3qu1 ys3qu2 ys3qu3 ys3qd1 ys3qd2 ys3qd3 ys3u2 ys3u3 ys3d1 ys3d2 ys3d3 xs xd xv DMT=2 [QCD]
> Interpreting 'DMT=2' as 'DMT<=2'
> QED order is missing in the process definition. It will be set to "default unser couplings": 99
> If this is not what you need, please regenerate with the correct orders.
> QCD order is missing in the process definition. It will be set to "default unser couplings": 99
> If this is not what you need, please regenerate with the correct orders.
> Order DMT is not constrained as squared_orders. Using: DMT^2=4
> Order QED is not constrained as squared_orders. Using: QED^2=198
> Order QCD is not constrained as squared_orders. Using: QCD^2=198
> INFO: Generating FKS-subtracted matrix elements for born process: u u~ > xm xm DMT<=2 QCD<=100 QED<=99 DMT^2=4 QCD^2=200 QED^2=198 / yf3qu1 yf3qu2 yf3qu3 yf3qd1 yf3qd2 yf3qd3 yf3u1 yf3u2 yf3u3 yf3d1 yf3d2 yf3d3 ys3qu1 ys3qu2 ys3qu3 ys3qd1 ys3qd2 ys3qd3 ys3u2 ys3u3 ys3d1 ys3d2 ys3d3 xs xd xv (1 / 2)
> INFO: Generating FKS-subtracted matrix elements for born process: u~ u > xm xm DMT<=2 QCD<=100 QED<=99 DMT^2=4 QCD^2=200 QED^2=198 / yf3qu1 yf3qu2 yf3qu3 yf3qd1 yf3qd2 yf3qd3 yf3u1 yf3u2 yf3u3 yf3d1 yf3d2 yf3d3 ys3qu1 ys3qu2 ys3qu3 ys3qd1 ys3qd2 ys3qd3 ys3u2 ys3u3 ys3d1 ys3d2 ys3d3 xs xd xv (2 / 2)
> INFO: Generating virtual matrix element with MadLoop for process: u u~ > xm xm DMT<=2 QCD<=100 QED<=99 DMT^2=4 QCD^2=200 QED^2=198 / yf3qu1 yf3qu2 yf3qu3 yf3qd1 yf3qd2 yf3qd3 yf3u1 yf3u2 yf3u3 yf3d1 yf3d2 yf3d3 ys3qu1 ys3qu2 ys3qu3 ys3qd1 ys3qd2 ys3qd3 ys3u2 ys3u3 ys3d1 ys3d2 ys3d3 xs xd xv (1 / 2)
> WARNING: Some loop diagrams contributing to this process are discarded because they are not pure (QCD)-perturbation.
> Make sure you did not want to include them.
> INFO: Generating virtual matrix element with MadLoop for process: u~ u > xm xm DMT<=2 QCD<=100 QED<=99 DMT^2=4 QCD^2=200 QED^2=198 / yf3qu1 yf3qu2 yf3qu3 yf3qd1 yf3qd2 yf3qd3 yf3u1 yf3u2 yf3u3 yf3d1 yf3d2 yf3d3 ys3qu1 ys3qu2 ys3qu3 ys3qd1 ys3qd2 ys3qd3 ys3u2 ys3u3 ys3d1 ys3d2 ys3d3 xs xd xv (2 / 2)
> WARNING: Some loop diagrams contributing to this process are discarded because they are not pure (QCD)-perturbation.
> Make sure you did not want to include them.
> INFO: Generated 2 subprocesses with 36 real emission diagrams, 4 born diagrams and 16 virtual diagrams

But does not explain your no loop problem.
I then tried to remove the model that I had on disk:
> [LTS]$ rm -rf ~/Desktop/UFOMODEL/DMSimp_t/

and retry:

> MG5_aMC>import model DMSimp_t-S3M_uR --modelname
> INFO: download model from http://feynrules.irmp.ucl.ac.be/raw-attachment/wiki/DMsimpt/dmsimpt_v1.3.ufo.tgz to the following directory: /Users/omattelaer/Desktop/UFOMODEL

> INFO: model loaded from PYTHONPATH: /Users/omattelaer/Desktop/UFOMODEL/DMSimp_t
> fail to load model but auto_convert_model is on True. Trying to convert the model
> convert model /Users/omattelaer/Desktop/UFOMODEL/DMSimp_t
> retry the load of the model
> import model DMSimp_t-S3M_uR --modelname
> INFO: load particles
> DEBUG: Handling couplings defined with CTparameters...
> INFO: load vertices
> INFO: The model has interaction violating the charge: Y

But again it was working.

So I do not have any real suggestion except
1) remove the model directory on mac to redo the download/conversion to python3
2) use the converted model from your linux machine on your mac machine.

Cheers,

Olivier

> On 17 Mar 2023, at 16:35, raseeb haroon <email address hidden> wrote:
>
> Question #705865 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/705865
>
> Status: Answered => Open
>
> raseeb haroon is still having a problem:
> Yes, I'm sure that it was done with the same exact model, I would like
> to give some more information.
>
> When using the command -> import model DMSimp_t-S3M_uR --modelname
>
>
> It gives the error-> Command "import model UFO_S3M_uR --modelname" interrupted with error:
> InvalidCmd : UFO model not python3 compatible. You can convert it via the command
> convert model /home/raseeb/MG5_aMC_v2_9_6/models/UFO_S3M_uR
> You can also type "set auto_convert_model T" to automatically convert all python2 module to be python3 compatible in the future.
>
> After which I used ->set auto_convert_model T
>
> Which was the case in both the mac and linux systems.
>
> Here is where it changes. The "loop error" was also occurring on the mac
> system but was fixed by simply by exiting madgraph and launching again
> with the command-> import model DMSimp_t-S3M_uR --modelname
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Can you help with this problem?

Provide an answer of your own, or ask raseeb haroon for more information if necessary.

To post a message you must log in.