System requirements for using the iTrace Eclipse Plugin are the same as the requirements for the eye tracker you intend to use. Please refer to your tracker vendor's documentation for exact specifications.
Help → Install New Software
Help → About Eclipse → Installation Details
This iTrace Eclipse plugin requires iTrace Core v0.1.0 to be downloaded and installed before you use the extension.
For help with installing the iTrace Eclipse plugin, please read the Installing the iTrace Eclipse Plugin document for instructions.
If the iTrace Eclipse Plugin window is not visible, you can open it using the following steps:
Window → Perspective → Open Perspectiveand click
Open Perspective Menuselect
iTrace Eclipse Pluginfrom the list of available perspectives
If you have changed the Socket communicate port number in the iTrace Core application, you will need to set the iTrace Eclipse plugin socket to listen for data on the same port number. You can edit the socket port number setting using the following steps:
iTrace Eclipse Plugin
Connect to Corebutton is clicked on the iTrace Eclipse Plugin. If iTrace Core and the iTrace Eclipse Plugin socket port values are not the same, the tools will not be able to communicate.
With the iTrace Core open, the iTrace Eclipse Plugin can be connected by clicking the
Connect to Core button found on the iTrace Eclipse Plugin window. When the iTrace
Eclipse Plugin is successfully connected, the button text will change to
NOTE: iTrace Core must be running before attempting to connect the iTrace Eclipse Plugin and both applications must be using same socket port setting value.
To start a tracking session, ensure that the iTrace Eclipse Plugin is connected and then click the
Start Tracking button on the iTrace Core application. When the session is complete,
Stop Tracking on the iTrace Core application. If you intend to start another
tracking session, it is NOT necessary to disconnect the iTrace Eclipse Plugin from iTrace Core. A
new session can be started by clicking
Start Tracking again on iTrace Core.
When you are completely finished with data collection from
your subject, stop the tracker using the
iTrace Core application and then click
Disconnect on the iTrace Eclipse plugin.
NOTE: Closing Eclipse without disconnecting will leave you with invalid XML.
highlight tokens feature highlights the source code tokens being viewed on the
screen in real
time while tracking. This feature is not intended for use during an actual study and is only
intended as a demo feature.
All data generated by the iTrace Eclipse Plugin is stored in an XML format. Each file name begins
itrace_eclipse_ and ends with a UTC Unix format timestamp in milliseconds to
indicate the start of the session. This timestamp is used to pair plugin data with the corresponding
iTrace Core data.
An example output file would look something like this:
<itrace_plugin session_id=""> <environment screen_width="" screen_height="" plugin_type="" /> <gazes> <response event_id="" plugin_time="[timestamp_milli]" x="" y="" gaze_target="" gaze_target_type="" source_file_path="" source_file_line="" source_file_col="" editor_line_height="" editor_font_height="" editor_line_base_x="" editor_line_base_y="" /> ... </gazes> </itrace_plugin>
session_id→ unique identifier for a recording session
screen_width→ width of display in pixels used for the study
screen_height→ height of display in pixels used for the study
plugin_type→ plugin used to record gaze data
event_id→ synchronizing id from core data (provided by Core)
plugin_time→ timestamp for data being recorded by tracker as a UTC Unix style timestamp in milliseconds
x→ screen based x coordinate (provided by Core)
y→ screen based y coordinate (provided by Core)
gaze_target→ UI element or source code file under gaze
gaze_target_type→ type of source code file or UI element
source_file_path→ file path of open source code file under gaze
source_file_line→ line in open source code file under gaze
source_file_col→ col in open source code file under gaze
editor_line_height→ size of editor line
editor_font_height→ font height in editor
editor_line_base_x→ line base x in editor
editor_line_base_y→ line base y in editor