EXPORT Behavioral Data > Interval-based Export

This section describes how you can transform Event-based data into interval-based data!

This is especially useful for further data processing that requires interval-based data, while you collected your data as it occurred using event-based coding.

IMPORTANT: In case you select multiple DataSets make sure the selected DataSets do NOT overlap in time!

Before you can perform the interval export for multiple overlapping DataSets at once, use the command Concatenate DataSets, to remove all gaps and overlaps between DataSets.

The Principle of Interval based Export Routines

In all cases, it works like slicing up a loaf of bread.

Presume that the current content (all visible codes) of the Timeline Chart is your bread. The length of you bread is determined by the total length covered by the time borders of the selected DataSets.

The thickness of your slices is set by the interval width on the Grid tab of the TLC options.

In this sample, the grid is set to 2 seconds, the most accurate results are achieved if you use slices of just 1 frame.

During the export, you start cutting of slices from the very start of the Timeline Chart. Each slice is represented by a single line in the export file.

In the Timeline Chart, the slices look like this:

Note: In case of overlapping Events, across DataSets as well as within, all data is accumulated, and only the first Code found in an interval is counted.

Content per Slice

Per default, a Code is exported whenever it covers at least 50% of the duration of the interval length (= one slice).

If you want to export every occurrence of a Code the moment it is detected within a 'slice', you need to adjust this percentage. Same thing, if you only want to count Codes that cover an interval completely.

Note: You can specify the % of coverage per slice during the export process.

Obvious Issues

•If no Codes are available in the first slices, because e.g. the start time of the DataSet is set to 00:00:00:00 but your first event is only logged after 10 seconds or so, you get many lines showing just 0 for all columns.

•If there are gaps between Events or between DataSets, you get lines showing only 0.

•If the time information of different DataSets overlap in time, maybe because they are based on different video files, multiple codes are counted as one!
This is because they fit inside the same time-'slice' when displayed in the Timeline Chart.

INTERACT does have of course solutions for all issues:

Remove 'Empty' Lines

To get rid of the unneeded 'empty' lines at the start and/or the end of your DataSets:

▪Click Transform - Time Values - Set Borders .
This command adjusts the start and end time for all DataSets, to exactly include all Events. For further details read Using DataSet Time Borders.

Remove overlaps AND Gaps between DataSets

To ensure that none of the DataSets overlap in time and to remove all gaps between DataSets:

▪Select Transform - DataSets - Time Shifts > Concatenate .
This command virtually queues all DataSets in the order of appearance. For further details read Move DataSets Virtually in Time.