Brian,
Last night (after upgrading to 10.16 during the day), the first record for today (in mysql) had the rainfall from yesterday i.e. the values were not reset before the first record was written at 12.00 am. The values were reset in the second record (12.01 am).
Cheers,
Ian
it wil be becuase the data is from the clientraw.txt file, and the separate wdmysql gets the midnight change before wd has done the midnight reset and update the clientraw.txt file
not much i can do about that
not much i can do about that
You could make the upload program not upload anything at 00:00 (or 00:01 depending on which upload is causing the problem). I know that gives a data gap, but perhaps a missing minute of data is better than incorrect data?
it depends on how much trouble this problem will cause…is it rally going to be a problem?
It could be a problem. If people start writing code to do analysis of daily MySQL data, then data retained from the previous day might cause some odd numbers to be generated.
but delaying it could cause similar problems…(not having the 0:00 update)
hummmm
Brian,
I didn’t just stumble across this, I have a lot of SQL queries I use and it was noticeable very quickly that the max/min/daily rain returned by these queries is affected by this issue. Before the mysql integration with WD, I had used my own program to convert the WD logfiles to mysql tables.
This problem did not occur for the logfiles that WD maintains itself. Can’t you use similar logic to prevent it happening for the clientraw/mysql data feeds?
If not, then at least an option in the wdmysql program to not write the first record after midnight would be better than storing inaccurate data in the database.
Cheers,
Ian
yes, not updating the minute after the daily reset time will fix it…yes?
That would make me happy - but someone else might complain! So put a check box next to this option!
Cheers
Ian
also,i am actualy thking of putting the data across via the registry…or dde …
as its looking like too many things accessing the clientraw.txt file is causing problems…
i will do both of these things soon (been at a school “olympics” add day today.,LOL
DDE would be better than registry. Or you could just use the UDP multicasting, and have the wdmysql listen in the same way as remote client. Then wdmysql could just run on the same machine as mysql, if it happens to be different.
/Ian
i have now set to transfer the data via the registry, that data being updated on the minute
that should fix this issue…you need to be using wdmyswl 1.3 and WD version 10.16e, full version i am uploading at the moment
it will be ready in an hour or less ( a new 10.16e)
yes, i could use dde
but for the first step i have used the registry (which has taken over form dde…the registry is actualy realy fast)
wdmyswl running on the pc where the mysql is…that would work if it was a windows pc running windows mysql…but not a linux server pc…