Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    old-square-eyes
    @old-square-eyes
    Screenshot 2021-07-24 at 9.07.54 AM.png
    Screenshot 2021-07-23 at 11.53.39 PM.png
    old-square-eyes
    @old-square-eyes
    I widened autosens min and max at one point because during sickness I couldn't get dosed enough.
    But that doesn't seem to be the underlying problem. What I can't get my head around is why autotune looks back at the end of the day and sees all this negative IOB and lows, zero temps etc and still seems to push out the recommendations.
    I saw somewhere else someone had to turn off autotune because thier sensitivity ratio was too different in the evening, than the morning.
    old-square-eyes
    @old-square-eyes
    Note the values in the screen shot for autotune results (actual pump values) have been ratcheted up by me over time to keep up with the recommendations. They are much higher than they used to be, and probably too high.
    Foxy7
    @Foxy7

    @old-square-eyes agree that autotune can go off course if ISF varies a lot during the day.
    Suggest you set both of these to equal 1 in preferences so autotune settings = pump settings (after next autotune run) this will reduce the amount of inuslin you carry after midnight.

            "autosens_max": 1,
        "autosens_min": 1,

    Annecdotally at least i think our DIA could be longer than 8 hours which we're currently using perhaps an issue for you too?

    old-square-eyes
    @old-square-eyes
    Thanks for the advice @Foxy7
    As it happens I have my DIA set to 8
    If I reduce max and min, will that not muzzle autosense also?
    Foxy7
    @Foxy7
    yeah it will. but once you've updated autotune results to match your pump settings (ie dialed it down) you can turn off autotune in cron and then put your autosens back on. that should reduce the overnight lows until you can figure out what's going on.
    old-square-eyes
    @old-square-eyes
    I have been having problems with NS lately due to payload size of upload.
    This error appears to have been fixed in the feature branch
    nightscout/cgm-remote-monitor#7129
    However, Autotune fails nightly for me, and also on manual run.
    In troubleshooting my NS issue I dropped the NS Treatments collection, and Device Status several times.
    I notice BGV in the OpenAPS Autotune dir has a number of days has an empty list.
    old-square-eyes
    @old-square-eyes
    I found...
    https://github.com/openaps/oref0/pull/1404/files
    I'm on Dev. My error seems to hit this new error handling... 
    /root/src/oref0/bin/oref0-autotune-prep.js:107
        return console.error("Warning: could not parse "+glucose_input", e);
                                                                      ^^^^^^

SyntaxError: Invalid or unexpected token
    at Module._compile (internal/modules/cjs/loader.js:723:23)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
Could not run oref0-autotune-prep ns-treatments.2021-10-15.json profile.json ns-entries.2021-10-15.json
    When I run Autotune web for a short perios (3 days) it works, suggesting the issue is with my rigs (this is happening on two rigs).
    On my rigs I have tried clearing the Autotune directory and also running manually for short periods. I get the error above.
    old-square-eyes
    @old-square-eyes
    After clearing the Autotune Dir, I inspected the json files... ns-entries.json has BGV. This tells me data from the NS API is present, and able to be downloaded.
    ns-treatments.json has data
    old-square-eyes
    @old-square-eyes
    I should expand... *clearing the Autotune Dir completely, and run manually over 3 days, where I know there is data there.
    Dana Lewis
    @danamlewis
    @old-square-eyes any chance it’s related to this pR Sarah just submitted? openaps/oref0#1410
    Dana Lewis
    @danamlewis
    It’s been merged to dev if you want to repull dev and see if that works for you
    old-square-eyes
    @old-square-eyes
    @danamlewis oh wow thank you.
    old-square-eyes
    @old-square-eyes
    Seems to be working
    Dana Lewis
    @danamlewis
    :+1:
    old-square-eyes
    @old-square-eyes
    And overnight too. I have an idea on how things could be improved safety wise. I'd like to see a stat in the autotune report "last successful run" or some sort of error count.
    Autotune was failing silently for me for the 3 months since the bug appeared. This was for a period when I was trouble shooting lows (just a few posts above no less!)
    I was accumulating files in the dir, but the fact they were all empty lists escaped me until another unrelated NS issue #7129 had me digging around.
    https://github.com/openaps/oref0/pull/1404/files should fix the issue of missing NS data causing the silent fail, for the most part. But I'd still like to see an Error/Warn count from the log in the actual report. As this will mean future bugs, whether in NS or not will be discovered.
    As that's what gets eyes most of the time.
    old-square-eyes
    @old-square-eyes
    I'm thrilled to see autotune has actually recommended very close to my manual basal (it's not longer insisting on heavy adjustments in two problem segments mentioned in July).
    Jane49
    @Jane49
    image.png
    Hi
    I'm trying to install autotune dev on linux (win10). It runs ok but I'm getting a problem with the autotune_recommendations.log
    Please can someone point me in the right direction?
    Thanks
    Jane49
    @Jane49
    Got it! I had a 0 value in a minutes entry of profile. All is good now :)
    Kelvin Kramp
    @KelvinKramp

    Hey everybody,
    I have been running into a problem. I don't get the same results here https://autotuneweb.azurewebsites.net/ as when I run autotune manually from my computer:

    I copied my profile.json to openaps/settings/autotune.json, openaps/settings/pumpprofile.json. and ran
    oref0-autotune-prep myopenaps/autotune/ns-treatments.json myopenaps/autotune/profile.json myopenaps/autotune/ns-entries.{date}.json myopenaps/autotune/profile.json
    in which date is replaced by dates of the different days

    I use as the startdate "2021-12-30" and as the enddate "2022-01-04" (the day of yesterday) and I get these results:
    00:00 | 0.360 | 0.432 | 2
    01:00 | 0.360 | 0.252 | 2
    02:00 | 0.360 | 0.252 | 0
    03:00 | 0.360 | 0.252 | 0
    04:00 | 0.360 | 0.252 | 2
    05:00 | 0.360 | 0.252 | 2
    06:00 | 0.360 | 0.432 | 2
    07:00 | 0.380 | 0.456 | 2
    08:00 | 0.380 | 0.266 | 2
    09:00 | 0.380 | 0.266 | 2
    10:00 | 0.380 | 0.456 | 0
    11:00 | 0.380 | 0.266 | 0
    12:00 | 0.320 | 0.224 | 2
    13:00 | 0.290 | 0.203 | 2
    14:00 | 0.280 | 0.196 | 2
    15:00 | 0.340 | 0.367 | 2
    16:00 | 0.360 | 0.242 | 2
    17:00 | 0.300 | 0.210 | 1
    18:00 | 0.320 | 0.245 | 1
    19:00 | 0.320 | 0.384 | 1
    20:00 | 0.380 | 0.428 | 2
    21:00 | 0.350 | 0.245 | 2
    22:00 | 0.330 | 0.231 | 2
    23:00 | 0.330 | 0.231 | 2

    When I run autotuneWeb on the azure platform I get these results, which seem better

    "Based on data entered between 2021-12-30 and 2022-01-04":

    Parameter | Pump | Autotune | Days Missing

    ISF [mg/dL/U] | 45.000 | 49.923 |
    Carb Ratio[g/U]| 16.000 | 14.852 |
    00:00 | 0.360 | 0.432 | 1
    01:00 | 0.360 | 0.432 | 1
    02:00 | 0.360 | 0.432 | 1
    03:00 | 0.360 | 0.432 | 1
    04:00 | 0.360 | 0.432 | 1
    05:00 | 0.360 | 0.432 | 1
    06:00 | 0.360 | 0.434 | 2
    07:00 | 0.380 | 0.454 | 2
    08:00 | 0.380 | 0.454 | 2
    09:00 | 0.380 | 0.456 | 1
    10:00 | 0.380 | 0.436 | 0
    11:00 | 0.380 | 0.369 | 1
    12:00 | 0.320 | 0.286 | 0
    13:00 | 0.290 | 0.241 | 1
    14:00 | 0.280 | 0.259 | 1
    15:00 | 0.340 | 0.291 | 0
    16:00 | 0.360 | 0.330 | 0
    17:00 | 0.300 | 0.280 | 1
    18:00 | 0.320 | 0.320 | 3
    19:00 | 0.320 | 0.320 | 3
    20:00 | 0.380 | 0.358 | 1
    21:00 | 0.350 | 0.387 | 1
    22:00 | 0.330 | 0.396 | 1
    23:00 | 0.330 | 0.396 | 1

    I think the problem has something to do with the input, but I can't figure out what Im doing wrong. I've tried to use different options for oref0-autotune-prep.js according to the help doc, ( -i and -u) but it doesn't get the results from manual autotune results better.

    Does anybody have an idea what I'm doing wrong?

    2 replies
    Denis Shevchenko
    @denisshevchenko
    Hi everyone.
    If I already set up myopenaps with --enable='autotune' - is it possible to disable autotune temporarily? I don't want to re-launch oref0-setup.sh, but just turn off autotune for a while.
    Scott Leibrand
    @scottleibrand
    are you trying to just prevent it from running every night? or go back to pump profile? the former is controlled by cron. for the latter you'd need to clean up some profile json files.
    oref0-runagain takes a few minutes to complete, but is an easy way to re-do oref0-setup without the full Q&A
    Denis Shevchenko
    @denisshevchenko

    @scottleibrand Thanks! But I'm trying to run it as ./oref0-runagain.sh --dir=/root/myopenaps ... --disable='autotune' ... and it shows me:

    Setting up oref0 in /root/myopenaps for pump 594848 with MDT CGM, 
NS host https://..., TTY /dev/spidev0.0, advanced features autotune

    So, it adds autotune again, right? Why?

    Scott Leibrand
    @scottleibrand
    you want to edit (with vi or nano) the ./oref0-runagain.sh file. It won't use command-line flags you pass like that.
    Or you can copy and paste the contents of ./oref0-runagain.sh and modify them
    dvdv
    @dvdv_gitlab
    is there a reason why autotuneweb insists on full access to a nightscout instance and does not accept tokens?
    Lloyd Mosley
    @bludevilx
    Hello all. I'm switching wife to a new phone and have never had this issue. The Bluetooth tethering is still trying to connect to the previous phone even after removing old phone and pairing with new phone. Can pair with new phone using sudo bt-pan client command but tries to connect to the old phone when we test it and leave the house. Any advice would be greatly appreciated. Thanks in advance.
    Edwin Hendriks
    @edwin-hendriks
    Hi there. Trying to use AutoTune (https://autotuneweb.azurewebsites.net/Results/Index?nsUrl=https://edwins-nightscout.herokuapp.com/). However, it is still saying that it is running. And it has for about an hour or 2. This seems long. Should I wait or is something wrong? And if so, how to fix it?