* In `StudyFramework/StudyRuns/Participant_[i].txt` the conditions planned/executed for participant i are stored as json.
* In `StudyFramework/DebuggingLogs/SFLog.txt` all logs generated by the study framework in the last run of Unreal are gathered (mainly for debugging).
### Back-Ups & Redundancy:
* Whenever any data contained in the Phase Tables (csv-files, "Phase_...") is overwritten or deleted (e.g. when a condition for one participant or the entire study is restarted), the files are not actually deleted, they are moved to the `StudyFramework/StudyLogs/RecyclingBin` folder. To recover the files, stop running the study, then choose the appropriate version in the recycling bin, 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. Make sure to check that all data is there and backup the files before replacing them. Potentially, you could also only copy over lines of the files individually to maintain full control.
* As for per-execution logs, i.e. GazeTrackingLogs, ParticipantLogs and PositionLogs, these files will never be overwritten by the Study Framework Plugin, instead unique names are chosen. **Currently, when the study is restarted, these files will be deleted for good. This will be addressed in #99**
* Theoretically, it is also possible to recover the contents of the Phase Tables from the ParticipantLogs (in case something happened to the RecyclingBin...), but this is quite involved, a last resort. For more info on that see the [FAQ-Section](/Trouble Shooting)
* Generally, it is recommended to back-up the `StudyFramework`-folder regularly during study execution, as this folder contains all study data and all of the backups...
# Recording Data
* You can record events happening during the execution (such as interactions done by the participant etc.) using
