You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This creates bounding boxes next to each image found (e.g. for img_001.png, creates img_001_dlib.ljson)
If --synthesize is passed, missing detections are generated from a PCA basis learned on the successful detections. See here for details. Would be great to have another pair of eyes check over that and make sure the approach seems sensible.
See here for where we use these new annotations in loading a dataset in menpobench. Also, note that I am moving to store the datasets on github, e.g menpo/lfpw-train. I think this could be a great way to iteratively fix issues with datasets in an open way.
Reopened as I'd like feedback on the design before we go too much further with it.
The code to generate bounding box initialisations should probably live inside menpobench. The two initialisations that interest us from the start are:
For the object detection, we will want to:
@patricksnape @nontas @jalabort Do you agree with this approach? Some help with the following questions would be great:
menpofit/refactor
?If we get this sorted I can add lfpw, afw, ibug, and helen datasets to menpobench with detections today. Any other datasets we want for testing?
The text was updated successfully, but these errors were encountered: