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

16th
Jul 2017
rsilvers129
@rsilvers129
Jul 16 2017 00:20 UTC
My desktop PC running the loop has a load average of 1.13. My Edison is more like 1.98. So 15 times faster. It is amazing how quickly it installs and updates. It is working to other rooms of the house. I could probably cover my house with 6-8 of them.
Dana Lewis
@danamlewis
Jul 16 2017 00:51 UTC
FYI all - just did a bunch of redirects on the old doc URLs, in case anyone had things bookmarked, should get you to the new pages. But let me know if anyone finds any I missed and I can add them.
rodzilla55
@rodzilla55
Jul 16 2017 00:57 UTC
upgraded to 0.5.1, all good. And docs are a nice improvement. THANKS @danamlewis @scottleibrand and ALL.
1 week in... improved my AVG BG by 10 points, and my STD Dev by 10.
Dana Lewis
@danamlewis
Jul 16 2017 00:58 UTC
:+1: @rodzilla55 thanks for the PRs, too - appreciate you chipping in.
:confetti_ball: :fire: :clap: :raised_hands: well done
Joey
@Cooljoe04_twitter
Jul 16 2017 01:06 UTC
Made some changes to my preferences.json, saved and issued a reboot. Unit came back up and is indicating the following on loop:
rm: cannot remove ‘enact/smb-enacted.json’: No such file or directory
ValueError: byte must be in range(0, 256)
grep: enact/smb-enacted.json: No such file or directory
ValueError: byte must be in range(0, 256)
cp: cannot stat ‘enact/smb-enacted.json’: No such file or directory
enact/smb-enacted.json: cat: enact/smb-enacted.json: No such file or directory
Unsuccessful supermicrobolus pump-loop at Sat Jul 15 21:02:01 EDT 2017
Dana Lewis
@danamlewis
Jul 16 2017 01:07 UTC
errant character in your preferences?
Joey
@Cooljoe04_twitter
Jul 16 2017 01:09 UTC
possibly. Was looking at the values, overlooked the fact I had the space after the value and before the comma, not before the value and comma.
Joey
@Cooljoe04_twitter
Jul 16 2017 01:19 UTC
No change. Attempted to raise my 3x safety a little to 3.5, thought it might be from my misplaced space, but correcting it did not correct the issue. Also thought the decimal might be causing the problem, so raised it to 4 and saved. No change/same error.
Dana Lewis
@danamlewis
Jul 16 2017 01:20 UTC
want to paste your preferences and we can eyeball it?
Joey
@Cooljoe04_twitter
Jul 16 2017 01:21 UTC
Sure, Just to verify, the preferences are re-read on every loop attempt, correct? Or do I need to reboot it after making changes to the file?
Dana Lewis
@danamlewis
Jul 16 2017 01:21 UTC
you don’t need to reboot
Joey
@Cooljoe04_twitter
Jul 16 2017 01:22 UTC
{
"max_iob": 30,
"max_daily_safety_multiplier": 4,
"current_basal_safety_multiplier": 5,
"autosens_max": 1.2,
"autosens_min": 0.7,
"rewind_resets_autosens": true,
"autosens_adjust_targets": true,
"adv_target_adjustments": true,
"maxCOB": 120,
"override_high_target_with_low": false,
"skip_neutral_temps": false,
"unsuspend_if_no_temp": false,
"bolussnooze_dia_divisor": 2,
"min_5m_carbimpact": 5,
"carbratio_adjustmentratio": 1,
"autotune_isf_adjustmentFraction": 0.5,
"remainingCarbsFraction": 0.7,
"remainingCarbsCap": 90,
"override_high_target_with_low": false,
"skip_neutral_temps": false,
"unsuspend_if_no_temp": false,
"bolussnooze_dia_divisor": 2,
"min_5m_carbimpact": 5,
"carbratio_adjustmentratio": 1,
"autotune_isf_adjustmentFraction": 0.5,
"remainingCarbsFraction": 0.7,
"remainingCarbsCap": 90,
"enableUAM": true,
"enableSMB_with_bolus": true,
"enableSMB_with_COB": true,
"enableSMB_with_temptarget": true
}
Prior to the change tonight, everything was working but it was not providing high enough temp basal to bring things back down on its own, which is why I started playing around with the 3x/4x logic
Dana Lewis
@danamlewis
Jul 16 2017 01:30 UTC
was that because you were running into those caps, or what were the logs saying?
also - feeling obliged to say YDMV, but that seems like an extremely high maxIOB and you may want to rethink that as a safety consideration.
cameronrenwick
@cameronrenwick
Jul 16 2017 01:31 UTC
@Cooljoe04_twitter is your max_iob actually 30? It starts as zero and generally is no more than 3x your highest basal. Dunno if that's correct or even important but...
Dana Lewis
@danamlewis
Jul 16 2017 01:31 UTC
also, was it giving the byte error when it was attempting to set a 6.3 or greater temp basal?
Joey
@Cooljoe04_twitter
Jul 16 2017 01:31 UTC
the math for the basal matched up to the 3x, which is why I believed it was coming from there
Dana Lewis
@danamlewis
Jul 16 2017 01:32 UTC
your regular basals reach 10u/hr?
Joey
@Cooljoe04_twitter
Jul 16 2017 01:32 UTC
yes to the byte error. 5.95 was the previous max and is maintaining my 300 sugar lol
Under normal conditions they are not 10u/hr, but last night for instance it spiked after I went to sleep and was over 300 for several hours becasue it was maxing at 5.95/hr and was not bringing it back down. By the time I woke up this morning it had finally gottenit back down to 120s.
Dana Lewis
@danamlewis
Jul 16 2017 01:36 UTC
the 3x rule of thumb for maxIOB isn’t “3 times the highest OpenAPS ever has tried to set” but 3x your normal basal amounts
maxIOB is an absolute number that helps limit how much insulin you’d ever want OpenAPS to give you.
Joey
@Cooljoe04_twitter
Jul 16 2017 01:37 UTC
Normal basals are around 1.6/hr
Dana Lewis
@danamlewis
Jul 16 2017 01:41 UTC
ah, so the error is probably from it trying to set a >6.3u/hr temp (related to the decocare fix we were discussing earlier). Should resolve once it’s no longer trying to set that. You can try to set a manual temp and watch it cancel that, and should resolve.
Joey
@Cooljoe04_twitter
Jul 16 2017 01:44 UTC
Figures, the one time i didnt scroll up and read everything from my last comments would be when something i need is being discussed. lol So in short, I set a temp (high? low?), it will cancel, and then it wont have any issues with >6.3/hr, or will that still be an issue for a future update?
Dana Lewis
@danamlewis
Jul 16 2017 01:48 UTC
no, you’d need to install the dev branch of decocare, but honestly - it may be setting such a high temp because maxiOB is 30. I’d set that to something more reasonable (say, 5u), and it is likely going to be capped by that or something else and not need the decocare fix.
Joey
@Cooljoe04_twitter
Jul 16 2017 01:59 UTC
changed maxiob to 5, set a temp high, smb loop completed, cancelled temp., loop set a 4.65 basal and .5 bolus. So was my maxiob being that high causing it to want to fix highs with high basals then, vs SMB?
Joey
@Cooljoe04_twitter
Jul 16 2017 02:14 UTC
Looks like it also issued a 6.33u/hr basal shortly afterwards, but that will still take an awfully long time to bring down the current 300 sugar. I know I can issue a bolus to get it down sooner, but I am trying to replicate last night's events and see what can be done to correct it without intervention as spikes like that are semi-common for me.
Scott Leibrand
@scottleibrand
Jul 16 2017 02:18 UTC
@fjungman yeah, the fix is in decocare/master, but that never got released to pypi, so installing with pip gets an older release. so even just installing the latest master with easy_install or setup.py should be fine.
@CaptainBalou happy to help you upgrade decocare if you want to. or you can wait until others have tested it enough to merge it to dev (or you get yourself a second dev rig). your call.
@Cooljoe04_twitter you either need to do what @fjungman is doing to get the updated decocare that can handle basals > 6.375U/h, or you need to set your max basal <= 6.3 U/hr on your pump to prevent it from getting stuck if it thinks you need something higher than that
Joey
@Cooljoe04_twitter
Jul 16 2017 02:25 UTC
max basal on pump is set to 10/hr, so i presume that means that decocare update is the only option currenty?
(or babysit it and handle spikes manually until decocare is rolled into next update)
Scott Leibrand
@scottleibrand
Jul 16 2017 02:26 UTC
or turn on SMB and let it do the extra insulin that way
Dana Lewis
@danamlewis
Jul 16 2017 02:27 UTC
*assuming you’ve been looping for a while and are comfortable with the basic functions and understanding of why OpenAPS does things
Joey
@Cooljoe04_twitter
Jul 16 2017 02:27 UTC
SMB is on, but isnt issuing much
Scott Leibrand
@scottleibrand
Jul 16 2017 02:27 UTC
have you reviewed your autotune output?
Joey
@Cooljoe04_twitter
Jul 16 2017 02:29 UTC
just watched the loop log
fjungman
@fjungman
Jul 16 2017 02:39 UTC
Thanks for the confirmation, @scottleibrand !
Scott Leibrand
@scottleibrand
Jul 16 2017 02:44 UTC
You should review your autotune recommendations to see whether it thinks your basals, ISF, or CR need adjusting.
Katie Aldridge
@kcrcgm
Jul 16 2017 02:55 UTC
Hi everyone. I'm logged in to my rig. How can I look at the xdrip data? Is the file name xdrip/glucose.json? How do I see what's in there? I want to see what it's doing, bc I don't actually have BT tethering on my phone and this means the rig hasn't been able to get my glucose data directly from xdrip. Instead it pulls my glucose data from NS, which is fine with me. But I have always gotten this error "Could not parse input data..." and wondered if this xdrip issue is the source of that error. Would looking in the file help me see that? How do I look? Sorry I'm a complete newbie at all this. Thank you for your patience.
Joey
@Cooljoe04_twitter
Jul 16 2017 03:13 UTC
Looking into autotune docs to see what it says.
Katie Aldridge
@kcrcgm
Jul 16 2017 03:34 UTC
@scottleibrand Hello and thank you for saying "well done". This stuff is foreign to me and I appreciate the encouragement! What are my next steps?
Scott Leibrand
@scottleibrand
Jul 16 2017 03:34 UTC
@kcrcgm ok, so you have narrowed down which report is giving you the error, and managed to reproduce it.
Katie Aldridge
@kcrcgm
Jul 16 2017 03:34 UTC
@scottleibrand Yes!
Scott Leibrand
@scottleibrand
Jul 16 2017 03:34 UTC
so let's see what exactly that report is configured to do
openaps report show settings/autosens.json --cli should show that
it should report back something like openaps use detect-sensitivity shell monitor/glucose.json settings/pumphistory-24h-zoned.json settings/insulin_sensitivities.json settings/basal_profile.json settings/profile.json - run whatever it reports, and let's confirm that also reproduces the problem
it might also give you some other output - if so, please paste that here
and, if it's running successfully, it'll take several minutes to finish, printing one character every couple seconds. if it's doing that, just let it run.
Joey
@Cooljoe04_twitter
Jul 16 2017 03:39 UTC
I am running an autotune report for the last week. Its about done. It occurred to me that I didnt have the edison rig for this entire time, meaning there will be gaps in the NS data for the times that i was using my Pi rig. Will the autotune report only factor in the times that it had openaps and NS data, or will it factor the NS data without the openaps data into its calculations?
Scott Leibrand
@scottleibrand
Jul 16 2017 03:40 UTC
@Cooljoe04_twitter it will take whatever data you've got. if you have times where there's only CGM data and no insulin dosing data, it won't be able to make any ISF suggestions. If there's no carb data, it won't be able to make any CR suggestions. it might still be able to make some useful suggestions about basals, though.
but if you see anything that doesn't quite jive with what you think it should be doing, feel free to re-run it just for the days where you have higher-quality data
@kcrcgm mine just now finished, and looks like this:
# openaps use detect-sensitivity shell monitor/glucose.json settings/pumphistory-24h-zoned.json settings/insulin_sensitivities.json settings/basal_profile.json settings/profile.json
Interpolated [ date: 1500140023000, glucose: 90 ]
Interpolated [ date: 1500138824000, glucose: 95 ]
----+----------------------->>>>>>>>>>>+++>>>>>>>>>>>>>>>>+->>++++++++-+>>>>>+++------+----+-----------+----+---+------++--------+-+--+++++---------------+++------+-+-+-++--+++-+++++++++-++++++-++++++++++++++++++++---+-+++-++++++++++++++--++++-+++-++++>>++++-->>>>>+++-++-+>>>>++++-- 48% of non-meal deviations <= 0 (target 45%-50%)
Sensitivity normal.
{
  "ratio": 1
}
Joey
@Cooljoe04_twitter
Jul 16 2017 03:43 UTC
ok. it should only be a couple days of being spotty openaps data. NS data should be complete for the whole time. The remainder of the week should be nearly complete openaps data. Just wanted to make sure the empty data fields wouldn't be causing the data results (and resulting recommendations) to be incorrectly adjusted one way or another.
Katie Aldridge
@kcrcgm
Jul 16 2017 03:43 UTC
@scottleibrand AH, I was trying to run each of those things separately (see screenshot). Now I'll do it the way you did.
Drilling down autosens 2.JPG
Scott Leibrand
@scottleibrand
Jul 16 2017 03:46 UTC
@Cooljoe04_twitter normally those won't be a problem, but if you see anything odd, feel free to dig into it, or simply exclude that timeframe.
Joey
@Cooljoe04_twitter
Jul 16 2017 03:47 UTC
I ran it for yesterday prior to running it for the whole week. There was some ISF and carb ratio recommendations for just the 1 day. The basals were all within .2, but I figured a week would provide a better pool to consider
Katie Aldridge
@kcrcgm
Jul 16 2017 03:47 UTC
@scottleibrand Here's mine
Drilling down autosens 3.JPG
Scott Leibrand
@scottleibrand
Jul 16 2017 03:47 UTC
@Cooljoe04_twitter it makes fairly small changes based on each day's data, but if you run it on multiple days, they all add up, and if they're all suggesting changes in the same direction, will hit the 20-30% caps after a week or so.
@kcrcgm ok, so nothing new there, but we're still reproducing it. so next step is to start looking at the contents of those files.
Katie Aldridge
@kcrcgm
Jul 16 2017 03:49 UTC
@scottleibrand openaps report invoke <whatever>?
Scott Leibrand
@scottleibrand
Jul 16 2017 03:49 UTC
no, invoke re-generates the files
we want to look at their contents. one sec, let me do it myself first
first, let's do something similar to what I had you do earlier: cat monitor/glucose.json | jq .[0] and then cat monitor/glucose.json | jq .[length-1]
that will show you the first and last record of the monitor/glucose.json file, pretty-printed in color. :)
also, run this to see how many glucose records total are in that file: cat monitor/glucose.json | jq length
Katie Aldridge
@kcrcgm
Jul 16 2017 03:56 UTC
@scottleibrand They both say "null" ... in GRAY :( And the glucose records total is zero.
Drilling down autosens 4.JPG
Scott Leibrand
@scottleibrand
Jul 16 2017 03:56 UTC
huh, that is odd. if you just do cat monitor/glucose.json does it show the file as completely empty?
Joey
@Cooljoe04_twitter
Jul 16 2017 03:56 UTC
(Also occurred to me that I was doing a karate camp this week, well outside of my normal activity level, so my "normal" basals and how they reacted may be totally off from what happens next week when I am back to work. I can always run this again next week though!)
Scott Leibrand
@scottleibrand
Jul 16 2017 03:57 UTC
@Cooljoe04_twitter yeah, that's why it's best to make small changes gradually over time. if you enable autotune in your loop, it will do that automatically, and you just need to review the autotune recommendations file periodically to see if your underlying pump settings need adjusting
Katie Aldridge
@kcrcgm
Jul 16 2017 03:58 UTC
@scottleibrand Yeah, it's empty. I have a feeling this is related to my xdrip problem. I use xdrip, which uploads to NS, but my phone won't BT tether to my rig. Tmobile has BT tethering turned off for this phone. So my rig has been looping using the glucose data from NS I guess. Would that explain it?
Scott Leibrand
@scottleibrand
Jul 16 2017 03:59 UTC
does pump-loop.log show that it's looping successfully with up-to-date glucose data?
Katie Aldridge
@kcrcgm
Jul 16 2017 03:59 UTC
@scottleibrand Yes, and I've been looping successfully for 3 weeks now
Scott Leibrand
@scottleibrand
Jul 16 2017 04:00 UTC
k. let's run this to see what your aliases look like that deal with that monitor/glucose.json file: openaps alias show | grep monitor/glucose.json
grep is just the unix tool for searching through output and displaying the lines that match
(TMI, but: it just occurred to me to look up why it's called that. apparently "Its name comes from the ed command g/re/p (globally search a regular expression and print), which has the same effect: doing a global search with the regular expression and printing all matching lines. ")
Joey
@Cooljoe04_twitter
Jul 16 2017 04:01 UTC
autotune should be enabled (will confirm once its done running), but I hadn't reviewed its reports yet. Wasn't expecting it to be involved with my spiking issue since it doesnt have a pattern to it.
Scott Leibrand
@scottleibrand
Jul 16 2017 04:02 UTC
@Cooljoe04_twitter if you just have random spikes with no pattern, it probably won't fix that. but if your basals are too low, or your ISF is too high, that might contribute to not coming down as fast as you'd like
Katie Aldridge
@kcrcgm
Jul 16 2017 04:02 UTC
@scottleibrand That's not TMI, that's stuff I need to know. :) I actually googled it earlier today when you told me to use that in the command. So I knew that! Haha
Scott Leibrand
@scottleibrand
Jul 16 2017 04:03 UTC
hehe, you knew more about it than I did then. :)
Joey
@Cooljoe04_twitter
Jul 16 2017 04:03 UTC
I didn't know the grep history, so now I do. lol
Katie Aldridge
@kcrcgm
Jul 16 2017 04:03 UTC
Drilling Down autosens 5.JPG
@scottleibrand Not sure if this will affect anything we're doing, but I've got a new sensor in that I haven't calibrated yet.
Scott Leibrand
@scottleibrand
Jul 16 2017 04:05 UTC
is your rig looping right this moment, or complaining about old data?
Katie Aldridge
@kcrcgm
Jul 16 2017 04:08 UTC
It's looping
Scott Leibrand
@scottleibrand
Jul 16 2017 04:08 UTC
ok, let's look at those other glucose.json files then
Katie Aldridge
@kcrcgm
Jul 16 2017 04:09 UTC
ok
Scott Leibrand
@scottleibrand
Jul 16 2017 04:09 UTC
just replace monitor/glucose.json with each of the other filenames from your grep output, in all three of those jq commands
so for example cat cgm/glucose.json | jq '.[0]'
Katie Aldridge
@kcrcgm
Jul 16 2017 04:12 UTC
And cgm/ns-glucose.json?
Joey
@Cooljoe04_twitter
Jul 16 2017 04:12 UTC
ISF | 13.000 | 18.014
CSF | n/a | 2.390
Carb Ratio | 5.000 | 7.537
Scott Leibrand
@scottleibrand
Jul 16 2017 04:13 UTC
yep. and cgm/cgm-glucose.json
@Cooljoe04_twitter does it seem like your ISF is too strong (low) or too weak (high)? do you feel like OpenAPS is "giving up too early" and not getting enough IOB for highs? Or is it overcorrecting and sending you low?
Katie Aldridge
@kcrcgm
Jul 16 2017 04:15 UTC
Drilling Down autosens 6.JPG
Scott Leibrand
@scottleibrand
Jul 16 2017 04:16 UTC
k. also do the length-1 and length ones too
Katie Aldridge
@kcrcgm
Jul 16 2017 04:17 UTC
Not sure what those are
Scott Leibrand
@scottleibrand
Jul 16 2017 04:19 UTC
I mean the cat monitor/glucose.json | jq .[length-1] and cat monitor/glucose.json | jq length ones on the other files.
that will also show us the newest CGM reading in each file, and how many records they each have
Joey
@Cooljoe04_twitter
Jul 16 2017 04:20 UTC
My issues have all been with highs not coming back down quickly enough. "Giving up too early" as you phrased it where its stopping the rate rise, but not actually bringing it back down after the rise. Essentially, it maintains the high with a very gradual decline usually. Generally, I am good on meals. Give a bolus, it tweaks with SMBs as necessary.
Scott Leibrand
@scottleibrand
Jul 16 2017 04:20 UTC
@Cooljoe04_twitter ok, I wouldn't make that recommended ISF change, then: it would be moving in the opposite direction of what you say you need
it'll be interesting to see if further autotune runs keep moving in that direction, or if they start to recommending lower ISF
it could be that these highs are caused by higher than normal resistance (lower than normal ISF) but that it doesn't last long enough to drown out the higher ISF calculated at other times during the day
do you have "adv_target_adjustments": true in preferences.json?
Joey
@Cooljoe04_twitter
Jul 16 2017 04:23 UTC
I'm going to save the results of this report, will run another one next week when I'm back to "normal" activies and compare the two.
yes, adv target adj is true
Scott Leibrand
@scottleibrand
Jul 16 2017 04:25 UTC
it might also be worth looking at your pump-loop.log from one of the times you were running persistently high to see if there are any other clues. maybe towards the tail end of the persistent high, autosens might start detecting some resistance...
Katie Aldridge
@kcrcgm
Jul 16 2017 04:25 UTC
Drilling Down autosens 7.JPG
Did I do that right?
Scott Leibrand
@scottleibrand
Jul 16 2017 04:27 UTC
yep, that's good, thanks. what time is it there? just after midnight EDT on the 16th?
Joey
@Cooljoe04_twitter
Jul 16 2017 04:28 UTC
:+1: 12:28am 7/16/17 lol
Scott Leibrand
@scottleibrand
Jul 16 2017 04:28 UTC
so your most recent data in any of those files is from 1pm
not sure how you could possibly be looping right now if that's what determine-basal is getting...
Katie Aldridge
@kcrcgm
Jul 16 2017 04:29 UTC
I'm Central so 11:29pm 7/15
Scott Leibrand
@scottleibrand
Jul 16 2017 04:29 UTC
ok, I misread -0500, sorry
same story either way though
Katie Aldridge
@kcrcgm
Jul 16 2017 04:29 UTC
It's not sending it to my pump the log shows it "thinking"
That hasn't ever happened before. I figured it was because we were messing with it
Scott Leibrand
@scottleibrand
Jul 16 2017 04:30 UTC
can you paste the last run or two from your pump-loop.log?
Katie Aldridge
@kcrcgm
Jul 16 2017 04:31 UTC
Drilling down autosens 8.JPG
Scott Leibrand
@scottleibrand
Jul 16 2017 04:33 UTC
and BG is currently 170 on your receiver?
Katie Aldridge
@kcrcgm
Jul 16 2017 04:33 UTC
I haven't calibrated it yet. I'll do that now
Scott Leibrand
@scottleibrand
Jul 16 2017 04:34 UTC
hmm, wait. you've been looping all this time on stale data?
that's not supposed to be allowed
Katie Aldridge
@kcrcgm
Jul 16 2017 04:34 UTC
No I hadmy rig turned off until I sat down to work on this at aboutu 9:30 pm
It started running but I wasn't getting any temp basals so I didn't worry about it
NS shows no bg data since this afternoon at around 1 or 2
I mean my my NS site
Scott Leibrand
@scottleibrand
Jul 16 2017 04:36 UTC
oh, I see: the suggested.json is old
ok, then yeah, all the problems we've been troubleshooting are just from not having your CGM running
let's get that CGM calibrated and start that part over
Katie Aldridge
@kcrcgm
Jul 16 2017 04:36 UTC
K, got it calibrated
Which part do I start at?
Scott Leibrand
@scottleibrand
Jul 16 2017 04:37 UTC
let's wait for pump-loop.log to get the new CGM reading and do something with it
and then start with running autosens again
Katie Aldridge
@kcrcgm
Jul 16 2017 04:41 UTC
Alrighty, it's working. Start with this? openaps report show settings/autosens.json --cli
Joey
@Cooljoe04_twitter
Jul 16 2017 04:41 UTC
I will see if I can jump in the logs the next time it gets high and stops responding. Unfortunately, it seems to be night time when I am sleeping mostly, but not always. We will see if the changes I made earlier with dana with my maxiob/etc might help with that a little. Thanks again for the help scott (and dana if you are still on too!).
Dana Lewis
@danamlewis
Jul 16 2017 04:42 UTC
:+1:
Scott Leibrand
@scottleibrand
Jul 16 2017 04:42 UTC
@Cooljoe04_twitter you can see all the historical pump-loop.logs too
the best tool for that is less
so less -R /var/log/openaps/pump-loop.log
@kcrcgm that command will tell you what to run next, yeah
Joey
@Cooljoe04_twitter
Jul 16 2017 04:44 UTC
can I filter by date?
was about 24.5 hours ago lol
Scott Leibrand
@scottleibrand
Jul 16 2017 04:45 UTC
you can search with the / key
Katie Aldridge
@kcrcgm
Jul 16 2017 04:45 UTC
@scottleibrand Got some different results this time, with colors :)
Drilling down autosens 9.JPG
Scott Leibrand
@scottleibrand
Jul 16 2017 04:46 UTC
@Cooljoe04_twitter and then use n to see the next result, or N to see the previous
Katie Aldridge
@kcrcgm
Jul 16 2017 04:46 UTC
@scottleibrand Keep going through the other files?
Scott Leibrand
@scottleibrand
Jul 16 2017 04:46 UTC
you have a typo on the .length one
oh nevermind, you fixed it
Katie Aldridge
@kcrcgm
Jul 16 2017 04:47 UTC
:)
Scott Leibrand
@scottleibrand
Jul 16 2017 04:47 UTC
I think I see a problem though: one moment you were able to see data in monitor/glucose.json, and the next moment its length was 0
which probably means xDrip is overwriting it with an empty file, and then get-ns-bg is writing it out again, and then it's getting overwritten again...
Katie Aldridge
@kcrcgm
Jul 16 2017 04:49 UTC
That makes sense
Scott Leibrand
@scottleibrand
Jul 16 2017 04:49 UTC
it's not supposed to happen that way, though: it means there's a bug in the xdrip logic
Katie Aldridge
@kcrcgm
Jul 16 2017 04:50 UTC
Ah. Would it fix it if I rerun the setup script and select a different cgm source? (I guess it would have to be G5 cause that's what I have)
Scott Leibrand
@scottleibrand
Jul 16 2017 04:52 UTC
depends, do you want to use xdrip?
Katie Aldridge
@kcrcgm
Jul 16 2017 04:52 UTC
Yeah I like the app, but I will give it up if necessary.
Scott Leibrand
@scottleibrand
Jul 16 2017 04:53 UTC
well, you can still use it to upload to NS regardless
question is whether you want to use it for offline
Katie Aldridge
@kcrcgm
Jul 16 2017 04:54 UTC
Yes. I'd love to use it offline, and I'm working on finding a phone that can BT tether so that I could try to set that up.
Scott Leibrand
@scottleibrand
Jul 16 2017 04:55 UTC
ok, then let's see if we can fix the bug
Katie Aldridge
@kcrcgm
Jul 16 2017 04:56 UTC
I'd be happy to test whatever to try to fix it! :) But I need to call it a night tonight! I have little ones that will be up way too early in the morning... ;)
Scott Leibrand
@scottleibrand
Jul 16 2017 04:57 UTC
ok, ping me tomorrow when you have some time and I might have some more troubleshooting for you to do
Katie Aldridge
@kcrcgm
Jul 16 2017 04:57 UTC
Will do. Thank you for your time tonight.
Scott Leibrand
@scottleibrand
Jul 16 2017 04:57 UTC
thx for your debugging help
Katie Aldridge
@kcrcgm
Jul 16 2017 04:58 UTC
Glad to help! :)
Joey
@Cooljoe04_twitter
Jul 16 2017 05:00 UTC
Checking pump clock: "2017-07-15T04:23:42-04:00" is within 1m of current time: S
at Jul 15 04:23:49 EDT 2017
and that pumphistory is less than 1m old. Temp refreshed
Autotune exists! Hoorah! You can use microbolus-related features.
{"carbs":0,"boluses":2.4,"mealCOB":0,"currentDeviation":17.47,"maxDeviation":16.
16,"minDeviationSlope":0}
{"iob":4.501,"activity":0.0518,"bolussnooze":0,"basaliob":4.501,"netbasalinsulin
":7.65,"hightempinsulin":7.65,"microBolusInsulin":0,"microBolusIOB":0,"time":"20
17-07-15T08:23:47.000Z","lastBolusTime":0}
{"delta":6,"glucose":374,"short_avgdelta":8.5,"long_avgdelta":4.75}
{"duration":11,"rate":4.525,"temp":"absolute"}
Autosens adjusting basal from 1.15 to 1.1; target_bg from 127.5 to 129; sens fro
m 18.6 to 19 (autosens ratio 0.98)
Adjusting targets for high BG: min_bg from 91 to 80; target_bg from 129 to 80; max_bg from 167 to 98
Carb Impact: 10.9 mg/dL per 5m; CI Duration: 0 hours; remaining 4h+ CI: 0 mg/dL per 5m
Accel. Carb Impact: 10 mg/dL per 5m; ACI Duration: 0 hours
UAM Impact: 9.7 mg/dL per 5m; UAM Duration: 3 hours
minPredBG: 344 minIOBPredBG: 344 avgPredBG: 344 COB: 0 carbs: 0
BG projected to remain above 80 for 240 minutes
bgUndershoot: -274 zeroTempDuration: 240 zeroTempEffect: 86 carbsReq: -135
jmcrawford
@jmcrawford
Jul 16 2017 05:00 UTC
@scottleibrand we're still seeing IOB decay completely over DIA/2. Logs show iob dropping normally each loop iteration until DIA/2, then 0. Is this new behaviour, or is my understanding of DIA way off?
Scott Leibrand
@scottleibrand
Jul 16 2017 05:01 UTC
@Cooljoe04_twitter can you get the next few lines as well, down to the reason field?
Joey
@Cooljoe04_twitter
Jul 16 2017 05:01 UTC
Checking deliverAt: 2017-07-15T08:24:01.457Z is within 1m of current time: Sat Jul 15 04:24:04 EDT 2017
and that smb-suggested.json is less than 1m old
enact/smb-suggested.json: {"insulinReq":13.89,"bg":374,"reservoir":"91.0","temp":"absolute","snoozeBG":354,"predBGs":{"IOB":[374,379,383,386,388,390,390,390,388,386,384,380,376,373,369,366,363,360,357,355,353,352,350,349,348,347,346,345,345,344]},"minPredBG":344,"IOB":4.501,"reason":"COB: 0, Dev: 66, BGI: -4.92, ISF: 19, Target: 80, minPredBG 344, IOBpredBG 344; Eventual BG 354 >= 98, adj. req. rate: 28.9 to maxSafeBasal: 4.532, temp 4.525 >~ req 4.55U/hr. ","COB":0,"eventualBG":354,"tick":"+6","deliverAt":"2017-07-15T08:24:01.457Z"}
No smb_enact needed. Temp refreshed: monitor/temp_basal.json: {"duration":10,"rate":4.525,"temp":"absolute"}
No bolus needed (yet). Settings less than 10m old
Edison on battery: 69%. Pumphistory-24 < 90m old
Completed supermicrobolus pump-loop at Sat Jul 15 04:24:11 EDT 2017:
It started rising around 1am, peaked about 4am
Scott Leibrand
@scottleibrand
Jul 16 2017 05:03 UTC
@Cooljoe04_twitter one thing I would definitely change: your max_bg is way too high, at ~160. that means openaps won't even try to bring you down if your eventualBG is less than 160. I would set them much close together, to something like 100 and 110, or even identical (both 100 or so)
in this case the adv_target_adjustment is helping out there, but I'm sure it could be doing a lot more high-temping when you first start rising, but isn't because of the high max_bg
@jmcrawford is your DIA 4 hours?
jmcrawford
@jmcrawford
Jul 16 2017 05:05 UTC
yes
Joey
@Cooljoe04_twitter
Jul 16 2017 05:05 UTC
This message was deleted
Scott Leibrand
@scottleibrand
Jul 16 2017 05:06 UTC
@jmcrawford in that case, it's apparently not properly merging pumphistory.json (which is now only 2h long) with pumphistory-24h. json
want to look at the first and last treatment entry in each of those files, and the monitor/pumphistory-merged.json, and see what's up there?
the 24h one is in settings/
Joey
@Cooljoe04_twitter
Jul 16 2017 05:15 UTC
the max_bg is changed in the /settings/profile.json file for autotune?
Scott Leibrand
@scottleibrand
Jul 16 2017 05:15 UTC
no, that's in your pump
in the bolus wizard settings
jmcrawford
@jmcrawford
Jul 16 2017 05:18 UTC
@scottleibrand oldest records in pumphistory-merged and pumphistory-24h match, pumphistory.json is 2 hours newer
Joey
@Cooljoe04_twitter
Jul 16 2017 05:18 UTC
Changed. I never use bolus wizard, would have never crossed my mind that it pulls that data lol
Scott Leibrand
@scottleibrand
Jul 16 2017 05:19 UTC
@jmcrawford are you running oref0 0.5.1?
do the newest records in pumphistory-merged and pumphistory.json also match?
jmcrawford
@jmcrawford
Jul 16 2017 05:20 UTC
close, -merged is 17min older
Scott Leibrand
@scottleibrand
Jul 16 2017 05:21 UTC
ok, they should be the same, but that wouldn't account for your symptoms
when did you last update oref0?
jmcrawford
@jmcrawford
Jul 16 2017 05:22 UTC
last night - but something is really wrong, it's reporting v0.4.3
I'll wipe out ~/src and start over
Scott Leibrand
@scottleibrand
Jul 16 2017 05:23 UTC
that may have been something I did. if so, it should be cosmetic. but just to be sure, want to try pulling and installing again and see what you get?
jmcrawford
@jmcrawford
Jul 16 2017 05:26 UTC
k
Joey
@Cooljoe04_twitter
Jul 16 2017 05:26 UTC
So changed my targets in the bolus wizard. Now loop is trying to set a 7.92u/hr temp basal and failing again, so it looks like I am still going to need to update the other stuff too for it to work with higher basals
Dana Lewis
@danamlewis
Jul 16 2017 05:27 UTC
@cooljoe04_twitter you should PR into the docs where you think you would have needed to find out about it pulling targets (and basals, ISF, dia, and carb ratio) from the pump if it wasn't obvious to you.
If you're that high, you may want to think about a manual correction/what you would do in a non-looping situation, but taking into account your netiob
Scott Leibrand
@scottleibrand
Jul 16 2017 05:28 UTC
@Cooljoe04_twitter until you get decocare updated, change your pump's max basal to 6.3U/h
that way it can at least high temp you that much, and will be able to SMB if those are enabled at the time
Joey
@Cooljoe04_twitter
Jul 16 2017 05:29 UTC
:+ Updated.
Scott Leibrand
@scottleibrand
Jul 16 2017 05:29 UTC
realistically, once you get everything else fixed and it can high-temp earlier, you may not need >6.3U/h temps very often
jmcrawford
@jmcrawford
Jul 16 2017 05:30 UTC
Ok, it's reporting as 0.5.1 now. Will need to wait till breakfast bolus to see what happens.
Thanks for looking at this, will let you know.
Joey
@Cooljoe04_twitter
Jul 16 2017 05:31 UTC
I will probably hold off on updating decocare since I know nothing about it and see nothing about it in the docs to help me muddle my way through without 100% hand holding. lol
Scott Leibrand
@scottleibrand
Jul 16 2017 05:34 UTC
k. we may also end up making some changes to make that happen automatically too. no guarantees though. :)
Joey
@Cooljoe04_twitter
Jul 16 2017 05:35 UTC
No worries. Appreciate all you guy's help so far! Going to get some sleep for tonight and see how the tweaks work over the next couple days. Thanks again.
Scott Leibrand
@scottleibrand
Jul 16 2017 05:40 UTC
:+1:
Martin Haeberli
@mhaeberli
Jul 16 2017 05:42 UTC
@scottleibrand sorry to bug you, but what is the incantation like killall -g openaps for dev ? (RTD doesn’t seem to say per google)
Scott Leibrand
@scottleibrand
Jul 16 2017 05:42 UTC
killall -g oref0-pump-loop
Martin Haeberli
@mhaeberli
Jul 16 2017 05:43 UTC
k thx
Scott Leibrand
@scottleibrand
Jul 16 2017 05:43 UTC
RTD has its own search function too
if that doesn't show it, a PR may be in order
(to change most/all instances of killall -g openaps to killall -g oref0-pump-loop)
Martin Haeberli
@mhaeberli
Jul 16 2017 05:43 UTC
rtd seems to reflect kind of now
but via google didn’t find it
Scott Leibrand
@scottleibrand
Jul 16 2017 05:44 UTC
Google doesn't re-index everything instantly
I highly recommend RTD search
Martin Haeberli
@mhaeberli
Jul 16 2017 05:44 UTC
current RTD (maybe overkill) says killall -g openaps; killall -g oref0-pump-loop
:+1:
Scott Leibrand
@scottleibrand
Jul 16 2017 05:44 UTC
ok, that works
we can remove the old one once most everyone has updated
Martin Haeberli
@mhaeberli
Jul 16 2017 05:48 UTC
so - mmtune succeeded, but openaps use pump model failed
like , returned empty string
reports 723 2.4A on the pump screen
Scott Leibrand
@scottleibrand
Jul 16 2017 05:51 UTC
transient?
Martin Haeberli
@mhaeberli
Jul 16 2017 05:52 UTC
looks transient i hope; just changed to new - to - us pump - enact succeded while (probably just before) I tried mmtune
mmtune happy
looping looks happy again
Scott Leibrand
@scottleibrand
Jul 16 2017 05:58 UTC
@kcrcgm or anyone else with an xdrip setup: I thought I had found the problem, but now I'm not so sure. could you watch your xdrip/glucose.json for a bit using tail -f xdrip/glucose.json and see if it changes at all? then, can you do the same with tail -f monitor/glucose.json and see if it says the file is getting truncated?
Matthias
@ceben80
Jul 16 2017 06:04 UTC
the xdrip/glucose.json needs head to be watched, new BGs are written to the top (don't know if it's the same with monitor/glucose.json)
Scott Leibrand
@scottleibrand
Jul 16 2017 06:05 UTC
well, in her case it's zero bytes. and head doesn't have an -f flag. any change to add stuff to the top of a file is a rewrite operation, not an append
Matthias
@ceben80
Jul 16 2017 06:14 UTC
K understood
Michael Spradling
@M1Sports20
Jul 16 2017 06:21 UTC
It looks like my cgm data is off by exactly 12 hours. However, it looks right in nightscout(excet for openaps pill) and xdrip. I am using G5 with xdrip+ to upload data to nightscout. Anyone seen anything simliar?
Scott Leibrand
@scottleibrand
Jul 16 2017 06:22 UTC
what timezone is your rig set to? does that match the CGM time?
Michael Spradling
@M1Sports20
Jul 16 2017 06:23 UTC
eastern
US/Easter
n
The rig time looks fine from the console. Only the bg looks wrong in ns. However, openaps seems to be working still
doing what I expect
And yes it matches the CGM timezone
Scott Leibrand
@scottleibrand
Jul 16 2017 06:25 UTC
how exactly are you seeing it off by 12h?
Michael Spradling
@M1Sports20
Jul 16 2017 06:31 UTC
Sent private message of my nightscout instance
Matthias
@ceben80
Jul 16 2017 06:42 UTC
@SebastienLussier decocare PR #29 is working, Scott created a seperate branch (thx for that Scott!), the BolusExpert entered BG is correctly shown in NS treatment now :star2:
Scott Leibrand
@scottleibrand
Jul 16 2017 06:42 UTC
@M1Sports20 I still need to know what you're seeing, because I'm not seeing anything amiss.
@M1Sports20 can you run the commands I pasted above for "anyone else with an xdrip setup"?
you'll just need to log into your rig and cd ~/myopenaps first
Michael Spradling
@M1Sports20
Jul 16 2017 06:46 UTC
"sgv": 158,
"device": "xDrip-DexcomG5",
"filtered": 156388.64730500002,
"date": 1500006502648,
"unfiltered": 179122.514455,
"rssi": 100,
"type": "sgv",
"glucose": 158
}
]
tail -f monitor/glucose.json ~/myopenaps {130}
"device": "xDrip-DexcomG5",
"unfiltered": 226980.51649473686,
"delta": 13.201,
"date": 1499922506586,
"rssi": 100,
"_id": "5967004b4fa40156661dd5ce",
"type": "sgv",
"glucose": 171
}
]
Scott Leibrand
@scottleibrand
Jul 16 2017 06:47 UTC
you'll need to let it run for a bit to see if the file gets truncated over the course of a few minutes
Michael Spradling
@M1Sports20
Jul 16 2017 06:49 UTC
alright, I will tomorrow, I really need to goto bed at the moment.
thanks
Scott Leibrand
@scottleibrand
Jul 16 2017 06:50 UTC
later
Matthias
@ceben80
Jul 16 2017 07:21 UTC
@/all anybody can point me to a 3d printed case for a TI stick? I have seen this here several month ago - thanks!
LilDucky
@LilDucky
Jul 16 2017 07:41 UTC
Pretty basic question - I am trying to get started on setting up a loop on an ancient raspberry Pi. The load averages are around 4 and mmtune does not run. Can I assume that this is due to lack of grunt?
Saskia
@Missdazzle
Jul 16 2017 08:39 UTC

