-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Description
Describe the bug
IOB tracking does not appear to be correct...
Attach an Issue Report
Don't have Issue Report, but do have data spreadsheet to illustrate.
https://docs.google.com/spreadsheets/d/1IXVDX_hM2O1cwRCKpOJoIomfy-GmPDTXzabkZMsrSP0/edit?usp=sharing
Pump
pods
Additional context
User's scheduled basal during this period of time was 0.2 u/hr. During this one hour span, temp basals were set every five minutes and always below 0.6 u/hr (the minimum required basal rate to guarantee a click of basal delivery within the 5 min in worst case scenario...as partially discussed here in this issue #1015 ). No Loop drops during this one hour, everything was running smooth.
I have two concerns:
-
IOB, as reported by the Loop pill in NS, was recorded in column C. (User reports that the Loop app had been freshly opened, so I don't think this is a repeat issue of the IOB rounding in another issue). From 4:42am to 5:22am, the temp basal rate that was set by Loop was always below scheduled basal rate...yet the IOB continued to rise. This is the incorrect trend that IOB should be making. I calculated the IOB, based on the set temp basals (column D), that I would have expected.
-
Column D IOB in this situation still doesn't represent the actual user experience as the basal click timer was being reset every five minutes for the hour captured in the spreadsheet. So, over the one hour, no clicks of any basal were delivered and the "in body" iob would've been closer to column E. Looking at how significant this might be...the difference between column d and column e at end of an hour is about 0.133 units IOB, this user's ISF is 185...so 25 mg/dl difference in the predicted curve.
However, current user experience is the difference between column C and column E...and that gets to be more significant at 63 mg/dl in predicted curve difference.


