There are 2 key components related to quality estimation configuration:

Ground Truth jobs and Quality settings. Ground Truth jobs are configured at the Task level.

In this section, we explain how to set up a Ground Truth job.

Read more about quality settings [here](#annotation-quality-settings).

A _configured_ Ground Truth job is required for all quality computations in CVAT.

Quality settings provide options to tweak some aspects of annotation comparisons and

quality estimation in general. For instance, you can configure which annotation overlap

should be considered good enough or how specific annotation types must be compared.

Quality settings can be set up at the Task or the Project level.

If a task is not bound to a project, it uses its own quality settings.

Tasks inside a project can use individual quality settings or inherit settings

from the project they belong to. Read more about quality settings in projects

[here](#project-quality-settings).

for a task or project, available in the **Actions** menu.


There is a number of parameters available for configuration.

Hover the mouse over a **?** mark to display a description for a setting.


After the settings are updated, remember to save the values using the **Save** button.

The updated settings will take effect on the next quality update.

| Job selection filter | The filter for the jobs included in quality computation. Only jobs matching the filter criteria will be included in the quality results. |

In CVAT, it is possible to group tasks into projects to share common configurations or establish

a logical grouping for datasets. In this section, we explain options for quality management

inside projects.

When tasks are inside a project, it can be convenient to reuse the same quality setup for

all the project tasks. There is an option to use quality settings from the parent project

for all or only for specific tasks inside a project. This is controlled by the corresponding

toggle on the **Quality control** page of the task:


If some of the project tasks have individual settings, a notification is displayed

on the project settings page. You can enforce project settings for all the project tasks

by clicking the **Force project settings** button.


By default, new tasks inside a project inherit the quality settings of the project.

You can freely switch between these 2 modes without losing the individual configuration

for the task.

Updating project quality includes quality computation for all the nested tasks. If the task

quality is updated in a specific task manually, project quality has to be recomputed to display

relevant values.

Depending on the situation, you may need or don't need to include specific jobs in

the quality report. For example, your workflow may require quality checks only for

completed jobs or maybe you want to exclude jobs from a specific task from

a project quality report. There is an option to filter which jobs are included in quality

computations. You can configure this by changing the _Job selection filter_

in quality settings. Only jobs matching the filter criteria will be included

in the quality results. If a filter is changed, quality must be recomputed for the filter

to take effect.