Comments (11)
We should disallow NAs as a looking target, but not discard them (because we need them to calculate time until first look).
If we want to include within-AOI fixation shifts, we would need a better definition of what counts as a fixation shift (some tolerance on the x and y positions?)
from mb2-analysis.
The topic whether we want to process data into fixations came up a few times in the past, but was so far always postponed to later/exploratory analyses. So the main focus is on unprocessed raw data. I should try to keep it that way. Regarding the definition from the RR: it works for some, but not all patterns, as you already mentioned, @mzettersten:
I am listing locations before anticipatory period, first look (at least 150 ms) in anticipatory period, and how it can be classified:
-
other, target -> correct
-
other, distractor -> incorrect
-
only other-> incorrect
-
distractor, target -> correct
-
distractor, other -> incorrect
-
only distractor -> incorrect
-
target, other -> incorrect
-
target, distractor -> incorrect
-
the problem: only target -> incorrect
I think it would be more accurate to define "only target" as correct. Do you agree? Does this work? We would then have to document this deviation from the preregistration. The argument is that we can not run this analysis without converting the data into fiaxations and saccades.
from mb2-analysis.
Started working on this, first stab at a function is now added!
from mb2-analysis.
@tobiasschuwerk: could you take a quick peek at the issue above before the next hackathon se we can pick up the conversation?
from mb2-analysis.
Additional question: how do we handle NAs at onset - probably we need to ignore them rather than treat them as separate "fixations"??
from mb2-analysis.
Yeah, I think we would need to process the data into fixations in general - but I sort of think we probably don't want to go that route, given thatit isn't really in the registered report and it would involve a more intense transformation of the data?
from mb2-analysis.
-
I agree that it would make sense to treat first looks that just stay on the target ("only target") as valid looks for the primary analysis (we can always look at it both ways).
-
I think we only want to count looks to either the target or distractor/ AOI exits as a first look, based on my reading of the Registered Report (and I think this makes sense in general). Here's the text I'm looking at:
First saccades will be determined as the first change in gaze occurring within the anticipatory time window that is directed towards one of the AOIs. The first look is then the binary variable denoting the target of this first saccade (i.e., either the correct or incorrect AOI) and is defined as the first AOI where participants fixated at for at least 150 ms, as in Rayner et al. (2009). The rationale for this definition was that, if participants are looking at a location within the tunnel exit AOIs before the anticipation period, they might have been looking there for other reasons than action prediction. We therefore count only looks that start within the anticipation period because they more unambiguously reflect action predictions. This further prevents us from running into a situation where we would include a lot of fixations on regions other than the tunnel exit AOIs because participants are looking somewhere else before the anticipation period begins.
A few reasons to not count looks to somewhere other than the two tunnel exit AOIs as first looks (other than I think this would represent a deviation from the registered report) is that if we count looks to "other" as valid first looks, it makes it difficult to identify a chance level (looks will predominantly be classified as "incorrect"), and it mixes together many different types of responses (e.g., shifts in looking between AOIs, delays in shifting towards the AOIs, moments of inattention, checking back to the tunnel beginning, etc.) as "incorrect", which would make any analysis much more difficult to interpret, in my opinion. But I might be thinking about this the wrong way?
So my reading is that we treat the first look as the first time infants land on the "target" or "distractor" tunnel exit AOI for at least 150 ms, within the anticipatory window. And then we just need to decide if the infant staying on the target/ distractor "counts", as discussed in (1).
from mb2-analysis.
@mzettersten : I totally agree, only count looks to either the target or distractor/ AOI exits as a (relevant) first look. I just listed all possible combinations, mostly for myself to sort things in my head;).
And: I vote for staying on the target/ distractor "counts"
from mb2-analysis.
Gotcha gotcha perfect! Maybe let's touch base about this one more time on Friday
from mb2-analysis.
Did some more work on this, incorporating some code improvements from @alvinwmtan and introducing the distinction between first valid look and first "shift" to a valid location, ignoring NAs. I think there is still some discussion needed about the NA issue.
One piece of good news is that it seems that the "first valid look" vs. "first valid shift" distinction makes very little difference in practice!!
from mb2-analysis.
Resolved remaining discussion points in the previous hackathon. There's still some work to do in terms of computing first looks for familiarization trials and adding the preregistered Bayesian analyses, but I'm going to close this issue now given that we've finalized the main function for computing first looks.
from mb2-analysis.
Related Issues (20)
- Diagnose eyetracking coordinate issues HOT 1
- Diagnose eyetracking timestamp issues HOT 1
- add participant to webcam eye-tracking data HOT 1
- Fix eyelink x-y coordinates HOT 2
- Document columns used for eye-tracking coordinates (and maybe other key decisions?) HOT 2
- diagnose issues for labs with unusual heatmap distributions HOT 13
- Diagnose issues for labs that did not make it to 005
- Add a function to pull metadata from Google Sheets HOT 1
- diagnose issues with labs with unusual looking score graphs HOT 3
- check x/ y coordinate rescaling in create_aoi_timepoints HOT 12
- MB2P: check pupil sizes for all labs
- Filtering session errors HOT 2
- Incorrect test trials for childdevlabAshoka_41A-adults HOT 3
- output a pre-exclusion full dataset in 006_exclusions.Rmd HOT 1
- exclusion reporting at the end of 006_exclusions.Rmd needs some clean-up HOT 2
- check on a few puzzling cases of missing data towards the end of the pipeline HOT 3
- Why is condition missing for some participants at the end of 005? HOT 2
- fix/ unify native language tracking in demographics
- figure out what to do with "NR-adults" participants
- cross check exclusion reporting in the paper against updated exclusion code in 006
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mb2-analysis.