You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on a recent discussion in #dynamic-isf-cr in discord, it appears that AAPS's autotune has an option to allow it to use multiple days of data, instead of just 'the last 24 hours', with their default set to 5 days, and recommendation in their docs not to go too low ( ie. you can do 24h, but they don't recommend it )
Not sure what would be involved in adapting that to our autotune .. it appears that theirs doesn't include javascript at all, its written in whatever language Android apps are written in ...
But maybe an area to focus on for some improvements to autotune accuracy?
The text was updated successfully, but these errors were encountered:
Based on a recent discussion in #dynamic-isf-cr in discord, it appears that AAPS's autotune has an option to allow it to use multiple days of data, instead of just 'the last 24 hours', with their default set to 5 days, and recommendation in their docs not to go too low ( ie. you can do 24h, but they don't recommend it )
Not sure what would be involved in adapting that to our autotune .. it appears that theirs doesn't include javascript at all, its written in whatever language Android apps are written in ...
But maybe an area to focus on for some improvements to autotune accuracy?
The text was updated successfully, but these errors were encountered: