Episodes
Model runs within a group can be organized into episodes. Episodes contain team assignments called worlds.
Episodes are represented in the Epicenter UI as run configurations.
Why episodes are important
Here are some example use cases.
Group runs by day
A common use of episodes is to group together runs played on a particular day:
- The facilitator will start a new episode and assign users to worlds.
- The participants will then do a set of runs, which the facilitator can review.
- On a different day, the facilitator will start a new episode, create new worlds, and the participants will do a new set of runs.
The advantage of using episodes in this scenario is that the facilitator can choose to view data separately for each episode. The data can include participant results, world assignments, and vault records tied to the episode.
Assess participant progress
Another common use case is to compare participant results before and after instruction. In this scenario:
- A group has an episode of runs.
- There is an instruction session.
- Another episode of runs to practice or test what the participants have learned.
A facilitator could assign the participants to worlds for the duration of an episode. For another episode, the facilitator could reassign teams and compare results across the two episodes.
Episodes are managed with the Episode adapter.
To see an example of how episodes are implemented in an application, see the Episodes tutorial.