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

Output flow on catchments with only an inflow node #583

Open
mattw-nws opened this issue Sep 9, 2022 · 1 comment
Open

Output flow on catchments with only an inflow node #583

mattw-nws opened this issue Sep 9, 2022 · 1 comment

Comments

@mattw-nws
Copy link
Contributor

The latest hydrofabrics do not contain outflow nexus nodes in some coastal catchments and inland sink catchments. For these catchments, ensure the inflow is added to the Q_OUT from the catchment model and is copied into the output so that there is some flow output recorded for every catchment.

Current behavior

Expected behavior

  • Need output somehow traceable to every catchment, even if it is not "routed"

Steps to replicate behavior (include URLs)

Screenshots

@mattw-nws mattw-nws mentioned this issue Nov 4, 2022
12 tasks
@jameshalgren
Copy link
Contributor

@mattw-nws This might be generalized as better handling of upstream inflows to a t-route-routed network.

Right now, we consider everything as inflow at the top of a node, whether it is lateral inflow or actual inflow at the top. This means that we have trouble separating something that might be a true upstream inflow boundary condition. (I might be misunderstanding, too...)

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