DreamDiver wrote:Wow - talk about crowd sourcing. This is incredible, dave21. Count me in.
Thanks DreamDiver! I'm really hoping we can get somewhere further to work out what's going wrong and the very least get this back to ResMed to fix in later S9's if it's the S9 firmware at fault.
DreamDiver wrote:I'm seeing data skew double every day from the data of card wipe - starting with one second the first day. However, data skew seems limited to the beginning and end of line-graph data. I have not let it go long enough that the skew is obvious for the events. It's harder to be sure there is data skew with the events, since they are point data rather than line data.
I think this is similar to what I've seen, when it starts to skew it almost doubles and gets compoundly worse and then to the point it skews too much that over time you then lose an hour of flow data.
DreamDiver wrote:20100405_041127_BRP.edf
05.04.1004.11.28768
4/5/2010 7:41 AM
So if I'm right on this, there's a 1.7 second skew (which is probably within tolerable levels)
DreamDiver wrote:20100402_215805_BRP.edf
02.04.1021.58.22768
4/3/2010 1:53 AM
Again if I'm right on this, there's a possible 17 second skew? Do you see see a similar skew in the flow data?
The problem I wonder why some aren't seeing the problem is whether they're not going down to the 30 second graph or higher as that's where it's more apparent as you, Katy and I have been seeing. Once it gets really out of hand you then seem to lose a 1hr block of Flow data towards the end of the night.
When I've seen these numbers not tally up >2 seconds, it seems that they never become in-sync again and continue to get more out of whack as new days go on, and I think (not 100% sure) that this is somewhat affecting in some way the skew.
The next thing I want to experiment with (I need to make a number of backups) is to write out a number of SD cards where the data is skewed and start hex editing these files and only replacing time values and see by doing this if the data comes back without a skew when re-importing the modified data into ResScan. I'm hoping it might just be that easy, but my guess is it probably won't be.
DreamDiver wrote:Apparently, locking the card, or not, has no effect best practices.
Other sources of variability to consider:
Line amperage/voltage? Seems unlikely.
Computer speed? Seems more likely to be specific to the S9 and not the computer reading the SD card.
Other ideas?
Yeah I'm pretty sure it has nothing to do with the computer or not write protecting the SD card when inserting it into a computer, although I still think it's best practise to write protect it so Antivirus software doesn't mess up the files when it tries to scan them.
I'm still sold on the S9 being the corruptor of the data, and if I can find a way to fix the skew temporarily by editing the data then I think that gives concrete evidence to what needs to be fixed permanently to stop it from happening. My guess is there might be a simple rounding exercise in the S9 that isn't rounding properly, e.g. summary data gets rounded down but detailed or hi resolution data gets rounded up. Some nights it doesn't make much of a difference, but it's possible the more start/stops you have throughout a day might be impacting it more. Hence why you and Katie have seen it more than I have.
EDIT:
The only other variable I can think of is are you pre-heating your water? And if so do you do it for the same length of time? I don't think it will be this but it's another thing to perhaps discount from the equation. I could possibly see something going wrong in the software because it knows it's pre-heating the water and it might start the logging earlier some nights depending on the length of pre-heat time is used in some files but not in others. e.g. because the blower is functional during that time frame of pre-heat and also cool-down.
Thanks
Dave