Loop 1.5 Suggests Bolus When BG is Below Suspend Threshold

My Suspend Threshold is set at 80.
My BG was below 80 (at 71 or below).
I consumed 20 carbs and recorded in Loop.
Loop recommended a bolus, but I cancelled it.
I opened the bolus screen immediately after that to make sure that what I thought I saw really happened (suggested bolus even though current BG was below suspend threshold).
Not only did it suggest another bolus, it INCREASED the suggested amount from the previous suggested bolus amount. Again, I cancelled it.
Repeated steps 5-6 a few times. Each time, the suggested amount increased from previous amount.

Please note other variables: At the time of this event, Loop was reporting the anticipated BG at 5 hours into the future at over 200 and had been reporting high future values for several hours. I assume that the future BG value is why I was receiving high temps during this time and is the reason I was low at the time I experienced this suggested bolus event. I finally greatly reduced the absorption time from earlier entries to get the future prediction to normalize. My BG maintained low-ish overnight (below target but not low enough to treat) after adjusting the absorption time on those earlier entries.

The time on the screenshot on the settings is after the time of the bolus recommendation. Is it possible that the suspend threshold was changed after the recommendation? The code does seem to behave as expected when we test situations like this. So the evidence points to a later settings change.

No change to suspend threshold at any point. I have never changed it. It has always been at 80.

…

Sent from my iPhone

On Oct 6, 2017, at 10:54 AM, Pete Schwamb ***@***.***> wrote: The time on the screenshot on the settings is after the time of the bolus recommendation. Is it possible that the suspend threshold was changed after the recommendation? The code does seem to behave as expected when we test situations like this. So the evidence points to a later settings change. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

In fact, if you look at the message at the top of each of the bolus screens, it says current BG of 71 is below the correction range. THAT is what got my attention that it was recommending any amount at all.

…

Sent from my iPhone

The message on the bolus screen indicates that it is below the correction range, not below suspend threshold. Those are two different things.

If you can reproduce this, please attach an issue report. That would help us see what's going on.

I see that. But, the fact stands that my suspend threshold is set to 80 and my BG was 71 while recommending correction. I have a note on the issue report about the projected BG of a high/higher #. Is that a factor? I will force a low bg # through the health app to see if I can recreate the problem. Thanks!

Loop doesn't support reading BG from HK as a data source, so that may not recreate the problem; you may have other issues.

Loop should still not suggest a bolus if current bg is below suspend threshold, even if eventual bg is higher.

Capturing an issue report from Loop would be the best way for me to be able to identify the issue. Please do not cause a low to test! :)

Perhaps capturing an issue report now might highlight if there is some mismatch in settings.

I entered 55 into HK and then managed to get this screen shot which says that my predicted bg of 59 is below suspend threshold. (My real BG is >120). I also entered a meal of 100 carbs so that is showing in this too. I think that is interesting. In the original situation I don’t recall seeing that specific message of suspend threshold (but I missed grabbing a screen shot the very first time I saw a recommended bolus.). I will keep my eye on it most definitely. Thanks for all your help. ![image1](https://user-images.githubusercontent.com/8145371/31294057-b815125a-aa96-11e7-8db5-f9d4ff62cca1.png)

This is unrelated to the issue, but I see your insulin model is fiasp. Are you actually using fiasp? If not, the differences in peak time could create significant issues.

@denvergail

@denvergail your last comment seems to indicate that you wanted to attach a screenshot. It seems like it didn't come through.

Yes, I am using Fiasp. Thanks for checking.

Pete: I added the screen shot to my comment a few above. It didn't come through while I was responding via email.

Attaching issue report now. Maybe you can see something I've missed. Thanks again!
deVore issue report 10-06-17.pdf

@denvergail

@denvergail has this issue resolved with updated Loop app since this?

Yes to the extent that I was concerned.

…

Sent from my iPhone so iTypo

On Oct 17, 2018, at 1:23 PM, katie disimone ***@***.***> wrote: @denvergail has this issue resolved with updated Loop app since this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Merge pull request #596 from tidepool-org/cameron/LOOP-4721-ui-update…

Navigation Menu

Repository navigation

Loop 1.5 Suggests Bolus When BG is Below Suspend Threshold #596

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Loop 1.5 Suggests Bolus When BG is Below Suspend Threshold #596

Description

Activity

ps2 commented on Oct 6, 2017

denvergail commented on Oct 6, 2017

denvergail commented on Oct 6, 2017

ps2 commented on Oct 6, 2017

denvergail commented on Oct 6, 2017

ps2 commented on Oct 6, 2017

ps2 commented on Oct 6, 2017

denvergail commented on Oct 6, 2017

jeremybarnum commented on Oct 6, 2017

ps2 commented on Oct 6, 2017

denvergail commented on Oct 6, 2017

denvergail commented on Oct 6, 2017

denvergail commented on Oct 6, 2017

Kdisimone commented on Oct 17, 2018

denvergail commented on Oct 17, 2018

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions