Go to file
Patrick Snape e3c3d39ab1 Add an API for the correlation tracker
This aids an API for the correlation based tracker that Davis
recently added to Dlib. I've made sure to allow overrides for
passing normal rectangles rather than drectangles (which isn't
currently supported in the Dlib C++ API). This is mostly
because I imagine people might initialize the tracking using
something like a bounding box from a detector (e.g.
load_frontal_face_detector).
2015-05-20 11:29:14 +01:00
dlib Added a max iterations option to the sequence labeling and segmentation 2015-05-05 18:01:52 -04:00
docs Created release v18.15 2015-04-29 21:39:59 -04:00
examples added comments about using imglab 2015-03-29 16:47:37 -04:00
python_examples Added default upsampling amount to detector.run(). Also moved the 2015-03-28 23:16:54 -04:00
tools Add an API for the correlation tracker 2015-05-20 11:29:14 +01:00
.gitignore updated ignore list 2015-03-28 23:16:35 -04:00
.hgignore updated ignore file 2014-03-08 21:41:59 -05:00
.hgtags Added tag v18.15 for changeset feaff82884de 2015-04-29 21:39:59 -04:00
README.txt updated readme 2014-08-19 19:11:24 -04:00


See http://dlib.net for the main project documentation.



COMPILING DLIB EXAMPLE PROGRAMS
   Go into the examples folder and type:
   mkdir build; cd build; cmake .. ; cmake --build .

   That will build all the examples.  There is nothing to install when using
   dlib.  It's just a folder of source files.  

RUNNING THE UNIT TEST SUITE
   Type the following to compile and run the dlib unit test suite:
       cd dlib/test
       mkdir build
       cd build
       cmake ..
       cmake --build . --config Release
       ./dtest --runall

   Note that on windows your compiler might put the test executable in a
   subfolder called Release.  If that's the case then you have to go to that
   folder before running the test.

DOCUMENTATION
   The source control repository doesn't contain finished documentation.  The
   stuff in the docs folder is just a bunch of scripts and xml files used to
   generate the documentation.  There is a readme in docs/README.txt which
   discusses how to do this.  However, unless you are trying to modify the
   documentation, you should just download a copy from http://dlib.net.