jvelasco2319
commented
5 years ago 5) wanted to save data from sensors after every session (total 3 sessions per patient) instead of instantaneously
12) Save data from:
- Calibration stage - data from the HTC vive sensors
- Score
- Rounds (3 Rounds per patient)
- words spelled correctly
- total words
- total wrong words spelled
- objects hit
- baseline
- speed
jsunthon
We'll be visiting Dr. Finley's Lab at (room G36) of the Center for the Health Professions (CHP) building at 1540 E. Alcazar St. This is a great opportunity to ask the following questions:
1)Could create a repository under the lab's GitHub account and invite us to it? everyone should provide their GitHub.com email address at that time....my email is jsunthon@gmail.com
2) Dr. Finley mentioned having already created a free AWS account. This is the AWS account for which we will host our backend services. Could he create an organization, then invite us to it (via supplying our email addresses)?
https://aws.amazon.com/premiumsupport/knowledge-center/get-started-organizations/ ...sign in, click on the username on top right, then click my organizations...create..then "add account"...then enter each persons email and an invite will be sent.
3) Get an idea for the communication cycle...will communications go from the VR headset -> Desktop Computer -> our microservices? Just want to get an idea of if it's the VR headset that is making the network calls or is it instead saving it temporarily to hard disk to a local desktop, and then that desktop make schedule archivals of the data via network calls to our bandend services.
4) What is the structure of the data (s) that needs to be stored? We'll be using JSON format as the input so this is important.
For example, if every second, the VR headset wanted to send the heart rate per second, it would send a request with a payload to us via HTTP network calls
{ "heartRate": 45 }it might do this N times, one for each heart rate record / event we received, and we would store it in the database.
It is possible that it might send N other properties besides heart rate....for example, there might be a module in the head set that monitors property Y and another module that handles property Z.
We can make an HTTP endpoint (URL) for each property (like to handle the heart rate above),
or just a single URL that takes in all the properties where the event might look like
{ "heartRate": 45, "X": SOME_VALUE, "Y": SOME_OTHER_VALUE }they are currently saving user profile into local mysql database
they've no idea how the sensor data is formatted because it has never been saved. might be a fixed schema as specified by oculus vr.
5) How much data needs to be stored? Get an idea of the sampling rate..like is it recording 1000 events per second?
6) Do we need to built some sort of data querying service? If so, what kind of special queries are desired? For example, do we want heart rate over time, over X days, ect?
7) Do users log in via some user interface before using the headset? If they don't do so now, will they in the future?
This is important because it'll help us design our authentication / authorization microservice, if it is even required.
*8) Is the stored data READ-ONLY? In other words, once a value X is saved at a given time, would it ever change?
9) Do we want a URL to enable the downloading of stored data in .csv or some other text format?
** TBD.
10) Will this data ever be deleted? If so, how often? Should this be on an automated schedule and/or should the user be able to manually delete the data somehow?
11) Do we need backups of this data?
12) Any other required features besides just storing / viewing data?