menu_book

Knowledge Base

Documentation, guides, and resources for Noldus products.

The Observer XT 17 - Carry Out an Observation - Score Data

Last updated: Jul 28, 2026

Score Data

Aim

To carry out an observation.

Prerequisites

You created and started an observation.

Procedure

Score the subjects, behaviors and their modifiers by typing the predefined key code or by clicking the key code in the Codes window. Typing key codes is generally faster. What you have scored appears in the Event Log window and is visualized in the Data and Audio Visualization window. Each row in the event log corresponds to one event. You can also type free text in the Comment column and press Enter. See Enter Events as Free Text.

Scoring Order

For each event line, score the subject first, then the behavior, and then the modifiers that are linked to that behavior. Of course, you score subjects and modifiers only if these are defined in your coding scheme. The Codes window displays which element should be scored next.

The following symbols appear in your Event Log:

  • The start of an event with duration (state event).
  • The stop of an event with duration (state event).
  • The start of an event in a mutually exclusive and exhaustive group. The state is active from that moment and the previous state is no longer active.
  • An event without duration (point event).
  • An instantaneous sample event.

For detailed scoring procedures, see the following topics:

  • Continuous Sampling
  • Instantaneous Sampling
  • Continuous and Instantaneous Sampling

Notes

When you save the project, the Event Log file is saved in the Event Data subfolder within your regular project folder. Make sure that the time before your computer goes into standby mode or hibernation is set to longer than the longest likely interval between scored events. To specify the interval for system standby and hibernation, in the Control Panel choose Power Options, click Change When the Computer Goes to Sleep, and make your selection.

Stop the Observation

Procedure

An observation is ended when either the maximum recording time has elapsed, the video ends, or you manually end the observation.

To stop the observation manually:

  1. Click the Stop Observation button in the Playback Control window.
  2. Depending on your Project Settings (see Value Update and Edit Independent Variables in Set Up Your Project), the Independent Variables window may appear. If so, enter the values.

Note

A confirmation window pops up when you stop the observation, unless you deselected this option in the Observation settings. The event log ends at the time point that you clicked the Stop Observation button. This is the Stop Time that you see in the Event Log. The observation stops at the time that you click Yes to confirm that you want to end the observation. This means that if you co-acquire external data, they extend beyond the end of the event log and are therefore grayed out.

What's Next?

  • To play back the data, use the Play button in the Playback Control window (not the Start Observation button).
  • To visualize data without the Event Log and Codes window, choose Analyze > Visualize Data, or click the Visualize button on the toolbar.
  • To analyze data, select data for analysis and then choose an option from the Analyze menu. See Calculate Statistics.
  • When closing an observation, the program checks if the event log currently open contains errors, for example a start code without a matching stop code. Event logs with errors are not analyzed or visualized. See Check the Event Log for Errors.

Notes

An event scored at the exact moment the observation stops is not included in the analysis. If the maximum time is reached while you are in the middle of scoring elements in an event line, that line is saved but is not complete. You can either delete or edit the incomplete line. See Correct Event Log Errors Manually.

Score Data: Detailed Procedure

What Is Your Observation Method?

  • Continuous Sampling
  • Instantaneous Sampling
  • Continuous and Instantaneous Sampling

Continuous Sampling

Aim

To code your observation with continuous sampling.

Prerequisites

  • You created and started an observation.
  • You chose Continuous Sampling as Observation method.

Procedure

The procedure described below is very general and may not apply to your own coding scheme. If you did not define subjects or modifiers, ignore the instructions referring to them. You can also change the usual order of scoring, for example to score the behavior before the subject.

  1. The first cell in the Subject column is selected. The Codes window shows all subjects. When a subject performs a behavior you are interested in, score the subject. The row is time-stamped and the time appears under Time.
  2. The Behavior cell in the event line is now selected. The Codes window now shows all possible behaviors for this subject. Score the behavior. The name of the behavior appears in the row in the Event Log and the event is visualized in the Data and Audio Visualization window. The event runs until the end of the video. The duration will be corrected as soon as you code the next event.
  3. If the behavior was linked to one or more modifiers, the Modifier cell in the event line is now selected. The Codes window now shows all the modifiers that can be attached to the scored behavior. Score the modifiers. The name of the modifier appears in the row in the Event Log. For numerical modifiers with a predefined range, first score the numerical modifier group and then type the value.
  4. Score the other modifiers that are linked to that behavior. If scoring modifiers is compulsory, the name of the modifier group which contains required modifiers is displayed in the event log before you actually score it. This helps you to see which modifiers (from which modifier group) need to be scored.

Compare solutions

Not sure which Noldus product fits your protocol? We can help you make the right choice.

Noldus is here to assist you throughout the whole process.

shopping_bag
check_circle

Thank you!

We'll get back to you shortly.

error

Please correct the following errors:

error

error

error

error

By clicking Submit, you consent to Noldus processing your data as described in our privacy policy.