Skip to content

Commit

Permalink
update some grammar and words, use forecast instead of predict
Browse files Browse the repository at this point in the history
  • Loading branch information
marionbarker committed Nov 4, 2024
1 parent c7d23ae commit 4851ce4
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 11 deletions.
2 changes: 1 addition & 1 deletion docs/data/nightscout.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ The dashed blue line represents the scheduled basal profile (as entered in your

### Predicted Blood Glucose

The purple line to the right of the blood glucose readings is Loop's predicted blood glucose curve. Watching the behavior of that purple line can help you understand why *Loop* is making decisions regarding high or low temporary basal rates. You can read more on that topic in the [Algorithm](https://loopkit.github.io/loopdocs/operation/algorithm/temp-basal){: target="_blank" } section of *LoopDocs*.
The purple line to the right of the blood glucose readings is Loop's forecasted blood glucose curve. Watching the behavior of that purple line can help you understand why *Loop* is making decisions regarding high or low temporary basal rates. You can read more on that topic in the [Algorithm](https://loopkit.github.io/loopdocs/operation/algorithm/temp-basal){: target="_blank" } section of *LoopDocs*.


### <span translate="no">L&#8203;oop</span> pill
Expand Down
8 changes: 3 additions & 5 deletions docs/data/tidepool.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ To use Tidepool&#39;s services, the process is pretty standard:
* Choose *Tidepool* and log into your *Tidepool* account
* As soon as you do this, *Loop* will upload the last 7 days of data to Tidepool

If both you and someone that you provide care for has diabetes, you should set up an account for each person. [Tidepool Docs](https://support.tidepool.org/hc/en-us/articles/360038567672-What-To-Do-If-You-and-Your-Child-Have-Diabetes){: target="_blank" }.
If both you and someone that you provide care for has diabetes, you should set up an account for each person. Refer to the [Tidepool Docs](https://support.tidepool.org/hc/en-us/articles/360038567672-What-To-Do-If-You-and-Your-Child-Have-Diabetes){: target="_blank" }.

Users can also choose to share data with their endocrinology clinic. You can also choose to share your diabetes data anonymously for the support of type 1 diabetes researchers if desired.

Expand Down Expand Up @@ -94,7 +94,7 @@ You will see your Loop&#39;s temporary basals, CGM readings, boluses, notes, car

If you hover over an item on the *Tidepool* web display, information is revealed indicating

* automatic (the word Automated is included) or manual (no notation) entry
* automatic (the word Automated is included) or manual (no notation)

![automatic bolus](img/tidepool-hover-automatic-bolus.png)

Expand Down Expand Up @@ -143,8 +143,6 @@ For an easy example, search for the word burrito (doesn’t have to be a hashtag

Hormones can also be easily tracked with notes. *What day-of-the-month and how did I change the basals?* Looking to find patterns in those female hormones? This could be a really slick tracking tool to easily log periods of insulin resistance and what part of the cycle they are occurring at.

### Is the Tidepool Mobile app only for Loop users?
The *Tidepool Mobile* application uploads diabetes-related HealthKit data regardless of the source. Loop users store their data in HealthKit, so this is a nice fit. Other diabetes devices (e.g., OneDrop BG meter) and apps (e.g., Spike and Dexcom) also store their data in HealthKit. Some people even manually enter their diabetes data into HealthKit. For all those uses, the <span>*Tidepool Mobile* application</span> will upload the HealthKit data. OpenAPS does not store its data in HealthKit, so this will not upload OpenAPS-related data. However, if OpenAPS users are using Spike app, some integration of information through Nightscout is possible. Currently, OpenAPS SMBs, boluses, and carbohydrates can be uploaded to HealthKit for OpenAPS+Spike+Nightscout+iPhone users. Spike does plan to add temporary basal integration to HealthKit at some time in the future.

### How can you get the Tidepool Mobile app?

*Tidepool Mobile* is available in the [iOS App Store](https://apps.apple.com/us/app/tidepool-mobile/id1026395200){: target="_blank" } on your Loop device.
10 changes: 5 additions & 5 deletions docs/how-to/iob.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ This Looped group post started the conversation:

*I've been having more lows recently than I would like. Any help here would be really really appreciated.*

*I took a screenshot of an example situation...LOOP is predicting that I'll eventually rise up to 124 and is therefore giving me my full regular basal rate EVEN THOUGH im currently way below my desired goal range. I have a better knowledge of my diabetes than LOOP does (sorry if that is heresy around here) and I would not like LOOP to be giving me basal right now OR ELSE I'LL GO LOW.*
*I took a screenshot of an example situation...LOOP is forecasting that I'll eventually rise up to 124 and is therefore giving me my full regular basal rate EVEN THOUGH im currently way below my desired goal range. I have a better knowledge of my diabetes than LOOP does (sorry if that is heresy around here) and I would not like LOOP to be giving me basal right now OR ELSE I'LL GO LOW.*

*QUESTION: Which parameter must I change on my loop settings in order to essentially tell LOOP to relax on the basal rates??*

Expand All @@ -33,16 +33,16 @@ Secondly, if the user were to go above their correction range, they would begin
* Blood glucose is still below or just below target, and
* Overnight basals were turning off/on.

So, what will you see after you adjust your basal lower? You will see some of the negative IOB disappear and, as a result, the predicted blood glucose curve will not show such an aggressive prediction for a blood glucose rebound.
So, what will you see after you adjust your basal lower? You will see some of the negative IOB disappear and, as a result, the forecasted blood glucose curve will not show such an aggressive forecast for a blood glucose rebound.

In this example, the user's basal rates were lowered across the board. All of the basal rates went down about 0.2 U/hr. It works out to about a 15% decrease, and is pretty standard adjustment for this user due to her monthly hormone changes.

The adjustment to basal rates caused Loop to reevaluate its math. After adjustment, Loop now has a negative IOB of -0.55 units vs the previous value of -1.33 units. This is a more reasonable given the situation. The prediction line with a -0.55 units IOB was not predicting nearly as aggressive of a "rebound" blood glucose rise.
The adjustment to basal rates caused Loop to reevaluate its math. After adjustment, Loop now has a negative IOB of -0.55 units vs the previous value of -1.33 units. This is a more reasonable given the situation. The forecast line with a -0.55 units IOB was not forecasting nearly as aggressive of a "rebound" blood glucose rise.

![Looped3](img/looped3.jpg){width="750"}
{align="center"}

Why did IOB and prediction change?
Why did IOB and forecast change?

The visualization below might be easier. The red line is how loop knew things to be before basal rates were adjusted lower. The purple line is how Loop viewed basal schedule after the adjustment lower.

Expand All @@ -67,4 +67,4 @@ The confirmation that adjustments were on-track would also be provided by lookin
{align="center"}


Note: This entire scenario can also be applied in situations where (1) blood glucose has been steady but above target and (2) Loop is holding significant positive IOB, and (3) Loop has been high temping fairly consistently. By increasing the scheduled basals, Loop will recalculate that the positive IOB was actually necessary (not extra) insulin delivery, and the positive IOB will decrease. This will help the prediction curve to more accurately realize that not all the insulin deliveries were being utilized as "corrections" but rather as needed background basal.
Note: This entire scenario can also be applied in situations where (1) blood glucose has been steady but above target and (2) Loop is holding significant positive IOB, and (3) Loop has been high temping fairly consistently. By increasing the scheduled basals, Loop will recalculate that the positive IOB was actually necessary (not extra) insulin delivery, and the positive IOB will decrease. This will help the forecast curve to more accurately realize that not all the insulin deliveries were being utilized as "corrections" but rather as needed background basal.

0 comments on commit 4851ce4

Please sign in to comment.