> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features/outlier.md).

# Outlier

Enabling the Outlier toggle highlights all points in the point cloud that have not yet been segmented or labeled. These unclassified points blink, drawing the user's attention to areas that may have been missed. This helps ensure correct coverage of the scene before a task is submitted, reducing the chance of overlooked objects or incomplete annotations.

{% hint style="info" icon="lightbulb-on" %}
Outlier highlights points in the point cloud that have not been classified.
{% endhint %}

![](https://content.gitbook.com/content/TcOUG6rfWxqGM0N4db2P/blobs/Gqz46XRV08XL2NEYm1Pe/image)

## Steps to use Outlier

{% stepper %}
{% step %}

#### Enable Outlier

Enable the "Outlier" toggle from the header of the annotation tool.
{% endstep %}

{% step %}

#### View unclassified points

All points in the point cloud that have not been classified will start to blink to draw attention to the areas of non-classified points.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.imerit.net/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features/outlier.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.