TypeError: fullTunneling() got an unexpected keyword argument 'phi' for "B-L-SM" model generated by SARAH

[smandal123]

Dear All,

I was trying to run Vevacious for the model "B-L-SM". I got the following results ending with TypeError: fullTunneling() got an unexpected keyword argument 'phi' ,

Setting up the VevaciousRunner object took 0.00162 seconds.
Please enter the option of homotopy method
1. The polyhedral homotopy
2. The classical linear homotopy
The classical linear homotopy
The # of paths followed = 9

The # of roots = 9
The # of real roots = 9
The # of paths followed = 9
The # of blow_up = 0 (before endgame)
The running time : 0.00000 s
The solutions are listed in file "data.roots"

Department of Mathematics, Michigan State University
Contact Info:
Tsung-Lin Lee : leetsung@msu.edu
Tien-Yien Li : li@math.msu.edu
Chih-Hsiung Tsai : tsaichih@msu.edu


Finding all the tree-level extrema and parsing the results took 0.006878 seconds.
rm: cannot remove ‘./Vevacious.pyc’: No such file or directory
trying to minimize { { vH -> ( 247.654147 ), vX -> ( 2500.0 ) }, TreeLevelPotentialValue -> -822558497.6, EffectivePotentialValue -> -1.11330757121e+13 } (T = 0.0)
VariableMetricBuilder: Tolerance is not sufficient - edm is 0.00112391 requested 1e-05 continue the minimization
VariableMetricBuilder: warning: no improvement in line search
VariableMetricBuilder: finishes without convergence.
VariableMetricBuilder: edm= 7.35719e+17 requested: 1e-05
FunctionMinimum is invalid.
The MINUIT wrapper threw an exception:
Function value is above the specified estimated distance to the minimum (edm).
while trying to minimize the potential starting at { vH -> ( 247.654147 ), vX -> ( 2500.0 ) }. MINUIT stopped at { vH -> ( -0.120258700773 ), vX -> ( 3016.51809167 ) }. MINUIT's estimate of how much deeper it should go is 9.48730901084e+18 GeV^4.
Taking the starting point as a vacuum candidate.
trying to minimize { { vH -> ( -247.654 ), vX -> ( -2500 ) }, TreeLevelPotentialValue -> -822558497.6, EffectivePotentialValue -> -1.11330757121e+13 } (T = 0.0)
VariableMetricBuilder: warning: no improvement in line search
VariableMetricBuilder: finishes without convergence.
VariableMetricBuilder: edm= 1.20071e+14 requested: 1e-05
VariableMetricBuilder: Tolerance is not sufficient - edm is 0.000185303 requested 1e-05 continue the minimization
rolled to { { vH -> ( -1.21258705923e-07 ), vX -> ( -4627.69120021 ) }, TreeLevelPotentialValue -> 3436752134.52, EffectivePotentialValue -> -1.55326344778e+13 }

trying to minimize { { vH -> ( -247.654 ), vX -> ( 0 ) }, TreeLevelPotentialValue -> -119433497.6, EffectivePotentialValue -> -89278808.0537 } (T = 0.0)
MnHesse: 2nd derivative zero for parameter 1
MnHesse fails and will return diagonal matrix
The MINUIT wrapper threw an exception:
Covariance is not positive definite.
while trying to minimize the potential starting at { vH -> ( -247.654 ), vX -> ( 0 ) }. MINUIT stopped at { vH -> ( -229.254113797 ), vX -> ( 0.0 ) }. MINUIT's estimate of how much deeper it should go is 0.00902701352356 GeV^4.
Taking the starting point as a vacuum candidate.
trying to minimize { { vH -> ( -247.654 ), vX -> ( 2500 ) }, TreeLevelPotentialValue -> -822558497.6, EffectivePotentialValue -> -1.11330757121e+13 } (T = 0.0)
VariableMetricBuilder: warning: no improvement in line search
VariableMetricBuilder: finishes without convergence.
VariableMetricBuilder: edm= 1.20071e+14 requested: 1e-05
VariableMetricBuilder: Tolerance is not sufficient - edm is 0.000185303 requested 1e-05 continue the minimization
rolled to { { vH -> ( -2.83909398421e-07 ), vX -> ( 4627.69141755 ) }, TreeLevelPotentialValue -> 3436753232.77, EffectivePotentialValue -> -1.55326344778e+13 }

