-
Notifications
You must be signed in to change notification settings - Fork 1
4 wearables ndx uml #7
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
base: main
Are you sure you want to change the base?
Conversation
|
FWIW: here is a shortcut url to view the rendered file: https://github.com/aplbrain/BBQS-EMBER/blob/4-wearables-ndx-uml/doc/design/wearables_ndx.mmd |
Wearables data types received from BaylorThis is all the most relevant data made available by the wearables being used (Oura Ring and Apple Watch) but it is not known whether all the data will be used/saved into NWB. A lot of this data will either be in the form of timeseries or sparse array. The current proposed structure only outlines how timeseries data will be stored, as we are still trying to determine the best course of action for sparse data. Any insight on that front would also be very much welome! Oura API Documentation
|
|
Dear @rly . For EMBER we are investigating optimal formats to store various data from wearable devices.
Dear @smoia, I will like many of the aforementioned datatypes fall under the auspice, or could be adopted by BIDS physio data/extension and physiopy... are you working with such data types? have examples to point to among public datasets? |
This is a rough class diagram of how we propose structuring the NWB wearables extension we're working on with the Baylor team and how it fits into the greater NWB data structures. Let me know what you think and if there's any suggestions for improvement!
Adding Erik for awareness