Because all Action-Unit-Codes should be available in a single pass AND because multiple Action Units can be used (partly) simultaneously, we need a separate Code for each Action Unit and each contraction of a specific Aciton Unit results in a separate Event line.
| TIP: | If you want to log an Event for which the same length applies to multiple Action Units, read the example FACS - Mulitple AU's per Event. |
AU-Code Definition
Because we need a separate Code for each Action Unit, the Codes are straightforward to implement, using a Class named 'AU' and entering the number for each Action Unit that is of interest for us into the Code column:
Each Action Unit is logged independently, thus each AU-Code requires a unique keyboard shortcut in the Key column.
INTERACT allows only one character as a [key] shortcut, so we entered the values 1 to 0 for the first 10 AUs and switched to letters after that.
Note: As shown in other examples, it is possible to create a setup in which you can type the AU numbers as they are.
But that does not work if you want to log unique AU-based Events that may overlap.
It only works if you use intervals or other Events that are logged based on a specific behavior and may hold contractions of multiple AUs per Event line.