ALL CLEAR about the urgent warning

Resscan is the apparent source of the problem. There is no problem with the data on the SD card. See my post at the end of page 2 or the top of page 3, wherever it lands!

To everyone who changed the time on your S9 for daylight savings time.

DO NOT DOWNLOAD LAST NIGHT'S DATA until I figure out how best to handle a sticky situation!

I, and a couple of other members, are seeing a one hour gap in last night's data. This is the data for the day following the change to to DST. BernieRay reports losing data in Resscan after downloading last night's data. I have downloaded my data but haven't yet closed Resscan and saved the changes to it. I'm working to try to figure out how best to handle this issue. Right now I'm not concerned with why this happened, but rather what we need to do to keep from having our data files clobbered.

Has anyone already downloaded data from last night and not had Resscan lose data? If so, did you see a one hour gap like there is my data below? What time of the day did you change the time in your S9?

I apologize to anyone who has already lost data. I really thought my time change procedure was working. This one day later thing is a bolt out of the blue, believe me!

That's where that hour went. I didn't remember taking my mask off and thought the 1 hour block was wierd.

I have downloaded data and exited ResScan and saved data and all of my data is intact other than the "hole" -- and from looking at my charts its not actually missing as the hours between 0100 and 0200 appear to be double reported.

Like I indicated in this post I can't post pics from work but there's a description of what I can see in the post.

viewtopic/t61545/S9-Time-Change-Bug.html

I changed the time on my machine about 9:00 PM last night.

Lizistired wrote:That's where that hour went. I didn't remember taking my mask off and thought the 1 hour block was wierd.

Do you still have all your data in Resscan? Please check it. If you still have Resscan open and have not saved the changes, discard the changes for now when you close it. BernieRay says his got clobbered when he closed and saved. I haven't closed mine yet. I made a backup of my patient folder so I can recover if necessary.

Tip10 wrote:I changed the time on my machine about 9:00 PM last night.

It'll be interesting to find out if you see the gap tomorrow in tonight's data, one day after making the change. Let us know tomorrow, please. Thanks.

I have no gap in the data for Saturday night. I changed mine about 10 PM Saturday.

I went back and looked at mine. i don't think we "lost" any data. I think it just plugged in an hour of deadspace. The graphs appear to line up on either side of the break.
Yours do to.
My sleep time is longer than my oximeter time and I took my mask off long before I turned off the oximeter.
Which is cool because I figured I had undocumented events. Apparently not.

Doesn't there have to be a one-hour gap since there is no actual time between 0200 and 0300 due to the clock skip?

Another way of looking at this is that if the start and end times are accurate according to the clock setting on the FG (which for most people who changed the time would mean that the FG's set time was one hour later than actual clock time assuming they went to bed before 0200), there's a bug in reality that must be accounted for in software.

It'll be interesting to see what is reported by users who didn't change the clocks on their S9's. I suspect their graphs still show a one-hour gap.

I did not change anything on my S9. I assumed its computer would compensate for the time change. I downloaded data this a m and noticed the gap of 1 hr in there. I had no memory of turning off the machine or getting up etc. All the stored data on the computer seems ok. I do always lock my SD card before putting it into the computer and I unlock it when I return it to the S9. so will I have problems TOMORROW?

Except for the 1 hour gap, everything looked fine for me this morning when I downloaded last night's data. It was only when I re-opened ResScan later in the morning that I noticed my summary data was wiped out and my stats show the 3/13 results for every day going back to 11/22, my first day with the S9.

For now, I'm keeping the RLK file for last night but restored summary.dat from my backup yesterday morning. It's not a perfect solution, but it may be the best we can do. Luckily, I keep daily backups of not only my SD card but also my patient folder, so the damage should be minimal.

Obviously (at least to me), something on the card allowed ResScan to detect that the time had been advanced. I suspect that either an erase of the card or an erase of the machine would have prevented this, but it's water under the bridge now.

BernieRay wrote:Obviously (at least to me), something on the card allowed ResScan to detect that the time had been advanced

Why on the card? The ResScan software itself needs to account for time. Windows has settings for time and knows about local DST conventions. It seems reasonably likely to me that this accounts for the data gap.

BernieRay wrote:Except for the 1 hour gap, everything looked fine for me this morning when I downloaded last night's data. It was only when I re-opened ResScan later in the morning that I noticed my summary data was wiped out and my stats show the 3/13 results for every day going back to 11/22, my first day with the S9.

Okay now this piques my interest because I'm only looking at my back-ups of the RLK files (on a thumb drive) and actually looking at them with a DIFFERENT installation of ResScan. I'll be interested to see if my install at homes shows this but I don't think it will.

Everything looks perfectly normal with all of my data EXCEPT the double data entries mentioned above and the gap.

mstevens wrote:Doesn't there have to be a one-hour gap since there is no actual time between 0200 and 0300 due to the clock skip?

Another way of looking at this is that if the start and end times are accurate according to the clock setting on the FG (which for most people who changed the time would mean that the FG's set time was one hour later than actual clock time assuming they went to bed before 0200), there's a bug in reality that must be accounted for in software.

It'll be interesting to see what is reported by users who didn't change the clocks on their S9's. I suspect their graphs still show a one-hour gap.

I understand what you are saying but that gap SHOULD be between 0200 and 0300 SUNDAY morning, not MONDAY morning.

And there would ONLY be a gap if the CLOCK had ACTUALLY changed DURING data collection -- it did not.

I went to bed approximately 2200 on Sunday evening (and that's when my graphs start), I awoke at approximately 0443 on Monday morning (and shut my machine off and removed the mask) and that's when the graphs stop. Note, I also was off mask from 22:21 to 22:25 and 22:31 to 22:46 (a total of 20 minutes) due to fighting with my masks.

The timespan between going to bed (2200) and waking up (0443) is 6:43 minutes and that minus the 20 minutes off mask yields 6:23 minutes which is exactly the timespan shown on my Summary data as being in mask.

Now charts show data between 2200 and 0200 (4 hours) and 0300 and 0443 (1 hour 43 minutes) for a total time of 5:43.

So if we did not lose any data -- just "skipped" over that hour then where is the other 1 hour's worth of data

Now, my charts seem to show some double entry data from 0100 to 0200. I only see it, however, in the AHI chart and the snore index chart. Does anybody else see that? Snore index is where it really shows up on mine but you have to zoom in tight.

I just had a look at my data. I have a 1-hour gap from exactly 0200 to exactly 0300 from last night.

I had changed the time on my FG around 1400 on Saturday in anticipation of the time change early Sunday morning.

A one-hour gap makes perfect sense to me. What doesn't make sense is that it was the day after DST started and not the night of the actual clock change.

In any event, it may be worth noting that I set the time on my S9 back an hour for a trip to another time zone and forward an hour when I returned home a week later. This did not cause any data gaps or overlaps. This is one reason why I believe the gap is being created by ResScan in response to DST rather than its being the result of anything happening on the S9 itself.

I re-opened mine and it looks good except for the 1 hour gap. The summary graph doesn't reflect the gap in mask events. So I'll see what it does tomorrow. Sure don't want to lose sleep over it.
Glad it was brought to my attention though since I was trying to line up my oximeter, ResScan, and video!

You may be interested in this thread from last year around this time, also just after the change to DST: viewtopic/t61557/viewtopic.php?f=1&t=50244.

I changed the clock on my S9 yesterday afternoon, just after 1:00. I only download the data into ResScan once a week now (Sunday mornings), so I won't know until then if anything's out of the ordinary. I always download the data before noon and choose "Discard Duplicate Data" when prompted.