eyetrackingR: Eye-Tracking Data Analysis

[rociojoo]

Are you the author of the package?

No

Is the package on a specific repository?

CRAN

Please provide the URL of the package repository

https://cran.r-project.org/package=eyetrackingR

Is there a dedicated website for the documentation (e.g. a pkgdown website)?

http://www.eyetracking-r.com/

If you are the author of the package, does it pass CRAN check tests?

Yes (package on CRAN).

Additional information

Briefly, can you describe the purpose of this package and how it fits into the Tracking CTV?
I actually think it doesn't, because I haven't found anything to deal with x, y axes. They use observations of given objects but not positions. I'm opening the issue so that I don't have to wonder about this package again.

In terms of the tracking workflow (see Figure in the CTV), where does the package fit? (Feel free to mention any particular functions and how they fit as well.)

[rociojoo]

We have a section of movement but not tracking data. Should we consider it as a candidate for that section, @basille ?

[basille]

Is that even movement to start with? I'm not sure I get it. See: https://cran.r-project.org/web/packages/eyetrackingR/vignettes/preparing_your_data_vignette.html

[rociojoo]

It comes from movement, since there has to be previous following of gaze, areas of interest, and so on. https://imotions.com/blog/10-terms-metrics-eye-tracking/
It's an area I'm not familiar with. I also have doubts which is why I'm asking.
But I didn't see any manipulation of tracking data in any example.

[basille]

Might be worth asking the devs how they feel about it?

[samhforbes]

Hi both,
Sorry it's a hard one for me to weigh in on without knowing the full aims of the tracking CTV, but for full information: while the package largely deals with whether the infants were fixated in an area (so binary outcome data) there are functions that turn the XY gaze location values on the screen into whether or not these land in an area of interest. So that may fall under your purview?

[basille]

Hi @samhforbes, thanks for your answer — and sorry about the long delay. We've been more than busy dealing with other tasks, and to be completely honest, this causes us a bit of a dilemma. So let me ask for more clarification: For those functions related to the search of areas of interest, does the package rely on tracking data (i.e. (x,y,t)) or simply spatial data (x,y)? That would already settle whether this falls under the definition of a tracking package. Otherwise, it could indeed belong to the "movement but not tracking data" section.

@rociojoo, are all the eye movement packages that we've encountered still in open issues? We haven't concluded on any of them yet? Shall we have a specific bullet point for eye movement in the aforementioned section?

[samhforbes]

There are a couple of functions that convert (x,y,t) data into binary in/ not in AOI per time data (T/F, t).
I can understand this is a bit of a dilemma, and as I say, I guess it depends on the goals of the CTV. I'm happy with whatever you decide.

[basille]

Thanks for the clarification! Let's see what @rociojoo thinks about it — we have other non-organismal movement packages (for eyes or computer mouse movement), we may as well include them all together.

I'm leaving this issue open until we figure this out.

[rociojoo]

@samhforbes thanks for your reply! Sorry for my long delay.

@basille , in the other eye tracking packages, unless I've mentioned it in the issue, have a time component, so it can still be movement.

@samhforbes could you please point us to the functions that convert (x,y,t) data into binary in/ not in AOI per time data (T/F, t)?

@basille since we haven't separated any other type of data into special categories (GLS, PTT, etc.) but rather mentioned that the package works with a certain type of data, I'd like to keep the same logic for eye packages.

[rociojoo]

@basille I haven't added this package to the table—until we figure things out.

[basille]

The function dealing with spatial coordinates is add_aoi. Given the limited focus on spatial coordinates, I suggest to include this package in Dealing with movement but not tracking data > Non-biologging data.