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
{{ message }}
Repository navigation
Setting Carb Ratio to 0g/u will crash loop sporadicaly #941
O dear. That is also very dangerous. Setting a zero ratio for carb ratios or insuline sensitivity will make loop think you need an infinite amount of insuline. Read the docs carefully. It's a good thing loop crashed or else you might have.
I started to do the test on my real phone running v2.2.5 instead of my backup phone.
I thought I had backed out the modification, but evidently it got saved.
I got a notification 20 min later that phone was not looping and Loop crashed upon opening several times.
I tried a few minutes later and I was able to open my real phone and remove the 0 u/g row so no harm done except an adrenaline spike.
In the meantime, verified with new build of v2.2.5 to my backup phone that a CR of 0 is accepted. In this case, there was no crash, but prediction says "Eventually NaN" as you'd expect when dividing by zero. This was using simulated pump and CGM.
This error will not be possible with the version being developed in dev.
If there are any updates to Loop in the interim, seems like guard-rails for CR (like the ones previously added for ISF) should be present.
Activity
RobCvdV commentedon Nov 8, 2019
O dear. That is also very dangerous. Setting a zero ratio for carb ratios or insuline sensitivity will make loop think you need an infinite amount of insuline. Read the docs carefully. It's a good thing loop crashed or else you might have.
marionbarker commentedon Sep 1, 2021
I tested this so I could recommend closure.
In the meantime, verified with new build of v2.2.5 to my backup phone that a CR of 0 is accepted. In this case, there was no crash, but prediction says "Eventually NaN" as you'd expect when dividing by zero. This was using simulated pump and CGM.
This error will not be possible with the version being developed in dev.
If there are any updates to Loop in the interim, seems like guard-rails for CR (like the ones previously added for ISF) should be present.
github-actions commentedon Nov 8, 2023
This issue is stale because it has been open for 30 days with no activity.
github-actions commentedon Nov 22, 2023
This issue was closed because it has been inactive for 14 days since being marked as stale.
[LOOP-5955] Remove Top Divider When All App Sounds are Muted (LoopKit…