I have the same issue with the Meteotemplate rain totals due to the midnight carry over of the previous day rain total. This occurs with the 5 second update rate. The problem has been occurring since the change over from clientraw to the API. It is fairly easy for me to fix the first line of the day in the database using the Meteotemplate editor. A possible solution could be to not do the API update for the 00:00 minute. The database will still get the 5 minute average or max value in the array depending on the variable.
Thanks,
Gus
Have either of you asked Jachym to take a look or improvise specific code changes to check for this, and do a one-time correction? It sounds as if you have analyzed this very well, have found what quirk makes the error occur. I would assume he could quickly do a check for that at the turn of midnight and do automatically what you guys have been doing manually.
Your analysis is very thorough. Hat’s off to your persistence and dedication to accurate data collection. Knowing what the error is caused by, and how it is fixed should make the programming much easier.
I have, and his initial response was to edit the database. I’ve posted follow-up the next time it occurred, after the next rain event, but no response, and no other user has said they have the same issue.
Gus is the only other person to post they also have experienced this. Maybe the rest of WD/MT users are still relying on clientraw.txt to update MT.
one solution is WD does not send a fast update to meteotemplate around that midnight change over time at the change of a new month (or even just around midnight any day?)?
I’m having WD send both the clientraw to have FreshWDL work, and also the API sending Meteotemplate data to the SQL database on my server.
And not having had anything but copious quantities of snow (and more to come by the sounds of it in another day or so) I’ve not followed the day to day periods. I am hoping for just plain rain soon.
I was going to text Jachym to see if he was still working on the project or not. I may still, to let him know there is interest in continuing on with this being resolved.
Dale
This has felt like a timing issue, but now I am not sure. I have WD’s API updater sending data every 3 seconds. To further trouble shoot, I have changed that to 1 minute intervals, and 5 minute intervals on days it has rained.
The same problem exists, the 00:00:00 entry in the MT database for the next day includes the rain total from the previous day, but the 00:00:05 does not. However that 00:00:00 entry throws totals off until corrected. Fortunately Jachym has made it easy to edit the SQL database on the server.
if there is no data sent right on the midnight time then MT must be like dividing up the time stamps it does receive into nice 5 minute intervals
and so if it got data with a time stamp before midnight and one after, then its ‘making up’ a time stamp of midnight
but it needs to use the data from the most recent data…not the one prior…the one prior will have the previous days rain total