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

depth bounds mesh size enforcement #230

Merged
merged 8 commits into from
Jul 26, 2021
Merged

depth bounds mesh size enforcement #230

merged 8 commits into from
Jul 26, 2021

Conversation

krober10nd
Copy link
Collaborator

@krober10nd krober10nd commented Jun 17, 2021

  • enforce the function between min and max depth bounds.

Keith Roberts added 2 commits June 17, 2021 17:42
* enforce the wavelength function between 10-m deep and infinity bathymetry by default.
@krober10nd
Copy link
Collaborator Author

we should address this #154 and also make all sizing functions consistent w.r.t. to the depth bound ranges the parameter is enforced on.

@WPringle
Copy link
Collaborator

WPringle commented Jul 15, 2021

Yes definitely need to make the depth bound criteria much easier to understand like suggested in #154 and make it consistent for all sizing functions, and add some information in the help.

@krober10nd krober10nd changed the title wavelength mesh size function enforcement depth bounds mesh size enforcement Jul 16, 2021
@krober10nd krober10nd requested a review from WPringle July 16, 2021 16:11
@krober10nd krober10nd linked an issue Jul 16, 2021 that may be closed by this pull request
@krober10nd krober10nd added the enhancement New feature or request label Jul 16, 2021
@WPringle
Copy link
Collaborator

The Example_6b is quite weird that for the max_el variable it sets the max_el both in ocean and overland to be the same (1 km). I guess is supposed to different?

Keith Roberts and others added 2 commits July 21, 2021 12:38
* Change maximum mesh resolution bound to 500 m overland.
…description

- In `edgefx` change all so-called depth bounds variables to z_min/z_max bounds to correctly represent that it is actually a topographic elevation bound
- add helper information for `edgefx` on the different variable types for each input and description of the topographic elevation bound structure
- correct description of elevation bounds in `Example_6b`
Copy link
Collaborator

@WPringle WPringle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made the changes to be consistent across all options and to make clear to us and the user that is an elevation bound not a depth bound (i.e, negative is underwater, same as DEM).

Checked the result on the Example_6b and mesh resolution distribution plot looks correct.

@krober10nd
Copy link
Collaborator Author

Okay thanks. Let’s update the change log so it refs this pull request and then merge it.

@WPringle WPringle merged commit 8c41c70 into Projection Jul 26, 2021
@WPringle WPringle deleted the wl_enforcement branch July 26, 2021 01:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

depth-based bounds enforcement
2 participants