Missing data error when no data is missing
Posted: Wed May 16, 2018 5:49 pm
Hello all,
I'm trying to run a Raven model with MultiData files as forcing inputs (precipitation, daily maximum temperature, daily minimum temperature). When I try to run the model, I get:
Exiting Gracefully: CGauge::Initialize: Raven cannot have blank data in temperature time series
Error Type: Bad input data
So naturally, I spent a long time trying to figure out where the missing data was. I created new files to run one basin at a time and varied the run time until I discovered the offending row of data. It turns out there is no data missing at all! Furthermore, if I change one of the values by just 0.001, it works! This is very reproducible - 100% of the time I run the model with the original data it fails, and 100% if I change the "offending" row, it works. The row causing the failure is (precipitation in mm, daily max temp in deg Celsius, and daily min temp in deg Celsius):
0.083 0.813 -3.282
which are physically reasonable values and which are formatted in the same manner as other lines in the input file.
Has anybody run into an issue like this? If not, is there at least a way to know what line(s) of input the model doesn't like? I'm happy to change the inputs by 0.001 where necessary, as such a change is well within the accuracy of my data anyway, but it's taking me an excessive amount of time to figure out where the problem(s) are located by trial and error. Thanks in advance!
I'm trying to run a Raven model with MultiData files as forcing inputs (precipitation, daily maximum temperature, daily minimum temperature). When I try to run the model, I get:
Exiting Gracefully: CGauge::Initialize: Raven cannot have blank data in temperature time series
Error Type: Bad input data
So naturally, I spent a long time trying to figure out where the missing data was. I created new files to run one basin at a time and varied the run time until I discovered the offending row of data. It turns out there is no data missing at all! Furthermore, if I change one of the values by just 0.001, it works! This is very reproducible - 100% of the time I run the model with the original data it fails, and 100% if I change the "offending" row, it works. The row causing the failure is (precipitation in mm, daily max temp in deg Celsius, and daily min temp in deg Celsius):
0.083 0.813 -3.282
which are physically reasonable values and which are formatted in the same manner as other lines in the input file.
Has anybody run into an issue like this? If not, is there at least a way to know what line(s) of input the model doesn't like? I'm happy to change the inputs by 0.001 where necessary, as such a change is well within the accuracy of my data anyway, but it's taking me an excessive amount of time to figure out where the problem(s) are located by trial and error. Thanks in advance!