These are chat archives for nightscout/intend-to-bolus

6th
Sep 2018
Travis Cannell
@diabeticpilot
Sep 06 2018 03:30
did a fresh flash and install of the latest dev branch. After 1 hr it still isn't looping, any ideas?
Preflight fail. Retry 1 of preflight
Preflight fail. Listening: .No interfering pump comms detected from other rigs (                                                                           this is a good thing!)
Continuing oref0-pump-loop at Wed Sep  5 20:26:48 PDT 2018
Retry 2 of preflight
Preflight fail. Listening: .No interfering pump comms detected from other rigs (                                                                           this is a good thing!)
Continuing oref0-pump-loop at Wed Sep  5 20:27:49 PDT 2018
Retry 3 of preflight
Preflight fail. Couldn't preflight
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 11 s silence before mmtuning
Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Sep  5 20:28:36 PDT 2018
Listening for 11 s silence before mmtuning: Listening: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Wed Sep  5 20:28:48 PDT 2018
mmtune:
waiting for 90 second silence before continuing
Listening: .
Scott Leibrand
@scottleibrand
Sep 06 2018 03:36
try a debug run to see what failing on the mmtune
Travis Cannell
@diabeticpilot
Sep 06 2018 03:40
how do you do a debug run?
I just re-ran setup script to see if that does something
Travis Cannell
@diabeticpilot
Sep 06 2018 03:52
thank you! re-running setup script fixed it. I think soemthing happened to the mmtune setup
Scott Leibrand
@scottleibrand
Sep 06 2018 03:55
:+1:
ideeagit
@ideeagit
Sep 06 2018 12:03
@danamlewis @scottleibrandI run autotune automatically at night now, and the problem got fixed. I have now the ISF value of midnight in autotune and also the rig takes this one.
But still have high deviations in the log. Dev should be the deviation from the last 5 minutes compared to BGI, right? BGI here is 0 and tick was -7, why is it then -30?
DEV.JPG
Scott Leibrand
@scottleibrand
Sep 06 2018 14:52
The deviation listed there is in units of mg/dL/30m, not mg/dL/5m, because it was originally used for subtracting from eventualBG.
ideeagit
@ideeagit
Sep 06 2018 15:35
Ahh okay then (BGI-tick)6 should be the deviation? But the deviation still adjusts evenutalBG...?
Is it possible to reset autotune, that it starts from the beginning, cose i had the pump off but the rig was connected, so adjustments should not be correct. Something like: rm ~/myopenaps/autotune/
.json
rm ~/myopenaps/settings/autotune.json
"code to start autotune again"
automatically
Scott Leibrand
@scottleibrand
Sep 06 2018 15:43
you can start by deleting all the json files like that, ya. then either wait until 4am for it to run again on today's data, or run it manually on whatever days are good. I wouldn't overthink it, though.
just get your pump settings as accurate as you manually can, and let autotune start running every morning to tweak them
toddclare
@toddclare
Sep 06 2018 15:50
hey all, getting started hardware question. want to do and Edison rig (smaller, less charging). found this https://www.ebay.com/itm/Intel-Edison-Standard-Power-On-Board-Antenna-EDI2-SPON-Arduino-EDI2ARDUIN-AL-K/223110635616?hash=item33f26e2060:g:M4MAAOSwrORbexaR ... I'm a SW not a HW guy... can this be the thing I want?
Eric
@ecc1
Sep 06 2018 16:09
@toddclare yes, that will work. (that auction includes the Arduino-compatible dev board which you don't need (you just need the Edison compute module itself, plus an Explorer Board))
Matt Kupisz
@rumil
Sep 06 2018 16:26
Zrzut ekranu 2018-09-06 o 18.15.04.png
Is Enlite accuracy dependent on pump’s firmware version? I switched from my 754 with 2.8 firmware to 722 with 2.2 firmware in order to start looping but at the same time I noticed much less accurate CGM readings. The worst thing is something that on the graph looks like a compression low but it’s not a compression low - happened on 2 sensors already. Since my ratios are still off such reading make me go down and up for quite some time
(I’m back to open loop, so it’s not visible in this graph)
Eric
@ecc1
Sep 06 2018 16:37
@rumil are those same dips on the pump display too, not just NS?
Matt Kupisz
@rumil
Sep 06 2018 16:44
Yes, pump displays the same drops
It might be that I got 2 faulty sensors in a row but I wondered if finding 722 with 2.4 firmware would improve
Eric
@ecc1
Sep 06 2018 16:54
can you leave the 754 running, just to see if it processes the sensor readings in the same way as the 722?
Matt Kupisz
@rumil
Sep 06 2018 16:56
Is it possible to connect 2 pumps to the same sensor? If so, I may try that
toddclare
@toddclare
Sep 06 2018 17:50
thank you, @ecc1
Eric
@ecc1
Sep 06 2018 18:03
@rumil pretty sure the sensor is a simple one-way radio broadcast, so any pump in range can receive its readings
MoyRivera
@MoyRivera
Sep 06 2018 18:04
Hi all, hope you are well. I would like to know if are there any procedure to enroll in this great community, and how is created. Somebody from Spain? Thx a lot for your time and support.
Samuchco
@Samuchco
Sep 06 2018 19:01
Autotune/Autosens issue: Trying to control "roller-coaster" effect, I'm looking at ISF settings. I see big difference between pump ISF (105) and Autotune ISF (148) and Limiting adjusting ISF (258 and sometimes higher).
I'm attaching the autotune log. Any suggestions?
Sep 06 04:05:54 loop2 autotune.log: p50deviation: -1.6 p50BGI -2.15 p50ratios: 1.746 Old ISF: 148.068 fullNewISF: 258.527 adjustedISF: 150 newISF: 148.454 newDIA: 6 newPeak: 75
Sep 06 04:05:54 loop2 autotune.log: Autotune pump profile recommendations:
Sep 06 04:05:54 loop2 autotune.log: ---------------------------------------------------------
Sep 06 04:05:54 loop2 autotune.log: Recommendations Log File: /root/myopenaps/autotune/autotune_recommendations.log
Sep 06 04:05:54 loop2 autotune.log: /usr/local/bin/oref0-autotune-recommends-report: line 25: warning: setlocale: LC_NUMERIC: cannot change locale (en_US.UTF-8): No such file or directory
Sep 06 04:05:57 loop2 autotune.log: Parameter      | Pump     | Autotune 
Sep 06 04:05:57 loop2 autotune.log: -------------------------------------
Sep 06 04:05:57 loop2 autotune.log: ISF [mg/dL/U]  | 105.000  | 148.454  
Sep 06 04:05:57 loop2 autotune.log: Carb Ratio[g/U]| 13.000   | 13.528   
Sep 06 04:05:57 loop2 autotune.log: Basals [U/hr]  | -        |
Sep 06 04:05:57 loop2 autotune.log:   00:00        | 0.350    | 0.246    
Sep 06 04:05:57 loop2 autotune.log:   01:00        |          | 0.246    
Sep 06 04:05:57 loop2 autotune.log:   02:00        |          | 0.246    
Sep 06 04:05:57 loop2 autotune.log:   03:00        |          | 0.252    
Sep 06 04:05:57 loop2 autotune.log:   04:00        |          | 0.250    
Sep 06 04:05:57 loop2 autotune.log:   05:00        | 0.400    | 0.290    
Sep 06 04:05:57 loop2 autotune.log:   06:00        |          | 0.293    
Sep 06 04:05:57 loop2 autotune.log:   07:00        |          | 0.320    
Sep 06 04:05:57 loop2 autotune.log:   08:00        |          | 0.320    
Sep 06 04:05:57 loop2 autotune.log:   09:00        |          | 0.319    
Sep 06 04:05:57 loop2 autotune.log:   10:00        | 0.300    | 0.316    
Sep 06 04:05:57 loop2 autotune.log:   11:00        |          | 0.316    
Sep 06 04:05:57 loop2 autotune.log:   12:00        |          | 0.318    
Sep 06 04:05:57 loop2 autotune.log:   13:00        |          | 0.322    
Sep 06 04:05:57 loop2 autotune.log:   14:00        | 0.500    | 0.344    
Sep 06 04:05:57 loop2 autotune.log:   15:00        |          | 0.344    
Sep 06 04:05:57 loop2 autotune.log:   16:00        |          | 0.344    
Sep 06 04:05:57 loop2 autotune.log:   17:00        |          | 0.350    
Sep 06 04:05:57 loop2 autotune.log:   18:00        | 0.400    | 0.299    
Sep 06 04:05:57 loop2 autotune.log:   19:00        |          | 0.297    
Sep 06 04:05:57 loop2 autotune.log:   20:00        |          | 0.297    
Sep 06 04:05:57 loop2 autotune.log:   21:00        |          | 0.297    
Sep 06 04:05:57 loop2 autotune.log:   22:00        | 0.350    | 0.297    
Sep 06 04:05:57 loop2 autotune.log:   23:00        |          | 0.277
Sep 06 04:05:54 loop2 autotune.log: Limiting adjusted ISF of 258.53 to 150.00 (which is pump ISF of 105 / 0.7 )
Scott Leibrand
@scottleibrand
Sep 06 2018 19:53
@MoyRivera I would start at OpenAPS.org, which has an overview and links to the documentation for getting started.
@Samuchco why do you think ISF is only 105? it sounds like autotune thinks you should raise it quite a bit, which would make the loop correct much less aggressively. if aggressive corrections are the cause of your roller coaster, that should help. it also looks like autotune wants to decrease basal quite a bit, FWIW...
MoyRivera
@MoyRivera
Sep 06 2018 20:18
Thx a lor @scottleibrand
Samuchco
@Samuchco
Sep 06 2018 20:54
@scottleibrand The autotune is already changing the 105 to 148 and it is roller-coasting. It looks like the ISF should be a lot higher (looking at Limiting adjusted ISF of 258). However I see also autosens adjusting the ISF down to 83 as well.
Sep 02 05:00:32 loop2 pump-loop.log: Autosens ratio: 1.19; Adjusting basal from 0.3 to 0.35; ISF from 100 to 84; CR: 13.822
Samuchco
@Samuchco
Sep 06 2018 21:05
Also, curious to know from where is autosens grabbing the ISF 100 if the pump is set to 105?
ElwinABC
@ElwinABC
Sep 06 2018 21:23
Is there any way to adjust the DIA from 5 to 6h? In the docs (link below) I have read that the DIA can be adjusted in preferences.json (edit-pref), but what command should I use to set the DIA from 5 to 6 hours?
Dana Lewis
@danamlewis
Sep 06 2018 21:46
@ElwinABC change it in your pump
Scott Leibrand
@scottleibrand
Sep 06 2018 22:00
@Samuchco do you have an ISF schedule in the pump? or just a single value?
Samuchco
@Samuchco
Sep 06 2018 22:37
schedule
@scottleibrand Sorry, to be more accurate, schedule but ALL at 105
Scott Leibrand
@scottleibrand
Sep 06 2018 22:52
k, then it may be using an old pumpprofile. you may want to update your pump profile to match what you think you need based on the previous autotune results, then rm ~/myopenaps/autotune/*.json, rm ~/myopenaps/settings/autotune.json, and rm ~/myopenaps/settings/*profile.json, and have it re-pull the profile and re-run autotune from those new pump settings