Talk:ITK Working Group Parallel Computation: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
m (Deleted spam) |
Kevin Hobbs (talk | contribs) (Build with mpiCC) |
||
| Line 1: | Line 1: | ||
I read [http://public.kitware.com/pipermail/insight-users/2003-July/004220.html here] that there is no support for clusters and ITK. This is a shame, but there must be a way to work around it. I'm thinking of loading different Regions Of Interest on each node. If whatever algorithm has edge effects, the ROIs might overlap just enough to eliminate them. | I read [http://public.kitware.com/pipermail/insight-users/2003-July/004220.html here] that there is no support for clusters and ITK. This is a shame, but there must be a way to work around it. I'm thinking of loading different Regions Of Interest on each node. If whatever algorithm has edge effects, the ROIs might overlap just enough to eliminate them. | ||
== Build with mpiCC == | |||
I used mpiCC for a build on our cluster and I get a lot of segfaults. I can do examples like ImageReadRegionOfInterestWrite, RGBToGrayscale, and RGBImageSeriesReadWrite but MedianImageFilter and WatershedSegmentation1 segfault. I assume they use more arithmetic. I did "make test" and saw a failure with VXL fly by. How should I investigate? | |||
Revision as of 16:58, 5 January 2005
I read here that there is no support for clusters and ITK. This is a shame, but there must be a way to work around it. I'm thinking of loading different Regions Of Interest on each node. If whatever algorithm has edge effects, the ROIs might overlap just enough to eliminate them.
Build with mpiCC
I used mpiCC for a build on our cluster and I get a lot of segfaults. I can do examples like ImageReadRegionOfInterestWrite, RGBToGrayscale, and RGBImageSeriesReadWrite but MedianImageFilter and WatershedSegmentation1 segfault. I assume they use more arithmetic. I did "make test" and saw a failure with VXL fly by. How should I investigate?
