After looking into this further, it looks like the value of "nValueSup"
is twice what it should be for the following loop:

for i in range(int(round(nLenWSO-self.NTP)), nValueSup):
    fFactor = fSlope*(i-nLenWSO+self.NTP)+fTdCorr
    naWS[i-self.NTP2] = fFactor*naWS[i-self.NTP2]

"nValueSup" gets set with the following code:
nValueSup = nLenWSO-self.NTP + 4*3600/metro_constant.fTimeStep

In the case I'm working on "nLenWSO-self.NTP" is equal to 0 and
"4*3600/metro_constant.fTimeStep" is equal to 480 (but should be equal
to 240 because the length of naWS is 240).

So, it looks like part of or all of the nValueSup assignment statement
should be divided by two, but I don't really understand the science
behind this, so I'm not sure which part (or maybe I'm not correctly
interpreting the problem, and there is a different problem entirely).

Julie

_______________________________________________
METRo-developers mailing list
[email protected]
https://mail.gna.org/listinfo/metro-developers

Reply via email to