3-index parameter

Report the bugs you found
Post Reply
Avelino
Posts: 46
Joined: 13. Apr 2016, 14:57
Contact:

3-index parameter

Post by Avelino » 29. Jul 2016, 11:07

Hi Florian, I think I found a potential bug in SARAH.

The model I am working on contains a Yukawa parameter (called 'Yep') that carries three indices. I traced the problems back to this parameter, which seems to lead to inconsistencies in line 283 of nonSUSYrges.m. In particular, SARAH fails when it tries getDimParameter[threeIndexParameter[]] because Position[parameters,x] returns nothing. This is because the Yukawa parameter 'Yep' appears as 'Yep' in the parameters array, while threeIndexParameter[] reads 'Yep(gt2, gt1,gt3)'. This mismatch seems to be at the origin of the problem.

I tried replacing

Code: Select all

threeIndexParameter=Intersection[Flatten[threeIndexParameter]];
in line 276 of nonSUSYrges.m by

Code: Select all

threeIndexParameter=Intersection[Flatten[threeIndexParameter]/.A_[b_, c_, d_]->A];
but now I get a different error:

Code: Select all

CheckModelFiles::MissingParameter: The following parameters are not defined in ParameterDefinitions in paramaters.m: {Yep(1),Yep(2),Yep(3)}  
CheckModelFiles::MissingOutputNameParameter: For the following parameters is no OutputName defined: {Yep(1),Yep(2),Yep(3)}
And therefore this solution is not satisfactory.

I attach the model files in case you find them necessary for testing.
Attachments
SISA4.tar.gz
(3.78 KiB) Downloaded 186 times

Avelino
Posts: 46
Joined: 13. Apr 2016, 14:57
Contact:

Re: 3-index parameter

Post by Avelino » 29. Jul 2016, 11:25

By the way, the model also contains 4-index parameters and a 1-index VEV. This could perhaps lead to problems as well, as these are unconventional features. Of course, a solution would be to split the 3-generation scalars into 3 independent fields, but that's of course not optimal.

FStaub
Site Admin
Posts: 822
Joined: 13. Apr 2016, 14:05

Re: 3-index parameter

Post by FStaub » 29. Jul 2016, 11:25

Well, you need to add the parameters, see e.g MSSM-RpV/TriRpV/parameters.m at the very end.

Cheers,
Florian

FStaub
Site Admin
Posts: 822
Joined: 13. Apr 2016, 14:05

Re: 3-index parameter

Post by FStaub » 29. Jul 2016, 11:29

Hmmm, a parameter with four indices is so far not supported. In that case it might work to run

Code: Select all

CalcRGEs[NoMatrixMultiplication->True]
Then you also don't need to define the additional parameters coming from the splitting of tensors into a set of matrices.

Avelino
Posts: 46
Joined: 13. Apr 2016, 14:57
Contact:

Re: 3-index parameter

Post by Avelino » 29. Jul 2016, 16:01

Not sure I understood the solution, sorry.

Since I also have 4-index parameters: just properly defining the parameters in the parameters.m file (as for trilinear RPV) would not be sufficient. Therefore, you propose

1) To change the nonSUSYrges.m file as explained above
2) To run MakeSPheno[] after CalcRGEs[NoMatrixMultiplication -> True]

is this correct? Because I tried this way and now I get error messages in CalcRGEs.

Thanks in advance.

FStaub
Site Admin
Posts: 822
Joined: 13. Apr 2016, 14:05

Re: 3-index parameter

Post by FStaub » 1. Aug 2016, 14:17

Hi Avelino,

checking your model, there is another problem beside the ones with quartics with four indices:

The RGEs are calculated for real scalars, ie. each complex scalar is decomposed by SARAH. That means, when it considers the diagrams with external leges re(H), re(H), re(Phi), re(Phi) the amplitude from that diagram contributes to the running of lambda5,6,7. Therefore, to single out the contribution to the running of one coupling, it must calculate the superposition of different combinations of re(X) and im(X). To find the correct superpositions is not trivial and my algorithm for that is not perfect for sure.
However, I'm still a bit surprised that it fails for your model because you don't have any other combinations than a THDM-III where it works...

Cheers,
Florian

FStaub
Site Admin
Posts: 822
Joined: 13. Apr 2016, 14:05

Re: 3-index parameter

Post by FStaub » 1. Aug 2016, 14:58

Hi,

I attach a first update of the routines. Unfortuantely, it still throws erros concerning lambda5 and lambda7. I guess the reason is that SARAH doesn't derive the symmetries of the quartics, yet. I hope I can continue looking at that issue tomorrow.

Cheers,
Florian
Attachments
nonSUSYrges.m
(64.82 KiB) Downloaded 208 times

Post Reply