> 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/sanity-checks.md). # Sanity Checks Sanity Checks are intelligent guardrails built into the 3D Multi-Sensor Fusion Labeling Editor that automatically monitor annotation quality in real time. They help annotators maintain geometric consistency and physically realistic object behaviour across frames - catching errors at the point of creation rather than during QA review. Each check runs continuously in the background and surfaces a non-blocking visual cue or warning only when a configured threshold is violated. Checks are configurable at the project workflow level (recipe) or in the project ontology, depending on the check type, and can be tuned to match customer guidelines or iMerit-recommended defaults. {% hint style="info" icon="lightbulb-on" %} Sanity Checks are non-blocking - annotators can always submit a task even when warnings are active. Persistent warnings are visible to QA reviewers and provide context for ambiguous or low-confidence annotations. {% endhint %} *** ## Introduction to Sanity Checks {% embed url="" %} Different types of available Sanity Checks 1. [Plausible Object Motion](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features/sanity-checks/plausible-object-motion.md) 2. [Plausible Object Rotation](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features/sanity-checks/plausible-object-rotation.md) 3. [Velocity](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features/sanity-checks/velocity.md) 4. [Minimum LiDAR Point Density](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features/sanity-checks/minimum-lidar-point-density.md) - currently not configurable from Ango Hub project settings 5. [Class-Based Cuboid Dimensions](/3d-multi-sensor-fusion/labeling/3d-multi-sensor-fusion-labeling-editor/key-features/sanity-checks/minimum-maximum-cuboid-volume.md) --- # 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/sanity-checks.md?ask=&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.