@SebastienLussier @scottleibrand Tried to test issue-fix openaps/decocare#29 Obviously making a mistake. Need help.
cd ~/src/decocare
sudo python setup.py develop
lets run a process which says at the end:

Finished processing dependencies for decocare==0.0.32-dev

But a
git checkout SebastienLussier-fixes
gives me a "did not match any file(s) known to git"
Which step am I missing?

fidoman
@efidoman
Jul 16 2017 11:09 UTC
@scottleibrand - what is RTD search? can you provide a link?
Saskia
@Missdazzle
Jul 16 2017 11:28 UTC
@SebastienLussier @scottleibrand Never mind, I already got help.
Phil
@drnoname82_twitter
Jul 16 2017 11:39 UTC
@ericfeibelman The search function on the readthedocs pages
fidoman
@efidoman
Jul 16 2017 12:00 UTC
@drnoname82_twitter - thanks! so obvious and I couldn't figure it out.
cameronrenwick
@cameronrenwick
Jul 16 2017 12:17 UTC
@scottleibrand just a little feedback, I've been watching my tail -f xdrip/glucose.json log for a bit and things are running fine. After that I tailed tail -f monitor/glucose.json and it too looks intact - no truncation. Dunno if that helps you out but, fwiw, my 2 cents
PieterGit
@PieterGit
Jul 16 2017 13:00 UTC
just had an idea. Should we set goals we would like to achieve for the 0.6.0 oref0 release. i think it would be good if we could shorten the release cycli of oref0 a bit, e.g. lets try to get approx 4 releases each year. The releasecycli tend to be quite different each release:
  • 0.2.0 -> 0.3.0: 201 days
  • 0.3.0 -> 0.4.0 61 days
  • 0.4.0 -> 0.5.0 162 days
