Skip to content

Commit c56a098

Browse files
committedFeb 7, 2020
Fix example safety caps table
1 parent f46aa4f commit c56a098

File tree

4 files changed

+12
-16
lines changed

4 files changed

+12
-16
lines changed
 

‎docs/docs/While You Wait For Gear/example-max-safety-chart.md

-12
This file was deleted.
Binary file not shown.

‎docs/docs/While You Wait For Gear/nightscout-setup.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -75,9 +75,9 @@ your data, customized watchfaces with your OpenAPS data, and integration with IF
7575
**The remaining variables can be left at their default values.**</br></br>
7676

7777
*****************
78-
**Note:** for `BRIDGE_MAX_COUNT`: This value sets the number of BG values to pull from Share per update. Each Dexcom BG value represent 5 minutes. Nightscout defaults to `BRIDGE_MAX_COUNT=1`. If you lose connectivity with your Dexcom transmitter, your Share app will automatically backfill data points when you regain connectivity. Nightscount does not do this and you will have gaps in the data for when you were out of range. More information [here](https://github.com/nightscout/cgm-remote-monitor#bridge-share2nightscout-bridge).
78+
**Note:** for BRIDGE_MAX_COUNT: This value sets the number of BG values to pull from Share per update. Each Dexcom BG value represent 5 minutes. Nightscout defaults to BRIDGE_MAX_COUNT=1. If you lose connectivity with your Dexcom transmitter, your Share app will automatically backfill data points when you regain connectivity. Nightscount does not do this and you will have gaps in the data for when you were out of range. More information [here](https://github.com/nightscout/cgm-remote-monitor#bridge-share2nightscout-bridge).
7979

80-
You can change the `BRIDGE_MAX_COUNT` value to pull more samples per query, which will backfill BRIDGE_MAX_COUNT values for you. This change increases your data usage and may affect your Nightscout billing tier. Setting BRIDGE_MAX_COUNT to 7 will update the previous 35 minutes of data and will keep OpenAPS up to date on your current BG trends. If you frequently have larger data gaps and you use autotune, you may consider increasing this number more to backfill data more aggressively.
80+
You can change the BRIDGE_MAX_COUNT value to pull more samples per query, which will backfill BRIDGE_MAX_COUNT values for you. This change increases your data usage and may affect your Nightscout billing tier. Setting BRIDGE_MAX_COUNT to 7 will update the previous 35 minutes of data and will keep OpenAPS up to date on your current BG trends. If you frequently have larger data gaps and you use autotune, you may consider increasing this number more to backfill data more aggressively.
8181
*****************
8282

8383
* Click the purple `Deploy` button at the bottom of screen.
@@ -139,7 +139,7 @@ Your NIGHTSCOUT site is now all set-up. Congrats!
139139

140140
## Nightscout Migrations
141141

142-
### Switching from `API_SECRET` to token based authentication for your rig
142+
### Switching from API_SECRET to token based authentication for your rig
143143

144144
You can secure your Nightscout and CGM data with [token based authentication](http://www.nightscout.info/wiki/welcome/website-features/0-9-features/authentication-roles).
145145
This requires Nightscout 0.9 (Grilled Cheese) and oref0 0.5.0 or later.

‎docs/docs/While You Wait For Gear/preferences-and-safety-settings.md

+9-1
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,15 @@ You can also view this message in the Nightscout OpenAPS pill (which pops up a d
138138

139139
#### A few examples:
140140

141-
![Example safety cap image - see raw file in the same folder of docs if needs editing](examples_safety_caps_in_play.png)
141+
| | Example 1 | Example 2 | Example 3 | Example 4 |
142+
| --- | --------- | --------- | --------- | --------- |
143+
| user's max basal safety setting (in pump) | 2.0 | 2.0 | 3.0 | 2.5 |
144+
| `max_daily_safety_multiplier` | 3 | 3 | 3 | 3 |
145+
| `current_basal_safety_multiplier` | 4 | 4 | 4 | 4 |
146+
| user's current basal rate | 1.0 | 0.4 | 1.2 | 0.7 |
147+
| user's highest programmed basal rate | 1.5 | 1.0 | 1.2 | 0.8 |
148+
| OpenAPS recommended temp basal rate | 3.0 | 1.8 | 2.4 | 2.6 |
149+
| Actual temp basal rate allowed | 2.0 | 1.6 | 2.4 | 2.4 |
142150

143151
* In **Example 1**, the user's max basal safety setting is the constraining limit on the OpenAPS recommended temp basal rate.
144152
* In **Example 2**, 4x the user's current basal rate is the constraining limit on the OpenAPS recommended temp basal rate.

0 commit comments

Comments
 (0)