More on MLTrainer

The last couple of weeks I have been working diligently on my detection software.  Many of the functions that I developed over time use the IplImage.  This of course means that in C++ I was limited to a non dynamic structure.  However, as part of my universal file format/database software I have an image format.  I was able to use this image format to manage blocks of memory for opencv (even using the iplimage).

So things might be a bit confusing to describe because of the nature of my program.  Before I had a memory management system with the interpreter.  But because I needed to open 3D Tiff stacks and other image formats, I had to rely on a structure that was more powerful than the IplImage.  This led me to incorporate the database library.  So now my software can open 3d tiff stacks and 2d images.

Since the database library has easy conversion between strings and datatypes I can theoretically now include other variables in my interpreter (and my RPN parser).  Unfortunately I have some other software and work to finish up before I can get to that level.

The next batch of software I will be making will be used for some image analysis utilizing our haar cascades.  I did this before for another project so the new batch of software should be a fast build.  I would like to try and make this software a bit more versatile so that I don't have to keep building analysis software; however, I don't expect that this should be easily accomplished as our needs are constantly changing and it would be difficult to predict our future analysis needs.