|
|
NEWS From Loop and Learn 💙 27 May 2023
- Jammin' in June
- Speaker Series: Kathryn Gentile on AB vs. TB
- How Loop Developers Use Shared Data
|
|
|
|
"Jammin' in June" Open Mics
| |
We had a couple of earlier Open Mic sessions this month, during which a bunch of our looping friends gathered to discuss whatever came to mind. We are planning to host more of these sessions on June 1st and 15th. Please join us to ask your Looping questions in a small group setting.
Join us at 11amPT/ 2pmET/ 8pmCET!
To encourage participation, these sessions will not be recorded for sharing.
|
|
|
|
|
|
Speaker Series: Kathryn Gentile on Automatic Bolus vs. Temp Basal
|
|
Wednesday, 7 June 2023 5pm PT/ 8pm ET Join us via Zoom or YouTube Livestream This event will be recorded.
In June, we'll be joined once again by Kathryn Gentile, MS, ACSM-CEP, EIM II, CPT, CSNC, CDCES. She is IDS's Director of Exercise Physiology, a Teen and Young Adult Specialist, and has been living with type 1 diabetes since the age of 12. Kathryn will help us understand when to use Automatic Boluses over Temp Basals and will address related topics. More info about Kathryn, as well as articles she's written, can be found here. You can also refer to the links below to learn more about dosing strategies and how the Loop algorithm works.
|
|
|
|
|
|
Share Data: How Your Data is Used by the Developers
| |
The Loop 3 Onboarding process asks what data you'd like to share with the developers. Many Loopers wonder what the best choice is. To help you make an informed decision, we have learned how these data are helpful: - Stats on loop failures show which devices are causing more issues and which issues are more widespread
- Pod failures 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
|
|
|
|
|