RT in pure trials: 490ms
RT in mixed trials: 825ms
Mixing cost: 335ms
RT in task-repeat trials (in mixed blocks): 825ms
RT in task-switching trials (in mixed blocks): 969ms
Task-switch cost: 144ms
Second time (while listening to music --- I decided to do this since I've noticed it somehow decreases my latency in typing tests significantly):
RT in pure trials: 436ms
RT in mixed trials: 673ms
Mixing cost: 237ms
RT in task-repeat trials (in mixed blocks): 673ms
RT in task-switching trials (in mixed blocks): 746ms
Task-switch cost: 73ms
Edit: third time, also while listening to music:
RT in pure trials: 435ms
RT in mixed trials: 608ms
Mixing cost: 173ms
RT in task-repeat trials (in mixed blocks): 608ms
RT in task-switching trials (in mixed blocks): 700ms
Task-switch cost: 92ms
I suspect this "game" is also amenable to practice, and find it at least a bit weirdly addictive in the same way as Flappy Bird.
I don't think this game is all that representative of context-switching overhead, as my 4th attempt gives evidence that this improves quickly with practice:
RT in pure trials: 422ms
RT in mixed trials: 611ms
Mixing cost: 189ms
RT in task-repeat trials (in mixed blocks): 611ms
RT in task-switching trials (in mixed blocks): 602ms
Task-switch cost: -9ms
The "mixed trials" are naturally slower because I'm having to recognise 4 patterns instead of 2, but only by ~50%.
Whoa, a negative task-switch cost! I didn't take it multiple times, but it makes sense that having practice at this specific task probably improves both your overall response times and maybe more specifically improves the different trials.
What I'm curious about is whether we also get specifically good at say, task-switching between a code editor and say, Stack Overflow, over time
