Usage tracking for Omnipod basal drift compensation

[nl-ruud]

Usage tracking: Omnipod basal drift compensation

This feature is available in 3.4.2.3 and later. It is currently gated by a semaphore file. We want to understand how many users have enabled it so we can confirm sufficient real-world usage and testing before safely removing the gating.

This feature compensates for basal insulin that the pump did not deliver as intended (e.g. due to frequent updates affecting delivery timing). The resulting deficit is detected and compensated for by delivering small (0.05U) boluses. For background and discussion, see issue #4158 and PR #4499.

Enable drift compensation

Create an empty file called omnipod_drift_compensation in the extra subfolder (lower case!) of your phone’s AAPS directory. After that, restart AndroidAPS.

Notes

• Basal drift may have (un)intentionally propagated into profiles — reassess your profile after enabling this feature.
• Compensation is delivered as a 0.05U bolus and will appear as such in the GUI and Watch app.

Are you using it?

Please leave a 👍 reaction on this issue if you enabled basal drift compensation.

Issues

Please do not report issues here. Open a separate issue with logs, steps to reproduce, and relevant details.

[xitation]

I'm running on 3.4.1.0 but I'm running with your PR cherry picked into it. Has been working great. I'm just lazy and most of the fixes in 3.4.2.2 don't apply to me so haven't rushed to update to it yet.

I'd obviously prefer that this is just merged into the mainline code base so we don't have to enable it as it's been a great fix for me and I suspect others when they realise there is an issue here too.

[nl-ruud]

I'd obviously prefer that this is just merged into the mainline code base so we don't have to enable it as it's been a great fix for me and I suspect others when they realise there is an issue here too.

Good news—it’s already merged, and the 3.4.2.3 release will include it. The semaphore file gating is temporary and will be removed once it’s proven stable in real-world use, this issue helps track that.

[AnthonyCW1999]

Is there a way to verify that this has been enabled?

[nl-ruud]

Is there a way to verify that this has been enabled?

Yes, if you get the log file after restart you should see Omnipod Dash drift compensation: enabled in the log and if it's not Omnipod Dash drift compensation: disabled.

[Josef-A]

Just a quick question.

If the compensation is logged as a bolus will that impact IOB calculation?
In that case will the IOB from basal that's not been delivered be redacted from IOB calculation?

[nl-ruud]

If the compensation is logged as a bolus will that impact IOB calculation?

No. This fix leaves the IOB calculation and its inputs unchanged, even if compensation is internally applied as a bolus. It monitors whether the insulin that should have been delivered is actually delivered, and compensates if it isn’t. As a result, delivered insulin more closely matches what the model expects in practice, without altering the IOB model itself.

For background and discussion, I recommend reading through issue #4158 and PR #4499.

[Josef-A]

I have read the issue and the PR.
But I did not see any mentions of how the IOB calculation is handled.
It might be obvious if I read the code, but I have not digged that deep.

Is the compensation bolus not included in the IOB calculation?

[nl-ruud]

The compensation bolus is not included the IOB calculation. If it would, the TDD would be off again.

[Navid200]

I have added the empty file and have restarted AAPS. But, I don't see a new setting. How/where can I find it?

[gerison77]

Is it gated in latest dev as well?

[nl-ruud]

Is it gated in latest dev as well?

Yes it is.

[Navid200]

I am running 3.4.2.3. I have added the empty file as instructed.
Where is the setting located?
I can see autotune under the hamburger menu that I had added quite a while ago. but, I don't see any related new setting there.

[nl-ruud]

I am running 3.4.2.3. I have added the empty file as instructed. Where is the setting located? I can see autotune under the hamburger menu that I had added quite a while ago. but, I don't see any related new setting there.

What makes you think there is a new setting somewhere? If you added the empty file and restarted AAPS it will be active: there's nothing else to set. If you want to verify it's active, check your logfile after AAPS restart. And you will probably notice a BASAL COMPENSATION BOLUS message from time to time.

[CeDoMain]

I think it would be good to link to this issue in the release notes (https://github.com/nightscout/AndroidAPS/releases/tag/3.4.2.3). I thought the tracking/compensation function is active per se but stumbled up on this issue here randomly while searching for dash bugs.