MeanShiftImageFilter and MeanShiftVectorImageFilter does not produce the same output according to the number of threads
Mantis Issue 36, reported by jmichel, assigned to jmalik, created: 2008-12-01
The ouptut of the MeanShiftImageFilter and the MeanShiftVectorImageFilter is different when the number of available threads changes. The difference can be quite huge, especially for the clustered outputs.
I would suggest to let down the ThreadedGenerateData() implementation and to use a simple GenerateData() instead.
1303471267 - mickaelThis issue seems to be not solved today, some tests are OK but the weird behavior is already here : bfTvMeanShiftImageFilter (test with streaming and threading) provide 4 different outputs:
- baselines.1 for Unix64/Leod
- baselines.2 for Win64 platforms
- baselines.3 for pc-christophe (32bit ?)
- baseline.3, baseline.4, baseline.3, baseline.3 for Win32 platform
bfTvMeanShiftImageFilterNotStreamedNotThreaded provide 2 different outputs:
- baseline.0 for all platforms except windows
- baseline.0, baseline.5, baseline.0, baseline.0 for windows platform
The following tests with VectorImage are KO on some platforms: bfTvMeanShiftVectorImageFilter provide 4 different outputs:
- baseline.1 for Unix64/Leod
- Win64, Win32 and pc-christophe have huge differences with output 2,3 and 4 although first output seems correct in the 3 cases.
bfTvMeanShiftVectorImageFilterNotStreamedNotThreaded provide 2 different outputs:
- baseline.0 for all platforms except windows
- windows plat