-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Move Amplitude to Outflows #58
Comments
Amplitudes are on links so not sure I understand how this loss could be On Mon, 23 Nov 2015 16:00:08 -0800, Quinn Hart notifications@github.com
Marion W. Jenkins, PhD |
@mimijenkins1 I think everyone of my examples are on links. Sorry, I see that I said node, where I meant to write 'link'. |
We are considering removing the amplitude on a link, and replacing that with changes to the sink/outflow parameters. This would be a more standardized method of description. In order to support that, we'd also need to have a new constraint type; at least something like EQF 'Equal Flow Percentage'
Some examples:
Consumptive Loss
Might become
Conveyance Loss
https://github.com/ucd-cws/calvin-network-data/tree/master/data/tulare-lake/c49-c51
to
Return Flows / Consumptive Use
Many (~40) of <0.2 amplitudes identifying some return flow from a consumptative use flow.
Would maybe become (Combining)
Reuse
There are about 20 examples of amplitudes > 1 for reuse: Many have the same descriptor 'Hideen ag delivery reuse calibration link'.
Might Become
The text was updated successfully, but these errors were encountered: