01
Defined native paths
Tobii HDF5 and EyeLink ASC are read through dedicated import paths.
03 / Analyze · Cross-vendor Import & Project Interoperability
Bring the recording. Inspect the mapping.
Iriscope combines defined native import paths with guided table mapping, so eye-tracking exports can enter a consistent analytical project without hiding their structure, coordinate system or prerequisites.
The capability
What you can inspect and control.
Use this workflow for the part of the research question it addresses.
02
Guided table import
CSV and TSV files are inspected for encoding, delimiter, structure and compatible field mappings.
03
Known formats first
Profiles support Tobii Pro Lab tables, Pupil Labs, SMI BeGaze and EyeLink Data Viewer exports.
04
AOIs travel with projects
PeriTag projects can provide their stored AOI sets, names, tags and timing context.
In the application
A workflow you can follow.
Keep the relevant material, definitions and review decisions connected at each step.
- Select a native recording, an ASC file, a known table export or a tabular CSV/TSV source.
- Review detected encoding, delimiter, available fields and any recognised import profile.
- Confirm or adjust the mapping for gaze, timestamps, participant and stimulus identity, events, pupil data, validity and geometry where available.
- Check the import summary before the project calculates its analytical layers.
- Continue with a project that keeps stimuli, selected data, AOIs and analysis state together.
Method context
Keep the scope of the result visible.
The relevant settings, prerequisites and interpretation stay attached to the workflow.
Method settings, scope and interpretation
Use formats deliberately — not by pretending every export is identical.
Tobii HDF5 recordings have a dedicated path. Tobii Pro Lab TSV/CSV exports can be recognised through the table-import workflow, including their relevant pupil and event fields when present.
EyeLink ASC has a native importer; table profiles support common Pupil Labs, SMI BeGaze and EyeLink Data Viewer exports. A non-standard vendor variant can still require mapping review.
Where the necessary fields exist, Iriscope can map a tabular export. The aim is a transparent input basis, not an unsupported promise that every file can be interpreted automatically.
Bring AOI work into the analytical project.
PeriTag is not a separate visual dead end. Its project import can bring stored AOI sets and their names, tags and time information into Iriscope, where those definitions remain part of the analysis context.
Compatibility is verified at the data level.
Iriscope does not claim that every proprietary export is automatically comparable. It supports defined readers and guided mappings, then makes the available fields and input choices inspectable before analysis proceeds.
Connect the workflow
Bring this capability into your study.
Tell us about the material, recording and result you need to inspect. We can identify the appropriate product and method scope.