Move Amplitude to Outflows

[qjhart]

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

"prmname":"HSU202SR_6-A202",
 "description":"Diversion from Oroville Lake to CVPM 5 (DA 69) via Palermo canal",
 "type":"Diversion",
 "origin":"HSU202SR_6",
 "terminus":"A202",
 "amplitude":0.959999978542328,
 "costs":{"type":"Constant",
 "cost":0},
 "bounds":[{"type":"NOB"}],
 "sinks":null,
 "flow":{"$ref" : "flow.csv"}

Might become

"prmname":"HSU202SR_6-A202",
 "description":"Diversion from Oroville Lake to CVPM 5 (DA 69) via Palermo canal",
 "type":"Diversion",
 "origin":"HSU202SR_6",
 "terminus":"A202",
  "sinks":{
  "cvpm5": {
    type:"consumptive use'",
   bounds: [{type:"EQF", bounds: 0.04}]
 }
}
 "flow":{"$ref" : "flow.csv"}}}

Conveyance Loss

https://github.com/ucd-cws/calvin-network-data/tree/master/data/tulare-lake/c49-c51

"prmname":"C49-C51",
 "description":"Friant-Kern Canal discharge to Kings River",
 "type":"Diversion",
 "origin":"C49",
 "terminus":"C51",
 "amplitude":0.910000026226044,
 "costs":{"type":"Constant",
 "cost":0},
 "bounds":[{"type":"UBC","bound":0}],
 "sinks":null,
 "flow":{"$ref" : "flow.csv"}}}

to

"prmname":"C49-C51",
 "description":"Friant-Kern Canal discharge to Kings River",
 "type":"Diversion",
 "origin":"C49",
 "terminus":"C51",
 "costs":{"type":"Constant",
 "cost":0},
 "bounds":[{"type":"UBC","bound":0}],
 "sinks":{
 "canal losses":{
  type : "conveyance loss",
 bounds : [{"type":"EQF", bounds:0.09}]
 "flow":{"$ref" : "flow.csv"}}}

Return Flows / Consumptive Use

Many (~40) of <0.2 amplitudes identifying some return flow from a consumptative use flow.

 "properties":{"prmname":"U102-INT_CVPM02",
 "description":null,
 "type":"Diversion",
 "origin":"U102",
 "terminus":"INT_CVPM02",
 "amplitude":1,
 "costs":{"type":"Constant",
 "cost":0},
 "bounds":[{"type":"EQT","bound": {"$ref":"./EQT.csv"}}],
 "sinks":null,
 "flow":null}

 "properties":{"prmname":"INT_CVPM02-HGR02",
 "description":"Interior GW return flow from fixed CVPM urban pumping demand",
 "type":"Diversion",
 "origin":"INT_CVPM02",
 "terminus":"HGR02",
 "amplitude":0.00100000004749745,
 "costs":{"type":"Constant",
 "cost":0},
 "bounds":[{"type":"NOB"}],
 "sinks":null,
 "flow":{"$ref" : "flow.csv"}}

Would maybe become (Combining)

"properties":{"prmname":"U102-INT_CVPM02",
 "description":null,
 "type":"Diversion",
 "origin":"U102",
 "terminus":"HGR-02",
 "bounds":[{"type":"EQT","bound": {"$ref":"./EQT.csv"}}],
 "sinks":{
  "percolation" : {
    type:"Return Flow"
     bounds":[{"type":"EQF";
                "bound":0.001}]
}

Reuse

There are about 20 examples of amplitudes > 1 for reuse: Many have the same descriptor 'Hideen ag delivery reuse calibration link'.

"prmname":"A103B-HU103B",
 "description":null,
 "type":"Diversion",
 "origin":"A103B",
 "terminus":"HU103B",
 "amplitude":1.18299996852875,
 "costs":{"type":"Constant",
 "cost":0},
 "bounds":[{"type":"NOB"}],
 "sinks":null,
 "flow":{"$ref" : "flow.csv"}}}

Might Become

"prmname":"A103B-HU103B",
 "description":null,
 "type":"Diversion",
 "origin":"A103B",
 "terminus":"HU103B",
 "costs":{"type":"Constant",
 "cost":0},
 "bounds":[{"type":"NOB"}],
 "sinks":{
"Ag Reuse" :{
 "type":"EQF",
 bound:-0.18
}

[mimijenkins1]

Amplitudes are on links so not sure I understand how this loss could be
attached to a node. For example, what happens if there is more than one
link going out from the node, each with a different amplitude? Don't we
need to keep these flow losses on their respective links?

On Mon, 23 Nov 2015 16:00:08 -0800, Quinn Hart [email protected]
wrote:

We are considering removing the amplitude on a node, 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 >CFP/CF%
'Constant Flow Percentage'
Some examples:
Consumptive Loss
"prmname":"HSU202SR_6-A202",
"description":"Diversion from Oroville Lake to CVPM 5 (DA 69) via
Palermo canal",
"type":"Diversion",
"origin":"HSU202SR_6",
"terminus":"A202",
"amplitude":0.959999978542328,
"costs":{"type":"Constant",
"cost":0},
"bounds":[{"type":"NOB"}],
"sinks":null,
"flow":{"$ref" : "flow.csv"}

Might become
"prmname":"HSU202SR_6-A202",
"description":"Diversion from Oroville Lake to CVPM 5 (DA 69) via
Palermo canal",
"type":"Diversion",
"origin":"HSU202SR_6",
"terminus":"A202",
"sinks":{
"cvpm5": {
type:"consumptive use'",
bounds: {type:"EQF", bounds: 0.04}
}
}
"flow":{"$ref" : "flow.csv"}}}

Conveyance Loss

Can't fine one

Return Flows / Consumptive Use

Many (~40) of <0.2 amplitudes identifying some return flow from a
consumptative use flow.

"properties":{"prmname":"U102-INT_CVPM02",
"description":null,
"type":"Diversion",
"origin":"U102",
"terminus":"INT_CVPM02",
"amplitude":1,
"costs":{"type":"Constant",
"cost":0},
"bounds":[{"type":"EQT","bound": {"$ref":"./EQT.csv"}}],
"sinks":null,
"flow":null}

"properties":{"prmname":"INT_CVPM02-HGR02",
"description":"Interior GW return flow from fixed CVPM urban pumping
demand",
"type":"Diversion",
"origin":"INT_CVPM02",
"terminus":"HGR02",
"amplitude":0.00100000004749745,
"costs":{"type":"Constant",
"cost":0},
"bounds":[{"type":"NOB"}],
"sinks":null,
"flow":{"$ref" : "flow.csv"}}

Would maybe become (Combining)

"properties":{"prmname":"U102-INT_CVPM02",
"description":null,
"type":"Diversion",
"origin":"U102",
"terminus":"HGR-02",
"bounds":[{"type":"EQT","bound": {"$ref":"./EQT.csv"}}],
"sinks":{
"percolation" : {
type:"Return Flow"
bounds":{"type":"EQF";
"bound":0.001}
}

Reuse

There are about 20 examples of amplitudes > 1 for reuse: Many have the
same descriptor 'Hideen ag delivery reuse calibration link'.

"prmname":"A103B-HU103B",
"description":null,
"type":"Diversion",
"origin":"A103B",
"terminus":"HU103B",
"amplitude":1.18299996852875,
"costs":{"type":"Constant",
"cost":0},
"bounds":[{"type":"NOB"}],
"sinks":null,
"flow":{"$ref" : "flow.csv"}}}

Might Become

"prmname":"A103B-HU103B",
"description":null,
"type":"Diversion",
"origin":"A103B",
"terminus":"HU103B",
"costs":{"type":"Constant",
"cost":0},
"bounds":[{"type":"NOB"}],
"sinks":{
"Ag Reuse" :{
"type":"EQF",
bound:-0.18
}

—
Reply to this email directly or view it on GitHub.

Marion W. Jenkins, PhD
Associate Research Engineer
Dept. Civil & Environmental Engineering
Ghausi Hall, Rm 3019
University of California at Davis
Davis, CA 95616
Tel: +1 530 754 6427
Fax: +1 530 752 7872

[qjhart]

@mimijenkins1 I think everyone of my examples are on links. Sorry, I see that I said node, where I meant to write 'link'.