[Insight-developers] ROI Spatial Object

[Miller, James V (Research)]

If any spatial object can be used as an ROI, then I think the
ROI spatial object should probably be renamed.  I have two
concerns:

1) I am not familar with the "strand" concept
2) When our users look for an ROI object, will they find it?



> -----Original Message-----
> From: Stephen R. Aylward [mailto:aylward@unc.edu]
> Sent: Tuesday, April 29, 2003 5:30 PM
> To: Insight-Developers (E-mail)
> Subject: [Insight-developers] ROI Spatial Object
> 
> 
> 
> Hi,
> 
> I'd like to suggest a better name for the ROI spatial objects.
> 
> itkROISpatialObjects are slice-based objects - they require 
> points to be 
> stored as "strands."   A strand holds either x, y, or z 
> constant while 
> the other two coordinates vary to define the object's 
> intersection with 
> the slice.
> 
> Since the data container is the only difference between this 
> and other 
> spatial objects, couldn't we instead call these 
> StrandSpatialObjects or 
> SlicedSpatialObjects or derive from blobSpatialObjects to be 
> SlicedBlobSpatialObjects?
> 
> All of the spatial objects can actually be used as ROIs...as can 
> itkSpatialFunctions, etc.
> 
> Also - in the comments of itkROISpatialObject it is stated 
> that some of 
> the definitions of IsInside are ad-hoc in the other spatial 
> objects...please let me know which ones and I will fix them.
> 
> Thanks,
> Stephen
> 
> -- 
> ===============================================
> Dr. Stephen R. Aylward
> Assistant Professor of Radiology
> Adjunct Assistant Professor of Computer Science
> http://caddlab.rad.unc.edu
> aylward@unc.edu
> (919) 966-9695
> 
> _______________________________________________
> Insight-developers mailing list
> Insight-developers@public.kitware.com
> http://public.kitware.com/mailman/listinfo/insight-developers
>