Log Overlapping Events - Push & Release mode

<< Click to Display Table of Contents >>

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

Log Overlapping Events - Push & Release 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.

For this example, we again use the coding mode Standard, but we have chosen to activate the option Push & Release mode.

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

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

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

Make sure the correct Code definition file is loaded.

Create a new data file.

To activate the Observation mode, click btn_session_start .

Press [c] and keep the key pressed for as long as the child keeps 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.

As soon as the strange person enters the room, press [s] as well and keep this key pressed for as long as she is in 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, press [m] as well.

Now 3 [keys] are kept pressed and all three characters are visible in the Start -Active Codes field. A third Event line appears as well in your document.

As soon as the child stops crying, release the [c] key.

The 'c' disappears from the Start -Active Codes field and the corresponding Event is 'closed' by entering the offset time for that behavior.

If the strange woman leaves the room, release the [s] as well.

The corresponding Event closes as well and the [s] also disappears.

Finally, release the [m] key when the mother leaves the room again at the end of the session (taking the child with her).

The third Event is now also closed.

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

In your current document, you now have 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 those results in the Timeline Chart:

Click Analysis - Evaluation - Timeline Chart Btn_TLC_Chart_AllData.

Select Analysis - Statistics per DataSet to get the corresponding statistical values.