Skip to content

Commit

Permalink
Drafting a new "optimizing settings" page (#1204)
Browse files Browse the repository at this point in the history
* Remove spacing

* try to force sphinx 1.5.6

* Update oref1.md (#1199)

Updated Troubleshooting section under common errors. Docs state loop log should include You should see “Starting supermicrobolus pump-loop at...” in pump-loop.log if you have successfully enabled everything. However, it just states "Starting oref0-pump-loop".  This would avoid confusion for future SMB users.

* Update loops-in-progress.md (#1203)

Added my name - first PR

* Drafting a new "optimizing settings" page
  • Loading branch information
danamlewis committed Jan 27, 2018
1 parent 12f7002 commit d9e7dac
Show file tree
Hide file tree
Showing 3 changed files with 30 additions and 2 deletions.
28 changes: 28 additions & 0 deletions docs/docs/Customize-Iterate/optimize-your-settings.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Optimizing your settings

Once you've been looping, you may look at your graphs and wonder how to achieve different results. It takes some time to do, but optimziing your settings is one of the keys to improving things, once you have basic looping up and running.

Note: if you're not familiar with the approach of optimizing settings, it's very important to understand that you should only change ONE thing at a time, and observe the impact for 2-3 days before choosing to change or modify a setting (unless it's obviously a bad change that makes things worse). The human tendency is to turn all the knobs and change everything at once; but if you do so, then you may end up with further sub-optimal settings for the future.

Think about this: when many people start looping, they often have too high basal and too low carb ratio or ISF. What this means is they're using basal insulin around mealtimes to compensate for not usually giving the amount of insulin needed for food. When you go on a DIY closed loop and the system begins to help with adjusting insulin for BGs, it can become apparent that settings need to be tweaked. Here are a series of general approaches you can take for optimizing your settings, with example patterns:

## Frequent negative IOB at the same time every day

Negative IOB happens when you are getting less insulin than your normal basal amount. We created Autotune to help deal with these situations and to automatically tune your basal rates for any recurring patterns where you need more or less basal. However, if you're not running autotune, and you're observing patterns of negative IOB (more than a day or two), indicating a trend, you may need to change your settings. Things to test include:

* Adjusting your DIA. In oref0 0.6.0 and beyond, regardless of what is in your pump, it will default to using a DIA of 5. It is also very common for OpenAPS users to have DIA of 6 or 7 set (in `preferences.json`)
* Basal rates are too high for the hours preceding the pattern of negative IOB.
* ISF is off. (Usually not this; start with testing and tweaking basals and DIA first)

## Hills and valleys / Peaks and troughs / Up and down patterns

Sometimes people observe "roller coasters" in their BG graph. Remember this is all relative - so a roller coaster to you of 20 points may not be a big deal (and a 50 point rise or drop is a roller coaster); to others, that bugs them.

First, you should eliminate human behaviors that cause these. Usually, it's things like giving a traditional dose of "fast carbs" (sugar, glucose tabs, candy, etc.) that is more than needed for a low or a pending low. Remember the system is reducing insulin, and so you often need way less carbs to deal with a low. As a result, you may rise afterward. That's a human-driven rise that won't be fixed by changing settings; just behaviors. Ditto for human-driven drops; e.g. by rage bolusing or otherwise bolusing too much. A better approach is to set a low temporary target, which asks OpenAPS to do "more", but will still keep you in a safe range.

Human behaviors set aside, if you are still seeing hills and valleys in your BG graphs, consider the following:
* ISF is often off. You may want to change your ISF. Remember, make small changes (say, 2-5 points for mg/dl, and .5 or less for mmol) and observe over 2-3 days.




2 changes: 1 addition & 1 deletion docs/docs/Customize-Iterate/oref1.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ There are multiple preference toggles for SMB/UAM. Check out the [preferences pa

1. Make sure you read the above, especially the "only enable oref1 if..." section. SMB will behave differently than oref0 would. Watch carefully, and use your common sense and do what's right for you & your diabetes.
2. Common errors include:
* Not changing the preferences to be "true" for the relevant settings after you've enabled the oref1 features. You should see "Starting supermicrobolus pump-loop at..." in pump-loop.log if you have successfully enabled everything.
* Not changing the preferences to be "true" for the relevant settings after you've enabled the oref1 features.
* Not running autotune. Remember, you don't have to enable it to run as part of your loop at night, but you should run it manually, review the results, and otherwise be VERY confident in your underlying pump settings (basals, ISF, carb ratio) before using oref1.
* Pump clock being >1 minute off from rig's time. This means 60 seconds. Not 61 seconds; 68 seconds; 90 seconds. Needs to be less than 60 seconds apart. `"Checking pump clock: "2017-05-16T15:46:32-04:00" is within 1m of current time: Tue May 16 15:47:40 EDT 2017` is an example of a >60 second gap that needs fixing before it will work properly. We added a script to automatically attempt to fix the pump time in case of a >60 second difference, but you may occasionally see this type of error in the logs until the script is able to properly adjust the pump time.

Expand Down
2 changes: 1 addition & 1 deletion docs/docs/While You Wait For Gear/loops-in-progress.md
Original file line number Diff line number Diff line change
Expand Up @@ -232,4 +232,4 @@ List of people who are working on closed loops:
- Ben Ortega (Minneapolis, MN)
- Reza Bolouri (Melbourne, Australia)
- Todd Radel (Doylestown, PA)

- Steve Mann (Bronx, NY)

0 comments on commit d9e7dac

Please sign in to comment.