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

periodic BCs incompatible with netcdf topo files #539

Open
bolliger32 opened this issue Aug 13, 2022 · 1 comment
Open

periodic BCs incompatible with netcdf topo files #539

bolliger32 opened this issue Aug 13, 2022 · 1 comment

Comments

@bolliger32
Copy link
Contributor

bolliger32 commented Aug 13, 2022

I'm having problems running a global model with periodic boundary conditions in the E-W direction and "extrap" conditions in the N-S direction. I believe this has to do with how netcdf's are loaded here, b/c they are clipped to within a dx and dy buffer of the domain. This means there is no topography loaded that lies outside of the domain within the ghost cell portion.

This comes into play in setaux.f90. When setting for ghost cells, wrap_coords is called, which, as expected, wraps the E-W cells but does nothing to the N-S cells (since yperdom is false).

Then cellgridintegrate is called, which due to this line, raises an error that there is no topography overlapping that cell.

Does that sound like the right culprit (cc: @mandli @rjleveque)? I imagine the fix would be to increase the extent of the netcdf that gets loaded if you are in this situation.

@mandli
Copy link
Member

mandli commented Aug 14, 2022

Makes sense to me. Periodic BCs are not used in GeoClaw except for planetary wide simulations and I am not sure we have used anything but the ESRI ASCII formats.

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