ARCCSS-extremes/climpact2

Test name Too_many_zeros

Closed this issue · 2 comments

Tests the possibility that missing data have been keyed as zero

I entered a period of 0 values in the Bathurst example file. The QC can identify bad temp data that has been keyed as 0 only if both tmax and tmin are 0. If only tmin is 0 it does not since 0 is not an unusual value. So this is merely the check that tmax is greater than tmin. Since it would be very unusual to have consecutive days of 0 values, there should be a check for this.

Done. Warning generated.

On Mon, May 18, 2015 at 12:32 PM, Tammas Loughran notifications@github.com
wrote:

I entered a period of 0 values in the Bathurst example file. The QC can
identify bad temp data that has been keyed as 0 only if both tmax and tmin
are 0. If only tmin is 0 it does not since 0 is not an unusual value. So
this is merely the check that tmax is greater than tmin. Since it would be
very unusual to have consecutive days of 0 values, there should be a check
for this.


Reply to this email directly or view it on GitHub
#28 (comment).