Skip to content

Submit a dataset

Use this page to give us a calibration recording of your rig. A rig we have not seen is worth more than another run on one we have. We credit every dataset we host.

The steps:

  1. Check that it is usable.
  2. Package it in a format MVIS reads.
  3. Write a dataset card.
  4. Choose the licence.
  5. Send it.

We can only calibrate from a recording that has:

  • Raw sensor streams: no rectified (pre-undistorted) images and no vendor-corrected IMU output. The IMU (inertial measurement unit) is the gyroscope and accelerometer. A correction we cannot undo hides the intrinsics, the sensor’s own parameters, so they cannot be calibrated.
  • A calibration board in view for most of the recording. MVIS reads AprilGrid, chessboard and ArUco boards. See Set up the board.
  • Motion on every axis: rotation about all three axes and translation along them, not just one kind. See Record the dataset and Degeneracy.
  • Timestamps from one clock for all streams, or a stated offset between clocks.

Run mvis inspect <path> on your recording before you send it. It reports which MVIS modes can read it, each camera stream (rate, resolution, encoding), each IMU stream (rate, units, timestamp order) and how long the camera and IMU streams overlap.

MVIS reads these inputs. Pick one that fits what you recorded:

  • ROS1 bag: Image messages, or PNG or JPEG CompressedImage. Reading it needs no ROS install.
  • ROS2 bag.
  • EuRoC / ASL folder: the mav0 layout used by EuRoC and TUM-VI.
  • Image folder, or timestamped images: camera only. These carry no IMU data, so use one of the formats above for a camera–IMU recording.

mvis inspect lists the modes (cam, cam-imu) that can read your recording.

Configuration lists the input fields for each.

MVIS does not read video files. Convert video to images first.

Send these details with the data:

ItemWhat to give
Boardtype, rows and columns, tag or square size in metres, tag spacing, tag family
Sensorsmodel, rate, resolution and topic of each camera and IMU
Shutterglobal or rolling for each camera; for rolling shutter, the readout direction if you know it
Timinghardware-synchronised or not, and how timestamps are taken
Referenceany existing calibration, and the tool that produced it

Send a reference calibration even if it is rough, and say how you got it. Then a method can be checked against your recording, not only run on it.

Add one short page (a README.md) next to the data:

  • Rig: what it is and what makes it different.
  • Recording: how and where you recorded it.
  • Known problems: dropped frames, clock jumps, saturated IMU segments, streams synchronised in software.
  • Licence: the licence, and how to cite the data.
  • Contact: who answers questions about it.

The licence must let us publish results computed on the data. For us to host a copy, it must also allow redistribution.

  • Hosted by us: recordings we host in the Hugging Face dataset calibench-vi/community use CC BY-NC 4.0 (non-commercial, attribution required). Downloads need a free Hugging Face login with automatic approval.
  • Hosted by you: if your data must stay under another licence, keep it where it is. We add a download recipe that points to your copy.
  • People and private spaces: blur faces, screens, documents and anything else private before you send the data. We do not publish recordings that still show them.
  • Your rights: you must own the data or have the right to grant the licence.

Open an issue on openmvis/mvis_pages. In it:

  • describe the rig in one or two sentences
  • link the data (any download link works)
  • attach or link the dataset card

We reply on the issue and arrange hosting from there. Data we host ends up in calibench-vi/community; open the request on the issue tracker, not there.

We credit every dataset we host. What that includes is listed in Governance › Credit. To send results on an existing dataset instead, see Submit results.