-
Notifications
You must be signed in to change notification settings - Fork 51
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
Expand diffusive domain to include tributaries #740
Expand diffusive domain to include tributaries #740
Conversation
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.
The master branch already has these csv files under LowerColorado_TX_v4 folder. Do we still need to merge these files?
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.
Yeah, the current LowerColorado_TX_v4 test case is using hydrofabric v2.0. These changes update it (geopackage and forcing files) to v2.0.1
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.
got it.
This allows the
routing
class diffusive object to add all tributaries to the diffusive domain. Because the diffusive module currently cannot handle reservoirs, this will always stop at the segment just below a reservoir. All other contributing segments will be added to the diffusive domain.This PR also restructures the
coastal_domain.yaml
file format.Additions
AbstractRouting.py
reachable
function on thereverse_connections
dictionary, starting at each diffusive domain tailwater. Waterbodies are excluded by providing their outlets as thetarget
input to thereachable
function.HYFeaturesNetwork.py
Removals
Changes
AbstractNetwork.py
waterbody_dataframe
as an input torouting
class to ensure the diffusive domain is cut-off at the outlets of waterbodies.AbstractRouting.py
upstream_boundary_mainstem_link
to excludeheadwaters
frommainstem_segs
list. Previously,upstream_boundary_mainstem_link
was a list of length 1, so that single value was removed. Now, because it can be a longer list, it is iterated through and all values within are removed frommainstem_segs
.Testing
Screenshots
Notes
Todos
Checklist
Testing checklist
Target Environment support
Accessibility
Other