-
A robot camera that remembers its earlier self-calibrations gets the next one right more often
On 53 real TUM windows, a soft k1 prior from the camera's other windows cut focal scatter by a quarter to half and the median error from 3.06% to 2.43%.
-
A free gyro time offset fixes the focal length, but the offset it reports is 3 ms off
In a 1.2 s self-calibration window, a free gyro-camera offset cuts a late gyro's focal error from 0.81% to 0.05%, but the offset absorbs unmodelled translation.
-
A wrong readout time costs a self-calibrating camera more than a misaligned or late gyro
A 10° camera-IMU rotation adds 0.42% to a window's focal error and a 10 ms lag 0.35%, but a readout 5% off adds 1.23%, always the same way.
-
Both TUM RGB-D cameras have a 26–28 ms rolling shutter, and it was hiding in the focal length
Mocap angular rates in a 1.2 s self-calibration window find a 27.6 ms readout on TUM's Kinect and 25.9 ms on its Xtion, and halve the Xtion's focal error.
-
What is left of TUM's self-calibration error is scatter between windows, not a bias
On 53 real TUM windows, the median focal length sits inside the 1.6% that three calibrations disagree by; k1 and the principal point track each window's error.
-
TUM's image stamps run 5 ms behind the motion, and the camera's translation does not bend its focal length
On 53 real TUM windows, motion-capture velocity fits the images but leaves the focal error unchanged; the camera-mocap offset is a steady 5 ms.
-
A gyro in the window solve undoes most of the rolling shutter, and measures the readout too
With per-frame gyro rates in a 1.2 s self-calibration window, the rolling-shutter focal shift fell from 4.17% to 1.14% and the readout came back within 3.6%.
-
A camera calibrating itself from ordinary video is 4 to 12 times overconfident
Self-calibration from SIFT tracks of 1.2 s video windows missed f by 3-7%, with a solver sd 4-12x too small; the median of many windows was within 1.5%.
-
A camera calibration check that knows when not to decide
Declining to judge a calibration update when a small-set solve lands far from the spec sheet cut false alarms to 0.3%, at a quarter of the 2% detections.
-
A self-calibrating camera can't spot a bad video window by how far it turned
On 57 windows of TUM RGB-D video, how far the optical axis swung in 1.2 s did not predict the self-calibrated focal error (Spearman +0.08).
-
A camera calibration fix tested on views it never saw: safe on one camera, not the other
On a third set of views, a per-view jitter kept the Xtion's calibration check at 0.5% false alarms but not the Kinect's (7.5%), where far solves did the damage.
-
An honest error bar for camera self-calibration from video: leave one keyframe out
A delete-one-keyframe jackknife cut the rms z of self-calibrated focal length from 9.3 to 1.8 on TUM RGB-D video. The honest error bar turned out wide.
-
Centring a camera calibration check on the camera's own calibration
Moving the withhold window from the spec-sheet focal length to the camera's own calibration made it symmetric and kept false alarms at 0.26%.
-
How many seconds of video does a robot camera need to self-calibrate its focal length to 2%?
Pooling 1.2 s windows of TUM RGB-D video: a random-effects pool keeps the error bar honest, independence overclaims 2.8x, and 2% takes about eight windows
-
Letting a robot camera skip its own calibration check: more power, but not the safety we expected
A twin-based gate that skips weak camera calibration checks catches 1.75× more 2% focal changes, but a flat set of views still raises false alarms to 5.9%.
-
One number that makes a robot camera's calibration check safe, and what it costs
A per-view focal jitter fitted from a camera's own solves cut calibration-check false alarms from 4.4% to 0.6%, but halved how often a 2% change is caught.
-
Pin a camera's whole lens model, not one coefficient: a known k1 made self-calibration worse
On TUM RGB-D video, fixing only k1 at a prior calibration raised self-calibration's median focal error from 5.25% to 7.01%.
-
We expected an extra lens term to cost the update test power. On the Kinect it doubled it.
Refitting TUM's Kinect with k1 + k2 instead of k1 doubles how often a 2% focal change is caught, 9.8% to 19.3%, at unchanged false alarms.
-
We tried to fix a calibration solver's far minima. They were the data.
Warm-starting 11,442 self-calibration solves from the spec focal length reproduced every far minimum, and a basin check made the update test worse.
-
A camera's twin can't make its views better, but it knows which ones to trust
A linearised twin of the camera's calibration ranks which updates can catch a 2% focal change, and testing its top quarter doubles detection.
-
A robot can't choose its old calibration, only its new views. How much does choosing them help?
Holding the old calibration fixed, the new views a camera twin rates highest catch a 2% focal change 1.33x as often as a blind pick, 1.63x with 28 candidates.
-
A checkerboard print worth more focal-length error than self-calibration itself
Paper draft: camera self-calibration matches Zhang to 0.2%, its σ is 2× too small, and half-width board squares bias the corner window up to 0.9%.
-
The 23-pixel window that bent our checkerboard
An 11×11 cornerSubPix window misplaced outer checkerboard corners by up to 6.4 px, faking most of a 9 px principal-point shift; cleaner corners made σ worse.
-
A flat checkerboard moved our principal point by 9 pixels
Assuming a printed checkerboard is flat shifted c_y by 5 to 10 px on real photos, with a 1 px error bar. OpenCV's released-object mode equals target-free BA.