[Insight-users] Re sampleImageFilter and ITK_USE_OPTIMIZED_REGISTRATION_METHODS

[Pete79]

<qoute>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.
</qoute>

Bradely, hi.

I guess ITK can host several pipelines though. Alas, on the outset I had
only made sure images fed to the thread were already updated - that's where
one would hope the main thread pipeline can be queried by multiple threads
without any harm being done. 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. I thought only updating (the actually
triggered process) changes status of a pipeline. Though, even if up-to-date,
calling Update must write to status status structures or so. I believe
that's where it gets multithread unsafe.

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-tp25967879p26017542.html
Sent from the ITK - Users mailing list archive at Nabble.com.