Sunday, May 24, 2015
Casually weird 3
Weather Bureau is still running the same defective software. The error seems to happen in the first three segments of the forecast.
Makes me wonder if this is happening nationally. Seems unlikely that Spokane would have its own custom software, and I can't see how a hardware problem or a data entry problem could be involved. The max and min timepoints are not on manually-read gauges, they're produced by software models. If you read those points from the screen and typed them into the language-generator by hand, you'd notice this problem instantly.
A quick check of 10 other cities finds no examples of the error, but that doesn't mean much. The error is clearly intermittent, doesn't happen every day.
¶ 1:48 AM 
Weather Bureau is still running the same defective software. The error seems to happen in the first three segments of the forecast.
Makes me wonder if this is happening nationally. Seems unlikely that Spokane would have its own custom software, and I can't see how a hardware problem or a data entry problem could be involved. The max and min timepoints are not on manually-read gauges, they're produced by software models. If you read those points from the screen and typed them into the language-generator by hand, you'd notice this problem instantly.
A quick check of 10 other cities finds no examples of the error, but that doesn't mean much. The error is clearly intermittent, doesn't happen every day.
¶ 1:48 AM
