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

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

Open olorinmaia opened this issue 1 year ago • 9 comments

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

Step-by-step to reproduce:

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

Can't see any issues with profile values.

Screenshots:

Feb 18 '24 15:02 olorinmaia

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.

Feb 18 '24 15:02 Heiner1

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 :)

Feb 18 '24 15:02 olorinmaia

I'll try to reproduce it the same way.

Feb 18 '24 15:02 Heiner1

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

Feb 18 '24 16:02 Heiner1

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.