Independent of the way you create your Events, the way you enter your Codes is the same, if you use this coding system.
In this example we presume that you want to describe multiple AU's within one Event, that is why we build this circle reference from the 'Modifier' file back to the 'master' file.
Presume we want to log information about 'Action unit 25":
▪Press [2] when the first level Code file "01_FACS_ActionUnit_Master.ikey" is open.
The next Codes level, containing the second digit of our 'Action unit', automatically appears.
▪Press [5] for the second digit of our 'Action unit'
INTERACT now 'knows' that the combined 'prefix' should be "25". The next Code file, containing our Intensity Codes, is opened automatically.
▪Press [b] to log the Intensity for 'Action unit 25'.
A Class column called "25I" is created, containing the Code "b".
The next Code definition file, containing the "Modifier" Codes, opens automatically .
▪Press [r] if you have identified this as the fitting Code for the Modifier of 'Action unit 25'.
A Class column called "25M", containing the Code "R" is created automatically.
Note: If a Class column already exists, the Code is entered into the existing column, like it would when using regular Class names.
Log next Event
As soon as you have Coded all Action Units for this frame or period you need to log the next Event:
 | Frame by Frame Observation |
▪Press the SPACEBAR again (or click 'Start event' in the Coding panel) to jump to the next frame and create a new single frame Event.
▪Enter your Codes to describe the necessary action units, as described before.
| Event-based Observation |
▪Click again the SPACEBAR (or on 'Start event' in the Coding panel) and proceed as described above.
| Predefined-Interval Observations |
▪Double-click the next Event line and continue as before.