-
Notifications
You must be signed in to change notification settings - Fork 3
Phase tracing issues #273
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingphysics questionQuestions that have more to do with physics than codeQuestions that have more to do with physics than code
Description
jorindevandevis
opened on Sep 24, 2024
Issue body actions
- Sometimes the phase tracing takes very long. One reason for this is that the tracer will try to follow the phase all the way to T = 0 (if it exists). In principle, there is no lower limit on the temperature that we could probe in WallGo, but in practice, one does not reach this minimum temperature. It is thus a waste of computational time to trace it all the way to T = 0, and it would be better to impose a minimum temperature. Need to come up with a good estimate for that.
- Sometimes the phase tracing proceeds without problem, but WallGo finds a run-away wall, which it wouldn't find for a different value of TemperatureScale. Need to figure out what causes this, and throw an error/warning earlier.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingphysics questionQuestions that have more to do with physics than codeQuestions that have more to do with physics than code