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

10th
Sep 2017
PieterGit
@PieterGit
Sep 10 2017 13:51
@scottleibrand @danamlewis : did anybody ever register jetpack webstorm licenses for oref0 use? If not, do you mind if I apply for licenses (see https://www.jetbrains.com/shop/eform/opensource?product=WS ). How many developpers are interested in using webstorm for oref0 development?
Scott Leibrand
@scottleibrand
Sep 10 2017 15:40
But you could count up the number of people who've committed to the oref0 codebase recently...
Lukasz Kaniowski
@lukasz-kaniowski
Sep 10 2017 16:56
hi guys, I'm experiencing timout when I try to upload glucose.json to ns. Rig was working offline for 2 weeks so glucose.json to be uploaded is around 39K. I'm getting at=error code=H12 desc="Request timeout" method=POST path="/api/v1/entries.json" in NS logs. Is there a way to increase timeout on NS to process bigger requests?
Miiko
@tw_miiko_twitter
Sep 10 2017 17:08

@scottleibrand @danamlewis @scottleibrand @danamlewis Before summer vacation I have a possible "conflict?" reported and followed. Until now, I'm always not sure if it really is, or just a setting error of mine. I would be happy to pass on the information for developers to check this. Also, I like to hear from other Openaps users, whether you also have so similar problem.

My Openaps version: 0.5.3 + SMB & UAM
Suspected Problem Source: Temporary Target in active.
Behavior: Temproray Target was activated before eating. While this activation gave bolus.
conflicts:
1, the last reported problem was "0 as the target BG for Looping",
2, today had a problem that would also be linked to Temproray's target that would rig stop working.

Improvement:
First solve Temproray target, then give eating bolus, then Rig runs well

An information exchange would be very glad. Many thanks to the developers.

cameronrenwick
@cameronrenwick
Sep 10 2017 17:45
20170910_132839_resized.jpg
20170910_132854_resized.jpg
20170910_133300_resized.jpg
20170910_132906_resized.jpg
Hey folks. A little update here. Finally finished my new rig. It contains a 4400 mAh battery, adafruit charger board, wixel, HM-17, EB and edison. Also added in is a switch to cold start the wixel (only - EB/edison is always live), a round headphone-like receptacle for charging, rugged ABS box with belt clip. This is going to be my "every day" one piece rig that should allow a 16 hour day and protection for the rig during my generally physical job and life. I've included a few shots for your viewing pleasure. I made a few USB to rig cables and that for me has been one of my biggest gains with this. Fiddling around with the micro-usb was the biggest annoyance and a part that will fail eventually. Also, adding the adafruit board for charging (with soldered 500 mAh bridge) means quicker charges overnight. I've still got my other slim rig for occasions where I want a minimum size of gear but this new one should handle day-to-day well I'm hoping.
Scott Leibrand
@scottleibrand
Sep 10 2017 17:49
@tw_miiko_twitter was this a one-time error, or is it something you can reproduce repeatedly by doing the same thing again?
Lukasz Kaniowski
@lukasz-kaniowski
Sep 10 2017 17:52
I figure out how to upload glucouse.json directly by using ns-upload-entries glucose.json, this worked
Craig Brenner
@cbrenner
Sep 10 2017 20:28
Anyone have any ideas as to one the two rigs we are using are showing different 'current' Carb Ratios in autotune (see pic below)? Shouldn't these be identical (pump's ratio is set for '18' at 00:00) since it is being pulled from the pump. The 'carb_ratios.json" files for each rig are identical as well.
image.png
Dana Lewis
@danamlewis
Sep 10 2017 20:30
The rigs run Autotune separately, so it depends on what data each rig has
Did you change the carb ratio on pump since that rig's last run?
Craig Brenner
@cbrenner
Sep 10 2017 20:35

@danamlewis No change since the last rig's run....but it should be pulling the 'current' carb ratio from the pump, right? And, since the 'carb_ratios.json" files are the same, I would thing the 'current' carb ratio would be the same.

On a similar topic, curious as to how the two rigs coordinate. It says in the docs that there is a 'hand off' but since they are not sharing a common 'myopenaps' directory, it seems that one rig predictions and execution will differ from the others when the hand off is made. Would think this would become more problematic the longer a rig is not actively looping.

Scott Leibrand
@scottleibrand
Sep 10 2017 20:50
Different rigs with different autotune results will have slightly different ideas of what temp basals you need. Usually they're pretty close, though.
Miiko
@tw_miiko_twitter
Sep 10 2017 21:05
@scottleibrand Until now, both are only once, but both seems to be related to temproray target. I'll keep watching. But I'm not sure it can be another reason right? So I ask, if someone also noticed similar problem. As a supplement: It has been seen in Loop-Log several times: "Eventual BG: NaN", and this prevents further looping.
I have MDT CGM.
NaN.png
drmartinezs
@drmartinezs
Sep 10 2017 21:12
need help Please, commit your changes or stash them before you can merge. Aborting Couldn't pull latest oref0 root@lukasrig:~#
Scott Leibrand
@scottleibrand
Sep 10 2017 22:29
@drmartinezs you just need to git stash as it suggests, from ~/src/oref0
@tw_miiko_twitter I suspect it was a temporary problem with pump communications that resulted in a bad reading. We get those occasionally, but then they clear up on the next refresh.
drmartinezs
@drmartinezs
Sep 10 2017 22:34
Just paste git stash on root@lukasrig:~# ??
cameronrenwick
@cameronrenwick
Sep 10 2017 23:12
anyone else finding mongo to be timing out a lot over the past 2-3 days? I'm wondering if it's storm related to the US in some way?