What happens to your CGM data for the extra hour on Daylight Savings Time Fallback day?

When I look at our 1:00-2:00am data for DST Fallback night, I cannot detect a difference: the curve, for us, is continuous at 1:00am and at 2:00am, and it is also differentiable.

So I am curious: what do you think happens to the data for the extra 1:00am hour on Fallback day? What is intriguing to me is that I was expecting to see somthing weird at 1:00am but did not.

Why my expectation:

  • if they use the 1st 1:00am hour, we should see a discontinuity at 2:00am

  • if they use the 2nd 1:00am hour, we should see a discontinuity at 1:00am

  • if they use a combo of both we should see discontinuities at both 1:00am and 2:00am

I don 't detect anything in our data, but it was not a very eventful hour, so it may be that I would not be able to see a big discontinuity.

1 Like

Umm, the data doesn’t change… just the number on the clock does.

Every time I’ve crossed the international dateline westbound and skipped a day I’ve wondered what would have happened if I’d committed a crime on that date that didn’t exist in my life. Could I be convicted by a jury of my peers— I certainly think the case could be made for reasonable doubt.

Well, that is not correct. There is real data for two of the same hour.

Yuck.
image
image
image
image
image
image

2 Likes

I do think you have to be careful about what conclusions are drawn.

This is specifically the G5 Transmitter going to an Apple iPhone on iOS 11.0.1 running the Dexcom G5 Mobile App v1.7.3 going into the Dexcom Clarity Servers.

Clearly something is less then “perfect” but exactly where the disconnect lies may not be immediately obvious.

@Michel - I am glad our lack of overnight straight line was able to assist you in your musing.
ha ha ha
:wink:

1 Like

Cue the Twilight Zone theme song… :notes:

2 Likes

XDrip+ just added an hour, i.e. there were two 2am-3am time frames on the continuous track.

So the track stayed constantly reading correctly, only the times were changed to protect the innocent :joy:

2 Likes

That’s an extraordinarily dumb design… why not just have the clock go from 0159 to 0100 and the data stream continue unbroken

That’s how it should be and any design other than that is totally silly

1 Like

That would take some fancy programming, and the FDA would take years to approve the change.

Does THAT require FDA approval? :astonished: Unbelievable.

1 Like

When I asked a while back if they could add a dimming feature to the G5 receiver because the backlight was way too bright they told me that it wouldn’t be until G6 was out because FDA approval takes so long.

So yes, every tiny little change they make has to be approved.

2 Likes

The reason I didn’t post a screenshot is because I didn’t want to make public my excursion to 270 :sob:. The 22u correction I took brought it down in a few hours

1 Like

That’s insane!

1 Like

@Boerenkool Ah, you seem to be getting a sense of how our government works over here. :stuck_out_tongue_winking_eye:

Sometimes I feel I have a better understanding of how your government works than of that organization in Brussels that rules Europe :stuck_out_tongue_winking_eye:

3 Likes

Heh. My son gets these every week :frowning: Last Sunday we blew through 30U on one peak that lasted all afternoon. 30U is darn close to his TDD.

3 Likes

15 posts were split to a new topic: FDA, drug approval and state bureaucracies

Terrifying. That’s close to my TDD too. I would be scared if it took that much insulin to bring down a peak.

1 Like

Even though it happens to us often, I am still worried every time. And frustrated: when the 3rd correction in 4 hours fails and we go up to 10U in one injection with no food coming, I can’t help checking his CGM follow app every 5 minutes and hoping that his sensor won’t fail in the next hour.

1 Like