<< Click to Display Table of Contents >> Navigation: BEST-PRACTICE Examples > Coding Facial Expressions > FACS - Multiple AU's per Event > Log 1-frame FACS Events |
During this example, we presume that you use the FACS Code definitions as pre-installed in the folder \Mangold INTERACT Data\Codedefinitions\FACs.
▪Click Start - Observation - Define Codes
▪Open the file 01_FACS_ActionUnit_Master.ikey in this code definition window.
▪Click Start - Observation - Observation settings .
▪Select the Coding Mode Lexical (post-hoc).
▪Click OK to confirm your settings.
Frame-by-Frame observation |
This means, that you want to analyze each single frame separately. To make that work:
▪Clear the option SPACEBAR is treated as a Code with duration in your 'Master' Code definition file, at the bottom of the Start - Observation - Define Codes dialog.
If this is all set, you have to code like this:
▪Click to start with your session.
▪Press the SPACEBAR to create the first Event*.
Immediately a single-frame-Event is created with the current time.
This little clip shows how each new Event creates a single line Event and positions the video accordingly:
Now you can press the desired keys to enter the FACS codes that describe the current image (frame):
▪Click or hit the first digit of the AU you want to describe e.g. [3].
▪Click or press the second digit of the AU you want to describe e.g. [6].
▪Click or press the Code that describes the observed Intensity e.g.[b].
▪Click or press the Code that describes the observed Modifier e.g.[r].
Your data file now holds at least two Class columns, both for the same AU, but one for the Intensity and one for the Modifier Code. In this case Class 36I holding code b and Class 36M holding Code R.
▪Click or press the first digit of the next AU you want to describe for this Event-line.
▪Continue as before.
After you have described all AU's for the current Event-line:
▪Press the SPACEBAR again to create a new Event for the next frame and continue as before.
IMPORTANT: Check whether the correct frame number is created and jumped to, because not all videos can be controlled correctly. Also additional registry settings can optimize the control depending on the graphics card used!
*) If you enabled the option SPACEBAR is handled as a Code with duration you need to press the SPACEBAR again to close the current Event.
▪Repeat those steps for each frame until you reach the end of the video sequence to be coded.
▪Close your observational session by clicking .
Event-based Observation |
If you want to log regular Events with individual durations:
▪Select the SPACEBAR is treated as a Code with duration option in your 'Master' Code definition file, at the bottom of the Start - Observation - Define Codes dialog.
▪Reduce the playback speed for observation in slow-motion.
▪Switch to the Observation Mode by clicking .
▪Press the SPACEBAR to log the start time of an Event, or click 'Start new event' in the Coding panel.
Per default, the video starts playing* automatically and an Event with corresponding start time is created.
*Note: If you want to proceed through the video frame-by-frame, deactivate the option Start multimedia files when logging an event in the Observation Settings. You can than use the ARROW keys to move the video the end of an Event.
▪As soon as your first Event ends, press the SPACEBAR again to log the offset of that Event (or click 'Stop current Event').
This Event now exactly covers the observed period.
▪Click on the available Codes to describe the current event. (See Enter FACS Codes for details.) Enter information for all AU's in action within the just logged Event.
▪Press F12 to replay the current Event to make sure you capture all activity.
▪Repeat the last three steps for each new Event.
TIP: | Click the Speed arrow down in the Observation Ribbon to reduce the number of frames per second at which the video runs! |