Incorrect nucleation temperature about cosmotransitions HOT 3 CLOSED

Hi Mike,

It's been a while since I've looked at this, but the intention was definitely to find the correct higher temperature in situations like this. The critical section of code is in transitionFinder.tunnelFromPhase(), in particular line 843. If it runs into a situation where S3/T is bigger than 140 at both Tmax and Tmin, it should attempt to find a new Tmin somewhere in between where S3/T is in fact at its minimum. It will then use that new minimum as the baseline for finding the point at which S3/T first drops below 140. I'm not sure why it would be returning the lower of the two temperatures instead.

If you provide a reproducible test case I should be able to dig into it some more.

Best wishes,
Max

from cosmotransitions.

Hi Max,

Thanks again for your swift reply. The problem seems to be with the new Tmax that's found by transitionFinder._maxTCritForPhase(), if f(a) and f(b) have the same sign. In my case, Tmax is getting set to 0. I think I've tracked down the cause of the problem to the function transitionFinder._potentialDiffForPhase().

Line 722 is currently

    V1 = V(start_phase.valAt(T),T)

whereas I think it should be

    V1 = V(phase.valAt(T),T)

Do you agree?

If I make this change, cosmoTransitions finds the correct, higher, nucleation temperature in my case.

Best,

Michael

from cosmotransitions.

That definitely looks like a bug. Thanks for catching it. I've pushed a commit with the offending line swapped out.

from cosmotransitions.