-
Notifications
You must be signed in to change notification settings - Fork 82
Adding threshold option to extract_subdomain #177
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
Conversation
* Elements/vertices can be trimmed inside polygons based on topobathymetry.
|
Perhaps the kwargs of |
|
Yes I agree we should change the kwarg to name/value pairs. Also can you have threshold work both ways or as a range. Often I want to do it so only elements shallower than 250 m are kept, i.e., only continental shelf. |
Singly elements can be deleted using |
WPringle
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can the threshold parameter be a bit more clearer and also allow for options both ways?
How about change to two parameters, min_depth and max_depth which are easier to understand and also allows for doing a range
|
Ok I'm still a little confused about the the description of min_depth and max_depth on the help and how it is actually implemented. I think the way it is implemented is correct; so that if depth is less than the max_depth and more than the min_depth and inside the polygon then it is trimmed. But help is saying max_depth is to keep parts that are sufficiently deep when it should be other way around. Keep the parts that are shallower than max_depth and deeper than min_depth right? |
|
and change the if statement to be |
|
Can change the max_depth to be sufficiently shallow and min_depth to be sufficiently deep on the help? |
help typo
polygonand remap all the attributes (nodal attributes and boundaries) back to the trimmed mesh.Note this maps all nodal attributes to the subdomain. For example, if the parent mesh had a directional wind stress nodal attribute, now the subdomain does too.