dlib/tools
Patrick Snape dd19ce846e Update the interface to be more Pythonic
This is the biggest change so far. Now, there are two different
classes of interface. One where you pass ONLY file paths,
and one where you pass ONLY Python objects.

The file paths are maintained to keep a matching interface with
the C++ examples of dlib. So shape predicition and object
detection can be trained using the dlib XML file paths and then
serialize the detectors to disk.

Shape prediction and object detection can also be trained using
numpy arrays and in-memory objects. In this case, the predictor
and detector objects are returned from the training functions.
To facilitate serializing these objects, they now have a 'save'
method.

Tetsing follows a similar pattern, in that it can take either XML
files are or in-memory objects. I also added back the concept of
upsampling during testing to make amends for removing the
simple_object_detector_py struct.
2014-12-11 14:06:05 +00:00
..
htmlify more cmake changes to avoid cmake warnings 2014-12-06 08:38:04 -05:00
imglab more cmake changes to avoid cmake warnings 2014-12-06 08:38:04 -05:00
mltool more cmake changes to avoid cmake warnings 2014-12-06 08:38:04 -05:00
python Update the interface to be more Pythonic 2014-12-11 14:06:05 +00:00