More info
and then Run anyway
to begin installation.
Add or remove programs
iTrace-Toolkit
in the list of installed programsUninstall
iTrace Toolkit v0.1.0 is only compatible with data generated by version 0.1.0 of iTrace Core, iTrace Visual Studio Plugin, and iTrace Eclipse Plugin. Data generated by older versions of these tools are NOT COMPATIBLE.
In order to perform post processing on your iTrace XML data files it is necessary to create a new
sqlite database or open an exiting database. To create a database click the
Create New Database
button on the Database window tab. In the new window that opens you can browse for the directory to
save the database and enter a name for the file. If you already have a sqlite database file, you can
click the Browse for Existing Database
button and the Database window tab and use the
file browser
to locate your database.
Once you have chosen to create a database or browse for an existing one, simply click
Load Database
to open and prepare the database for use.
With the database loaded, choose the Import XML window tab to begin importing iTrace Core or Plugin
XML data files. Simply use the Browse for iTrace XML
button to launch the file browser
and select
your input file. With a file selected, you can then click the Import XML Data
button to
import the
data into your database file. This will need to be repeated for each file you wish to import, but
only needs to be done once per database file. To avoid duplicate imports of XML data files, each
import file will be compared against a hash value (SHA 1) of existing imported data files and reject
any file hash that matches a previously imported file.
If you have srcML format XML documents of the source code used during a study, it is possible to use the Token Analysis window tab to automatically have source code token information added to your database file. To load a srcML file for token analysis, use the Browse for srcML Archive button to located your srcML file and click Identify Tokens to begin mapping tokens to gazes in the database.
To perform token analysis tasks with iTrace Toolkit it is necessary to provide an XML marked up
version of the source code under study using srcML (v1.0 or higher only). This can be done with the
following command: srcml [source code] --position -o output.xml
In the command above,
source code
can be individual files, a directory, a compressed archive, or any combination of the three. The
position option addes details concerning line and column information of the original source code. If
there are issues with position data encoded into the output XML such as invalid positions, you can
supplement the above command with the option --jobs 1
which may resolve the issue. For
additional
information about srcml, please visit https://www.srcml.org/
To perform fixation calculation on your dataset, select the Fixation
window tab. The
fixation
algorithm dropdown list contains the three currently supported fixation approaches. Selecting an
algorithm changes the parameters that can be configured for fine tuning the algorithms. Clicking
Generate Fixation Data
to run the fixation algorithm. All fixation runs are recorded in
the same
database for later querying/analysis. Fixations are currently run in groups based on the session
(all gazes recorded between the start and stop of a tracker using iTrace Core).
iTrace Toolkit can output HTML versions of the source code with tokens associated with each fixation highlighted. This is done per fixation calculation and output into a folder named after the ID number of the fixation processing run (timestamp recorded by iTrace Toolkit).
Some tasks such as token analysis are computationally expensive. The UI will be unavailable for
interaction until the processing task is finished. Completion of a processing task is indicated by
the status bar of the application displaying the text Ready
.
gaze
attributes:
Table used to contain all gazes captured
event_time
→ unique id for each gaze recorded by the tracker (Windows OS file
time resolution)session_id
→ referencing the session during which the gaze was captured
(generated by iTrace)calibration_id
→ id referencing the calibration used when gaze was captured
(generated by iTrace)participant_id
→ id referencing the participant who provided the gaze data
(user defined)tracker_time
→ time of gaze as given by the trackersystem_time
→ time of gaze as given by the OS system clockx
and y
→ horizontal and vertical screen coordinates of the gaze
(calculated by iTrace)left_x
and right_x
→ horizontal offset value of the left and
right eye provided by the trackerleft_y
and right_y
→ vertical offset value of the left and right
eye provided by the trackerleft_pupil_diameter
and right_pupil_diameter
→ diameter of the
left and right eye provided by trackerleft_validation
and right_validation
→ validation value for the
left and right eye data provided by trackeruser_left_x
and user_right_x
→ real world horizontal position of
user's left and right eye with respect to the tracker's positionuser_left_y
and user_right_y
→ real world vertical position of
user's left and right eye with respect to the tracker's positionuser_left_z
and user_right_z
→ real world distance of user's left
and right eye from the trackersession
table:
Table used to contain details about a recording session. Starting tracking with the Core always creates a new session.
session_id
→ unique id value of a tracking session (generated by iTrace)participant_id
→ id referencing the participant in the tracking session (User
defined)screen_height
and screen_width
→ height width of the display used
by the participant (display set as
Primary
in Windows)
tracker_type
→ model type of the eye tracker usedtracker_serial_number
→ serial number of the tracker usedsession_date
and session_time
→ Unix timestamp representing the
date and time of the tracking session
screen_recording_start
→Unix timestamp representing the system start time for
recorded videotask_name
→ user defined name of the task/study a participant is performing
fixation
table
Table used to contain calculated fixations
fixation_id
→ unique id for the calculated fixation (generated by iTrace)fixation_run_id
→ id referencing a particular run of the fixation filters
(generated by iTrace)fixation_event_start_time
→ event time of the first gaze that belongs to this
fixationfixation_order_number
→ order of the fixation with respect to all fixations
from a session of collected datax
and y
→ calculated horizontal and vertical screen position of
the fixationfixation_target
→ file where the fixation liessource_file_line
and source_file_col
→ source file line and
column that represents the fixationsyntactic_category
→ syntactic context of the token (represented as a
hierarchy)xpath
→ XPath navigating to the token in the srcML version of the source code
left_pupil_diameter
and right_pupil_diameter
→ diameter of left
and right pupil during fixationduration
→ duration of the fixationfixation_run
Table:Table used to data for a particular run of a fixation algorithm
fixation_run_id
→ unique id representing a run of a fixation filter (generated
by iTrace)session_id
→ id referencing the session data this fixation run processeddate_time
→ Unix timestamp when the data was generatedfilter
→ fixation filter and settings used (comma separated)fixation_gaze
Table:Table for a many to many relationship mapping gazes with their fixations
fixation_id
→ id referencing a fixationevent_time
→ id referencing a particular raw gaze data pointcalibration
Table:
Table used to contain a full calibration and information
calibration_id
→ unique id to represent a calibration activity as a Unix
timestamp (generated by iTrace)calibration_point
Table:
Table used to contain all calibration point data provided by the tracker
calibration_point_id
→ unique id representing a specific point used for
calibration (generated by iTrace)calibration_id
→ id referencing a given instance of a calibration eventcalibration_x
and calibration_y
→ horizontal and vertical
position being used for the calibration by the trackercalibration_sample
Table:
Table used to contain samples used to determine calibration for a calibration point
calibration_point_id
→ id referencing a given calibration pointleft_x
and right_x
→ horizontal position of the left and right
eye observed by the trackerleft_y
and right_y
→ vertical position of the left and right eye
observed by the trackerleft_validation
and right_validation
→ Validation of left eye
dataide_context
Table:
Table used to contain information pertaining to an IDE used during a session
event_time
→ id referencing a recorded gaze eventtime_stamp
→ Unix timestamp when the data was processed by the IDE pluginide_type
→ name of the IDE plugin providing the datagaze_type
→ name of the file being observedgaze_target_type
→ file type (extension) being observedsource_file_path
, source_file_line
and source_file_col
→ path, line, and column of the source file being observededitor_line_height
→ height of a line set in the editoreditor_font_height
→ height of the font set in the editoreditor_line_base_x
and editor_line_base_y
→ base x and y
positions of the line in the editorsource_token_type
→ WORK IN PROGRESS
source_token_xpath
→ XPath navigating to the token in the srcML version of the
source codesource_token_syntactic_context
→ syntactic context of the token (represented
as a hierarchy)web_context
Table:
Table used to contain information pertaining to a web browser used during a session WORK IN PROGRESS
event_time
→ id referencing a recorded gaze eventbrowser_type
→ browser use to capture plugin dataurl
→ URL of the site being observedtag
→ HTML web element tagfiles
Table:Table containing information on those files who's data has been added to the database already
file_hash
→ hash value for imported iTrace XML data filefile_full_path
→ path of the iTrace XML data importedparticipant
Table:
Table containing participant ids
participant_id
→ anonymous id for the participantCopyrights © 2022 - SERESL, All Rights Reserved.