LoopKit/Loop

Too low prediction after override

smlcngl opened this issue · 1 comments

smlcngl commented

The Bug:

I encountered an issue where the Loop app v3.4.1(4) provided an incorrect low blood glucose prediction after I added and then removed an override setting. Here's what happened:
I added an override setting %10 to adjust my insulin sensitivity and target range.
Shortly after, I removed the override and returned to my usual settings.
Following the removal, the app predicted a significant drop (-400 mg) in blood glucose, far lower than expected based on my usual settings and recent insulin doses.
This low prediction seemed to persist for 4 hours (still ongoing). I believe this may be a bug related to how the app recalculates predictions after override settings are removed.

Screenshots:

image

To Reproduce
Steps to reproduce the behavior:

  1. Activate an override
  2. deactive Override

Expected behavior
I would expect loop to turn normal settings after override is turned off.

Screenshots
image
image

Phone

  • Hardware: iphone SE 2nd Edition
  • OS Version: 17.6.1

Loop Version

  • Version Number: 3.4.1 (4)
  • Repo: LoopKit/Loop

CGM

  • Device: Dexcom G6
  • Manager app: Dexcom App

Pump

  • Manufacturer: Omnipod Dash
  • Model:
  • Firmware version:

Additional context
n/a

marionbarker commented

If you enter carbs or insulin with an extreme override, it can cause this type of problem.

https://loopkit.github.io/loopdocs/operation/features/overrides/#avoid-extreme-insulin-needs-setting

we can confirm what happened from the critical log export. That is quite a large file. Let me know if you want it analyzed. You can send me a direct message on zulipchat.