error in computing decay widths

Asked by Basabendu

Dear calcHEP team,

                                      I am using calchep 3.6.25 to study beyond standard model physics. I have implemented a model of my own and trying to find decay width of some exotic particles. Now, in doing this, when I am generating the .slha file, in the terminal a message is showing 'can not find |m0|. There is no such parameter as |m0| in my model. Secondly, when I am trying to run event_mixer, it is showing 'There are no events' but I can see the event files have been generated inside the 'results' directly (I am using 'subproc_cycle' to generate events). What is the possible source of error here?

Thank you so much for your time.

Question information

Language:
English Edit question
Status:
Answered
For:
CalcHEP Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Alexander Pukhov (pukhov) said :
#1

 New model should be checked before usage.
  Under GUI interface use menus
        Edit Model
               CHECK MODEL

More likely using this way you'll get error message.
In particular m0,m1,m2,m3,... are reserved for Lorentz indexes
and can not be used for variables.

Best
     Alexander Pukhov

Revision history for this message
Basabendu (bb1988-1) said :
#2

First of all thank you so much. I did check my model and was able to fix possible errors. There is one more problem though, it is taking HUGE amount of time in generating .lhe file, for ~20,000 events. Any suggestion on how to run "event_mixer?"

Revision history for this message
Alexander Pukhov (pukhov) said :
#3

It could be. For some tasks like 2->4 processes CalcHEP works slowly.
But in some cases problem can be solved. If you send me your model and batch file, I'll try to find a time to look one this problem.

Best
    Alexander Pukhov

Revision history for this message
Alexander Belyaev (alexander.belyaev) said :
#5

Do you still have problem?

Revision history for this message
Pradyumna (pradyumnah) said :
#6

I am facing a similar issue. I changed the muon mass to 100GeV for testing something but the decay widths are coming out to be negative. Setting the Force Unitary gauge did not change anything.

Revision history for this message
Alexander Belyaev (alexander.belyaev) said :
#7

Which model are you talking about and how do you evaluate the muon width?
This definitely not he case of the SM model which
does not have the problem.
If this problem appears in your own model,
this could be an indication that you have incorrectly implemented it,
or the model is not gauge invariant, i.e. has the problem.
Alexander

On 07/03/2021 11:15, Pradyumna wrote:
> Question #279895 on CalcHEP changed:
> https://answers.launchpad.net/calchep/+question/279895
>
> Pradyumna requested more information:
> I am facing a similar issue. I changed the muon mass to 100GeV for
> testing something but the decay widths are coming out to be negative.
> Setting the Force Unitary gauge did not change anything.
>

--
______________________________________________________________________
Prof. Alexander S Belyaev (<email address hidden>)
https://www.hep.phys.soton.ac.uk/content/alexander-belyaev

School of Physics & Astronomy, University of Southampton
Office 5047, SO17 1BJ, TEL: +44 23805 98509, FAX: +44 23805 93910
.....................................................................
Particle Physics Department, Rutherford Appleton Laboratory
Didcot, OX11 0QX, TEL: +44 12354 45562, FAX: +44 12354 46733
.....................................................................
CERN, CH-1211 Geneva 23, Switzerland
Office 40/1-B20, Mailbox: E27910, TEL: +41 2276 71642
______________________________________________________________________

Revision history for this message
Alexander Belyaev (alexander.belyaev) said :
#8

P.S.
Please close the previous question and open the new one
The very first question was opened 5 years ago

Can you help with this problem?

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

To post a message you must log in.