Skip to content

update progressCell for bolus display, finish update for dev branch #2298

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Mar 23, 2025

Conversation

marionbarker
Copy link
Contributor

@marionbarker marionbarker commented Mar 22, 2025

Purpose:

This PR should resolve Issue #2196.

I failed to test PR #2295, which was supposed to resolve the issue, in a LoopWorkspace build.

As explained here, I was given a version of the patch that worked with dev, but had to modify it for tidepool-merge.

LoopWorkspace Status

The dev branch of LoopWorkspace is still pointing to an earlier commit for Loop, so my mistake in PR 2295 does not affect LoopWorkspace dev.

Tests

Build and Run Tests

With the addition of this PR to Loop dev (commit 710182e, resultant commit prior to merge: 46f7a49):

  • building LoopWorkspace to a phone simulator succeeds
  • running the Tests all succeed

My next comment will cover testing using a Test Phone to demonstrate the UI glitch is resolved.

@marionbarker
Copy link
Contributor Author

Test Efficacy

Tested that this PR fixed Issue #2196.

Configuration

  • iPhone SE 3rd generation using Nightscout as a CGM and rPi DASH pod, use Automatic Bolus Dosing Strategy

Test Plan

  • set CGM values to steady state (110 +/-1)
  • add carbs but bolus 1 U (as opposed to recommended amount)
  • as soon as Bolus Progress display is shown, lock the phone
  • watch the rPi display and when the next bolus starts (insulin command is visible), unlock the phone

Confirm Error happens with older version

Error was confirmed

Details

Configure Loop to commit f63edf9 (before the fixes for Issue 2196)
Run Test:

  • enter carbs, modify recommended bolus from 4.5 to 1.0 and bolus
  • bolus progress before locking: 0.3 of 1.0 U
  • bolus progress after unlocking, immediately after program insulin command is issued by rPi: 0.1 of 1.0 with final bolus progress showing 1.7 of 1.0 U.
  • confirm the auto bolus was for 1.7 U

Test with code from this PR

Correct display of bolus total was confirmed

Details

Configure Loop to commit 46f7a49 (includes both commits to fix Issue 2196)
Run Test:

  • enter carbs, modify recommended bolus from 8 to 1.0 and bolus
  • bolus progress before locking: 0.1 of 1.0 U
  • bolus progress after unlocking, immediately after program insulin command is issued by rPi: 0.1 of 2.9
  • confirm the auto bolus was for 2.9 U

Copy link
Contributor

@itsmojo itsmojo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@marionbarker marionbarker merged commit 760174b into dev Mar 23, 2025
@marionbarker marionbarker deleted the fix/issue-2196-dev_part2 branch April 24, 2025 14:46
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants