Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Insulin Peak Time: confusing / wrong help text, may affect oref algorithm #347

Open
DreyCon-Raphael opened this issue Jul 9, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@DreyCon-Raphael
Copy link

Describe the bug

*OpenAPS settings pull information of which insulin curve type to select from the set insulin type of the configured pump. In my case it is Dash with Fiasp.
While making some adjustments / finetuning on the OpenAPS settings I discovered this help text:
image
This made me selecting "rapid-acting" Insulin curve manually as it states:
"Oref assumes for ultra-rapid (Lyumjev) & rapid-acting (Fiasp) curves minimal (35 & 50 min) and maximal (100 & 120 min) [...]"

Oref might interprete fiasp as ultra-rapid as well! So we need to check wich oref modell will be used in case of Fiasp. So maybe the wrong model might be selected.

Attach a Log

no log available

To Reproduce

Steps to reproduce the behavior:

  1. Go to 'Settings -> OpenAPS OTHER settings - Insulin Peak Time'
  2. Click on 'Insulin Peak Time' for help text to pop up

Expected behavior

A clear and concise description of what you expected to happen.
Depending on the set insulin type in pump settings the correct Insulin curve (and therefore OpenASP curve type) should be set. After this check this help text may need an adjustment.

Screenshots

If applicable, add screenshots to help explain your problem.
image

Setup Information (please complete the following information):

Smartphone:

  • Hardware: iPhone 15 Pro
  • OS Version: iOS 17.5.1

Pump:

  • Manufacturer: Insulet
  • Model: Omnipod Dash

CGM:

  • Device: Dexcom G7
  • Manager app: Dexcom App

Trio Version:

  • Version Number: [v0.1.0 (1)] Branch: alpha 7c88bac
  • Repo: nightscout/trio
  • Git Reference: []

Technical Details

If applicable, provide any technical details that might help in diagnosing the problem. This could include logs, error messages, or relevant configuration details.

Additional context

Add any other context about the problem here.

@DreyCon-Raphael DreyCon-Raphael added bug Something isn't working needs-triage labels Jul 9, 2024
@snickerdoodleparent
Copy link

Insulin Peak Time popup came from iAPS. It's problematic because it seems to suggest Fiasp is rapid-acting instead of ultra-rapid and Novolog/Humalog/Apidra aren’t mentioned at all. (It's still wrong in the newest version despite crowdin suggestions.)

Refer to the Trio docs: Insulin Curves
rapid-acting: This is a default setting for Novolog, Novorapid, Humalog, and Apidra insulins. Selecting this setting will result in OpenAPS to use an exponential activity curve with peak activity set at 75 minutes and duration of insulin action set at 300 minutes (5 hours).
ultra-rapid: This is a default setting for Fiasp. Uses an exponential activity curve with peak activity set at 55 minutes and duration of insulin action set at 300 minutes (5 hours).

I'm pretty sure 75 should be 65, and 55 minutes should be 50 in the Trio docs. @MikePlante1 had found the times in the iAPS code:
image

Good catch, this has been long time discussed in iAPS, most of us probably forgot this text is still kicking around.

@tmhastings
Copy link
Contributor

Corrected with PR #348

Copy link

github-actions bot commented Aug 9, 2024

hey 👋 - no triage is done for 30 days 🤐 ... anybody? triage is required!

@github-actions github-actions bot added the stale label Aug 9, 2024
@github-actions github-actions bot removed the stale label Aug 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: In review
Development

No branches or pull requests

4 participants