diff --git a/docs/browser/bb-errors.md b/docs/browser/bb-errors.md index 99f6f137afe..f69903dde51 100644 --- a/docs/browser/bb-errors.md +++ b/docs/browser/bb-errors.md @@ -7,6 +7,7 @@ If you are still unsuccessful, then post your request for help along with the li * [https://github.com/loopdocs-tester/LoopWorkspace](https://github.com/loopdocs-tester/LoopWorkspace){: target="_blank" } Mentors can go to your public _GitHub repository_, make sure your code is up to date, examine your customizations (if any), then click on the Action tab and view your log files directly. + * Do not copy from the log file and post the words * Do not take a screenshot of what you think is an error diff --git a/docs/faqs/glossary.md b/docs/faqs/glossary.md index a1912a8d193..ca436eb0dd7 100644 --- a/docs/faqs/glossary.md +++ b/docs/faqs/glossary.md @@ -76,6 +76,8 @@ When Google Translate is selected: **dynos**  (dynos): used to reboot a Nightscout Site +**dynamic carb absorption**  (dynamic carb absorption): Loop models the expected glucose change based on carbs entered, absorption time and your settings; and adjusts based on measured glucose + **EmaLink**  (EmaLink): radio-frequency device Loop uses to control Eros pods (aka. Gen 3) and older Medtronic pumps **EGP**  (EGP): Endogenous Glucose Production: glucose produced by the body from its reserves (mainly glycogen in the liver) @@ -114,7 +116,7 @@ When Google Translate is selected: **HUD**  (HUD): Heads-Up Display at top of Loop main screen, phone in portrait mode -**ICE**  (ICE): Insulin Counteraction Effect - Loop models the expected glucose change based on carbs entered, absorption time and your settings; and adjusts based on measured glucose +**ICE**  (ICE): Insulin Counteraction Effect - Refers to the difference between observed change in blood glucose and the change in blood glucose that Loop models based on the effects of insulin. **Identifiers**  (Identifiers): names of modules found on your Apple Developer Identifiers page that are required for GitHub build method diff --git a/docs/nightscout/remote-errors.md b/docs/nightscout/remote-errors.md index 26fd8ed3e72..c42be3b5eef 100644 --- a/docs/nightscout/remote-errors.md +++ b/docs/nightscout/remote-errors.md @@ -3,7 +3,7 @@ * This is a _Loop_ and/or *Nightscout* issue, not related to remote configuration * Review the [LoopDocs: *Nightscout* with _Loop_](update-user.md) page * Check out links on the [LoopDocs: *Nightscout* Troubleshooting](troubleshoot.md) page -* Make sure Looper's phone is connected to the internet so it can upload to *Nightscout* +* Make sure the Looper's phone is connected to the internet so it can upload to *Nightscout* ## Remote Commands Stopped Working @@ -18,9 +18,9 @@ If you are using LoopCaregiver, try the remote command directly from Nightscout ### *Nightscout* Config and *Loop* Build Method -Ensure your *Nightscout* version is at least version 14.2.6. +Ensure your *Nightscout* version is at least 14.2.6. -Verify that you performed all the [Remote Configuration](remote-config.md) steps for the *Nightscout* site including sending an override from the _Loop_ phone to *Nightscout*. +Verify that you performed all the [Remote Configuration](remote-config.md) steps for the *Nightscout* site, including sending an override from the _Loop_ phone to *Nightscout*. #### BadDeviceToken @@ -35,7 +35,7 @@ If you attempt to issue a command from *Nightscout* Careportal; after you hit su Error: APNs delivery failed: BadDeviceToken ``` -If you attempt to issue a command using *Loop Caregiver* ; after you authenticate the command, you will see the error message listed below and shown in the screenshot. +If you attempt to issue a command using *Loop Caregiver*; after you authenticate the command, you will see the error message listed below and shown in the screenshot. ``` HTTP Error @@ -54,19 +54,19 @@ If you added this Build-Time Flag: `REMOTE_OVERRIDES_DISABLED` You will not see any errors, but nothing will happen when you issue any kind of remote command. -**Solution**: Remove `REMOTE_OVERRIDES_DISABLED` from `LoopConfigOverride.xcconfig` file and rebuild the _Loop_ app. +**Solution**: Remove `REMOTE_OVERRIDES_DISABLED` from `LoopConfigOverride.xcconfig` file and rebuild the _Loop_ app. ### Incorrect Password (OTP) Error -The references to Caregiver below is the person sending the commands. There are specific *Loop Caregiver* app insructions that you modify for your authenticator. You must have the _Loop_ phone with you to troubleshoot this problem. +The references to ‘caregiver’ below refer to the person sending the commands. You must have the _Loop_ phone with you to troubleshoot this problem. -* The Apple clock should be set to automatic on both the Looper's phone and Caregiver’s device. +* The Apple clock should be set to automatic on both the Looper's phone and the caregiver’s device. * If the clock is incorrect, even slightly, remote commands will fail. -* Check if One-Time Passwords (OTP) align between Caregiver and _Loop_. +* Check if One-Time Passwords (OTP) align between *Loop Caregiver* and _Loop_. * In _Loop_: Settings -> Services -> *Nightscout* - * In *Loop Caregiver* : Settings -> Tap on Loopers Name + * In *Loop Caregiver* : Settings -> Tap on Looper's Name * Observe the 6-digit OTP as they change -* If the OTP don't match, you can reset it: +* If the OTPs don't match, you can reset it: * **Warning**: If there are multiple devices (or people) sending remote commands, this procedure **resets the OTP for all** * _Loop_: Settings -> Services -> *Nightscout* -> One-Time Password -> Tap Reload button * The QR code is different as soon as you hit `Reload` @@ -77,71 +77,64 @@ The references to Caregiver below is the person sending the commands. There are ## Undelivered or Expired Commands -Apple Push Notifications will often not make it to an app, either due to your settings or intentional limitations by Apple. This error can appear in various forms: - -* Push notification banner never shows on Looper’s device. -* Push notification banner shows but nothing happens in _Loop_ (no error or success message afterwards) -* Error message shows that Password (OTP) is expired - -While _Loop_ does not have control over Push Notification timely delivery, there are things that can be done to mitigate these issues. Note that rebuilding _Loop_, *Loop Caregiver* or *Nightscout* is generally not going to help. - -Check these settings on the Looper’s device, not the Caregivers. Several of these are related to Apple suppressing notifications. - -* Notifications - * Settings -> Notifications -> _Loop_ - * Turn on “Allow Notifications” - * Turn on “Time Sensitive Notifications” -* Focus Modes - * For all focus modes (ex: Do Not Disturb, Sleep), make sure _Loop_ is listed as an app allowing Notifications. - * To Adjust - * Settings -> Focus - * Select the focus mode (ex: Do Not Disturb, Sleep) - * Under “Allow Notifications, tap “Apps” - * Add “ _Loop_ ” to the list. - * Turn on “Time Sensitive Notifications”. -* Background App Refresh - * Settings -> General -> Background App Refresh - * Select “On” up top - * Activate _Loop_ toggle in list -* Lower Power Mode - * Turn off if able - -Some other things to try on the Looper’s phone: - -* Reboot phone - * This sometimes resets Apple’s push notification limit. -* Try wifi instead of cellular, if able - * Apple may not deliver notifications on cellular as often as wifi. -* Charge the phone - * If the battery is low, iOS may not deliver notifications to save battery life. -* Limit the number of _Loop_ commands you send in a short period. Apple may throttle notifications if too many are received. (i.e. no more than 1 or 2 per hour may help). -* Consider disabling “spammy” notifications from other apps. This is only a theory, but it is possible that other apps can cause the system to throttle all notifications, including _Loop_. -* Wait 24 hours or so as it often just takes time for the push notification limits to “reset”. -* iOS 15.3.x: Note there are reports of Remote notifications not being received to the Loopers device for iOS version 15.3 and 15.3.1. This is fixed in iOS version 15.4. +Apple push notifications may not always reach your app due to various settings or Apple's intentional limitations. This issue can manifest in several ways: + +* The push notification banner never appears on the Looper’s device. +* The push notification banner appears, but nothing happens in _Loop_ (no error or success message afterward). +* An error message in *Nightscout* or *Loop Caregiver* indicates the Password (OTP) is expired. + +While _Loop_ cannot control the timely delivery of push notifications, there are several steps you can take to mitigate these issues. Note that rebuilding _Loop_ or *Loop Caregiver* generally will not resolve the problem. + +Check these items on the Looper’s phone, not the caregiver's. + +1. Reboot the phone. +1. Wait 24 hours as it often takes time for the push notification limits to reset. +1. Limit the number of _Loop_ commands you send in a short period. + * Apple may throttle notifications if too many are received. + * Sending no more than 1 or 2 per hour may help. +1. Disable notifications from other apps. + * It is possible that other apps can cause the system to throttle all notifications, including _Loop_. +1. Enable Time Sensitive Notifications: + * Apple Settings -> Notifications -> _Loop_. + * Turn on “Allow Notifications”. + * Turn on “Time Sensitive Notifications”. +1. Upgrade *Nightscout*: + * *Nightscout* version 15.0 (released late 2023) and greater supports time sensitive notifications. + * This can help iOS to deliver remote notifications faster. +1. Adjust Focus Modes: + * For all focus modes, make sure _Loop_ is listed as an app allowing Notifications. + * Apple Settings -> Focus + * Select the focus mode (e.g., Do Not Disturb, Sleep). + * Under “Allow Notifications,” tap “Choose Apps”. + * Add _Loop_ to the list. +1. Turn on Background App Refresh: + * Apple Settings -> General -> Background App Refresh + * Select “On” at the top. + * Activate the _Loop_ toggle in the list. +1. Try using Wi-Fi instead of cellular if possible: + * Apple may not deliver notifications on cellular as often as on Wi-Fi. +1. Charge the phone: + * If the battery is low, iOS may not deliver notifications to save battery life (e.g., while on Low Power mode). ## How to Ask for Help This is helpful information to share when requested by helpers. If you are not using *Loop Caregiver*, review the response seen on the *Nightscout* site. -1. Activate an override _from within _Loop_ _. Does *Nightscout* show the active override? -1. Activate an override _from *Nightscout* _. Does it change the active override in _Loop_? +1. Activate an override from within _Loop_. Does *Nightscout* show the active override? +1. Activate an override from *Nightscout*. Does it change the active override in _Loop_? 1. Do errors show in *Loop Caregiver* or *Nightscout* Careportal when you send a remote command? - * Share screenshots of error if any -1. Do errors show in iOS Notifications on the Looper’s device? - * Check their Notification history in iOS by swiping down - * Share screenshots of errors if any + * In both *Nightscout* and *Caregiver*, you can tap on an error to read specific error details. + * Share screenshots of errors 1. What _Loop_ version are you using? Released (main) or development (dev)? Approximately when did you update last? - * The minimum version that support remote bolus and carbs is _Loop_ 3 + * The minimum version that supports remote bolus and carbs is _Loop_. 1. What iOS version is being used on the Looper’s device? - * Note that iOS 15.3.x had notification issues - * Update to a newer version 1. How did you build _Loop_? - * Build with Xcode to device (typical)? - * Using AppCenter or Diawai? A special environment variable must be set LOOP_PUSH_SERVER_ENVIRONMENT=production + * Web browser using GitHub Actions? + * Xcode? + * AppCenter or Diawi? A special environment variable must be set: `LOOP_PUSH_SERVER_ENVIRONMENT=production` Mention which troubleshooting steps you have completed so we know whether to ask about these again. - ## Other Errors Once you've set up remote commands, you may encounter errors when trying to run them via *Nightscout* or iOS Shortcuts. Below are the most common and typical solutions. diff --git a/docs/operation/algorithm/prediction.md b/docs/operation/algorithm/prediction.md index 84fabdf4b7a..9b7bb677533 100644 --- a/docs/operation/algorithm/prediction.md +++ b/docs/operation/algorithm/prediction.md @@ -4,7 +4,7 @@ Loop uses an algorithm to maintain blood glucose in a correction range by predic $$ BG[t] = Insulin[t] + Carb[t] + RetrospectiveCorrection[t] + Momentum[t] $$ -Note that the [Momemtum](#blood-glucose-momentum-effect) term does not just add to the other effects as implied in the simple formular above; it is blended with the other terms as described in more detail in the [Momemtum](#blood-glucose-momentum-effect) section below). +Note that the [Momemtum](#blood-glucose-momentum-effect) term does not just add to the other effects as implied in the simple formula above; it is blended with the other terms as described in more detail in the [Momemtum](#blood-glucose-momentum-effect) section below). You can see the individual contributions of these effects by tapping on the predicted blood glucose chart on Loop's status screen. Loop updates this blood glucose prediction every five minutes when a new CGM value has been received and the pump's status has been updated. @@ -48,21 +48,27 @@ The active insulin at any time is the product of original insulin delivered and ![bg drop from 2 units](img/bg_drop.png) -NOTE: ISF is also a function of time, which means if the user’s scheduled ISF changes during the insulin activity time, it will change the expected drop in blood glucose due to the insulin effect. +NOTE: ISF is also a function of time, as set in the ISF schedule in therapy settings or in accordance with any overrides. Loop uses the ISF that applied at the time of an insulin dose to predict the expected change in blood glucose due to the insulin effect, and sums the effect from all still-active doses. -### Expected Change in Blood Glucose +### Expected Change in Blood Glucose for Each Loop Interval Lastly, taking the first derivative (i.e., the rate of change) of the cumulative drop in the blood glucose curve yields the expected change in blood glucose over the insulin activity duration. For each dose of insulin given, Loop calculates the expected discrete drop in blood glucose at each 5-minute period for the insulin activity duration, as shown below. ![rate of bg change](img/derivative.png) -### Insulin Effect on Blood Glucose +The insulin effect for a given dose can be expressed mathematically: + +$$ \Delta BG_{dose}[t] = ISF[t_{dose}] \times IA_{dose}[t] $$ + +where $\Delta BG_{I}$ is the expected change in blood glucose due to insulin with the units (mg/dL/5min), ISF is the insulin sensitivity factor (mg/dL/U) at the time of the relevant dose, and IA is the insulin activity (U/5min) at time *t*. Insulin activity can also be thought of as a velocity or rate of change in insulin in the blood as it acts on glucose. Insulin activity explicitly accounts for active insulin from temporary basals and boluses, and implicitly accounts for scheduled basal which is assumed to balance out with EGP. + +### Insulin Effect on Blood Glucose Over Time For this example, assuming a user’s blood glucose was 205 mg/dL at the time of insulin delivery, Loop would predict a drop in blood glucose due to the two units delivered at 12 pm as shown in the figure below. ![two unit example](img/two_units.png) -### Scheduled Basal Rates +### Treatment of Scheduled Basal Rates In traditional basal/bolus pump therapy, basal rates are set to accommodate the user's endogenous glucose production (EGP) that causes blood glucose to rise. If a user's basal settings were exactly right in traditional pump therapy, the user would have perfectly flat blood glucose all day, all other factors being equal. @@ -82,19 +88,21 @@ Here is a real-world example where Loop is setting many temporary basal rates ov ![Loop's temp basal chart over day](img/temp_basal_day.png) -### Total Insulin Effect (combining boluses and temporary basal rates) +### Total Active Insulin (combining boluses and temporary basal rates) -Loop will combine or stack the active insulin of all the discrete (individual) boluses and temporary basal rates over the past insulin activity duration (6 hours), to predict the active insulin for the next 6 hours. As demonstrated above, using the predicted active insulin Loop can predict the blood glucose drop over the next 6 hours. +Loop will combine or stack the active insulin of all the discrete (individual) boluses and temporary basal rates over the past insulin activity duration (6 hours), to predict the active insulin for the next 6 hours. -Lastly, the combined effect of bolus and basal insulin are visually represented for the user by Loop’s insulin charts: +The active insulin taking into account boluses and variations from scheduled basal basal rates are visually represented for the user by Loop’s insulin charts: ![Loop's iob and temp basals](img/insulin_delivery_iob.jpg) -The insulin effect can be expressed mathematically: +### Total Insulin Effect (combining boluses and temporary basal rates) + +The sum of all doses' effects on blood glucose are shown for the user in the 'Insulin' curve in the predicted glucose screen. -$$ \Delta BG_{I}[t] = ISF[t] \times IA[t] $$ +The total insulin effect at time *t* is the sum of effects from each active dose or temporary basal rate: -where BG is the expected change in blood glucose with the units (mg/dL/5min), ISF is the insulin sensitivity factor (mg/dL/U) at time t, and IA is the insulin activity (U/5min) at time *t*. Insulin activity can also be thought of as a velocity or rate of change in insulin in the blood as it acts on glucose. Insulin activity explicitly accounts for active insulin from temporary basals and boluses, and implicitly accounts for scheduled basal which is assumed to balance out with EGP. +$$ \Delta BG_{I}[t] = \sum_{dose=1}^{n} \Delta BG_{dose}[t] $$ ## Carbohydrate Effect @@ -118,17 +126,17 @@ where MAR is the minimum absorption rate (g/hr), CA is the number of carbohydrat The linear model above is modulated by an additional calculation that uses recently observed blood glucose data to estimate how fast carbohydrates have been absorbing. The expected change in blood glucose due to insulin effects alone is compared to the actual observed changes in blood glucose. This difference is termed the insulin counteraction effect (ICE): -$$ ICE[t] = OA[t] + IA[t] $$ +$$ ICE[t] = \Delta BG_{O}[t] - \Delta BG_{I}[t] $$ -where, ICE (mg/dL/5 min) is the insulin counteraction effect, OA is the observed activity (mg/dL/5min) or observed change in blood glucose at time *t*, and IA is the insulin activity (mg/dL/5min). +where, ICE (mg/dL/5 min) is the insulin counteraction effect, $\Delta BG_{O}$ is the observed change in blood glucose (mg/dL/5min) at time *t*, and $\Delta BG_{I}$ is the modelled change in blood glucose due to insulin alone (i.e. the insulin effect as described above mg/dL/5min). Insulin counteraction effects are caused by more than just carbohydrates, and can include exercise, sensitivity changes, or incorrectly configured insulin delivery settings (e.g., basal rate, ISF, etc.). However, since the effect of carbohydrates is often dominant (after insulin), Loop can still make useful ongoing adjustments to its carbohydrate model by assuming that the increase in blood glucose is mainly carbohydrate absorption in the period following recorded meal entries. -The insulin counteraction effect is converted into an estimated carbohydrate absorption amount by using the current carbohydrate-to-insulin ratio and the insulin sensitivity factor at the time of the recorded meal entry. +The insulin counteraction effect is converted into an estimated carbohydrate absorption amount by using both the carbohydrate-to-insulin ratio and the insulin sensitivity factor that were current at the time of a recorded meal entry. -$$ AC[t] = ICE[t] \times \frac{CIR[t]}{ISF[t]} $$ +$$ AC[t] = ICE[t] \times \frac{CIR[t_{meal}]}{ISF[t_{meal}]} $$ -where AC is the number of carbohydrates absorbed (g/5min), ICE is the insulin counteraction effect, CIR is the carbohydrate-to-insulin ratio (g/U), and ISF is the insulin sensitivity factor (mg/dL/U) at time *t*. +where AC is the number of carbohydrates absorbed (g/5min), ICE is the insulin counteraction effect, CIR is the carbohydrate-to-insulin ratio (g/U) at the time of the relevant meal entry, and ISF is the insulin sensitivity factor (mg/dL/U) at the time of the relevant meal entry. If multiple meal entries are active (i.e., still absorbing), the estimated absorption is split between each carbohydrate entry in proportion to each carbohydrate entry’s minimum absorption rate. For example, if 72g carbohydrates with an expected absorption time of 4 hours was consumed at 12 pm, and another 72g of carbohydrates with an expected absorption time of 2 hours was consumed at 3 pm, then the minimum absorption rate (see MAR equation above) would be 12 g/hr and 6 g/hr respectively, or 1 g/5min and 0.5 g/5min. @@ -160,13 +168,13 @@ resulting in 1g of absorption being attributed to Meal 1 and 2g attributed to Me ### Minimum Carbohydrate Absorption Rate -If the estimated carbohydrate absorption of a meal entry is less than what would have been absorbed using the minimum absorption rate, then the minimum absorption rate is used instead. This is to ensure that meal entries expire in a reasonable amount of time. +If the dynamically-estimated carbohydrate absorption of a meal entry up to the current time *t* is less than what would have been absorbed using the minimum absorption rate, then the minimum absorption rate is used instead. This is to ensure that meal entries expire in a reasonable amount of time. ### Modeling Remaining Active Carbohydrates After the estimated absorbed carbohydrates have been subtracted from each meal entry, the remaining carbohydrates (for each entry) are then forecasted to decay or absorb using the minimum absorption rate. Loop uses this forecast to estimate the effect (active carbohydrates, or carbohydrate activity) of the remaining carbohydrates. The carbohydrate effect can be expressed mathematically using the terms described above: -$$ \Delta BG_{C}[t] = MAR[t] \times \frac{ISF[t]}{CIR[t]} $$ +$$ \Delta BG_{C}[t] = MAR[t] \times \frac{ISF[t_{meal}]}{CIR[t_{meal}]} $$ ## Retrospective Correction Effect @@ -264,7 +272,7 @@ As described in the momentum effect section, the momentum effect is blended with $$ \Delta BG[t] = \Delta BG_{M}[t] + \left(\Delta BG_{I}[t] + \Delta BG_{C}[t]+ \Delta BG_{RC}[t] \right) \times min\left(\frac{t-5}{15}, 1\right) $$ -Lastly, the forecast or predicted blood glucose BG at time *t* is the current blood glucose BG plus the sum of all blood glucose effects BG over the time interval [t5, t]: +Lastly, the forecast or predicted blood glucose BG at time *t* is the current blood glucose BG plus the sum of all blood glucose effects $\Delta BG$ over the time interval $[t_{5}, t]$: $$ \widehat{BG}[t] = BG[t_{o}] + \sum_{i=5}^{t} \Delta BG[t_{o+i}] $$ diff --git a/docs/operation/features/ice.md b/docs/operation/features/ice.md index cd284d3e622..8bf4e0bfbc4 100644 --- a/docs/operation/features/ice.md +++ b/docs/operation/features/ice.md @@ -16,7 +16,7 @@ Consider the possible effects that counteract insulin (in other words, make gluc As we all know, this list can be long; but on "normal" days, food is the primary reason glucose levels go up. By "normal", we mean basal rates and settings are close to correct, illness is not an issue, and the site is good. We depend on the Loop dynamic carb absorption and other prediction effects to keep glucose in our desired range. -When you have carbs on board, Loop _always_ assigns _ICE_ to carbs, not just on a normal day. +When you have carbs on board, Loop _always_ assigns positive _ICE_ to carbs, not just on a normal day. This is how _Loop_ looks at it. Keep in mind that in situations where you have other positive _ICE_, like insulin resistance, and carbs on board, _Loop_ will attribute all the positive _ICE_ to carbs until all the entered carbs are considered absorbed. At that point, _ICE_ will start driving _RC_ upward. @@ -27,15 +27,15 @@ At that point, _ICE_ will start driving _RC_ upward. The graph at the top of your "Carbohydrates" details page shows the effect *Loop* expects carbs to have on your glucose (gray bars) compared to the actual effect, or *ICE*. The units on the graph are mg/dL/5-min or mmol/L/5-min -- ⬜️: The gray bars represent the effects of carbohydrates on your blood glucose that *Loop* is currently modeling. -- 🟩: As a meal is tracked by *Loop*, you'll see green bars of observed carb absorption (including *ICE*). +- ⬜️: The gray bars represent the effects of carbohydrates on your blood glucose that *Loop* is currently modeling. This will be a combination of dynamically-estimated carb absorption (where meals are absorbing faster than Loop's conservative estimate based on your carb entries) and static absorption based on Loop's conservative, minimum-absorption-rate estimate. +- 🟩: The green bars represent the observed change in blood glucose compared to Loop's prediction based on insulin alone (or *ICE*). !!! info "How *Loop* thinks about carbs" [*ICE*](#insulin-counteraction-effects) is just one important component of how *Loop* thinks about carbs. The other parts are the user-entered data (amount of carbs, and absorption speed). - Sometimes *Loop* falls back to a default absorption model when *ICE* is less than the minimum absorption rate. + *Loop* falls back to a default absorption model when the total *ICE* for a meal up to the current time is less than the minimum absorption rate. - In the graphic below, early in the meal timeline, the green bars are below the grey bars. _Loop_ uses the minimum absorption instead of estimating absorption from glucose change. For example, if a pre-bolus was "perfect" leading to a constant glucose after a meal, the ideal grey bars will be used by _Loop_ throughout. + In the graphic below, early in the meal timeline, the green bars are below the grey bars. _Loop_ uses the minimum absorption instead of estimating absorption from observed glucose change. For example, if you overestimated the amount of carbs in a meal, the meal absorbs slower than you estimated, or exercise leads to less insulin needs than normal, the grey bars predicted at the start of a meal will be used by _Loop_ throughout. ![image of ice screen](img/ice-meal-example.svg){width="500"} {align="center"} diff --git a/includes/tooltip-list.txt b/includes/tooltip-list.txt index 355983b9e5d..548b2e5fb34 100644 --- a/includes/tooltip-list.txt +++ b/includes/tooltip-list.txt @@ -31,6 +31,7 @@ *[DIY]: Do it yourself, a common acronym for the open-source software community (and the maker community) *[Dosing Strategy]: chosen method for increased insulin dosing: (1) High Temp Basal or (2) Automatic Bolus with scheduled basal *[dynos]: used to reboot a Nightscout Site +*[dynamic carb absorption]: Loop models the expected glucose change based on carbs entered, absorption time and your settings; and adjusts based on measured glucose *[EmaLink]: radio-frequency device Loop uses to control Eros pods (aka. Gen 3) and older Medtronic pumps *[EGP]: Endogenous Glucose Production: glucose produced by the body from its reserves (mainly glycogen in the liver) *[Event History]: record of pump events (bolus or temp basal) reported and used by Loop @@ -50,7 +51,7 @@ *[Guardrails]: limits in the code for user selected settings, recommended and absolute limits are provided *[Hamburger Menu]: three parallel lines that, when tapped, open a new menu *[HUD]: Heads-Up Display at top of Loop main screen, phone in portrait mode -*[ICE]: Insulin Counteraction Effect - Loop models the expected glucose change based on carbs entered, absorption time and your settings; and adjusts based on measured glucose +*[ICE]: Insulin Counteraction Effect - Refers to the difference between observed change in blood glucose and the change in blood glucose that Loop models based on the effects of insulin. *[Identifiers]: names of modules found on your Apple Developer Identifiers page that are required for GitHub build method *[IOB]: Insulin on Board, affects automated insulin delivery: the current active insulin (above or below the basal rate) that Loop calculates and uses for glucose prediction *[iOS]: operating system used by Apple Mobile devices (iPhone, iPod, iPad)