[Insight-users] Re sampleImageFilter and ITK_USE_OPTIMIZED_REGISTRATION_METHODS

[Pete79]

Bradley Lowekamp wrote:
> 
> It sounds like you are doing your own threading, and you have multiple  
> threads trying to execute the pipeline. ITK expects only one thread to  
> be executing or updating the pipeline. The pipeline is not thread safe  
> in the way you appear to be assuming. This would explain the sporadic  
> crashing.
> 

Bradely, hi.

I cannot see a reason why ITK couldn't let host several pipelines - each per
its own custom thread - and this is what I'm doing. I make sure images fed
to the thread are already updated - that's where one would hope the main
thread pipeline ends basically. Then, each thread has its own pipeline
related to locally allocated filters. Though (!!!) ...

I can imagine that when I relied on ROI filter, it was reaching source image
pipeline while being updated itself. Source image was fed to many threads
and that could potentially confuse behaviour of this pipeline being queried
by a bunch of ROIs at the same time.

Well done then, coz copying image ROI with an iterator (instead of ROI
filter) separates pipelines and this seems like the right way forward then.

Cheers a lot,
Peter
-- 
View this message in context: http://www.nabble.com/ResampleImageFilter-and-ITK_USE_OPTIMIZED_REGISTRATION_METHODS-tp25967879p26016716.html
Sent from the ITK - Users mailing list archive at Nabble.com.