Skip to content

Result formats

Use this page to see what a run writes and which file to use for what.

RunFilesUse for
mvis cam<name>_calib.yaml, <name>_full.yaml, <name>.html, <name>.logDeploy the _calib.yaml; keep the rest to reproduce the run
mvis cam-imucam_imu.json, cam_imu_calib.yaml, cam_imu_camchain-imucam.yaml, cam_imu_report.htmlRead the JSON; deploy or apply the _calib.yaml; give Kalibr users the camchain
mvis apply-calib<bag>.corrected.bag, <bag>.corrected.bag.recalib.yamlThe corrected recording and how it was made
mvis roundtripforward/, recal/, report.txt, report.jsonPASS or FAIL with every check

Rotations are stored as matrices (3×3 or 4×4) or log(R) rotation vectors in radians, never roll, pitch and yaw. Board tilt against gravity is the one angle given in degrees.

mvis cam writes into the run folder (-o; by default a folder named ablation next to output_file). <name> is <config folder>_<config file name>: -c t265/cam.yaml gives t265_cam_calib.yaml.

FileContainsUse for
<name>_calib.yamlIntrinsics, distortion, extrinsics, time offsets, readout, reprojection statisticsDeploy. The calibration itself
<name>_full.yamlThe above, plus per-frame board poses, board corners, timings, filter statistics, motion metricsReplay. Rebuild the report or the 3D view without detecting again
<name>.htmlThe reportRead it first; see below
<name>.logThe run logDebugging
detections.mvisdbDetections and this run’s estimatesSee Capture database

With rerun_outliers: true, the first pass is kept as <name>_pass1_calib.yaml, <name>_pass1_full.yaml and <name>_pass1.html when it differs from the final result. The config’s output_file gets a copy of the result, in YAML or JSON (output_format).

FieldMeaning
cameras[]Per camera: id, model (pinhole_<distortion model>), intrinsics (fx, fy, cx, cy), distortion (model, coeffs), image_size, rolling_shutter_readout (s)
cameras[].rolling_shutter_readout_sigmaFormal 1σ of the readout (s), when it was estimated
cameras[].valid_domainkb4 only: the largest angle the fit can project, up to the model’s first fold
extrinsicsreference_camera and transforms[]: from, to, T_to_from (4×4), so3 (log(R), rad), translation (m)
time_offsetsreference_camera and offsets[]: camera, dt (s)
reprojection_errorsoverall_rms and per_camera[]: rms, mean, median, p90, p95, max (px), num_observations
board_shapeWith estimate.board_points: true: heights_m per corner, rms_mm, peak_to_peak_mm, n_obs
board_point_biasMean residual per board corner: median_px, max_px, n_points_seen
corner_accountingWhat became of every detected corner; see below

mvis cam-imu names every file after output.path. With output.path: results/run/cam_imu.json:

FileContainsUse for
cam_imu.jsonA compact summary in practical units (mm, ms)Read, compare, grade with mvis verdict
cam_imu_calib.yamlThe full calibration in SI units, with each sensor’s topicDeploy, and the input of mvis apply-calib
cam_imu_camchain-imucam.yamlKalibr camchain-imucamTools that read Kalibr files
cam_imu_report.htmlThe reportRead it first
cam_imu_views.jsonThe report’s 3D scene and rig views, without camera framesRebuild the 3D views elsewhere, for example on openmvis.com
cam_imu_board_shape.yamlThe estimated board shape, with estimate.board_points: trueboard.heights_file of a later run
cam_imu_sensor_clock.jsonPer-frame stamp maps, with retime_sensor_clockcamera_input.cameras[i].retime_map of a later run
FieldMeaning
okThe solve finished and passed its own gates. Not proof of a good fit
reproj_rms_px, reproj_median_px, reproj_p95_pxReprojection error over all cameras (px)
solve_sSolve time (s)
diagnosticsiterations, max_iterations, cam_chi2_dof, imu_chi2_dof, n_states
cams[]Per camera: td_ms, reproj, reproj_median, reproj_p95 (px), intr, p_CinI_mm (camera position in the base IMU frame), rotvec (log(R) of T_CtoI, rad), p_CtoC0_mm (position relative to camera 0), corner_accounting
imu_modelkalibr, rpng or calyx
Dw_diag, Da_diagDiagonals of the base IMU’s gyroscope and accelerometer matrices
Dw_scale, Dw_shear, gyro_misalign_rotveccalyx only: Dw split into a rotation (log(R), rad) and an upper-triangular part with the scales on its diagonal
t_ga_ms, t_ga_sigma_msBase IMU gyro-to-accelerometer time offset and its 1σ (ms)
imus[]Per auxiliary IMU: td_ms, t_ga_ms, chi2_dof, p_IsinI_mm (position in the base IMU frame), rotvec, Dw_diag, Da_diag
boardBoard pose against gravity: T_BinW, g_inB, normal_tilt_deg, g_inplane_deg; shape with estimate.board_points: true

td convention: an image stamped t matches the IMU at t + td.

