You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to bluetooth dropping between the phone and the Dexcom receiver, as well as other connectivity issues, the most recent glucose data isn't always uploaded to the Share servers when Loop goes to retrieve it. While this cannot be solved for the present loop cycle, the failed retrieval has impacts on the follow-on cycles as well, specifically regarding prediction calculations. A method for backfilling missing data from the Share servers would fix this.
How many data points to backfill is an open question, but probably at least the last 15 minutes.
Activity
loudnate commentedon Jul 5, 2016
Step 1: LoopKit/LoopKit#33
loudnate commentedon Jul 6, 2016
Step 2: LoopKit/LoopKit#36
Backfill up to 6 values (30 minutes) of glucose from Share
Merge pull request #21 from loudnate/dev
Use new ISF and Correction Range interfaces with guardrails (#21)
Merge remote-tracking branch 'upstream/dev' into dev-spike
Tidepool merge (LoopKit#21)