@@ -56,4 +56,7 @@ so that all data generated during debug runs is removed and the study startes wi
...
@@ -56,4 +56,7 @@ so that all data generated during debug runs is removed and the study startes wi
* You can start study maps directly (for debugging) once you have started on the setup map once and the system picks the first condition for the last participant that is situated on the map you started to choose the appropriate factor levels etc.
* You can start study maps directly (for debugging) once you have started on the setup map once and the system picks the first condition for the last participant that is situated on the map you started to choose the appropriate factor levels etc.
* You can create a bunch of study runs for different participant IDs, to check whether the setup works as expected, use this section in the StudySetup actor: \
* You can create a bunch of study runs for different participant IDs, to check whether the setup works as expected, use this section in the StudySetup actor: \
Put in the number of runs to generate and click the button, then you can find the ``Participant_[i].json`` files at ``StudyFramework/StudyRuns`` and it also creates a ``GeneratedDebugRuns.txt`` file there which helps to inspect multiple runs as concise as possible.
* Put in the number of runs to generate and click the button
\ No newline at end of file
* You can find the ``Participant_[i].json`` files at ``StudyFramework/StudyRuns``
* It also creates a ``GeneratedDebugRuns.txt`` file there which helps to inspect multiple runs as concise as possible.
* You can exlude factors which you don't want to show up in the ``GeneratedDebugRuns.txt`` file by adding their names to ``ExcludeFactorsFromGeneratedRunsTable``. This is only meant to increase readability of the ``GeneratedDebugRuns.txt`` file and will change nothing else.