Skip to content

Commit

Permalink
first draft of next edition
Browse files Browse the repository at this point in the history
  • Loading branch information
@marionbarker
marionbarker committed Feb 21, 2024
1 parent 4d8e8c9 commit a785306
Show file tree
Hide file tree
Showing 4 changed files with 202 additions and 140 deletions.
102 changes: 32 additions & 70 deletions docs/edition/2024-02-05.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,17 +2,14 @@

_Master Your DIY Closed-Loop Insulin Delivery System_

Published on 12 February 2024.
Published on 21 February 2024.

## In this edition:

* [*Zoom* Sessions](#upcoming-zoom-sessions)
* [Love from Members](#love-from-members)
* [Wait before Updating iAPS](#wait-before-updating-iaps)
* [Selecting iAPS version](#selecting-iaps-version)
* [iOS Update](#ios-update)
* [New Phone](#new-phone)
* [Expiration Times](#expiration-times)
* [Battery Drain: Phone and Dexcom](#battery-drain-phone-and-dexcom)
* [Pod Site Stability](#pod-site-stability)
* [Meal Time Tips]()
* [Helpful Links](#helpful-links)

## Upcoming *Zoom* Sessions
Expand All @@ -32,89 +29,54 @@ _<span translate="no">Loop and Learn</span>_: Informal Discussion in 2024 is sch

Need help figuring out when an event happens in your time zone? Try the [SavvyTime: UTC Converter](https://savvytime.com/converter/utc){:target="_blank"}.

## Love from Members
## Battery Drain: Phone and Dexcom

If you participate in our group on [*Facebook*](https://www.facebook.com/groups/LOOPandLEARN){:target="_blank"}, the team wants to thank you for all your messages of appreciation.
If you are a [`Loop Follow`](https://www.loopandlearn.org/loop-follow/){: target="_blank" } user, you may find that your iPhone’s battery gets depleted faster than before you started using that app. We suggest you note how quickly your battery drains and make a habit of charging regularly. Keeping a charger or a power bank in your diabetes supplies kit is good plan.

* It’s a joy to see how our members’ lives are improved by DIY looping! We appreciate all the love you send in the form of “Thank You” posts.
Another source of battery drain affects Dexcom and [Anubis](https://www.facebook.com/groups/247952672307306/posts/1901312990304591/){: target="_blank" } transmitters. Our friends at Anubis warn that the [*xDrip4iOS*](https://xdrip4ios.readthedocs.io/en/latest/){: target="_blank" } and [*Shuggah*](https://apps.apple.com/gb/app/shuggah/id1586789452){: target="_blank" } apps both drain the batteries of these transmitters at a rapid rate. Thankfully, we hear that a fix is in the works.

* If you’re on the fence, deciding whether you want to give Loop a try, read some of the posts- they may just push you over the edge!
## Pod Site Stability

## Wait before Updating iAPS
Those of us who use pods occasionally encounter site issues like leaky pods, bloody sites, bruising, and painful sites, which can lead to poor absorption. Fortunately, a simple and effective solution has been suggested by a user on Discord and tested by several members of our team, yielding positive results. If you're experiencing any of these problems, you can consider this method.

The [following post](https://www.facebook.com/groups/1351938092206709/posts/1534888703911646/){:target="_blank"} was written by Magnus Reintz in the *iAPS* *Facebook* group. The specific update mentioned here is from 2.3.3 to 3.0, but this holds for all updates in the future.
> The information given here is based on personal experiences and is not intended as medical advice. Always consult your healthcare provider before making any changes to your treatment.
For those readers who use *iAPS*, please wait to update any iAPS release until experts in the community have a chance to test and confirm the release.
> Consider the fact that this method depends on inserting the cannula through a piece of medical tape attached to the skin. You may not be willing to take that action.
!!! warning "Post from 10 February 2024 repeated here:"
iAPS has had a large increase in users over the last year. However, the development method has not changed. iAPS is still maintained by Jon B. Mårtensson with contributions from other developers. Jon decides when to merge code into the different branches, and he decides when to make a Main release. Jon is not on Facebook, and will not be commenting on this post. He is available on Discord.
The [method](https://www.facebook.com/groups/LOOPandLEARN/posts/3627796764143468/){: target="_blank" } involves placing a piece of Tegaderm or OpSite Flexifix dressing on your skin prior to applying your pod. Apply the pod directly over it without cutting a hole for the cannula. The dressing only needs to be in the area of the cannula, it does not need to be as big as the pod. This technique has been successful in stabilizing the cannula and preventing many of the aforementioned issues, ultimately extending the use time of the site.

With the increasing number of users, some of us (including Theresa Hastings, Dan H. Moody, Tom Barrows, Mike Plante, and many more) have tried to help Jon move towards a more controlled release cycle, with peer programming, proper release testing, improved documentation, etc. Jon, bless him, spends most of his free time developing iAPS. He believes that changing the ways of work will slow down development and take away his freedom to choose what to do with the app. I believe he is right, but I still believe this is what should be done - to make sure iAPS has a level of quality that matches the increasing number of users. It's not just a few advanced users anymore.
The rationale behind this approach is that it stabilizes where the cannula enters the skin, limiting motion that can lead to leaking. Several members report the site remains functional for a longer duration with more stability in day-to-day insulin needs.

With the help from Kelsey Huss we also got Scott and Dana (authors of the Oref algorithm) involved, to try to find a way to move things forward in a safe manner. Still, all code from the DEV branch was merged into MAIN and released as version 3.0 today.
For individuals dealing with pod adhesive irritation, apply a sufficiently large piece of dressing to fit under the entire pod. Additionally, spraying Flonase on the area and allowing it to dry before applying any dressing can help mitigate adhesive-related issues.

The release notes are not complete. We know that this version contains several bug fixes, some design changes and some new features. That is a good thing! But we also know that this release contains code that has not been tested for more than a couple of days, and other changes that should have been tested on a broader user base before releasing to everyone - like the new bolus calculator, and new remote features.
Some ways we can tell we have a leaky pod:

I believe that iAPS Main 3.0 is an experimental app at the moment. It should be used with caution, only by people who are closely following the Discord group and ready to re-build on short notice. If you decide to use iAPS Main 3.0 now, you should be prepared for it not to work as expected. That includes bringing along low treatments, extra pods, your PDM (if you use Omnipod) and insulin pens at all times.
* Glucose is not responding to known sufficient insulin dosing
* Wet and/or discolored adhesive around pod
* Smell of insulin
* Cannula is visually dislodged
* For some: leaking leads to bleeding and stinging with large boluses

Some of us will devote our time to testing this release and let you all know when it is safe. This will take time.
## Meal Time Tips

Link to [*iAPS* Discord](https://discord.gg/ptkk2Y264Z){:target="_blank"}.
When you enter carbs, the *Loop* app makes a meal bolus recommendation that will keep your glucose just above your Glucose Safety Limit. But in the next Loop cycle, it may restrict basal rate with a zero temp basal because it is considering your Correction Range. As your glucose rises following the meal, Loop will **not** automatically provide insulin until your current glucose rises into your Correction Range.

### Selecting iAPS version
This Tip lets you temporarily lower your correction range so the *Loop* app begins to respond (automatically) as soon as your glucose starts to rise.

#### Browser Build
Option 1: Use Premeal target after carb entry

This great (< 3 minute) video shows how to build 2.3.3 with Browser Build. Then when the all-clear is given, you can use the same video to update to the appropriate main release.
* Set your premeal target to match your Glucose Safety Limit
* As soon as you enter carbohydrates for a meal, tap on the premeal icon - this will last for 1 hour or until you enter more carbohydrates

* [iAPS-main 2.3.3 & 3.0 Building Tips](https://www.youtube.com/watch?v=bT1YXsgyxMY&t=3s){:target="_blank"}
Option 2: Create a named override

The long alphanumeric string you need to add to your *GitHub* repository to make a branch called 2.3.3, is reproduced below for your convenience.
* Created a named override (you could call it Meal) set to last 2 hours with a correction range lower limit near your Glucose Safety Limit
* Enable the Meal override prior to entering carbohydrates
* Enter the meal information

``` { .bash .copy title="Copy and Paste to select commit for iAPS 2.3.3" }
https://github.com/YOUR-GITHUB-USERNAME/iAPS/tree/f404fc49bfe4732dbb61c3a1b202d5b1f22ce178
```
Superbolus Trick:

Replace `YOUR-GITHUB-USERNAME` with your GitHub username.

#### Mac Build

The Build_iAPS script has been updated to make it easy to select by option number:

1. tested main
2. the latest version on `main` branch (today that is a 3.0.1)
3. the latest version on `dev` branch

As of 12 February 2024:

* tested main is 2.3.3

When the main release has been deemed sufficiently reviewed, tested main in the script will be updated appropriately.

Copy and paste the commands below into a terminal on your Mac and follow the directions.

``` { .bash .copy title="Copy and Paste to start the Build iAPS Script" }
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/loopandlearn/lnl-scripts/main/Build_iAPS.sh)"
```

## iOS Update

Apple released iOS 17.3.1 and watchOS 10.3.1 on 8 February 2024. It has been tested and is stable for DIY looping. See [Version Updates](https://www.loopandlearn.org/version-updates/){:target="_blank"} for more information.

## New Phone

A reminder when transferring your DIY loop app to a new phone: disable Closed `Loop` and keep it disabled until the full transfer and checkout is complete. It may take time for Apple Health to transfer recent looping data from the old phone via iCloud.

* For start to finish suggestions for a new phone, see [New Phone](https://loopkit.github.io/loopdocs/faqs/new-phone.md){:target="_blank"}
* For details on why to stay open `loop`, see [Check out the Transfer](https://loopkit.github.io/loopdocs/faqs/new-phone.md#check-out-the-transfer){:target="_blank"}

## Expiration Times

If you built released `Loop` code (version 3.2.x) using the Browser Build method, the reported expiration time is not correct. You have to look at the *TestFlight* app to see when it expires.

As soon as the next version is released, this will be fixed.

In the meantime, you can add this [customization](https://www.loopandlearn.org/custom-code/#tf-expire){:target="_blank"} to your browser build to get the correct date and stop the warning messages. Should you get stuck and need help, copy and paste the URL from your Actions page in a post on Facebook or zulipchat.
* For confident Loopers, you can "borrow" an hour of scheduled basal and add that to what the *Loop* app recommends for your meal bolus

## Helpful Links

Expand Down
Loading

0 comments on commit a785306

Please sign in to comment.