Skip to content

Commit

Permalink
Merge pull request #1684 from openaps/peterleimbach-patch-2
Browse files Browse the repository at this point in the history
Update Open-APS-features.md
  • Loading branch information
peterleimbach committed Sep 9, 2023
2 parents 2138bfd + da4b497 commit eadf0ff
Showing 1 changed file with 39 additions and 2 deletions.
41 changes: 39 additions & 2 deletions docs/EN/Usage/Open-APS-features.md
Original file line number Diff line number Diff line change
Expand Up @@ -202,13 +202,50 @@ Default value: 2
(Open-APS-features-DynamicISF)=
## DynamicISF

DynamicISF was added in AAPS version 3.2 and requires you to start Objective 11 to use. Select DynamicISF in the config builder > APS to activate. It is recommended only for advanced users that have a good handle on AAPS controls and monitoring.
DynamicISF was added in AAPS version 3.2 and requires you to start Objective 11 to use. Select DynamicISF in the config builder > APS to activate. It is recommended only for advanced users that have a good handle on AAPS controls and monitoring.

Please note that to use Dynamic ISF effectively, the AndroidAPS database needs a minimum of five days of data.

DynamicISF adapts the insulin sensitifty factor dynamically based on total daily dose of insulin (TDD) and current and predicted blood glucose values. The only user selected parameter is the DynamicISF Adjustment Factor % found under Preferences > OpenAPS SMB. Select a value below 100% to make the DynamicISF effect less aggressive and greater than 100% to make it more aggressive. It is recommended that you start with a small value (less than 100%) and monitor your blood glucose levels closely.

Additional advanced detail on the methodologies used by DynamicISF to set the ISF value and safeties in place can be found here: [DynamicISF on github](https://github.com/aptash/AndroidAPS-DynISF)
Dynamic ISF uses Chris WIlson's model to determine ISF instead of a static profile settings. This is applied only in the openAPSSMB plugin. The openAPSAMA plugin continues to use profile settings for ISF.

The equation implemented is: ISF = 277700 / ( BG * TDD )

The implementation here splits the use into two. One to calculate current ISF for use with predictions, the other to calculate future ISF for use with dosing.

### Current ISF

This uses a combination of the 7 day average TDD and a linear extrapolation of the pumps current total insulin delivered to calculate a TDD for today.

The total daily dose used in the above equation is generally weighted 40% to the 7 day average and 60% to the extrapolation from the pump data. There are some special cases where this isn't applied. These are:

* *When the time is earlier than 5am and the pump TDD is greater than 7 day TDD*
* *When the time is earlier than 7am and the pump TDD is less than 80% of 7 day TDD*

In both these cases, a value of 80% of TDD is used in the caluclation.

*When the pump TDD is less than 33% of 7 day TDD*

In this case, the weighting is changed to be 75% pump TDD, 25% 7 day average TDD.

The dynamic ISF value is still adjusted when setting an activity or eating soon temp target, as per the standard oref model.

### Future ISF

Future ISF uses the same TDD value as generated above. It then uses different glucose values dependent on the case:

If delta is +ve or zero, or delta is negative but predicted glucose is above target, the future ISF value used for determining insulin required is the same as the current ISF.

If delta is -ve, and the predicted glucose level is below target, then the future ISF value is used, as this is a less aggressive value.

### Dynamic ISF Adjustment Factor

The 1.5 version of the code includes an adjustment factor that allows the user to specify a value between 1% and 300%. This acts as a multiplier on the TDD value and results in the ISF values becoming smaller (ie more insulin required to move glucose levels a small amount) as the value is increased above 100% and larger (ie less insulin required to move glucose levels a small amount) as the value is decreased below 100%.

### Autosens and sensitivity ratio

In this version of the code, the autosens value no longer uses the traditional oref1 deviation based model and instead uses rolling 24 hour TDD / 7-day average TDD. This is used to adjust basal and targets when the options are selected in preferences.

(Open-APS-features-overview-of-hard-coded-limits)=
## Overview of hard-coded limits
Expand Down

0 comments on commit eadf0ff

Please sign in to comment.