Hi Giov,

You can find all previous verions of CosmoTransition here: https://github.com/clwainwright/CosmoTr ... s/releases

Best,
E.

Dear Sanjoy, The reason you can approximate the potential as \lambda_eff (H H^\dagger)^2 at high energies (notice the square) is due to the fact that for very high semi-classical field values (H_0 -> ∞ ), the quartic part of the potential dominates. Provided that your potential does not have any fla...

Dear smandal123, I think you are trying to tackle a different problem than what Vevacious is designed for at the moment. Vevacious works at a fixed scale so essentially the question it answers is: at a given scale, are there any deeper minima than the DSB (desired symmetry breaking) and if so what i...

Hi Sam,

It is hard to tell what is going on. Could you attach the model file and parameter point you are trying to run?

Best, E.

Dear Sam,

Have you by any chance accidentally deleted the file "__init__.py" in the cosmoTransitions folder?

Best,
E.

Hi again, Vevacious will start at the point you tell it and numerically minimize the one-loop potential. Modulo numerical errors or pathologically very shallow potentials, it will find the closest (or one of the closer) minima. If the DSB is there at one-loop but far away from the two-loop minimum (...

Hi Jyotiranjan, You can see an example of such behaviour (with 2-loop corrections being necessary for a stable DSB) in https://arxiv.org/abs/1605.02072. As Ben very well said, 2-loop corrections can be the difference between having a DSB minimum or not at all. If Vevacious goes to a point in field s...

Dear Liang, I took a quick look and ran your spectrum file with the NMSSM model files and I get the same issue. Looking closely, it seems that your "physical" minimum does not really seem to be a minimum of the potential defined by the parameters (I tried just numerically minimizing the tree-level p...

Dear Liang, Regarding your questions about the difference between quantum and thermal corrections, perhaps in https://arxiv.org/pdf/1405.7376.pdf you can find some more details and references about how we deal with those in Vevacious. The block mass-squared_matrix is used in all calculations, as the...

Dear Roberto, It would be useful to know with a bit more detail what is going on. I don't see a priori why Vevacious should crash if the depth is very close. Could you specify which model are you using and exactly at which point Vevacious crashes? perhaps if possible you can post what is the output ...