@channemann great deck and presentation! thanks for sharing... Quick question: what are you using outside of NS for data visualization?
also, just noticed that the documentation is being updated. Just learned something: my loop was failing from time. The root cause was that the clock of the Dexcomm, the pump and the Raspberry were slightly off - close or sometimes over 5 minutes...perhaps a note to make sure all the device clocks are in synch?
yes, some people are starting to do that. the main thing i heard is it is a bit funky inside the app and you gotta make sure you flip the camera the same way each time so front/back are not upside down.
but i am going to test it soon that way
it’s actually a rolling 24 hours thing. but you can download the rolling 24 hours whenever you want. it’s not that hard to stitch them together. you can actually do that inside youtube’s editor now.
it’s 5 mins long for today already. feeling like there will be some sort of optimal length once i get it figured out.
@bewest it was the ENV, but actually something else: I had a subdomain to my personal domain pointing to my NS site in my Azure acct. The NS uploader does not like that, although NS actually works well with a re-directed domain name. As soon as I changed it to the Azure site (no domain redirection), it worked fine. Of course, I had resolved that a while ago and never changed the ENV variables in Cron...
maybe another note for that pull request... I will get around sometime next week. I will try to loop through the weekend now that everything seems to be in place
i do want to understand @mariusae’s analysis more. I’d really like to see a little competiton brew between the few different loop code that he’s using vs @loudnate vs @scottleibrand ’s advanced meal assist. push the envelope a bit.
it’d be nice to do something like apple health (which i know sucks in a lot of ways) but where you can easily go from hour to day to week to month to year. and drill in anywhere. would be awesome to tie video reactions and be able to filter on > 300 and jsut watch those videos. ok, probably crazy idea that is 10x effort vs value
i was thinking about how much insulin must get wasted from stopping early, the long canula wires, etc. especially people with 5xx’s that are wasting a higher % of insulin. Then the damn pharmacy guys give you crap about how many bottles you are covered for etc
i think their new app sounds fricking awesome if i can log what i eat and then see what happened last time i ate it! i just want to use that!! but getting my pump data in is a big issue. and then the x22 issue. it does bum me out. would love to use the work they/ve done
Hi, i have a question on HotSwap: As i dont have an on transmitter, i was looking for a 3D printable version. I thought a Dummy to press down the movable part would be enough. Now someone askes me: "How your sensor will stabilized without supplying a power on it? The transmitter constantly applied to the sensor is about 0.2 volts for proper chemical reactions. So the first two hours the system reaches equilibrium. A dummy is not capable to this and will have no effect. In other words, stabilization only starts when you put on the transmitter and it makes no sense to install the sensor without it. " I thought the old transmitters you are using
@bewest@jmatheson I just saw the videos! and love the idea of documenting the looping and decision making for each project to compare and learn! It would be cool to develop a standard process of documentation so we can compare with the same/similar process and before that just make sure others want to participate
@julza78 pretty sure the dead transmitter we use isn't supplying current. Apparently that isn't a big deal, and most of the benefit from the 24h soak is from the letting the "wound healing" reactions stabilize. When we swap the transmitter we still get an hour of ??? from the switch. Haven't looked at raw data to see how quickly that stabilizes.
Do you mean map my names to the ones in the documentation? For clarification, I used the report and device names in the main openaps documentation, but they don't exactly match the auto-sens documentation.
Okay, I think we're saying the same thing. The determine-sensitivity report is similar to the determine-basal report, except that it has a few new inputs. So I should use it instead. Thank you.
I'm going to finish auto-sens, then tackle meal-assist. After that, I plan to completely refactor my openaps.ini. It really is a tangled knot right now, but I'm finally starting to understand where all of the threads come from....
Hey everyone. It’s been weeks now, and I still haven’t been able to find a compatible pump for a reasonable price (<=$600). One person on craigslist decided not to sell, and no one on MedWow has even responded to me. There are lots of pieces of the project that I would like to contribute to, but it seems like getting support for more recent Medtronic pumps working is critical to a lot of people. Who on the project can I talk to about contributing to this? :) ( ping @scottleibrand )
I want to write a reply to the email i got about upgrading from Medtronic. I just made a google doc. Would love thoughts, edits, comments etc. feel free to sugget them inside the doc. I can publish what we end up with back to this group
hi ... my loop is stuck because it just gets old bg values (half an hour old). the pump is showing current bg values and the times seem to be okay. Reboot of the edison didn't help. Every time I ask the pump by use of iter_glucose I get the same old values. Any ideas?
the command : mm-send-comm.py --init --serial 123456 tweak ReadHistoryData --save --page 0 I found did't work because of the port that is not open. But it seems for me, that the calibration has fixed it. The iter_glucose is working again. I had this a couple of days ago - strange