ITK Insight Toolkit - Slow Canny Filter?

Off the cuff, that seems a bit slow to me too, but i'll need a lot more info to help. Hardware specs? OS/IDE/how did you build ITK?

In debug or release? Are you using C++, or one of the other language wrappers? Can you put some clock() statements before and after the filter->update() call to verify the exact amount of time thats going to the edge detector, and what's going to overhead?

Many filters in ITK were written to be generic, but not necessarily optimized. OpenCV, on the other hand has been heavily optimized. It's not surprising that ITK would be much slower.

Because ITK is heavily templated, it relies on the compiler inlining function calls. If you compiled Debug (which might be your default), ITK will be really slow (make that Reaaaaaallllllllyyyyyy sssssslllooooowwwww). Try again after compiling in Release mode.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.