|
| |
NEWS From Loop and Learn 💙 8 August 2023
- Next Open Mic
- Still Using Loop 3? You NEED to Upgrade
- Please Share Your Loop App Info w/ Developers
- IRC Has Been Updated
- LnL HCP Resource
- How Often Do You Check In?
|
|
|
|
| |
Next LnL Open Mic
| |
 |
Our next Open Mic will be on
Thursday, 10 August
11 am PT/ 2 pm ET/ 8 pm CET
This one will be Loop-focused.
We are loving having so many members of the Loop and Learn community join us for these Open Mics and encourage those who can to join!
For those who want more on iAPS, we have more of those sessions coming, too!
|
|
|
|
|
|
|
| |
PLEASE Stop Using Loop 3.0
 | |
Pete Schwamb recently said that more than 250 people are still using Loop 3.0 (which has dangerous bugs) and need to update. Please update to the current version, which is 3.2.2. The >250 to which Pete refers are just those that are reporting analytics; the actual number is larger... "the important thing with DIY is that people who choose to do this understand that they are taking the responsibility for the system they build, and that they do so with a clear understanding of what DIY Loop is (an open source insulin delivery automation app) and what it isn't (an FDA approved service provided by a company)."
If you are still using Loop 3.0, you are putting yourself or your dependent, as well as the entire DIY community at risk. PLEASE upgrade to version 3.2.2.
|
|
|
|
|
|
|
| |
Sharing Loop App Info
| |
 |
You may not have realized this, but when you started DIY Looping, you joined a club! A family! A team! Please help us all by making the selection you see in the photo on the right. Sharing your app info with Loop's developers aids in ongoing development of Loop by giving important feedback to them.
- Stats on loop failures show which devices are causing more issues and which issues are more widespread
- Pod failure data show whether particular versions of Loop affect the rate of failure, which helps determine fixes
- Learning how often particular features, like overrides, are used helps with future user interface design and improvements
- Language/ location info helps understand the user base so localization can be prioritized
- Version info helps quantify risk when a bug is found in a particular version of Loop, giving an indication of how many people may be affected
If you are not currently doing so, we ask that you update your configuration to share this valuable info, which is anonymized. Click this link to see how to share:
|
|
|
|
|
|
|
| |
IRC Has Been Updated
 | |
After the initial merge of Integral Retrospective Correction (IRC) into Algorithm Experiments in dev, an additional modification was added (PR 2028). This modification limits the aggressiveness of IRC during an initial unexpected rise in glucose, bringing it more in line with traditional RC. With this change, IRC still increases dosing for extended periods of unexpected high blood glucose, and still reacts quickly to ramp down dosing when the unexpected upward effect ends.
This graphic shows a situation where glucose was falling and is now rising. The glucose momentum term is positive. With PR 2028, the IRC contribution is 0 for several Loop cycles. Without PR 2028 and with IRC enabled, the IRC contribution would have been positive, making Loop more aggressive in suggesting a correction. - PR 2028 was merged to the dev branch on 22-July-2023
- The PR 2028 update was added to the Customization Select Script on 25-July-2023
If you are using IRC and have not updated since whichever of these dates is applicable to you, please do so.
To read more about IRC and other Algorithm Experiments, click the links below. If your email client doesn't show the desired link, open in your browser.
|
|
|
|
|
|
|
| |
LnL DIY- Friendly Healthcare Provider Resource
This great resource continues to grow, with over 300 providers listed! Make sure yours is on there, please, and if you're looking for a DIY-friendly HCP, well, here ya go! You can utilize the resource or add to it via this link.
|
|
|
|
|
|
|
|
| |
How Often Do You Check In?
 | |
You may want to step it up!
Loop's development team has grown and, with that, Loop's capabilities are rapidly growing. New safety and convenience features are being developed daily and are added at an increasingly rapid rate. You may think that, because you have a paid Developer account (or for some other reason), you only need to check in once a year, when your account needs renewal. Not the case! Our recommendation has long been that everyone should rebuild at least 3 or 4 times per year, if for no other reason than to keep skills fresh. With the increased rate of change, more often is even better!
|
|
|
|
|
|
