Log Overlapping Events - Standard

<< Click to Display Table of Contents >>

Navigation:  BEST-PRACTICE Examples > Logging Behavior that Overlaps in Time >

Log Overlapping Events - Standard

For this example, we have chosen the Standard logging mode.

Example: You are observing a situation where a mother is in a room with her child. As soon as she leaves the room, the child starts crying. A short time later, a strange woman enters the room, trying to comfort the child which keeps on crying. When the mother enters the room the child calms down after a short while and after a few more sobs the child is happily playing again. We start this example at the very moment the child starts crying.

Click Start - Observation - Define Codes btn_codedefinitionen to setup your Codes.

Presume we define the following 3 Codes for the Class 'Action':
[c] = child crying
[m] = mother in room
[s] = stranger in room

You can log Events by clicking the Codes in the Coding panel or by pressing the assigned [keys].

This clip shows you the steps described as a tiny slide-show:

Log overlapping Events

To log everything that happens after the child starts crying, do as follows:

Make sure the correct Code definition file is loaded.

Click btn_session_start, to activate the observation mode.

Press play to start the video.

Click on the Code 'crying' or press [c] once, to log the fact that the child starts crying.

A [c] appears in the Start -Active Codes field and a new Event line, with the exact start time as well as the code 'crying', appears in our data file.

Click on the Code 'Stranger in room' or press [s] once, as soon as the strange person enters the room.

Additionally to the '[c] crying', the '[s] stranger in room' appears in the Start -Active Codes field. Also another Event line with time and Code information appears in your data file.

When the mother enters the room, click the Code 'mother in room' or press [m].

Now all three Events are 'open' and the corresponding [keys] are visible in the Start -Active Codes field.

As soon as the child stops crying, click on the Code 'child crying' or press the [c] for a second time.

This 'closes' the corresponding Event and enters the exact offset time. The "c" disappears from the Start -Active Codes field.

Now click the Code 'stranger in room' or press the [s] key, to log the end of the Event 'Stranger in room'.

This closes the corresponding Event and the [s] disappears from the Start -Active Codes field as well.

Finally, click the Code 'mother in room' or press [m], when the mother leaves the room again at the end of the session (taking the child with her).

Now the third event is also closed.

To exit the observation mode, click btn_session_stop in the Observation Controls.

Note: If you click STOP while there are still open Events, all will be closed automatically with the current video time.

Your current document now contains three Event lines: One for each different kind of behavior.
Each Event includes a behavioral Code and the corresponding start time and offset  time of this specific behavior.

Visualize and Analyze

Visualize those results in the Timeline Chart:

Click Analysis - Evaluation - Timeline Chart Btn_TLC_Chart_AllData.

Click Btn_TLC_DataSetStatistics or Btn_TLC_FullStatistics to get the corresponding statistical values.

Note: A computer keyboard was not designed to press multiple keys simultaneously (except for the special keys like CMD or SHIFT etc.). That is why, while simultaneously logging different Codes, sometimes a specific key combination does not work correctly, because the keyboard is not able to send those combined signals to the computer. In this case, assign different [keys] to the problematic Codes and try again.