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

Not specifying basin areas correctly can lead to bad results/not be mass conservative #100

Open
arbennett opened this issue Aug 20, 2023 · 5 comments

Comments

@arbennett
Copy link
Member

bmorph relies on an undocumented assumption when using SCBC that flows coming out of the local bias correction are volumes and need to have a specific modification to the network topology basin areas so that when rerouting mizuRoute interprets the flows correctly. In the case of daily flows the basin areas must be set to 86,400,000 which is the number of milliseconds in a day to work appropriately. If the basin areas are left as is, the flows will be converted to incorrect units, but simply run through mizuRoute. Here's a comparison - scaled is the correct version and unscaled is if you use the actual physical areas:

image

@bartnijssen
Copy link
Member

🤯

@blounsbury-usbr
Copy link
Contributor

Just a note that this is documented in issue #54 as well.

@arbennett
Copy link
Member Author

🤯 - thanks @blounsbury-usbr, hopefully I won't file another issue outlining the same thing in another two years 😓

@bartnijssen
Copy link
Member

It's probably not simply milliseconds/day, but a combination of seconds/day and some other unit conversion (like mm /m). Obviously the end result is the same, but it may provide a hint in tracking this down in the code.

@bartnijssen
Copy link
Member

I should have read Issue #54 first. As stated there it is m/km.

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

3 participants