B e h a v i o r T r a c k e r
Can I export a session's list of observed records to use in other programs like SAS, or Excel?
You certainly can. You can export the raw data for a single session or multiple sessions all at once (depending on which sessions you have selected in the View program). For information on how to do so, click or follow this link. Please note that the final step to export the data is disabled until you purchase the software.
Why doesn't the Time-Stamp column always match the Latency column?
The time stamp column shows the time that events happened based on your computer clock. So if you clicked on event A and then paused for ten seconds, unpaused and hit even A again, then there will be a ten seconds difference between the second event's time stamp column and its latency (since while the pause button pauses the latency clock, stopping the flow of normal time/space continuum is beyond the scope of this software). Also the milliseconds of each column might add up differently (1.600 seconds + 1.500 seconds leads to 3 seconds and 100 milliseconds where as 1.300 + 1.500 will add up to only 2 full seconds and 800 milliseconds). That is why the milliseconds column is also provided. You can of course use it to do your own rounding.
Why are the Time-Stamp and Latency milliseconds columns off by a few milliseconds?
A 1/1000 of a second is pretty short time. So depending on the speed of your computer, you might see a couple of milliseconds difference between the two since it had taken that long for the computer to process the next line or two of code. So, for example, if the start time is 3:01pm and 500 millisecond and the latency start time of 0 seconds and 000 milliseconds and you pressed Event A about 100 milliseconds after the start of the session, then event A might have the time stamp of 3:01pm and 600 milliseconds but the latency might read 0 seconds and 102 milliseconds. Those 002 millisecond difference is the time it took your PC to process and capture the first clock and to move on and capture the second clock.
It is in general recommended to round milliseconds to the nearest hundred resulting in tenths of a second for accuracy and to account for the reaction time of the human observer to react and click a button, for the computer to process the button's click and the time it takes to process the code to capture the two time stamps. You can of course ignore the milliseconds all together and only use them for rounding to the nearest second (ie you might want to round 12 seconds and 958 milliseconds to 13 if your are going to keep your measurements' accuracy down to the second).
In the media addon (DVRecord) some of my events with duration seem to have mismatched start and ends. This will also result in incorrect sum of a behavior's duration in the Viewer.
The normal Recorder, records in real time, so there is no way to start an event with a duration and then go back in time to end it. The media addon DVRecorder however, records the timestamps using the media file's time. So it is possible to mark the start of a behavior three minutes into a video and then rewind or jump to a playback location that's only two minutes into the video and end it. Thereby creating a paradox and having a recorded behavior that has negative one minute in duration. Care should be taken not do such a thing, this isn't the software failing, it is the user creating an inaccurate recording.
If you have any other questions, problems, suggestions or think you have found a bug, please don't hesitate to write us.
Support: Support@BehaviorTracker.com
Registration questions/problems: Registration@BehaviorTracker.com