Home Methods Use Tips Download References & Credit

Use Tips -Cali Cam requires several pictures with the calibration target at different orientations. If the orientations of the targets are not different enough, numerical instabilities can result. -In practice, if the skew is calculated absudly high then the set of images is probably degenerate. -The 'no skew' option is usually a fair assumption and can provide better results -If the principle point (u0,v0) is far from the center of the picture, more views of the target near the edges of the image are probably needed. -Currently Cali Cam does not verify that all images are the same dimensions and if the views are not degenerate. -The model points are now normalized! However absurd values (near and at zero, extreme large magnitude values) may still cause problems -The save pictures option will save the undistorted calibration pictures in the same directory of the source image--"result" or "failed" will be appended depending if a picture was used for calibration or not. On "result" pictures, the calibration points are marked with dim markers and the bright markers depict the projection of of the abstract model points onto the picture. On "failed pictures, the markers will be brighter but will only correspond to either the points found or the partial grid constructed. -A low memory option has not yet been implemented. Currently all pictures must be able to fit in memory. -During calibration, Cali Cam will appear to freeze for a time. This is due to the calibration not being forked to a separate thread and is only an aesthetic issue. Future versions of Cali Cam will be improved so that the calibration can proceed in the background without affecting the responsiveness of the GUI as well as providing status updates. If Cali Cam is run from the command line, information of the progress of the calibration is relayed to the user.