Should go past time scan path analysis take long fixations into consideration?

[jjarosch]

While comparing the output of sideeye to that of EyeDry, I noticed that apparently EyeDry took fixations excluded for length into consideration for the start and end of the go past scan path.

With sideeye I observed cases where a fixation excluded for length (> 800ms) in the post-target region did not terminate the go past scan path, and (what might be considered) a ‘second pass’ through the target region was included in the go past.

Based on this, I wondered whether it would be sensible to only exclude long/short fixations from go past duration sums, but take them into consideration for the scan path?

Alternatively – is this behaviour documented? If it remains unchanged, I will adjust the cutoff settings to include long fixations.