Skip to content

Conversation

@danamlewis
Copy link
Contributor

This set of autosens tweaks was created to enable us to run autotsens retrospectively on data. There are a few small tweaks, however, that we'd like to test before merging this to dev. Please check out this branch, watch your autosens carefully & let us know if you see anything odd.

@tim2000s
Copy link
Contributor

Tried to run autosens-history and running into the following. It's not clear why this is happening:

root@ed201:~/myopenaps/tims# ~/src/oref0/bin/all-autosens-history.sh
Checking / waiting for system load to be below 5 before continuing
Processing participant tims
Waiting 10 seconds before processing next participant
Checking / waiting for system load to be below 5 before continuing
Processing participant tims treatments for 2018 07
Processing participant tims entries for 2018 07
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/src/oref0/bin/oref0-autosens-history.js:18:13)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
All participants have now been started. Above is the output generated so far. Review for any errors - if errors exist...there's an error. Remaining participants may still be running.

@scottleibrand
Copy link
Contributor

Are you trying to run it on OpenHumans data? If not, there’s no need to run the new history scripts: they’re only for retrospective analysis of OH data. We just need you to test that the changes to the lib files don’t break normal autosens operation.

@tim2000s
Copy link
Contributor

I’m trying to run the retrospective analysis to look back over some data I have. Figured out I need to create a participant and give it data from NightScout, which sits in the participant/direct-sharing-31 directory, but not clear why it’s failing at the lib/profile/basal point.

@scottleibrand
Copy link
Contributor

Does your data have a valid profile.json?

@tim2000s
Copy link
Contributor

I've pulled the profile.json from Nightscout. Let me try it again with the valid one from looping.

@tim2000s
Copy link
Contributor

tim2000s commented Jul 23, 2018

Replacing profile.json with a current active one results in the following, which appears to be dumping out at the same place.

root@ed201:~/myopenaps/tims# ~/src/oref0/bin/all-autosens-history.sh
Checking / waiting for system load to be below 5 before continuing
Processing participant tims
Waiting 10 seconds before processing next participant
Checking / waiting for system load to be below 5 before continuing
Processing participant tims treatments for 2018 07
Processing participant tims entries for 2018 07
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/src/oref0/bin/oref0-autosens-history.js:18:13)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)
All participants have now been started. Above is the output generated so far. Review for any errors - if errors exist...there's an error. Remaining participants may still be running.

It appears to be having problems with basal according to 2018-07.out:

module.js:340
    throw err;
          ^
Error: Cannot find module 'oref0/lib/profile/basal'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/root/src/oref0/bin/oref0-autosens-history.js:18:13)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Function.Module.runMain (module.js:497:10)

@scottleibrand
Copy link
Contributor

@tim2000s Do you have any reason to think this is a problem with the changes in this branch? Or have you seen any regressions in normal autosens use? Or are we good to merge this to dev?

@tim2000s
Copy link
Contributor

I’ve seen nothing to suggest that autosens of its own accord is affected by the changes. Only the history functions causing me issues.

@scottleibrand
Copy link
Contributor

Ok, I’ll merge this then if no objections.

Want to hit me up on Slack or Gitter sometime to troubleshoot the history stuff?

@tim2000s
Copy link
Contributor

Will do. Probably be later this week.

@scottleibrand scottleibrand merged commit ed671c1 into dev Aug 1, 2018
@scottleibrand scottleibrand deleted the autosens-history branch August 1, 2018 05:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants