-
Notifications
You must be signed in to change notification settings - Fork 63
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
Running with NetCDF forcing provider requires forcing data and start_time
to be the same
#451
Comments
Does running bmi_c_cfe model reproduce this behavior? I just want to test on a simpler model at the start. |
My output: |
The last column is Q_OUT, and if that output was produced with CFE only the result can definitely vary, as Noah will change the input that CFE receives. Either way, the first two columns are relevant to the issue and it looks like you are reproducing it successfully. |
NetCDF provider is returning wrong values for time values when the simulation start time is not the same as the forcing file start time.
Current behavior
When using
"forcing":{"provider": "NetCDF"...
and astart_time
that does NOT equal the T0 time in the forcing file, the wrong data is returned for the wrong timesteps, effectively using the timestep index instead of the correct time value.CsvPerFeature
does not exhibit this behavior.Expected behavior
In the example below, the precip starting at 1700 (timestep 38) should start at 1400 (timestep 35) instead.
Steps to replicate behavior (include URLs)
data
:and you will get incorrect data for the timesteps, e.g. cat-27 timestep 38:
This should start at 1400, not 1700, which is timestep 38 in the forcing data...i.e. if you change the
start_time
above to"2015-12-01 00:00:00"
, it will produce:instead.
Screenshots
The text was updated successfully, but these errors were encountered: