source: proiecte/pmake3d/make3d_original/Make3dSingleImageStanford_version0.1/third_party/BlueCCal/MultiCamSelfCal/changes.txt @ 37

Last change on this file since 37 was 37, checked in by (none), 14 years ago

Added original make3d
File size: 2.2 KB
Line 
1$Id: changes.txt,v 2.2 2005/05/24 09:15:31 svoboda Exp $
2
3%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
4
5List of the most significant changes since the last public release
6from 30th July 2003
7
8- The RANSAC validation was rewritten as m-functions. Hence, no
9  re-compilation of the c-codes is necessary. The user can switch
10  between the mex- and m- version of the RANSAC by specifying the path
11  in gocal.m addpath ../RansacM; % ./Ransac for mex functions The
12  m-version can be slow for highly noisy data.
13
14  The m-version of the RANSAC uses the 8-point algorithm not the
15  7-point algorithm as the c-version. It is then less optimal. I was
16  just too lazy to rewrite the more complicated 7-point algorithm. I
17  did many experiments, the 8-point algorithm did well in all cases.
18
19- gocal.m ... code cleaned, output better formatted (new function
20  dispcamstats)
21
22- local alignments ... code cleaned, redundant I/O parameters
23  (possible source of errors) removed
24
25- getpoint.m ... code cleaned, made a bit faster. Made compatible with
26  the newest image processing toolbox, ver>5
27
28- showpoints.m ... it possible to switch between single images and
29  image mosaics. The image mosaics may sometimes speed-up the
30  debugging process when something goes wrong with the point
31  detection. 
32
33- The standard Matlab function quiver was copied to the BlueCCal
34  distribution since it has problems in the newest Matlab ver>7.
35
36%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
37
38List of changes against to the last public release from 18th July 2003:
39
40Fixed Bugs in Code:
41
42- radial distorion ... proper handling of images with resolution
43  different than 640x480
44
45
46Functionality:
47
48- support for non-color images added. You may either specify
49  config.imgs.LEDcolor='intensity' and the color images will be
50  converted to a grayscale or the GETPOINT detects that the image is
51  only grayscale and it will be handled as such
52
53- main cycle in GOCAL. Some upgrade to make it more robust. I am
54  testing the upgrades on all datasets I have. It should be backward
55  compatible. Typically, new bad data discovers a small
56  functionality-bug in the main iterative cycle.
Note: See TracBrowser for help on using the repository browser.