trying to minimize { { vH -> ( 0 ), vX -> ( -2500 ) }, TreeLevelPotentialValue -> -703125000.0, EffectivePotentialValue -> -1.1132986429e+13 } (T = 0.0)
eigenvalues:
-12.2173
14.2173
matrix forced pos-def by adding 12.2315 to diagonal
VariableMetricBuilder: Tolerance is not sufficient - edm is 0.00484088 requested 1e-05 continue the minimization
VariableMetricBuilder: warning: no improvement in line search
VariableMetricBuilder: finishes without convergence.
VariableMetricBuilder: edm= 3.45324e+07 requested: 1e-05
FunctionMinimum is invalid.
The MINUIT wrapper threw an exception:
Function value is above the specified estimated distance to the minimum (edm).
while trying to minimize the potential starting at { vH -> ( 0 ), vX -> ( -2500 ) }. MINUIT stopped at { vH -> ( -1.31627555654e-06 ), vX -> ( -3936.64777066 ) }. MINUIT's estimate of how much deeper it should go is 7052778292.97 GeV^4.
Taking the starting point as a vacuum candidate.
trying to minimize { { vH -> ( 0 ), vX -> ( 0 ) }, TreeLevelPotentialValue -> 0.0, EffectivePotentialValue -> 0.0 } (T = 0.0)

.......................................
..................................

DSB vacuum: { { vH -> ( 247.654147 ), vX -> ( 2500.0 ) }, TreeLevelPotentialValue -> -822558497.6, EffectivePotentialValue -> -1.11330757121e+13 }
Panic vacuum: { { vH -> ( -7.71967873826e-08 ), vX -> ( 3588.59398016 ) }, TreeLevelPotentialValue -> 87623523.666, EffectivePotentialValue -> -1.55326346578e+13 }
Global minimum found: { { vH -> ( -6.5496774844e-09 ), vX -> ( -3588.59084348 ) }, TreeLevelPotentialValue -> 87618151.9985, EffectivePotentialValue -> -1.55326346578e+13 }


tunnelingCalculator.npoints being given 22
falseVacuumArray = [ 247.654147 2500. ]
trueVacuumArray = [ -7.71967874e-08 3.58859398e+03]
Traceback (most recent call last):
File "./Vevacious.py", line 117, in <module>
thermalNotQuantum = False )
File "/home/smandal/packages/VEVA/Vevacious/bin/VevaciousParameterDependent.py", line 1242, in CalculateAction
quickTunneling = False )
TypeError: fullTunneling() got an unexpected keyword argument 'phi'

Minimizing the one-loop potential, calculating the tunneling time or its upper bound, and printing the results took 3.26742 seconds.

Warning! "/home/smandal/packages/VEVA/Vevacious/MyResult.vout" was not produced!

Vevacious finished. Total running time was 3.27601 seconds.

I dont have any clue what is going wrong. Looking forward for your answer.

Cheers,
Sanjoy

[FStaub]

Hi,

Might it be that you are looking at a unbounded from below direction ? CT can't be used in that case.

Cheers.
Florian

[smandal123]

Hi,

Maybe you are right. I attached the LesHouches.inBLSM file. When I increased the vXinput from 3.00E+03 to 3.500E+03, its working and I am getting the following results,

Result summary (not recapping warnings):
<reference version="1.2.00" citation="arXiv:1307.1477, arXiv:1405.7376 (hep-ph)" />
<stability slha_summary_code="1" > stable </stability>
<quantum_stability> stable </quantum_stability>
<thermal_stability> stable </thermal_stability>
<global_minimum relative_depth="-4.68840430378e+13" vH="247.677103" vX="3500.0" />
<input_minimum relative_depth="-4.68840430378e+13" vH="247.677103" vX="3500.0" />
<lifetime action_calculation="unnecessary" > -1.0 </lifetime>
<tunneling_temperature survival_probability="1.0" > unnecessary </tunneling_temperature>

[benoleary]

Well, the potential is a bit difficult to do at one loop numerically, it seems. MINUIT complains a lot about being unable to get to a minimum within its tolerances:
"
VariableMetricBuilder: Tolerance is not sufficient - edm is 0.00112391 requested 1e-05 continue the minimization
VariableMetricBuilder: warning: no improvement in line search
VariableMetricBuilder: finishes without convergence.
VariableMetricBuilder: edm= 7.35719e+17 requested: 1e-05
FunctionMinimum is invalid.
The MINUIT wrapper threw an exception:
Function value is above the specified estimated distance to the minimum (edm).
while trying to minimize the potential starting at { vH -> ( 247.654147 ), vX -> ( 2500.0 ) }. MINUIT stopped at { vH -> ( -0.120258700773 ), vX -> ( 3016.51809167 ) }. MINUIT's estimate of how much deeper it should go is 9.48730901084e+18 GeV^4.
Taking the starting point as a vacuum candidate.
"

So the tree-level minimum at vH -> ( 247.654147 ), vX -> ( 2500.0 ) seemed to be very problematic for MINUIT. Vevacious has no better idea than to just take the tree-level minimum as a substitute in that case, but since MINUIT tried to roll away from there, it is probably not anything like a minimum, so CosmoTransitions is probably trying to calculate tunneling for an invalid set-up, and failing.

Regards,
Ben