Skip to content
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

Change handling of source terms in a many-levels domain #28

Open
rthedin opened this issue Nov 10, 2020 · 0 comments
Open

Change handling of source terms in a many-levels domain #28

rthedin opened this issue Nov 10, 2020 · 0 comments
Assignees

Comments

@rthedin
Copy link
Collaborator

rthedin commented Nov 10, 2020

The source terms get read before they are interpolated onto all the different levels (heights) of the new grid. In the reading routine, it computes all the levels present in the grid. That is usually not a problems because we do simple grids with flat boundaries, resulting only in a handful of levels (which was even recently improved by PR #26).

The problem, however, arises when using any complex geometry as the bottom boundary, resulting in LOTS of different levels. The solver hangs in the computation of those levels, during zPlanes_.initialize(), which triggers zPlanes_(mesh_). I let the solver run for over a day and it did not get past that call.

@ewquon ewquon self-assigned this Feb 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants