same error on my local rig.
AUTH_DEFAULT_ROLES config var in Heroku (not nightscout settings) must be "readable" without the quotes.
This makes your site publicly available. But you can put it back to "denied" later
NS settings admin subjects & roles are for the API
They come in to play when AUTH_DEFAULT_ROLES is set to "denied"
I don't use autotune web pretty much for this reason. It's not worth the hassle.
But you can run it manually too of course. Scenarios are described here: https://openaps.readthedocs.io/en/latest/docs/Customize-Iterate/autotune.html#different-ways-to-utilize-autotune
OK I set AUTH_DEFAULT_ROLES=readable in heroku and played around with my API_SECRET based on openaps/oref0#397 and it's still not working on my local rig.
Running like
oref0-autotune --dir='~/openaps' --ns-host='https://xxx.herokuapp.com' --start-date='2021-03-10' --end-date='2021-03-24'
For CLI
When you installed OpenAPS, did you select API SECRET, and then use a token by any chance?
That is a pretty old ticket.
Are you running autotune CLI from a mac?
I was under the impression you were running it from your rig
pulled that ticket off of the docs
It's also still giving the same error on autotune web when i have
AUTH_DEFAULT_ROLES= readableCompressing old json and log files to save space...
gzip: ns-*.json: No such file or directory
gzip: autotune*.json: No such file or directory
Autotune disk usage:
16K .
Overall disk used/avail:
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 69G 55M 65G 1% /mnt
Grabbing NIGHTSCOUT treatments.json and entries/sgv.json for date range...
Query: https://hsghori-nightscout.herokuapp.com entries/sgv.json find%5Bdate%5D%5B%24gte%5D=1616151600000&find%5Bdate%5D%5B%24lte%5D=1616238000000&count=1500
-rw-r--r-- 1 _azbatch _azbatchgrp 3 Mar 25 23:13 ns-entries.2021-03-19.json
Query: https://hsghori-nightscout.herokuapp.com treatments.json find%5Bcreated_at%5D%5B%24gte%5D=2021-03-18T06:00-07:00&find%5Bcreated_at%5D%5B%24lte%5D=2021-03-20T18:00-07:00
-rw-r--r-- 1 _azbatch _azbatchgrp 149942 Mar 25 23:13 ns-treatments.2021-03-19.json
oref0-autotune-prep ns-treatments.2021-03-19.json profile.json ns-entries.2021-03-19.json profile.pump.json > autotune.2021-03-19.json
undefined:1
undefined
^
SyntaxError: Unexpected token u in JSON at position 0
at JSON.parse (<anonymous>)
at categorizeBGDatums (/usr/src/oref0/lib/autotune-prep/categorize.js:73:28)
at generate (/usr/src/oref0/lib/autotune-prep/index.js:23:30)
at Object.<anonymous> (/usr/src/oref0/bin/oref0-autotune-prep.js:131:27)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
Warning: API_SECRET is not set when calling oref0-autotune.sh
(this is only a problem if you have locked down read-only access to your NS).
Could not run oref0-autotune-prep ns-treatments.2021-03-19.json profile.json ns-entries.2021-03-19.json
and after saving
export API_SECRET=token=<again your token>
hey team, just started with openaps over the past week and a bit still getting used to everything, just wanted to check as docs aren't entirely clear on this: when autotune runs and updates the profile do the new ISF/carb ratio and basal rates need to be updated on the pump? or does openaps just achieve this on its own through temp basals over current pump setting?
The latter. If you want to change your default pump settings you can, but no need (Autotune profile is used via the rig to drive its decisions. Pump settings will only come into play if your rig is off and you “fall back” to those settings.) so if they’re quite a bit different over time you may want to adjust the pump settings, but it’s not a daily thing you have to do.
PRs welcome to the docs if you have an idea for making that point more clear!
will have a read through the docs and see if I can word differently to clarify! thanks again :)
a good commentary on how this works over time https://www.diabettech.com/openaps/autotune-reviewing-the-outputs/
Are all recommendations used like this? e.g. ISF
Hi, I am running autotune with a cron job on my own server (dev branch with AAPS, omnipod, G6) daily. It has tuned my night basal rates very well (hard to tell with my day basal rates though). However, I was wondering if there are any suggestions on the number of days to run it on if you use it on a daily basis? I am currently using 5 days.
This certainly isn’t a recommendation, I’m just sharing what I do and why. I run AT every few weeks on the maximum amount of data (30 days) because I find it works well for me if I treat basal, ISF & CR changes as a long term thing whilst sensitivity deals with faster changes.
oref0-autotune-core autotune.2021-05-07.json profile.json profile.pump.json > newprofile.2021-05-07.json
CRTotalCarbs: 0 CRTotalInsulin: 0 totalCR: NaN
ERROR: bad basalProfile { i: 0, minutes: 0, rate: 0, start: '00:00:00', untuned: 1 }
parse error: Invalid numeric literal at line 2, column 0
jq: error: syntax error, unexpected LITERAL, expecting $end (Unix shell quoting issues?) at <top-level>, line 1:
newprofile.2021-05-07.json
jq: 1 compile error
Warning: API_SECRET is not set when calling oref0-autotune.sh
(this is only a problem if you have locked down read-only access to your NS).
newprofile.2021-05-07.json invalid
Also, I would like to specify, I'm running it off AutotuneWeb, not a localized instance.