Wednesday, June 22, 2011

WPF

Program save button removed - On measure, the program will automatically save a thumbnail of the diatom.

Perimeter works (Accuracy unknown) - Uses convex hull.

Erosion and Threshold functions work much better now. Still bugs with overlapping diatoms currently.

Tried a few different grayscaling algorithms, but none have worked. I tried using histograms (Red, Green, and Blue) to get which there were more of for the normal Grayscale. Still, doesn't function on one entire set of images.

Can now open images after another image has been opened. Program frees unused memory and clears garbage collection. But even with that it still has out of memory errors. There must be something that I am creating that isn't being disposed.

Idea for running on an entire folder of images.

If all the images are similar user can "calibrate" the program on the first image.
-set up the grayscale coefficients, and the threshold that gives the best result.

Then the program can run with this information, placing copies in a folder named after the original (-processed added to the end).

Then the user can do the calculations/actions required on each image. Because the original and new images are both accessible the overlay will still work (but not for Edge Detection, Fill Holes, Grayscale, etc.)

1 comment:

  1. I like your idea for processing a sequence of similar images in a folder. Some people may even want to go back and forth between images (maybe with prev/next buttons?)

    The greycale may be difficult because the exposure changes for every frame captured? I don't know if the images are captured with the camera running in fully automatic mode.

    To look for memory errors, you may want to try a code profiling tool. I think all of these profile memory as well as execution speed:

    http://en.wikipedia.org/wiki/List_of_performance_analysis_tools#.NET

    Some are commercial products with trial periods.

    ReplyDelete