Gaga readings from FO - when to edit the data files?

[fractonimbus]

My FO unit went gaga for a few minutes this afternoon, reading impossible wind and rainfall figures. I edited the data files to the previous backup, but on reloading the data from the FO, the same silly values reoccurred, so they are embedded on the FO memory.

What's the best thing to do to get rid of these nonsense values? I presume I need to wait for a few days until the bad data is overwritten, then edit the various data files to remove the nonsense values.

Advice appreciated.

DN

[steve]

It doesn't really make any difference whether you do it now or wait a couple of days. Changing today's rainfall is the trickiest bit (in 1.9.1).

If you do it today, you need to edit today.ini rather than dayfile.txt. You may also need to edit this month's/this year's/all-time highs and lows, if they were affected.

Edit: Looking at your site, today's rainfall total corrected itself anyway, so that simplifies things.

[fractonimbus]

Thanks, Steve. Yes, for some reason the revised rainfall stuck, but the record values are wrong, so I'll edit out everything that's bad.

Maybe we need a "kill silly readings" button

DN

[steve]

Maybe we need a "kill silly readings" button

Tricky. I tend to concentrate on 'stop silly readings being recorded'. I can't remember exactly what's in 1.9.1 compared to 1.9.2, but the 'spike removal' settings seem to work quite well. And 1.9.2 is getting better at ignoring rainfall total problems, I think.

[The QCC]

If Cumulus has read the data from the FO data logger, you can use the FO Clear data option to purge the errors in the console.

Carl.

[fractonimbus]

Steve: The bad values are now edited.
Carl: Thanks, I didn't know there was a purge control.

DN