iTrace-Dev / iTrace-Eclipse

Eclipse plugin to identify textual and interface elements based on iTrace Core gaze data
GNU General Public License v3.0
5 stars 2 forks source link

Plugin needs to write XML to correct path #8

Closed dtg3 closed 5 years ago

dtg3 commented 6 years ago

Output path information is provided by the Core via socket when "Start Tracker" is clicked. This needs to be the location where the plugin writes out the XML data.

File name should be: eclipse_[sessionid].xml

Example: eclipse_1525791821.xml

Core manages directories named after the session id, so the last part of the output path is the session id.

Examples:

cabryant20 commented 6 years ago

I've made an adjustment to how the plugin XML is written out. The event id string was being written out in place of the trackerTime, which is needed to match the individual gazes. This is fixed and the trackerTime is no longer divided by 1000, this is to keep the same level of accuracy as the XML file generated by the core.

ashwin9999 commented 6 years ago

Is this issue tested out? @cabryant20

shbonita commented 6 years ago

@cabryant20 I thought we wanted the event id to be written out and not tracker time. We are joining by event id. @dtg3 can you confirm?

dtg3 commented 6 years ago

The problem is that event_time (the unique ID that links core and plugin data) was being written like this:

event_time="C:/Users/cbrya/Documents/Git/samples\mouseTest1\001\1526490384"

This is just the output file path, and every response has the same event_time text for the session meaning none of them can be mapped to core data. I have not confirmed what event_time stamp is now being used, but it MUST be whatever is sent from the core to the plugin or the data cannot be linked. I think that the confusion is due to the eclipse code variables not use the same nomenclature. So "tracker time" in this instance might be the event_time provided by core. Again, this needs verification to make sure it is working again.

shbonita commented 6 years ago

If it is using different nomenclature then we should change it. Could someone please make sure both mean the same thing in Core and Plugin when we refer to event time?

ashwin9999 commented 6 years ago

I'll rename those. @shbonita

shbonita commented 5 years ago

@ashwin9999 are we okay with closing this issue?

shbonita commented 5 years ago

This has been tested.