Overview
MVIS is open-source multi-visual-inertial sensor calibration: a Python toolbox for camera and camera–IMU calibration, from a single camera to multi-camera, multi-IMU rigs. An IMU (inertial measurement unit) is the sensor with a gyroscope and an accelerometer.
- Package:
pymvis. You import it asmvisand run it as themviscommand. - Runs on: Linux and macOS (Windows tentative), Python 3.11 and 3.12, with no ROS install. See Requirements.
- Code: github.com/openmvis/openmvis.
OpenMVIS, the project around MVIS, also publishes calibration datasets, a benchmark against Kalibr and Basalt, and a device wiki of calibrated sensors.
What it solves
Section titled “What it solves”MVIS solves the quantities below from one recording, in a camera solve and then a camera–IMU solve.
| Quantity | Scope | Notes |
|---|---|---|
| Camera intrinsics + distortion | per camera | Focal length, image centre and lens model. Eight models, mixable in one rig (Camera model) |
| Camera extrinsics | per camera | Where each camera sits relative to the reference camera |
| Camera–camera time offset | per camera | For cameras that are not hardware-synced |
| Rolling-shutter readout | per rolling-shutter camera | The time the camera takes to read its rows, top to bottom (why) |
| Board poses and board shape | per frame / per corner | The shape is one height per corner, off by default (why) |
Camera–IMU extrinsics T_CtoI and time offset td | per camera | |
| IMU–IMU extrinsics and time offset | per auxiliary IMU | Each extra IMU relative to the base IMU, the first IMU in the config |
IMU intrinsics Dw, Da, optional Tg | per IMU | Gyro and accel scale and misalignment, in one of three conventions (IMU model) |
| IMU biases | per IMU | |
Gyro–accel time offset t_ga | per IMU (not gyro-only IMUs) | The delay between the gyro and accel channels of one IMU, on by default (why) |
Several of these have no counterpart in Kalibr or Basalt. The comparison lists them.
How a run works
Section titled “How a run works”A calibration has two solves and a check.
- Cameras:
mvis camsolves each camera’s lens and the camera–camera extrinsics from a board recording. It writes a camera YAML and an HTML report. - Cameras + IMUs:
mvis cam-imureads that camera YAML as its starting point and solves the camera–IMU extrinsics, time offsets and IMU intrinsics. It writes a JSON result, a calibration YAML, a Kalibr camchain where the camera model allows, and an HTML report. - Check:
mvis verdictgrades a result GREEN, YELLOW or RED.mvis roundtripapplies a camera–IMU calibration to its own recording and calibrates again: the IMU intrinsics must come back as identity and the geometry must not move. A digital twin of your rig tells you what the recording can pin down before you trust it.
mvis run starts either solve from the config’s mode: field. Every command
is in the CLI reference.
Inside the camera solve, the steps are:
- Detection: find the board corners in every image.
- Quality gating: drop frames with too few tags and corners seen too rarely.
- Init: a first guess of each lens and each board pose.
- Per-camera solve: refine each camera on its own, with its rolling-shutter readout if it has one.
- Alignment: find where the cameras sit relative to each other, and their time offsets.
- Joint solve: refine all cameras together.
- Outlier rerun: drop corners with large error and solve again.
The camera–IMU solve starts from the camera YAML, picks the part of the recording with the most motion and runs one joint solve with the IMU data.
You can also start from an existing calibration, such as Kalibr output, and pin what you trust. See Configuration.
Where to go next
Section titled “Where to go next”- First run: Installation, then Quickstart.
- Coming from Kalibr or Basalt: Comparison.
- Your own rig: the guides, from the board to the round-trip check.
- Results on public data: Leaderboard and Examples.
- The maths: Concepts.