FieldMeaning
cameras[]As in the camera-only file, plus td (s), T_cam_imu (4×4, IMU to camera), reproj_rms_px, p_CtoC0_m, rostopic
imus[]First the base IMU (role: base), then each auxiliary IMU (role: aux)
imus[].b_g, imus[].b_aGyroscope (rad/s) and accelerometer (m/s²) bias
imus[].Dw, imus[].Da3×3 gyroscope and accelerometer matrices, in the convention of model
imus[].imu_intr_xiEvery IMU intrinsic in one vector, including Tg and the internal rotation; the form apply-calib reads
imus[].R_wtoI, imus[].U_wBase IMU, calyx: rotation and upper-triangular factor of Dw
imus[].t_ga, imus[].t_ga_sigmaGyro-to-accelerometer time offset and its 1σ (s), when estimated
imus[].td, imus[].p_IsinI_mAuxiliary IMU: time offset (s) and position in the base IMU frame (m)
imus[].gyro_onlyPresent and true when an auxiliary IMU was calibrated from its gyroscope alone; its lever, Da and accelerometer bias were held fixed
imus[].topicSource topic; apply-calib uses it to map topics to sensors

With input.bags, each recording gets its own folder next to output.path:

results/sweep/
bag01/cam_imu.json
bag02/cam_imu.json
bag03/cam_imu.json

<NN> is the last number in the bag file name (for a EuRoC mav0 folder, the first number of its parent folder).

Every result has a corner_accounting block per camera. It says what happened to each detected corner, so a fit cannot look better by silently dropping corners. Every corner lands in exactly one category: detected = used + past_fold + other_invalid + outliers + no_pose_corners + not_in_solve.

FieldMeaning
detectedEvery corner given to the solve
usedHad a factor in the final solve and projects at the final fit
past_foldFails to project at the final fit, at or past a Kannala–Brandt model’s fold
other_invalidFails to project for another reason, for example behind the camera under equidistant
outliersRemoved by the outlier filter; still projects
no_pose_frames, no_pose_cornersFrames, and their corners, that reached no factor (no pose, too few points)
not_in_solveNever reached the final solve: thinned by rate or corner_subsample, or dropped by a gate
past_fold_pass1past_fold at the first pass’s fit, before the outlier rerun. Above zero also raises the alarm
n_cornersused + past_fold + other_invalid
max_theta_deg, max_theta_used_degLargest angle from the optical axis, of all corners and of the used ones
fold_deg, fold_levelkb4: angle of the fold. fold_level is alarm when corners lie past the fold, warn when the fold lies inside the image, else none

Every run writes one self-contained HTML file. It has no external files, so you can mail it. It prints cleanly and has a dark mode.

The camera-only report has:

  • Summary: stat cards and a table of contents
  • Intrinsics and distortion: tables per camera
  • Extrinsics: a table and a 3D plot
  • Temporal calibration: time offsets and readout
  • Reprojection: per-frame median and P95, per tag, error-vector histograms, corner heatmaps
  • Data quality: motion-excitation grades, rotation-axis spread, angular-velocity timeline, image coverage
  • Detection statistics, pipeline timing and collapsible appendices

The camera–IMU report adds:

  • Summary: status, reprojection RMS, χ²/dof, with grade badges
  • 3D views: the sensor rig (each camera at its T_CtoI, each auxiliary IMU, levers in mm) and the recovered trajectory with the board
  • Cameras, base IMU, auxiliary IMUs: every estimate, with its 1σ where the solve gives one
  • Against reference: lever, rotation and baseline differences, when the config has a reference: block

The reprojection and χ²/dof badges use the same thresholds as mvis verdict. See Evaluation & metrics.

To rebuild a camera-only report from a finished run folder without solving again:

Terminal window
python -m mvis.analysis.regenerate_html results/run --config t265/cam.yaml

mvis apply-calib writes an ordinary ROS1 bag. Anything that read the raw bag reads the corrected one. Next to it, <bag>.recalib.yaml records:

  • the source bag and the calibration file, with its SHA-256
  • the base IMU topic and the timeline (base_imu_clock, or the original stamps with --no-td)
  • the td convention: t_on_base = t_sensor + td
  • which corrections ran: remove_bias, undistort, imu_intrinsics, td, t_ga
  • which topics were corrected and which were copied unchanged

mvis.io.kalibr reads and writes Kalibr files:

FunctionDirectionDoes
read_camchaininA Kalibr camchain → per-camera intrinsics, distortion, resolution
read_camchain_imucaminAlso each camera’s T_cam_imu and the stereo T_cn_cnm1
write_camchain_imucamoutA camera–IMU result → a camchain-imucam dict
AprilTagBoard.from_kalibr_yamlinA Kalibr AprilGrid target file (in mvis.detection.apriltag_board)

So a Kalibr calibration can be an MVIS start (camera_input.path takes a camchain), and an MVIS result can go to tools that expect Kalibr. Notes on the exported camchain-imucam:

  • kb4: written as Kalibr pinhole + equidistant with the same coefficients. Exact for points in front of the camera; MVIS warns when the fit used corners past 90°.
  • Readout: written as Kalibr’s line_delay, the readout divided by the image rows.
  • rostopic: written as /camN/image_raw; set your own topics before you use the file with Kalibr.
  • Skipped export: when a camera cannot be expressed in Kalibr’s form (for example ucm with α outside [0, 1)), the camchain is not written and MVIS logs a warning. The MVIS files still hold the full result.