-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hydrostatic condition for open domain #91
Comments
I realized now that I can just force the hydrostatic condition with |
That rings a bell with an old issue of PeleLM that @nickwimer found a while back. |
Sounds great! Those snippets do seem like they would do the trick. |
Just checking in to see if this issue has been resolved? |
Not yet, the entire infrastructure to handle the phi BC isn't setup in LMeX. I'm thinking it could actually live into AMReX-Hydro projectors, but I need to discuss that with the LBNL team. |
Is this problem solved now? |
For myself, I just set |
I am in the middle of a rewrite to sections of the code to fix the underlying issue at play here. In the meantime, @mameehan5 would you be willing to share your solution involving the |
Yep! In the input file, if using gravity, say |
Did this get resolved @nickwimer ? |
Hi all,
I am looking to run a buoyancy-driven flow that is open to atmospheric conditions. However, when running a simulation with boundary conditions specified as "Outflow" normal to the direction of gravity, the hydrostatic condition induced by the gravitational field disappears.
To show this most clearly, starting from the HotBubble tutorial case, the following conditions
produced an
avg_pressure
field (usingyt
)as expected for the first snapshot with a hydrostatic condition.
Using
produced
Again, this is expected.
And finally, using
produced
This last image I would have expected to be quite similar to the other two. Is there a physical justification for this behavior or a bug? If the former, is there a way to introduce the hydrostatic condition?
Thank you very much!!
The text was updated successfully, but these errors were encountered: