-
Patrick Snape authored
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.
dd19ce84