Talk:ITK Working Group Parallel Computation: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
m (Reverted edit of SssSss1, changed back to last version by Kevin Hobbs) |
Kevin Hobbs (talk | contribs) (Big Memory) |
||
| Line 4: | Line 4: | ||
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? | 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? | ||
== Big Memory == | |||
How could a cluster be used to allow ITK to handle Images larger than the memory on a single machine? | |||
Revision as of 20:36, 13 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?
Big Memory
How could a cluster be used to allow ITK to handle Images larger than the memory on a single machine?
