(This may seem redundant but recall that Session is meant to abstract over blocks. Block takes a path to a specific experiment administration as an argument, whereas Session takes a path to a participant's folder and loads all the blocks contained therein. Session operates at the participant level. BTW, Task is the next level of abstraction, taking as its argument a folder full of participant folders.)
With Session, the trials in the second block are renumbered.
There's no good reason to keep this behavior around. The ordering does not reflect the ordering which the participant saw items (Block1 is always ordered before Block2). It also makes it harder to isolate specific trials in blocks.
Let's load two Blocks of eyetracking from the same participant with
Block
and then alternatively withSession
.(This may seem redundant but recall that
Session
is meant to abstract over blocks.Block
takes a path to a specific experiment administration as an argument, whereasSession
takes a path to a participant's folder and loads all the blocks contained therein. Session operates at the participant level. BTW,Task
is the next level of abstraction, taking as its argument a folder full of participant folders.)With
Session
, the trials in the second block are renumbered.There's no good reason to keep this behavior around. The ordering does not reflect the ordering which the participant saw items (Block1 is always ordered before Block2). It also makes it harder to isolate specific trials in blocks.