LoopKit
Increase Loop Carb History ICE Screen Timeline
Is your feature request related to a problem? Please describe. No technical problem at all. It is purely a functional usage problem. As a caregiver to a young Looper (12 years old), I am finding her/our carb counting and impact still very much a learning game. The ICE screen is very helpful in gauging carb impacts retroactively. The problem is, with respect to supper and evening snacks, that often have fat/protein impacts, that we are not able to view the impacts until after midnight (when we are sleeping) In order to see what is/has happening/ed, i would be required to go into her room at 2am, launch Loop, go to ICE, take screenshots, etc.... In the morning when we wake up, all the data is gone.
Describe the solution you'd like
I would like to see something like, the current view able to display the last 24 hours of data.
Otherwise, perhaps a new tab that shows the previous day's snapshot, maybe a day could be between 5am and 5am+24h, as opposed to 12am
Describe alternatives you've considered The only other alternative is Nightscout reports. Which I find is similar but much harder to read (for me). And way beyond a child's understanding.
Additional context Previous Issues https://github.com/LoopKit/Loop/issues/681 https://github.com/LoopKit/Loop/issues/840
Previous PR (later deleted I believe) https://github.com/LoopKit/Loop/pull/738
I use sugarmate, works well for this use case.
From: flyingpie101 @.> Sent: Wednesday, December 7, 2022 9:54:54 AM To: LoopKit/Loop @.> Cc: Subscribed @.***> Subject: [LoopKit/Loop] Increase Loop Carb History ICE Screen Timeline (Issue #1861)
Is your feature request related to a problem? Please describe. No technical problem at all. It is purely a functional usage problem. As a caregiver to a young Looper (12 years old), I am finding her/our carb counting and impact still very much a learning game. The ICE screen is very helpful in gauging carb impacts retroactively. The problem is, with respect to supper and evening snacks, that often have fat/protein impacts, that we are not able to view the impacts until after midnight (when we are sleeping) In order to see what is/has happening/ed, i would be required to go into her room at 2am, launch Loop, go to ICE, take screenshots, etc.... In the morning when we wake up, all the data is gone.
Describe the solution you'd like I would like to see something like, the current view able to display the last 24 hours of data. Otherwise, perhaps a new tab that shows the previous day's snapshot, maybe a day could be between 5am and 5am+24h, as opposed to 12am
Describe alternatives you've considered The only other alternative is Nightscout reports. Which I find is similar but much harder to read (for me). And way beyond a child's understanding.
Additional context n/a
— Reply to this email directly, view it on GitHubhttps://github.com/LoopKit/Loop/issues/1861, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQUBHGTQXR4AECRDIW2C3HTWMCXM5ANCNFSM6AAAAAASW7QCOI. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Or the perfect use case for Nightscout. It stores 36 hours visible on the screen and can be adjusted in view from 2-24 hours. This is how I rework any ISF, basal, or carb ratios for a 12 yo T1D also.
Ben
From: darrelld3 @.> Sent: Wednesday, December 7, 2022 8:06:31 AM To: LoopKit/Loop @.> Cc: Subscribed @.***> Subject: Re: [LoopKit/Loop] Increase Loop Carb History ICE Screen Timeline (Issue #1861)
I use sugarmate, works well for this use case.
From: flyingpie101 @.> Sent: Wednesday, December 7, 2022 9:54:54 AM To: LoopKit/Loop @.> Cc: Subscribed @.***> Subject: [LoopKit/Loop] Increase Loop Carb History ICE Screen Timeline (Issue #1861)
Is your feature request related to a problem? Please describe. No technical problem at all. It is purely a functional usage problem. As a caregiver to a young Looper (12 years old), I am finding her/our carb counting and impact still very much a learning game. The ICE screen is very helpful in gauging carb impacts retroactively. The problem is, with respect to supper and evening snacks, that often have fat/protein impacts, that we are not able to view the impacts until after midnight (when we are sleeping) In order to see what is/has happening/ed, i would be required to go into her room at 2am, launch Loop, go to ICE, take screenshots, etc.... In the morning when we wake up, all the data is gone.
Describe the solution you'd like I would like to see something like, the current view able to display the last 24 hours of data. Otherwise, perhaps a new tab that shows the previous day's snapshot, maybe a day could be between 5am and 5am+24h, as opposed to 12am
Describe alternatives you've considered The only other alternative is Nightscout reports. Which I find is similar but much harder to read (for me). And way beyond a child's understanding.
Additional context n/a
— Reply to this email directly, view it on GitHubhttps://github.com/LoopKit/Loop/issues/1861, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQUBHGTQXR4AECRDIW2C3HTWMCXM5ANCNFSM6AAAAAASW7QCOI. You are receiving this because you are subscribed to this thread.Message ID: @.***>
— Reply to this email directly, view it on GitHubhttps://github.com/LoopKit/Loop/issues/1861#issuecomment-1341192792, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACWNLO6AGX5WPNQE6DRU2C3WMCYYPANCNFSM6AAAAAASW7QCOI. You are receiving this because you are subscribed to this thread.Message ID: @.***>
I use sugarmate, works well for this use case. …
I also use Sugarmate ? Where do you see Carbs absorbed vs entered ?
I am specifically referring to the seeing the ICE screen, where you may have entered 40g carbs for a meal at 3 hours. But 4.5hours later, loop will show 45g carbs observed. Which I love. My problem is having a late supper at 7pm with a 5-6 hours absorption. The observed isn't fully available until 8-9 hours later, which is 4am. But when I look at her phone in the morning all the carb data from previous day is gone, so no observable carb data from that supper of previous day
I realized after my reply which screen you were refereeing too. I personally do not use this screen, I don’t find it as useful since our carb counts are very accurate, and we have very steady/balanced meals. In the event we have a high fat meal, or a large meal with more than average carbs we enact an override manually for 3-6 hours to help with these types of highs. I use Nightscout to determine all that data because I can see this data on a large scale over 24 hours with each point storing estimated IOB and COB. The raw data received from Nightscout seems to be much easier to use for these types of long term decisions in my use case.
Ben
From: flyingpie101 @.> Date: Wednesday, December 7, 2022 at 8:16 AM To: LoopKit/Loop @.> Cc: blameitonben @.>, Comment @.> Subject: Re: [LoopKit/Loop] Increase Loop Carb History ICE Screen Timeline (Issue #1861)
I am specifically referring to the seeing the ICE screen, where you may have entered 40g carbs for a meal at 3 hours. But 4.5hours later, loop will show 45g carbs observed. Which I love. My problem is having a late supper at 7pm with a 5-6 hours absorption. The observed isn't fully available until 8-9 hours later, which is 4am. But when I look at her phone in the morning all the carb data from previous day is gone, so no observable carb data from that supper of previous day
— Reply to this email directly, view it on GitHubhttps://github.com/LoopKit/Loop/issues/1861#issuecomment-1341220970, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACWNLO3STUMD6ZAJ5YQ5DKLWMCZ65ANCNFSM6AAAAAASW7QCOI. You are receiving this because you commented.Message ID: @.***>
That's fair. For me, I could probably come to grips with understanding all the data NS provides. But until someone reaches that level of understanding of how NS presents its data, I am thinking a user, especially a new or young user, would prefer to view that screen to provide insight into history. And I would expect that not every looper uses NS (but I hope they do) ;)
You don’t see this directly, I estimate based upon the graph trajectory in sugarmate compared to loops.
From: flyingpie101 @.> Sent: Wednesday, December 7, 2022 10:45:16 AM To: LoopKit/Loop @.> Cc: darrelld3 @.>; Comment @.> Subject: Re: [LoopKit/Loop] Increase Loop Carb History ICE Screen Timeline (Issue #1861)
That's fair. For me, I could probably come to grips with understanding all the data NS provides. But until someone reaches that level of understanding of how NS presents its data, I am thinking a user, especially a new or young user, would prefer to view that screen to provide insight into history. And I would expect that not every looper uses NS (but I hope they do) ;)
— Reply to this email directly, view it on GitHubhttps://github.com/LoopKit/Loop/issues/1861#issuecomment-1341259005, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQUBHGQ5QSALMLBBPXHO7OTWMC5JZANCNFSM6AAAAAASW7QCOI. You are receiving this because you commented.Message ID: @.***>
I second this. I also use the Loop screen to see how carbs are absorbed. And I also use it so my son, now 15, can learn and pay attention on how different meals affect his BG. He is taking over and he needs to learn. Giving him 3 different systems to learn how his carbs are absorbed is not efficient. I don’t find NS as easy to read as Loop. Many times I want to see what happened with the carb count absorption and as I can only see the “same day’s” data, I just can’t because I remembered too late and the info is no longer there. Tidepool is also not very helpful here...Thanks again for all you do and the always enriching conversation. Sofia. On Dec 7, 2022, at 11:45 AM, flyingpie101 @.***> wrote: That's fair. For me, I could probably come to grips with understanding all the data NS provides. But until someone reaches that level of understanding of how NS presents its data, I am thinking a user, especially a new or young user, would prefer to view that screen to provide insight into history. And I would expect that not every looper uses NS (but I hope they do) ;)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
This issue is stale because it has been open for 30 days with no activity.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
This issue is stale because it has been open for 30 days with no activity.
I think this could be addressed by substituting 'midnight' to an earlier time, e.g. 24 hours prior to 'now', on lines 141-142 in Loop/Loop/View%20Controllers/CarbAbsorptionViewController.swift
let midnight = Calendar.current.startOfDay(for: Date())
let listStart = min(midnight, chartStartDate, Date(timeIntervalSinceNow: -deviceManager.carbStore.maximumAbsorptionTimeInterval))
Yes 🙏 This would be such a welcome improvement.
Hanna SandovalSent from Yahoo Mail for iPhone
On Thursday, May 2, 2024, 5:43 AM, oliverstory @.***> wrote:
I think this could be addressed by substituting 'midnight' to an earlier time, e.g. 24 hours prior to 'now', on lines 141-142 in Loop/Loop/View%20Controllers/CarbAbsorptionViewController.swift let midnight = Calendar.current.startOfDay(for: Date()) let listStart = min(midnight, chartStartDate, Date(timeIntervalSinceNow: -deviceManager.carbStore.maximumAbsorptionTimeInterval))
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
A customization was added for either 2 full days or 1 week of Carb History (ICE) display. Once new work on dev proceeds (expect a lot of changes to code so the PR will require an update). In the meantime:
- https://www.loopandlearn.org/custom-code/#custom-list