--- title: "High control point residuals in z-direction in NavVis IVION" slug: "high-control-point-anchor-residuals-in-z-direction" description: "High z-direction anchor residuals near 80-85 cm in a processed NavVis VLX dataset trace to the device not being taken off during the anchor. Also check the control point button push, the mapping log, and residuals_xyz.png." tags: ["NavVis IVION Processing", "SLAM Anchor File"] updated: 2026-02-24T14:22:01Z published: 2026-02-24T14:22:01Z canonical: "knowledge.navvis.com/high-control-point-anchor-residuals-in-z-direction" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.navvis.com/llms.txt > Use this file to discover all available pages before exploring further. # High control point / anchor residuals in z-direction ## Introduction ### Problem description After processing, a Dataset shows high residuals in z-direction for some anchors. You can see that either in the anchor residual text field (both on-premise and on Cloud) or in the residual plots. A typical example from /datasets_proc//internal/anchors/optimization/residuals_xyz.png: ![](https://cdn.document360.io/bf174766-fa1a-4fe1-a4d7-b1db1e7cb996/Images/Documentation/vlx-high-control-point-anchor-residuals-in-z-direction-image-do46akej.png?sv=2026-02-06&spr=https&st=2026-10-14T07%3A49%3A16Z&se=2026-10-14T08%3A49%3A16Z&sr=c&sp=r&sig=JJqR9kUjaQW%2B%2Fq%2FJZI6vrX5hk4lXoz%2FE5ndGe0BbcDA%3D) The mapper has likely either not taken off the device while [scanning the anchor](/v1/docs/scanning-with-control-points-1) or did not correctly push the control point button on the device (repeating the push later via the display). This can be observed in the residual plot, since the residuals in z-direction are approximately 80-85cm. That is the typical height of the NavVis VLX belt on a medium sized person. ### Scope Solution applies to: NavVis VLX ## Troubleshooting procedure ### 1 Check the mapping log Another indication of this problem is the delay between the changed z-pose of the NavVis VLX and the actual triggering, shown in the mapping log. ```plaintext [ INFO][1613634432.531936797][/surveyorslam_node] Added pose at: 0026.865 -28.8519 01.16539 ... [ INFO][1613634435.031290403][/surveyorslam_node] Added pose at: 026.7683 -29.0148 0.531467 ... [ INFO][1613634437.526578808][/surveyorslam_node] Added pose at: 026.4843 0-28.899 0.146602 [ INFO][1613634440.035568989][/surveyorslam_node] Added pose at: 026.4033 -28.8714 0.124203 ... [ INFO][1613634465.594447634][/surveyorslam_node] Added pose at: 026.4289 -28.7787 0.151877 ... [ INFO][1613634468.084122845][/surveyorslam_node] Added pose at: 026.9166 -28.9612 0.972301 ... [ INFO][1613634470.585018289][/surveyorslam_node] Added pose at: 026.9896 -28.8361 01.18751 [ INFO][1613634472.685712847][/dashboard2] Setting anchor at time 1613634472.672829 [ INFO][1613634472.685771480][/dashboard2] Disabling the SLAM anchor laser cross. [ INFO][1613634472.687014723][/dashboard2] Disabling the SLAM anchor laser cross. [ INFO][1613634472.736529808][/controller] controller: added SLAM anchor '301' at stamp 1613634472.672828736 ``` ### 2 Analyze how an anchor was taken 1. Analyze the mapping behavior using `rqt_bag` on the main bag-file (start roscore first in another terminal), eg: ```plaintext rqt_bag /mnt/support-data/.../datasets_rec//internal/bags/bag_2020-10-05-17-45-37_0.bag ``` 2. Analyze when and how an anchor was taken by checking the two ros-messages `/hw_anchor_button_pressed` (GCP button on the head) and `/hw_trigger_button_pressed` (Pano button next to the display). A mixed dataset with both wall and ground control points as well as manual panorama triggering looks like this: ![](https://cdn.document360.io/bf174766-fa1a-4fe1-a4d7-b1db1e7cb996/Images/Documentation/image-1707138261339.png?sv=2026-02-06&spr=https&st=2026-10-14T07%3A49%3A16Z&se=2026-10-14T08%3A49%3A16Z&sr=c&sp=r&sig=JJqR9kUjaQW%2B%2Fq%2FJZI6vrX5hk4lXoz%2FE5ndGe0BbcDA%3D) ### 3 Check the Point cloud 1. Since the data was already processed, check that: 1. the correctly scanned anchors all show low residuals after optimization 2. the xrays in all directions look very precise 2. If this is true, the optimization has correctly identified the discrepancy in anchor location and the point cloud will be fine. 3. If you have any doubt about the correctness of the data, delete the incorrect anchor locations from the dataset and re-process without them. 4. If this happens frequently, submit a case with NavVis Customer Support to investigate if there is a possible lag in anchor capturing. A dataset is a piece of a site, the result of a continuous recording with a NavVis mapping device or the result of an imported point cloud. Datasets can contain panoramic images and point clouds. Ground Control Point A Point Cloud is as a collection of data points in space that typically represent the external surface of an object or environment. Point clouds are used in various applications, including 3D scanning and mapping, and can be visualized and manipulated using Navvis IVION. You can perform actions such as panning, orbiting, cleaning up noise, cropping, and downloading data in formats like .e57 or .ply. The resolution of point clouds processed with NavVis Software achieves a minimum detail of 5mm, indicating the precision of the spatial data points.