This section holds a detailed example of various implementations of a coding project that involves Tasks, multiple subjects, and several variables to rate per subject and task.
There is a wide range of possible implementations, and the solutions provided can be applied to many other types of projects. What suits you best depends on your study's scope, the number of different ratings, and your rating process, to name just the most prominent influences.
How complex your setup and coding process will be, depends on the complexity of the observations you are aiming at.
Every setup explained can be tweaked to your needs and probably combined with other approaches. These are all just EXAMPLES of presumed situations.
In each example, we explain the basics of the required Code Definitions and provide a possible Data Structure example. A short Coding Process description should enable you to get going.
Because each project is different, you probably need to alter, expand, and combine parts of the examples collected here.
Use these examples as an inspiration to make the best of all possibilities INTERACT has to offer:
 | Rate Once per Task and Subject - This first example presumes you need to rate each variable for each subject only once per Task. It is a relatively simple implementation that presupposes that all Tasks start and end at the same time for all participants. Therefore, we can log the time information for each Task only once and duplicate these Events for each participant. The example includes two different approaches, showing you how to rate your variables all in a predefined sequence or on demand, whenever they occur. |
| Rate per Activity and Subject - A bit more complicated from a coding point of view is a situation where each participant is working at its speed, which means that both duration and start time for each task can be different among your participants. |