Thanks for submitting the patch. However, OutputVector is not used in any performance critical areas (and never should be); it's just a simple data structure that keeps class/cost correspondences. The classifier pushes results into the output vector and then the SimpleGrouper steps through the results and adds them to the recognition lattice.
Also, we don't want any STL dependencies in OCRopus (see the coding conventions) because STL causes numerous problems and has few benefits for OCRopus. Tom On Sep 11, 8:45 am, MattH <[email protected]> wrote: > I have submitted to the issues section a patch to OutputVector that > uses the STL hash_map. I would be interested to know if this increases > performance. > > Also, would it be worth while to have a smart outputvector that chose > between dense and sparse vectors? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ocropus" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/ocropus?hl=en -~----------~----~----~----~------~----~------~--~---
