Change min_5m_carbimpact from 3 to 8 #3563
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some reason the autotune branch used a
min_5m-carbimpact
of 3 instead of 8 as oref0 does, leading to unrealistic carb absorption results and thus wrong autotune results. Changingmin_5m-carbimpact
from 3 to 8 leads to Nightscout autotune providing results very similar to autotune running on a rig (still not perfectly identical for reasons I have not yet understood)PS: Do we need these codacy-bot entries? I find that they make some longer discussions completely unreadable.