Merge pull request #61 from marionbarker/claude_suggestions

Overall update for LoopTips using claude suggestions

Author: marionbarker

dev-requirements.in

@@ -0,0 +1 @@
+pip-tools

dev-requirements.txt

@@ -0,0 +1,24 @@
+#
+# This file is autogenerated by pip-compile with Python 3.12
+# by the following command:
+#
+#    pip-compile --output-file=dev-requirements.txt dev-requirements.in
+#
+build==1.2.2.post1
+    # via pip-tools
+click==8.1.7
+    # via pip-tools
+packaging==24.1
+    # via build
+pip-tools==7.4.1
+    # via -r dev-requirements.in
+pyproject-hooks==1.2.0
+    # via
+    #   build
+    #   pip-tools
+wheel==0.44.0
+    # via pip-tools
+
+# The following packages are considered to be unsafe in a requirements file:
+# pip
+# setuptools

docs/data/nightscout.md

@@ -57,7 +57,7 @@ The day-to-day report will show a detailed overlay of boluses, basal rates, carb
 
 ### Daily Stats report
 
-The daily stats report is a pie chart showing the daily breakdown of your low, in-range, and high time in target, as well as other statistical analysis of your BG trends.
+The daily stats report is a pie chart showing the daily breakdown of your low, in-range, and high time in target, as well as other statistical analysis of your glucose trends.
 
 ![Daily Stats](img/daily-stats.png){width="700"}
 {align="center"}

docs/data/overview.md

@@ -11,10 +11,28 @@ When you go to your endocrinology office, they need to have a method to view all
 
 ## Available solutions for DIY apps
 
-The good news is that the community has some very useful tools to help address the shortcomings in the traditional data aggregation for Loop users. There are several tools available to help you and/or your endocrinologist evaluate your Loop data. Specifically, this section covers:
+The good news is that the community has some very useful tools to help address the shortcomings in the traditional data aggregation for Loop users. There are several tools available to help you and/or your endocrinologist evaluate your Loop data.
 
-* *Apple* Health app
-* *Nightscout*
-* *Tidepool*
-* *Perceptus*
+### Comparison of Data Tools
+
+| Tool | Best For | Data Retention | Cost | Setup Complexity |
+|------|----------|----------------|------|------------------|
+| **Apple Health** | Quick daily review, on-device access | Indefinite (on device) | Free | None (built-in) |
+| **Nightscout** | Remote monitoring, real-time troubleshooting, detailed Loop data | Varies by hosting plan | Low ($0-12/month) | Moderate |
+| **Tidepool** | Endo appointments, professional reports, long-term trends | Indefinite (cloud) | Free | Low |
+| **Perceptus** | Advanced algorithm analysis, deep insights | As long as you maintain account | Free | Low |
+
+### Which Tool Should You Use?
+
+- **Start with Apple Health** - It's already there and requires no setup
+- **Add Nightscout** if you need remote monitoring or want detailed troubleshooting capabilities
+- **Use Tidepool** for sharing data with your healthcare team and generating reports
+- **Try Perceptus** when you want advanced analysis of how Loop's algorithm is performing
+
+This section covers each tool in detail:
+
+* Apple Health app
+* Nightscout
+* Tidepool
+* Perceptus
 

docs/data/tidepool.md

@@ -101,7 +101,7 @@ If you hover over an item on the *Tidepool* web display, information is revealed
 * details about a manual bolus:
     * the recommended value with notation if this recommendation was modified (override or underride)
     * if this was a meal entry: Carbs and IC (insulin to carb ratio, called CR in Loop) are shown
-    * in all manual bolus, the Glucose, IOB, ISF and correction target range are shown
+    * in all manual bolus, the Glucose, IOB, ISF and correction range are shown
     * in the graphic below, the left image is from meal entry and the right from a bolus added after the meal
 
     ![meal entry details](img/tidepool-hover-meal-postmeal.png)

docs/how-to/cgm.md

@@ -3,15 +3,18 @@
 Obviously, without CGM data your Loop will not function. With the stability that Looping brings, many people are looking for ways to minimize their Loop downtime due to avoidable factors. Factors that make CGMs a potential problem include sensor failure, transmitter signal loss, poor calibrations, and the warmup period.
 
 ## Sensor warmup
-One of the obvious downtimes is during new sensor warmup. Unfortunately, the only way to avoid the 2-hour warmup (in the case of Dexcom's system) is to overlap your sensor sessions and this just isn't feasible for most people.
+One of the obvious downtimes is during new sensor warmup. 
 
-* Insurance doesn't provide adequate supplies to overlap sensor supplies; you would need two active transmitters and enough sensors to allow for overlap of use.
-* Sometimes sensors fail before a session was due to expire, making a planned overlap impossible.
-* Some people just don't want to wear two sensors at once. 
+### Dexcom G7 CGM
+One of the nice things about the Dexcom G7 is that many people begin the warm-up of the new sensor while the current sensor is in the grace period. Amazing - no gap in CGM coverage.
+
+### CGM that cannot be overlapped
+
+Unfortunately, many sensors cannot be overlapped, so there will be a period without CGM data between sensors.
 
 Since warmups are an important part of stabilizing CGM values and decreasing sensor noise, they are just going to continue to be a no-Loop time period for the foreseeable future. Most people simply cancel a currently running temporary basal, or let it run its course, when they start a new sensor session. For the two hours of warmup, the Loop will revert to the basal schedule programmed into the pump.
 
-Some people have opted to keep looping during sensor warmups by manually entering blood glucose checks through the Apple Health app for Loop to read. While technically Loop can use those values, the entries would have to be sufficiently frequent to be meaningful. If a person is willing to test 8-12 times in a two hour span, then looping through sensor warmup could be feasible through this method.
+Some people have opted to keep looping during sensor warmups by manually entering blood glucose checks, either through the *Loop* app (with version 3 and newer) or through the Apple Health app. While technically Loop can use those values, the entries would have to be sufficiently frequent to be meaningful. If a person is willing to test 8-12 times in a two hour span, then looping through sensor warmup could be feasible through this method.
 
 ## Sensor noise
 Depending on which CGM device you use, you may observe a sweet spot of data accuracy in the middle of your sensor's session but have sensor "noise" at the beginning and end of the session. Generally speaking, Loop does fairly well despite these times of sensor noise, although having a reasonable maximum basal rate does help mitigate the risk due to a noisy sensor.

docs/how-to/disconnect.md

@@ -1,8 +1,8 @@
 # Disconnecting from Pump
 
-For Medtronic pump users, you will have times where you need to disconnect from your insulin infusion site. Showers, some sports activities, swimming, and medical exams are some of the common reasons when disconnections are unavoidable.
+For tubed pump users, you will have times where you need to disconnect from your insulin infusion site. Showers, some sports activities, swimming, and medical exams are some of the common reasons when disconnections are unavoidable.
 
-The simplest way to deal with periods of disconnect is to suspend the Medtronic pump so that Loop knows no insulin was being delivered while you were disconnected. This will let Loop know that there is missing basal insulin that may need to be considered as part of the blood glucose prediction. Typically when disconnected from insulin delivery and negative insulin on board has developed, blood glucose will start to rise so Loop will expect to need to make up the missed insulin from disconnections.
+The simplest way to deal with periods of disconnect is to suspend the pump so that Loop knows no insulin was being delivered while you were disconnected. This will let Loop know that there is missing basal insulin that may need to be considered as part of the blood glucose prediction. Typically when disconnected from insulin delivery and negative insulin on board has developed, blood glucose will start to rise so Loop will expect to need to make up the missed insulin from disconnections.
 
 Some users are prone to forget to resume insulin delivery after suspending for disconnects.  One option is to use Siri by simply saying "Hey Siri, set a timer for 30 minutes" and that can serve as a reminder alarm to resume the pump after the shower is over. Other users may want to consider canceling any running temporary basal, setting a 30 minute zero temporary basal, and then setting Loop to open loop.  This will keep IOB fairly accurate while at the same time providing an automatic restart of normal basals if the user forgets to resume delivery. The user will then have to close loop again when ready to resume looping. Find what option works for you (or your child) the best; there are a number of ways to deal with disconnects.