-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create analysis data runner and sensor delegate adapter #42
Comments
5 tasks
Also required for completion:-
|
Currently experiencing a fatal error running on nRF5340dk. Likely caused by the logging delegate's default constructor due to how the analysis runner works currently. Need to investigate. |
Fixed for all but nRF52832 due to memory issue. Completing for now. Full test after memory tuning will fix that platform's issues. |
adamfowleruk
added a commit
that referenced
this issue
Apr 21, 2021
Fixes #42. Analysis API complete. Signed-off-by: Adam Fowler <adam@adamfowler.org>
adamfowleruk
added a commit
that referenced
this issue
Aug 30, 2021
Signed-off-by: Adam Fowler <adamfowleruk@gmail.com>
adamfowleruk
added a commit
that referenced
this issue
Aug 30, 2021
Known issue: Still experiencing stack overflows in wearable example. Signed-off-by: Adam Fowler <adamfowleruk@gmail.com>
adamfowleruk
added a commit
that referenced
this issue
Aug 30, 2021
Known issues:- - Sensor Logger doesn't allow data parameters to be logged without hard fault on Zephyr Signed-off-by: Adam Fowler <adam@adamfowler.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please start with a use case description for a USER of this enhancement
[Who] As an epidemiologist-developer OR DCT app developer
[What] I need to easily 'plug in' my data analysis pipeline to a real app, live
[Value] In order to evaluate and use my analysis algorithms within an app and evaluate their efficacy, and provide value to app users (E.g. a read out of their risk exposure estimate)
Describe the potential solution you'd like
Describe alternatives you've considered
Manual linking - complex and a repeatable pattern everyone will need, so it makes sense to solve it once.
Additional context
Please use template classes to allow type of Device and DeviceID to be dynamic (i.e. not just limited to the BLEDevice class and data)
Relative priority
High: Required for release v1.3
The text was updated successfully, but these errors were encountered: