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

Landfast bathymetry implementation #594

Open
apcraig opened this issue Apr 8, 2021 · 1 comment
Open

Landfast bathymetry implementation #594

apcraig opened this issue Apr 8, 2021 · 1 comment

Comments

@apcraig
Copy link
Contributor

apcraig commented Apr 8, 2021

See #573. We want to move away from the hardcoded 40 level implementation and rethink how that is implemented. One other issue is that even if bathymetry and landuse is off, it still reads in the hardcoded 40 levels and blows out of bounds if max(kmt)>40. This is the case in RASM and is why #593 was needed in the mean time.

@TillRasmussen
Copy link
Contributor

I would force the code to read the depth. This can either be done through the existing variable kmt or by creating a new variable, which could be Bathymetry.
One exception would be if someone passes the depth through an coupling interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants