Log Post-Hoc Events

<< Click to Display Table of Contents >>

Navigation:  BEST-PRACTICE Examples > Observe Multiple Subjects > Observe One Subject per Pass > Observe your Subject >

Log Post-Hoc Events

When using the Lexical (post-hoc) Coding Mode, all Events are all logged with the SPACEBAR, per default, creating a string of mutually exclusive and exhaustive Events.

If the behaviors you observe in a single pass do overlap, another approach is required.

Keep in mind that each Event is ALWAYS closed with the same [key] or Code as it was started with.

Sequential Events

Concentrate on one type of mutually exclusive behavior:

Hit the SPACEBAR to start the video AND to log the start time of the first Event.

Hit the SPACEBAR again as soon as the behavior changes to log the Offset of the current Event. This automatically PAUSES the video.

Enter the behavioral Code you just observed, while the video is paused.

Hit F12 to replay the just created Event to verify what you saw.

If the selected Code has any sub-codes/modifiers linked to it, these sub-levels automatically pop-up one after the other.
This won't happen in our first pass with the 'Movement' Codes, though.

Hit the SPACEBAR again to start the video AND log the start time of the next Event.

Continue as before.

This way of coding has an additional advantage: In the Observation Settings you can specify how empty Events are handled. That is not part of this example though.

TIP:More details about logging sequential Events using the Coding Mode Lexical can be found in Log Events - Lexical (post-hoc).

Note: If you are focusing on a single type of behavior, but do not have any hierarchy to deal with, you can still use this post-hoc coding mode instead of using mutually exclusive Codes in the Coding Mode Standard.
It allows you to log each Event with the SPACEBAR, leaving you more time to realize what the change in behavior turned into.

Overlapping Events

This method is required if you decide to log all behaviors in one pass per Subject. To log multiple behavior types simultaneously, you need to log the start time and Offset for each Event using the top-level Codes instead of the SPACEBAR.

Pick a Code to log its start time.

Pick another Code if it starts before the first behavior has endet.

The moment one of the active Codes ends, select that Code again.

The moment an Offset is logged, the video pauses, the Offset time is entered into the Event for that Code and the Coding Panel switches to the sub-level Codes of the Code you just ended.

Pick the sub-level Code that applies to the Event just closed.

If you are unsure what sub-code or modifier applies, hit F12 to replay the current Event.

The moment you picked a Code from the last level, INTERACT switches back to the top-level Codes and you can continue coding.

To start the video again, click either on the behavior that comes next or click btn_control_play Play to start  the video again.

This way of coding is faster, because it saves you multiple runs through the video, but it also requires a lot of practice. concentrating on a sinlge type of behavior per pass is more accurate.

TIP:More details about logging overlapping Events using the Coding Mode Lexical can be found in Log Overlapping Event - Lexical.