Fix the code for imu+mocap calibration. #733
Open
+12
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
We fixed the IMU-Motion Capture (MoCap) calibration tool. It can now perform the spatiotemporal extrinsic calibration between the IMU and the MoCap trajectory. This enables the conversion of the raw MoCap data into a trajectory referenced to the IMU local frame, meeting the requirements of tasks such as VI-SLAM benchmarking.
Command
One can run the IMU - MoCap calibration function with the following code:
For more parameter descriptions, one can use the following command to view the help information:
Verification
We conducted verification on the EuRoC dataset and our own MoCap dataset. The code functions properly. As shown in the figures below, the running log and output results for one sequence of the EuRoC dataset indicate that the estimated trajectory is basically consistent with the one published by EuRoC.
Notes
Meanwhile, we also noticed that the calibration accuracy is higher when there is sufficient motion excitation. Therefore, we recommend performing an additional calibration operation first and applying the calibration results to all subsequent data collection processes.