Avoid split carbs

[snchivs]

Hello. Thanks for the app. We love it and use it many times a day. Since my looper is 4 year old, many times I have to go back and edit the carbs in case she doesn't finish it. This becomes really difficult when the carbs are split in 1g blocks. Is there any way it can be just exported with labels? Say, Pizza - 2 g Pizza sugar for 1 hour, 11 g Pizza carbs for 3 hours 5 mins later, 8 g pizza e-carb for 4 hours 1 hour later --> This is how I'll get the info from EasyFPU app and then write it manually to the loop app. Thanks.

[UlricusR]

Hi

Thanks for using the app :-) and happy to hear it helps.

Doesn't the meal summary provide exactly this information? The splitting into 1g chunks is only for direct export, if you manually transfer the values, the meal summary should contain the information you need.

See also there user manual, chapter Meal Summary: https://www.rueth.info/iOS-EasyFPU/manual/

[snchivs]

Thank you for your reply. It’s our second most used app after loop for our DM management, so I can’t thank you enough. Is there no way to export to Apple health without breaking it into 1 g chunks?On May 12, 2023, at 12:05 PM, Ulrich R. @.***> wrote: Hi Thanks for using the app :-) and happy to hear it helps. Doesn't the meal summary provide exactly this information? The splitting into 1g chunks is only for direct export, if you manually transfer the values, the meal summary should contain the information you need.

See also there user manual, chapter Meal Summary: https://www.rueth.info/iOS-EasyFPU/manual/

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[UlricusR]

Not yet - I'll consider it for the next release - can't promise when this will be, though.

Also need to check if Loop has the possibility to import carbs together with an absorption time - I think it wasn't in the past (long time ago since I programmed it), which is why I had to "chunk" the carb information.

One question for my understanding, though: Let's assume you can import the three carb types together with an absorption time, will you then delete this entry if your 4yo does not finish the meal?

[snchivs]

Thank you. Thanks for the explanation. I now understand why you broke it in 1 g chunks. Yes. So, as in my previous example if she only has half a slice of pizza - I’ll go ahead and half all the 3 carbs - sugar, carbs and e-carbs. Loop prediction will give me a rough idea when she’ll drop and I’ll plan the next snack around that time. Works well for us and we don’t have to treat many lows. - Ritu On May 12, 2023, at 1:18 PM, Ulrich R. @.***> wrote: Not yet - I'll consider it for the next release - can't promise when this will be, though. Also need to check if Loop has the possibility to import carbs together with an absorption time - I think it wasn't in the past (long time ago since I programmed it), which is why I had to "chunk" the carb information. One question for my understanding, though: Let's assume you can import the three carb types together with an absorption time, will you then delete this entry if your 4yo does not finish the meal?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[UlricusR]

I check with the Loop developers and let you know.

What you could do to ease your life a little bit is to increase the interval time between the "chunks". In the app settings, you can choose the interval for all the carb types. By default, sugars are set to 5 min intervals, regular carbs to 5 mins and e-carbs to 10 mins. This is how the export looks like in that case:

If you increase this to 60 mins for both regular and e-carbs, the export changes to this:

If even longer (180 mins each):

However, I definitely wouldn't recommend such a long interval, as then the idea of e-carbs is kind of dead. It's just as if you give a bolus for regular carbs in the future. Maybe 30 mins is a good compromise?

[snchivs]

This makes sense and helps. Much appreciated. Thanks. On May 12, 2023, at 2:21 PM, Ulrich R. @.***> wrote: I check with the Loop developers and let you know. What you could do to ease your life a little bit is to increase the interval time between the "chunks". In the app settings, you can choose the interval for all the carb types. By default, sugars are set to 5 min intervals, regular carbs to 5 mins and e-carbs to 10 mins. This is how the export looks like in that case:

If you increase this to 60 mins for both regular and e-carbs, the export changes to this:

If even longer (180 mins each):

However, I definitely wouldn't recommend such a long interval, as then the idea of e-carbs is kind of dead. It's just as if you give a bonus for regular carbs in the future. Maybe 30 mins is a good compromise?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>