Skip to content
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

Error with multipath forcing #172

Closed
hboisgon opened this issue Nov 8, 2021 · 3 comments
Closed

Error with multipath forcing #172

hboisgon opened this issue Nov 8, 2021 · 3 comments

Comments

@hboisgon
Copy link
Contributor

hboisgon commented Nov 8, 2021

Hi,

With @christianli24 we've been trying to use the new functionality for multipath forcing in Wflow (inmaps-*.nc).
However, it seems that the full range of the dates is not properly loaded resulting to this type of errors:
“ERROR: DomainError with time 1991-01-02T00:00:00 after dataset end 1991-01-01T00:00:00”.

The model we are using has daily forcing from 1990-01-01 to 2020-12-31 stored in yearly files (first one 1990-01-01 to 1990-12-31). The model runs fine from 1990 until that date (even for 1991-01-01 which is the first timestep in the second netcdf file). Changing the startdate used in the TOML to a later one (ex 1995), still gives the same error (the dataset end in the ERROR message is always 1991-01-01).

Attached is the TOML (text version) and full log message
Wflow.log
wflow_sbm_test.toml.txt

@hboisgon hboisgon added the bug Something isn't working label Nov 8, 2021
@verseve
Copy link
Member

verseve commented Nov 8, 2021

The units of time of each NetCDF file needs to be the same (“days since…”).

@verseve
Copy link
Member

verseve commented Nov 17, 2021

@hboisgon : is this issue resolved with changing the units of time in the NetCDf files?

@verseve verseve removed the bug Something isn't working label Nov 17, 2021
@hboisgon
Copy link
Contributor Author

Yes it is! @christianli24 tested it and is now adding it in the "small_things" branch

@verseve verseve closed this as completed Nov 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants