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
{{ message }}
Repository navigation
feature request: configurable glucose graph eventually field #933
This is a feature request. By default, the glucose chart displays an extrapolation of the eventual blood glucose. As a user, it would be much more useful to have display the blood glucose at a user specified time in the future. For example 30 minutes, 1 hr, 2 hr, etc., into the future. There reason are as follows:
I have not found the extrapolation to be very accurate past a couple of hours anyways
Stuff happens, and blood glucose 4+ hrs away is not that useful to the caretaker of a T1
The main reason that it is shown that far out is not necessarily that that prediction is expected to be accurate (often you hope it isn't!), but rather that that shows what Loop is using to make its dosing decisions. For example, if your eventual blood glucose number is above your target range (and you aren't otherwise predicted to go below target in the meantime), it will give you insulin to return you to target. Seeing what that forecast line looks like, and what the currently-predicted "eventual" number is, is essential to understanding how Loop operates.
Activity
elnjensen commentedon May 2, 2019
The main reason that it is shown that far out is not necessarily that that prediction is expected to be accurate (often you hope it isn't!), but rather that that shows what Loop is using to make its dosing decisions. For example, if your eventual blood glucose number is above your target range (and you aren't otherwise predicted to go below target in the meantime), it will give you insulin to return you to target. Seeing what that forecast line looks like, and what the currently-predicted "eventual" number is, is essential to understanding how Loop operates.
github-actions commentedon Nov 9, 2023
This issue is stale because it has been open for 30 days with no activity.
github-actions commentedon Nov 23, 2023
This issue was closed because it has been inactive for 14 days since being marked as stale.
[LOOP-5769] Temporarily revert LOOP-5769 (LoopKit#933)