3.4.2 Medtronic Overlapping Basals
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
Compare temp-basal handling between versions 3.3.2.1 and 3.4.2.3, focusing on how pump history supplies the stopped basal's end time. Reproduce the overlapping-basal state shown in the Treatments screenshots and verify that a normal update records the correct end time and IOB without requiring an app restart.
Written by the indexing model from the issue text.
Description
Being a bit behind, I just recently updated from 3.3.2.1 to 3.4.2.3
Somewhere between those versions a critical, previously fixed bug was reintroduced.
When temp basals are set, then stopped/updated with a new basal on a subsequent loop cycle the stopped basal does not get updated with the time that it finished, leading to significantly incorrect IOB. Since someone like myself using SMB, there is a higher likelihood of zero-temp basals stacking incorrectly, leading to lower IOBs and then to insulin overdosing.
Previously this was solved by getting a complete history from the pump, which then would populate the end time of the basal correctly. It looks like this may have been removed for some reason along the way?
Two screenshots from the treatments view below shows this behavior on the left, and a matching view taken after restarting AAPS (which forces a full history refresh from the pump)
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 6.4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 19
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nightscout/AndroidAPS
-
enhancement for_discussion
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nightscout/AndroidAPS#5057 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
nightscout/AndroidAPS#5142 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
nightscout/AndroidAPS#5140 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
nightscout/AndroidAPS#5132 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
nightscout/AndroidAPS#5121 · 4 comments ·
All issues in nightscout/AndroidAPS
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Good First Issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ankidroid/Anki-Android#21942 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
libre-tube/LibreTube#8781 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
MetrolistGroup/Metrolist#4396 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100