Issue description
Processing fails with the following error:
Segmentation fault (core dumped)
ERROR: Could not process dataset '/tmp/inputs/larkin1stB2cut2': Command 'rosrun quality_map quality_map_processing_node --laser-bags /tmp/navvis_postproc_dataset_larkin1stB2cut2@2020-11-05_16.10.48/rewritten/bag_sensor_data_1.bag /tmp/navvis_postproc_dataset_larkin1stB2cut2@2020-11-05_16.10.48/rewritten/bag_sensor_data_0.bag --laser-topics /laser_vert_top_left/scan /laser_vert_bottom/scan /laser_vert_top_right/scan --destination=/tmp/outputs/datasets_proc/larkin1stB2cut2_1 --tf-bags /tmp/outputs/datasets_proc/larkin1stB2cut2_1/artifacts/trajectory.bag /tmp/outputs/datasets_proc/larkin1stB2cut2_1/artifacts/height_adjust.bag --tf-topics tf_trajectory head_body --create-georegistration-maps=False --create-quality-map=True --control-topics /trigger_event /user_interaction /slam_anchor --sensor-frame=/tmp/inputs/larkin1stB2cut2/sensor_frame.xml --velodyne-calibration=/opt/NavVis/ros-shared/share/velodyne_pointcloud/params/VLP16db.yaml --floor-list=/tmp/outputs/datasets_proc/larkin1stB2cut2_1/artifacts/floors.json --apply-intensity-filter=False --min-laser-range=0.1 --max-laser-range=30.0' returned non-zero exit status 139.This error happens during quality map generation.
Root cause
The Dataset was cut at a problematic step in time, e.g.:
At an exact trigger event.
Before the first trigger event, when no pose and trajectory have been computed yet.
Scope
This solution applies to all versions of NavVis IVION Processing and Desktop Processing,
Troubleshooting procedure
Cut the dataset at a different point in time, refer here. A few seconds in one or the other direction might be enough (at least one trigger event in each direction). Then re-process. refer here for