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
As highlighted in the red box:The code is comparing with maxIOBPredBG rather than maxCOBPredBG when recording the maximum COB prediction.
My questions are:
1、Is this an intentional design choice to only record COB predictions that exceed the maximum IOB prediction? Or should it have been comparing COBpredBG > maxCOBPredBG to simply track the absolute maximum of COB predictions?
2、2、If this is intentional, what is the purpose of this design? Is it to highlight the additional blood glucose rise caused by carbohydrates?
I appreciate your insights on this matter.
The text was updated successfully, but these errors were encountered:
It looks like that variable was updated as part of 7c8556f, which has a commit comment of "fix minPredBG logic for high-temping based on minIOBPredBG". Previous to that it was introduced in 44e54fb with the comment
"output predBGs as an object with three different predictive arrays"
Beyond that, I don't remember why I changed that particular variable (back in April 2017).
As highlighted in the red box:The code is comparing with maxIOBPredBG rather than maxCOBPredBG when recording the maximum COB prediction.
My questions are:
1、Is this an intentional design choice to only record COB predictions that exceed the maximum IOB prediction? Or should it have been comparing COBpredBG > maxCOBPredBG to simply track the absolute maximum of COB predictions?
2、2、If this is intentional, what is the purpose of this design? Is it to highlight the additional blood glucose rise caused by carbohydrates?
I appreciate your insights on this matter.
The text was updated successfully, but these errors were encountered: