Laserfiche WebLink
<br />. <br /> <br />. <br /> <br />. <br /> <br />o Q J :5 TJ <br /> <br />If the shortage threshold is going to be applied and a shortage exists (request are <br />greater than deliveries), the method needs to calculate the percent shortage as: <br /> <br />shortage ~ 100.0 . (1.0 - (diversion requested I diversion delivered)) <br /> <br />If the shortage is greater than 75 percent, do not apply salt pickup. <br /> <br />It the diversion is a WOIP, the salt pickup will be negative. If the salt pickup is <br />negative, the method will determine if sufficient salt exists in the river to satisfy the <br />WQIP. If not, the amount of removal is set equal to the amount available. A slot will <br />be created to remember the deficient which the method will attempt to repay in <br />subsequent time steps. Alternatively, it may be feasible to identify two separate return <br />flow methods, one for regular return flows, and one for WOIP's. Regardless, a slot will <br />be needed to track the salt debt. <br /> <br />3.4 Confluences <br /> <br />As noted above, we should be able to borrow the code of the existing method, delete <br />the temperature component, and have a useable method. <br /> <br />4.0 Remaining Issues <br /> <br />We need to clarify units. Because we are going to recycle some existing water quality <br />slots which have default units defined, the user will bear some responsibility in <br />providing consistent data and units. <br /> <br />We need to decide if the percent shortage threshold will be used.. <br /> <br />We need to decide it WOIP's should be handled as a separate method. <br />