| ... | @@ -44,11 +44,13 @@ for filename in os.listdir("./"): |
... | @@ -44,11 +44,13 @@ for filename in os.listdir("./"): |
|
|
<br>
|
|
<br>
|
|
|
<br>
|
|
<br>
|
|
|
|
|
|
|
|
* I lost some data in the phase data tables due to whatever reasons during study execution.
|
|
|
|
|
> If you lost data because of selecting "Restart Study" or accidentally restarted a condition, for which data has already been collected, see below. If you lost data another way: Fortunately everything is logged redundantely also per participant, so you data can most probably be recovered. Here is a script that, when placed in the ``StudyFramework`` folder should do the trick. Maybe you need to adapt parts, since it was developed and tested for one specific study setup. SO CHECK YOUR DATA CAREFULLY! [ReconstructPhaseTablesFromParticipantLogs.py](uploads/a97f6c3b8caebd3c21b9ae6c903a6314/ReconstructPhaseTablesFromParticipantLogs.py)
|
|
|
|
|
|
|
|
|
|
* I accidentally restarted the study or restarted a condition
|
|
* I accidentally restarted the study or restarted a condition
|
|
|
> Whenever a condition or the entire study is restarted, a backup of the changed/deleted files can be found under `StudyFramework/StudyLogs/RecyclingBin`. To recover the files, stop running the study, then choose the appropriate timestamps, copy/paste the files from the recycling bin back into the `StudyFramework/StudyLogs`-folder, replacing the edited files, if necessary. You can then start the study again.
|
|
> Whenever a condition or the entire study is restarted, a backup of the changed/deleted files can be found under `StudyFramework/StudyLogs/RecyclingBin`. To recover the files, stop running the study, then choose the appropriate timestamps, copy/paste the files from the recycling bin back into the `StudyFramework/StudyLogs`-folder, replacing the edited files, if necessary. You can then start the study again.
|
|
|
|
|
|
|
|
|
* I lost some data in the phase data tables due to whatever reasons during study execution.
|
|
|
|
> If you lost data because of selecting "Restart Study" or accidentally restarted a condition, for which data has already been collected, see above. <br> If you lost data another way: Fortunately everything is logged redundantely also per participant, so your data can most probably be recovered. Here is a script that, when placed in the ``StudyFramework`` folder should do the trick. Maybe you need to adapt parts, since it was developed and tested for one specific study setup. SO CHECK YOUR DATA CAREFULLY! [ReconstructPhaseTablesFromParticipantLogs.py](uploads/a97f6c3b8caebd3c21b9ae6c903a6314/ReconstructPhaseTablesFromParticipantLogs.py)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Eye tracking does not work - Error 1036
|
|
* Eye tracking does not work - Error 1036
|
|
|
> Make sure you are using a Vive Pro Eye and also an appropriate adapter box. Older adapter boxes (for Vive Pro 1) do not support eye tracking and while the HMD will work, eye tracking will not. |
|
> Make sure you are using a Vive Pro Eye and also an appropriate adapter box. Older adapter boxes (for Vive Pro 1) do not support eye tracking and while the HMD will work, eye tracking will not. |
|
|
|
\ No newline at end of file |