search

nightscout / AndroidAPS

Opensource automated insulin delivery system (closed loop)
https://wiki.aaps.app
GNU Affero General Public License v3.0
667 stars 1.58k forks source link

[DEV] Error "Profile sensitivity value" is out of hard limits when enabling "Dynamic sensitivity" #3226

Open olorinmaia opened 5 months ago

olorinmaia commented 5 months ago

AAPS 3.3.0-dev-a Build: 9c327b4e4c-2024.02.17 Logs: AndroidAPS_LOG_1708209853078.log.zip

Step-by-step to reproduce:

  1. Start with "Dynamic sensitivity" disabled in SMB plugin. Run a loop or two.
  2. Enable "Dynamic sensitivity". Execute loop, either on next loop run or manually via Loop plugin. Error should pop up.
  3. After error, when next BG arrive then automatic looprun returns no error.

Can't see any issues with profile values.

Screenshots: image image image image

Heiner1 commented 5 months ago

Same to me. Did you also switch from another AAPS-development-idea to the original dev-version? NSv3 Full Sync doesn't help if you want to get all data e.g. older than 10 days.

olorinmaia commented 5 months ago

No, this is a long running test-rig which I regularly update to latest dev. I've noticed the error many times before, but now I found a way to reproduce it, and it will be easier to find out what's causing it :)

Heiner1 commented 5 months ago

I'll try to reproduce it the same way.

Heiner1 commented 5 months ago

You're right, error message is reproducable, exactly the same behaviour. For me the difference is now: DynISF Loop is running again. Bevor I got more error messages and no falling back to normal SMB mode - loop had been deactivated. So I think it has something to do with database? AndroidAPS.log

ga-zelle commented 5 months ago

I came across that message a lot in the recent days. I was focused on some other topic and did not drill down to base reason. However, my impression was that the message text is very misleading because it seems related to variable_sens as used in DynamicISF and has nothing to do with the pump profile sensitivity. If not yet calculated then variabale_sens may get assigned 0.0 or 1.0 which triggers the message. If assigning 100.0 when not used or not yet calculated then there was no message.

vanelsberg commented 5 months ago

Step-by-step to reproduce:

Confirming, Seeing the same on current dev#9c327b4e

lostboy86 commented 5 months ago

it's the same issue of mine :

https://github.com/nightscout/AndroidAPS/issues/3192

robinsondan87 commented 1 month ago

Is there a way to work around this or stop the error from happening?

vanelsberg commented 1 month ago

Step-by-step to reproduce

Confirming. Have also been seeing this some time ago. Looks like your repro...