-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev-b AutoISF / Can't calculate acceleration #3413
Comments
There are only 4 loop events in a single log file. It would help if under Maintenance you disable WEAR (because it just jams the file and makes reading very hard) but enable GLUCOSE which I think is the important one here. |
OK, I found 2 cases in the logs where Parabola settings change to 0 after a BG time recalculation and the BGs go into a "loop" with 3 minAGO coming over and over. In the first ZIP, it is 30, 40 and 45 min ago. Look before 9:16:34:840 |
Recalculated data period is over. There are no more dark green dots on the graph and AutoISF is working normally once again. There is a problem with the recalculated data and AutoISF. |
The problem is with gaps in data, not recalculated ones. AutoISF deals with them as expected. |
Sorry but I disagree. As soon as the yellow triangle disappeared (and the dark green dots too), the problem of parabola at 0 stopped. Field test says that I'm right ;) The recalculated data of Libre and G6 seems to be different. No idea what difference. Maybe the difference is that Libre has just seconds of difference when a transmitter change makes minutes of difference... Another possibility : Are you using the AutoISF plugin in AAPS dev or are you using your "own" AutoISF build ? |
I switched G6 transmitters which resulted in a desynchronisation of the 5 minutes interval which started the recalculated values.
I think (just a guess) that AutoISF plugin does not like recalculated values and can't get a "reliable" acceleration; all acceleration numbers are at 0.
As it didn't see the deceleration, it selected an agressive ISF for those 3 last BGs (were over target).
As you can see, just before the drop, there was a dark dot.
Here are the logs (around 22h13 and before)
The text was updated successfully, but these errors were encountered: