Closed andrewfowlie closed 6 years ago
It looks like there was a problem with the optimization function in SingleFieldInstanton.findRScale()
. Replacing the optimize.fmin
with optimize.fminbound
seems to have fixed it, although I'm not sure why exactly changing the number of points in the fitted potential should have made a difference. In any case, the change is pushed to the develop
branch. Try it out and let me know if you have any problems before I merge it into master.
Thanks, that's fixed it for me. I've added a PR with tests of path deformation for the 1d and 2d potentials - https://github.com/clwainwright/CosmoTransitions/pull/7 - should add the above problematic case to it as well.
Hi Clarence, I never found any problems with this fix (https://github.com/clwainwright/CosmoTransitions/commit/222bb9faeef534323bcf8ca280fe024c8a121837). Can it be merged to master?
Merged, and did a bump up to v2.0.3. I'll update the version on PyPI in minute.
(Who's Clarence?)
Thanks for this, and I'm very sorry for calling you Clarence.
Hi,
I was testing the path deformation algorithm for various 1d potentials. I am parametrising my potentials such that the true and false vacua are always at 1 and 0. I noticed that in rare cases whether it succeeds is sensitive to the number of points I use in my guess of the solution (
n_points
below). If this is too small, I seeOf course, increasing
n_points
is rather easy, but maybe something is wrong with the code here, I'm not sure.