You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending the game home with a patient for training, it would be ideal to backup the logged data somewhere in case technical issues come up.
Proposed Solution
This could be solved with a fairly adhoc approach (e.g., installing the game to a automatically syncing dropbox / google drive folder on the patient's computer, or using a tool like rsync or cron), or could be addressed in more formally (e.g., having the game push all saved data to a server after each calibration / gameover).
Thoughts?
The text was updated successfully, but these errors were encountered:
On first thought, I think an adhoc approach is probably sufficient for our case (since we're only deploying with 1-2 patients). Dealing with exceptional cases (like when the user is playing the game while not connected to the internet) might make a more formal approach error-prone.
When sending the game home with a patient for training, it would be ideal to backup the logged data somewhere in case technical issues come up.
Proposed Solution
This could be solved with a fairly adhoc approach (e.g., installing the game to a automatically syncing dropbox / google drive folder on the patient's computer, or using a tool like rsync or cron), or could be addressed in more formally (e.g., having the game push all saved data to a server after each calibration / gameover).
Thoughts?
The text was updated successfully, but these errors were encountered: