Roadmap
Use this page to see what we plan after MVIS 0.1.0. These are intentions, not commitments with dates. What shipped is on the Changelog.
Toolbox
Section titled “Toolbox”| Item | Status |
|---|---|
pip install pymvis from PyPI | with the v0.1.0 release; until then, install from source (Installation) |
| Public code repository | done: github.com/openmvis/openmvis |
omni_radtan | experimental in 0.1.0 |
| Stable config schema | not before 1.0: 0.x releases may change it |
| Windows, Python 3.13 | blocked upstream: GTSAM has no Windows wheels, and the NumPy 1.x that GTSAM 4.2 needs has no 3.13 wheel |
Documentation
Section titled “Documentation”The CLI, Configuration and
Python API pages were checked against MVIS 0.1.0.
When they differ from the code, mvis <command> --help and mvis check are
authoritative.
Benchmark and datasets
Section titled “Benchmark and datasets”| Item | Status |
|---|---|
| New results submission process | being set up; see Submit results |
| Verified results (a maintainer re-runs a submission) | planned |
| Contributed datasets | open; see Submit a dataset |
Not planned
Section titled “Not planned”- Replacing Kalibr for single-IMU rigs. Kalibr is mature and widely used.
MVIS adds what Kalibr does not cover, such as rolling-shutter readout on
several cameras, camera–camera time offsets, the gyro–accel offset
t_gaand the board shape. See Comparison. - A single combined score on the leaderboard. How to weigh one parameter against another is the reader’s call, not the benchmark’s. See Methodology.
Missing something you need? Open an issue on the toolbox repository (or on the site repository for this site).