4 releases per year means ~ 91 days between releases, so that will be about friday october 13th for the 0.6.0 release
francesc0-cgm
@francesc0-cgm
Jul 16 2017 13:31 UTC
I think a game changer will be a gui on android phone to bolus from
live4sw
@live4sw
Jul 16 2017 13:44 UTC
I didn't even realize 0.5.0 had come out! Are there release notes, etc?
Wow, just saw on github. Guess I will have to get started on updating my 4 rigs!
Tim Street
@tim2000s
Jul 16 2017 13:53 UTC
@tepidjuice I'm not sure where to go next. The only thing left is that there's something up on the rest feed to your rig, but I don't know how to fix that.
PieterGit
@PieterGit
Jul 16 2017 15:03 UTC
@live4sw : see https://github.com/openaps/oref0/releases for the release notes. Note this is a summery, so even more has changed
PieterGit
@PieterGit
Jul 16 2017 15:11 UTC
my wishlist for 0.6.0:
  • increase security, support debian9 and maybe even kernel 4.11+
  • out of the box pancreable support
  • pebble support for warning for carbs/insulin
  • update node to node6 or node8 and update node packages
  • only use pacakged versions for master releases, so we don't need oref0 releases just like with mraa forced us to release a hotfix
  • update releases for all openaps project applicactions. fix outstanding bugs, merge outstanding pullrequests and branches. Project that need a release: dexcom_reader, openaps, decocare, etc
  • optional git usage, openaps/oref0#549
  • ...
live4sw
@live4sw
Jul 16 2017 15:39 UTC
Thanks @PieterGit - very exciting.
Martin Haeberli
@mhaeberli
Jul 16 2017 15:45 UTC
Pulled latest dev last night. Bolused for 20 g carbs at 8:10 this am. Shows up in NightScout. COB stuck at 0 still 1/2 hour later. What should I look for / at? Only one forecast showing...
fjungman
@fjungman
Jul 16 2017 17:19 UTC
In a bit of an emergency here. My kid leaves in a few hours for a month in Central America. I've been trying to get camping mode going, but it the rig won't get BG data from xDrip+. This was all working, then stopped Monday. I've reinstalled using the script, yesterday. I just updated xDrip+ to be safe, and I bought him an S7 Edge, which was listed as most reliable in the docs. It sees old BGs, but won't get the new ones. I deleted the .json files holding the old data, but it just comes back. I've spent hours combing this Gitter and the docs, but I'm stuck. How can I clean out the database on the rig so it gets new data from the phone?
I bought the phone Wednesday, as an attempt to fix this.
Here is the loop output:
Starting pump-loop at Sun Jul 16 11:15:03 CST 2017:
Waiting up to 4 minutes for new BG: ........................Radio ok. Listening: .No pump comms detected from other rigs
Profile less than 60m old. temp_basal.json more than 5m old.
Temp refreshed
{"carbs":0,"boluses":8.5,"mealCOB":0,"currentDeviation":null,"maxDeviation":0,"minDeviationSlope":0}
BG data is too old (it's probably this), or clock set incorrectly. The last BG data was read at Sun Jul 16 2017 08:41:14 GMT-0600 (CST) but your system time currently is Sun Jul 16 2017 11:20:10 GMT-0600 (CST)
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
{"reason":"BG data is too old (it's probably this), or clock set incorrectly. The last BG data was read at Sun Jul 16 2017 08:41:14 GMT-0600 (CST) but your system time currently is Sun Jul 16 2017 11:20:10 GMT-0600 (CST)"}
{"reason":"BG data is too old (it's probably this), or clock set incorrectly. The last BG data was read at Sun Jul 16 2017 08:41:14 GMT-0600 (CST) but your system time currently is Sun Jul 16 2017 11:20:10 GMT-0600 (CST)"}
Waiting for ntpd to synchronize... OK!
enact/enacted.json: {"insulinReq":0,"bg":234,"reservoir":null,"temp":"absolute","snoozeBG":229,"rate":2.45,"predBGs":{"IOB":[234,233,232,232,231,230,230,229,229,229,229,229,229]},"minPredBG":229,"IOB":0,"reason":"COB: 0, Dev: -6, BGI: 0, ISF: 27, Target: 80, minPredBG 229, IOBpredBG 229; Eventual BG 228 >= 80, max_iob 0, 0m@3.80 > 2 insulinReq. Setting temp basal of 2.45U/hr. ","COB":0,"eventualBG":228,"recieved":true,"duration":30,"tick":-1,"timestamp":"2017-07-16T08:33:33.020146","deliverAt":"2017-07-16T14:33:28.624Z"}
pumphistory more than 5m old. : Refreshed pumphistory
{"carbs":0,"boluses":8.5,"mealCOB":0,"currentDeviation":null,"maxDeviation":0,"minDeviationSlope":0}
BG data is too old (it's probably this), or clock set incorrectly. The last BG data was read at Sun Jul 16 2017 08:41:14 GMT-0600 (CST) but your system time currently is Sun Jul 16 2017 11:20:35 GMT-0600 (CST)
determine-basal://text/shell/enact/suggested.json
reporting enact/suggested.json
{"reason":"BG data is too old (it's probably this), or clock set incorrectly. The last BG data was read at Sun Jul 16 2017 08:41:14 GMT-0600 (CST) but your system time currently is Sun Jul 16 2017 11:20:35 GMT-0600 (CST)"}
{"reason":"BG data is too old (it's probably this), or clock set incorrectly. The last BG data was read at Sun Jul 16 2017 08:41:14 GMT-0600 (CST) but your system time currently is Sun Jul 16 2017 11:20:35 GMT-0600 (CST)"}
Waiting for ntpd to synchronize... OK!
enact/enacted.json: {"insulinReq":0,"bg":234,"reservoir":null,"temp":"absolute","snoozeBG":229,"rate":2.45,"predBGs":{"IOB":[234,233,232,232,231,230,230,229,229,229,229,229,229]},"minPredBG":229,"IOB":0,"reason":"COB: 0, Dev: -6, BGI: 0, ISF: 27, Target: 80, minPredBG 229, IOBpredBG 229; Eventual BG 228 >= 80, max_iob 0, 0m@3.80 > 2
insulinReq. Setting temp basal of 2.45U/hr. ","COB":0,"eventualBG":228,"recieved":true,"duration":30,"tick":-1,"timestamp":"2017-07-16T08:33:33.020146","deliverAt":"2017-07-16T14:33:28.624Z"}
Settings less than 10m old
Edison on battery: 73%. Pumphistory-24 < 90m old
Completed pump-loop at Sun Jul 16 11:20:37 CST 2017
Note that I setup the pump, phone and rig to CST for the area he is travelling to, and the phone TZ update is turned off.
By the way, I like the idea of waiting for the next BG reading, but is there a way to turn that off, 'cuz it sucks for debugging... :)
live4sw
@live4sw
Jul 16 2017 17:26 UTC
I am almost definitely not going to be able to help, but how many hours off are you from the destination time zone?
Scott Leibrand
@scottleibrand
Jul 16 2017 17:26 UTC
Did you try deleting your entire myopenaps directory and reinstalling?
You can manually bypass the next BG thing by removing the pump_loop_completed file.
fjungman
@fjungman
Jul 16 2017 17:30 UTC
Ok, I'll do the bypass first. I'll do the deletion as a last-resort.
Scott Leibrand
@scottleibrand
Jul 16 2017 17:30 UTC
Maybe try deleting .xdripaps directory first then.
fjungman
@fjungman
Jul 16 2017 17:32 UTC
ok, doing that...
Actually, "not finding that"... Where is that directory located?
Scott Leibrand
@scottleibrand
Jul 16 2017 17:37 UTC
In myopenaps I think. Check capitalization.
Or search oref0-setup to see where it puts it.
fjungman
@fjungman
Jul 16 2017 17:41 UTC
Thanks!
Martin Haeberli
@mhaeberli
Jul 16 2017 17:43 UTC
@PieterGit FYI I'm talking about the OpenAPS pill pop up cob report, NOT the separate COB pill, which I know doesn't work w OpenAPS.
Dana Lewis
@danamlewis
Jul 16 2017 17:45 UTC
@PieterGit I am all for goals of what we want to see happen next, but with a scratch your own itch and 100% volunteer project, I don't think pushing for x releases a year makes sense. It's highly dependent on what ends up being developed and the testing needs related to that.
@live4sw make sure you see it's 0.5.1 you're going for, not 0.5.0
fjungman
@fjungman
Jul 16 2017 17:46 UTC
@scottleibrand looks like it is in the home directory.
# xdrip CGM (xDripAPS)
if [[ ${CGM,,} =~ "xdrip" ]]; then
    echo xdrip selected as CGM, so configuring xDripAPS
    sudo apt-get install sqlite3 || die "Can't add xdrip cgm - error installing sqlite3"
    sudo pip install flask || die "Can't add xdrip cgm - error installing flask"
    sudo pip install flask-restful || die "Can't add xdrip cgm - error installing flask-restful"
    git clone https://github.com/colinlennon/xDripAPS.git $HOME/.xDripAPS
    mkdir -p $HOME/.xDripAPS_data
    for type in xdrip-cgm; do
        echo importing $type file
        cat $HOME/src/oref0/lib/oref0-setup/$type.json | openaps import || die "Could not import $type.json"
    done
    touch /tmp/reboot-required
fi
Should I just remove the .xDripAPS_data directory?
Scott Leibrand
@scottleibrand
Jul 16 2017 17:47 UTC
@PieterGit so far the signs point to us moving backwards on "only use packaged versions for master releases" until someone convinces Ben to give someone perms to do releases on packages he used to maintain.
I think node8 will be something we can pretty easily do and test for the next minor version. sounds like it has quite a few speed improvements too.
we also might be able to do more and smaller patch or minor releases if we can get new features tested fast enough, instead of batching them all up with big stuff...
live4sw
@live4sw
Jul 16 2017 17:54 UTC
Thanks @danamlewis - I'm going to update my daytime rig tomorrow and will just use the normal upgrade commands to get the newest.
PieterGit
@PieterGit
Jul 16 2017 17:56 UTC
@danamlewis @scottleibrand : perhaps I should say let's try to do more "release often, release early" just like linux (https://en.wikipedia.org/wiki/Release_early,_release_often ) , instead of proposing a fixed number of releases per year. I think for the 0.5.0 release it would have been better (in hindsight) to release oref0 just before we started with merging oref1/SMB. For oref0 i think it will be a good practice to do very major stuff (e.g. node upgrades) at the beginning, and less risky stuff (e.g. bug fixes) at the end. On the other hand that might cause that people only to use the releases, and that will slow down dev development.
Dana Lewis
@danamlewis
Jul 16 2017 18:03 UTC
@PieterGit yea.
Matthias
@ceben80
Jul 16 2017 18:14 UTC
@SebastienLussier thx again for PR #29 solution, just using the BolusExpert again w/ my 754, works great!
PieterGit
@PieterGit
Jul 16 2017 18:36 UTC
@SebastienLussier and @ecc1 thanks for finding the root cause for openaps/decocare#29 . It now works for me with Meal Bolus, but somehow it still is in mg /dl form for BG check.
Martin Haeberli
@mhaeberli
Jul 16 2017 19:17 UTC
so in this logentry {"insulinReq":0.7,"bg":141,"reservoir":null,"temp":"absolute","snoozeBG":172,"rate":2.85,"predBGs":{"IOB":[141,145,149,152,155,158,161,163,165,167,168,169,170,170,171,171,171,171,172,172,172,172,172,172,172,172,173,172]},"minPredBG":172,"IOB":-0.283,"reason":"COB: 0, Dev: 20, BGI: 0.93, ISF: 41, Target: 142, minPredBG 172, IOBpredBG 172; Eventual BG 171 >= 154, temp 1.875<2.85U/hr. ","COB":0,"eventualBG":171,"recieved":true,"duration":30,"tick":"+5","timestamp":"2017-07-16T08:09:17.351172","deliverAt":"2017-07-16T15:09:12.616Z”} why is reservoir null ? - seems to be consistently null, even though pill reporting reasonable levels
fjungman
@fjungman
Jul 16 2017 19:19 UTC
@scottleibrand I deleted the myopenaps directory and started over. After I deleted the .xDripAPS_data folder, the loop was erring out.
Jul 16 12:07:34 VmaxAPS1 pump-loop.log: .jq: error: null and number cannot be divided
Jul 16 12:07:34 VmaxAPS1 pump-loop.log: date: invalid date ‘@’
Jul 16 12:07:44 VmaxAPS1 pump-loop.log: .jq: error: null and number cannot be divided
Jul 16 12:07:44 VmaxAPS1 pump-loop.log: date: invalid date ‘@’
Jul 16 12:07:54 VmaxAPS1 pump-loop.log: .jq: error: null and number cannot be divided
Jul 16 12:07:54 VmaxAPS1 pump-loop.log: date: invalid date ‘@’
Scott Leibrand
@scottleibrand
Jul 16 2017 19:20 UTC
@fjungman was that after you re-ran oref0-setup?
@mhaeberli not all of the code paths check reservoir level. seeing null there is common if you're not in SMB mode.
if you know of a way to delete the variable it so it's not displayed when it's null, that might be better
fjungman
@fjungman
Jul 16 2017 19:21 UTC
I don't see them anymore. I'm hopeful it works now! I am still getting a lot of these:
Jul 16 12:18:46 VmaxAPS1 pump-loop.log: Old pumphistory: mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
Jul 16 12:18:46 VmaxAPS1 pump-loop.log: Error, retrying
When I run mmtune, I get -48dBm signals...
...consistently.
Martin Haeberli
@mhaeberli
Jul 16 2017 19:23 UTC
@scottleibrand thx
fjungman
@fjungman
Jul 16 2017 19:26 UTC
@scottleibrand I'll post the complete log of one loop, but first, I usually edit cron to have the loop only run every 5 minutes (change all the to /5). Is this ok, or is there a reason it defaults to every minute? Does this cause multiple instances of the loop to be running simultaneously?
Jul 16 12:24:00 VmaxAPS1 pump-loop.log: Old pumphistory: mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
Jul 16 12:24:00 VmaxAPS1 pump-loop.log: Error, retrying
Jul 16 12:24:01 VmaxAPS1 network.log: Starting oref0-online.
Jul 16 12:24:02 VmaxAPS1 network.log: At Sun Jul 16 13:24:01 CST 2017 my local IP is: 192.168.44.2
Jul 16 12:24:02 VmaxAPS1 autosens-loop.log: Sun Jul 16 13:24:02 CST 2017
Jul 16 12:24:02 VmaxAPS1 autosens-loop.log: settings/autosens.json
Jul 16 12:24:02 VmaxAPS1 ns-loop.log: Starting ns-loop at Sun Jul 16 13:24:02 CST 2017:
Jul 16 12:24:03 VmaxAPS1 network.log: At Sun Jul 16 13:24:02 CST 2017, my wifi network name is , and my public IP is: 50.107.80.3
Jul 16 12:24:03 VmaxAPS1 network.log: Finished oref0-online.
Jul 16 12:24:05 VmaxAPS1 pump-loop.log: Starting pump-loop at Sun Jul 16 13:24:05 CST 2017:
Jul 16 12:24:05 VmaxAPS1 pump-loop.log: Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed
Jul 16 12:24:11 VmaxAPS1 ns-loop.log: ns://JSON/shell/cgm/ns-glucose.json
Jul 16 12:24:11 VmaxAPS1 ns-loop.log: reporting cgm/ns-glucose.json
Jul 16 12:24:20 VmaxAPS1 ns-loop.log: ns://JSON/shell/settings/temptargets.json
Jul 16 12:24:20 VmaxAPS1 ns-loop.log: reporting settings/temptargets.json
Jul 16 12:24:20 VmaxAPS1 ns-loop.log: get-profile://text/shell/settings/profile.json
Jul 16 12:24:20 VmaxAPS1 ns-loop.log: reporting settings/profile.json
Jul 16 12:24:25 VmaxAPS1 ns-loop.log: Refreshed temptargetsns://JSON/shell/monitor/carbhistory.json
Jul 16 12:24:25 VmaxAPS1 ns-loop.log: reporting monitor/carbhistory.json
Jul 16 12:24:26 VmaxAPS1 ns-loop.log: and meal-carbs
Jul 16 12:24:27 VmaxAPS1 ns-loop.log: {"batteryVoltage":3861, "battery":68}
Jul 16 12:24:39 VmaxAPS1 pump-loop.log: Radio ok. Listening: .No pump comms detected from other rigs
Jul 16 12:25:02 VmaxAPS1 network.log: Starting oref0-online.
Jul 16 12:25:02 VmaxAPS1 network.log: At Sun Jul 16 13:25:02 CST 2017 my local IP is: 192.168.44.2
Jul 16 12:25:02 VmaxAPS1 autosens-loop.log: Sun Jul 16 13:25:02 CST 2017
Jul 16 12:25:02 VmaxAPS1 autosens-loop.log: settings/autosens.json
Jul 16 12:25:03 VmaxAPS1 network.log: At Sun Jul 16 13:25:02 CST 2017, my wifi network name is , and my public IP is: 50.107.80.3
Jul 16 12:25:03 VmaxAPS1 network.log: Finished oref0-online.
Jul 16 12:25:07 VmaxAPS1 pump-loop.log: Old pumphistory: mmeowlink.exceptions.CommsException: No acknowledgement from pump on wakeup. Is it out of range or is the battery too low?
Jul 16 12:25:07 VmaxAPS1 pump-loop.log: Error, retrying
Jul 16 12:25:12 VmaxAPS1 pump-loop.log: Starting pump-loop at Sun Jul 16 13:25:12 CST 2017:
Jul 16 12:25:12 VmaxAPS1 pump-loop.log: Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed
Jul 16 12:25:16 VmaxAPS1 ns-loop.log: Uploaded
Scott Leibrand
@scottleibrand
Jul 16 2017 19:29 UTC
@fjungman all of the cron lines check if anything is already running. if you change them to */5, then your rig won't retry for up to 5 minutes if you have an error running the loop. with the new wait-for-bg stuff, I don't think there's any reason to change them to */5
fjungman
@fjungman
Jul 16 2017 19:32 UTC
Ok, that is good to know. I understand the pieces of the loop, but the logic in the main code is a mystery to me.
any thoughts on the "Old pumphistory" errors?
Michael Spradling
@M1Sports20
Jul 16 2017 19:37 UTC
@scottleibrand: I wanted to reinstall openaps, the 12 hours seems to not be showing up at the moment. I will let you know
Does anyone know how to have the openaps rig send its battery status to nightscout, maybe it does, but my xdrip+ overrides it with my cell phone battery voltage
Katie Aldridge
@kcrcgm
Jul 16 2017 19:41 UTC
@scottleibrand Hey Scott, I've got about 45 minutes, is that enough time to do any debugging? Otherwise I can get back on here tonight around 9:00 (central).
Dana Lewis
@danamlewis
Jul 16 2017 19:43 UTC
@kcrcgm he's driving, but if you can start doing some of the things he was talking about you doing last night, then we should be out of the car in 15 min and he can take a look at where you are then
Katie Aldridge
@kcrcgm
Jul 16 2017 19:44 UTC
@danamlewis Ok, I'm working on that now. Thanks! :)
Dana Lewis
@danamlewis
Jul 16 2017 19:44 UTC
:+1:
fjungman
@fjungman
Jul 16 2017 19:47 UTC
I'm getting temps set now!!! Thanks Scott! Careful driving... ;) Odd, I hadn't actually set a MaxIOB number yet, since I wiped out my previous settings. It is set to zero, but it has 9 units on board, and it set a temp of 3.3units...
Dana Lewis
@danamlewis
Jul 16 2017 19:48 UTC
Basaliob probably negative, read your logs
fjungman
@fjungman
Jul 16 2017 19:51 UTC
Have you programmed "read your logs" into a function-key-macro? :) Yes, you are correct, of course.
Dana Lewis
@danamlewis
Jul 16 2017 19:57 UTC
It's usually "what do your logs say?" ;) :+1:
fjungman
@fjungman
Jul 16 2017 19:58 UTC
That is more "customer oriented"... :)
Scott Leibrand
@scottleibrand
Jul 16 2017 19:59 UTC
And then there's rtfd.io ;-)
fjungman
@fjungman
Jul 16 2017 20:08 UTC
I used to have a link to lmfgtfy.com on my desktop at work, so I could respond to emails with that...
Dana Lewis
@danamlewis
Jul 16 2017 20:08 UTC
Hehehe
fjungman
@fjungman
Jul 16 2017 20:08 UTC
His rig is (seemingly) 100%. I have another here I'm going to duplicate as a backup. I sent him out on the lake so it wouldn't interfere with his rig...
Katie Aldridge
@kcrcgm
Jul 16 2017 20:15 UTC
@scottleibrand I ran the tail commands on both monitor/glucose.json and got some data (like a ton, all at once) and then it said the file was truncated. I ran it on xdrip/glucose.json and it just says the file was truncated. Tried the command on both files several times and got the same results each time.
@scottleibrand Sorry, meant to say I ran the tail commands on both files (xdrip/glucose.json and monitor/glucose.json)
I got data on monitor/glucose.json (then truncated) and none at all with xdrip/glucose.json (truncated)
Hope that makes sense
Scott Leibrand
@scottleibrand
Jul 16 2017 20:21 UTC
Thanks. Can you paste the output from the xdrip/glucose.json one?
Katie Aldridge
@kcrcgm
Jul 16 2017 20:23 UTC
Debugging xdrip 1.JPG
Scott Leibrand
@scottleibrand
Jul 16 2017 20:27 UTC
Aha! Didn't realize it alternated between [] and empty. I think the fix I drafted last night might work then.
Katie Aldridge
@kcrcgm
Jul 16 2017 20:31 UTC
Ok, awesome
What does [] mean?
vladysdelaplace
@vladysdelaplace
Jul 16 2017 20:31 UTC
hello everybody. I have some problems with nightscout. I have message Application error
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. And i have this erreur type unable to ensureIndex for: enteredBy - MongoError: Btree::insert: key too large to index, failing vladys07.treatments.$enteredBy_1 1038 { : "openaps://medtronic/ via Nightscout via Nightscout via Nightscout via Nightscout via Nightscout via Nightscout via Nightscout via Nightscout via please ..i dont know why its very havy to log?
Scott Leibrand
@scottleibrand
Jul 16 2017 20:34 UTC
@kcrcgm that means "empty array"
Katie Aldridge
@kcrcgm
Jul 16 2017 20:38 UTC
@scottleibrand I have just a few more minutes if you want me to test anything else? I can get back on tonight too
Scott Leibrand
@scottleibrand
Jul 16 2017 20:39 UTC
I think I have everything I need. I'll get you directions to test the fix tonight.
Katie Aldridge
@kcrcgm
Jul 16 2017 20:40 UTC
Ok, great!
fjungman
@fjungman
Jul 16 2017 21:12 UTC
@scottleibrand @danamlewis both rigs working! Off he goes to 28 days without internet!
Scott Leibrand
@scottleibrand
Jul 16 2017 21:25 UTC
:+1:
tepidjuice
@tepidjuice
Jul 16 2017 21:28 UTC
@tim2000s surely there's some debugging that could be done to narrow down what's going wrong. Like running parts of xDripAPS seperately.
Martin Haeberli
@mhaeberli
Jul 16 2017 21:47 UTC
What does a treatment note lan69 723 mean in NS!
Dana Lewis
@danamlewis
Jul 16 2017 22:23 UTC
@fjungman yay! Hope he has fun
jordan-berger
@jordan-berger
Jul 16 2017 23:07 UTC
Has anyone experienced nightscout indicating that it is not connected to the AP but is running temp basal's?
Marcus Lindfors
@Mackwe
Jul 16 2017 23:41 UTC
In what way would you say it says 'not connected'?
jaylagorio
@jaylagorio
Jul 16 2017 23:49 UTC
I'm considering building a Pi-based rig that will be in a place where it won't be on the Internet. 24/7/365, this thing will never be on the Internet for its entire existence after I get OpenAPS configured. It will, however, have a keyboard and a monitor attached. Is there any way I can inject a temp target in the same way as if the rig had picked it up off of a Nightscout instance? Maybe by crafting some a file in some way and positioning it somewhere to get picked up by the loop?
Dana Lewis
@danamlewis
Jul 16 2017 23:50 UTC
If you have keyboard and monitor, you could probably create and do a similar temp target process?
jaylagorio
@jaylagorio
Jul 16 2017 23:51 UTC
How do you mean? I don't know the specifics of what the loop does when it picks data up out of Nightscout to influence itself. What's that temp target process?
Dana Lewis
@danamlewis
Jul 16 2017 23:53 UTC
You'd have to look and see how it grabs temp targets from NS, and manually create the same kind of files for it. You may can create an alias or a series of them so it's easy to do without having to format the files each time.
jaylagorio
@jaylagorio
Jul 16 2017 23:58 UTC
That's the kind of thing I thought I might have to do, thanks for confirming and for the link!