[Insight-developers] Draft for the ITK statistical modelling module

[Miller, James V (CRD)]

I would put that statistics is a separate names under the ITK
namespace.

namespace itk {
	namespace statistics {

	}
}

I have not looked at the particular names yet. 

If it makes sense to have an operator< on itk::Index() then add it
there.  The trouble here is what does operator< mean on a multidimensional
index?

I1 < I2 could be true if one of the components of I1 is less than the
corresponding component in I2 AND the remaining components are less than
or equal to the corresponding component in I2. The intuition in 2D is that
I1 is "below and to the left of" I2.

Does operator< makes sense for an Index? Or do we need it just that we can 
used the MapContainer?

If the latter, does it makes sense to use the MapContainer? Or should we use
a container that does not sort its "keys".




-----Original Message-----
From: Jisung Kim [mailto:bahrahm@yahoo.com]
Sent: Thursday, October 11, 2001 10:29 AM
To: insight-dev-list
Subject: [Insight-developers] Draft for the ITK statistical modelling
module


Hi.

I made a document about ITK statistical modelling
module. Neither the document nor the module is
complete in any sense. However, the document explains
the architecture of the module and reflects current
implementation of the module. The attached document is
a text file with column size 79. I haven't check in
the new codes. As soon as naming and namespace issues
are settled down, I will check in the new codes.
Before you read the following "some current issues"
section, please read the attached document first.

Thank you,
Jisung.

-- Some current issues

   * Do we need a separate namespace for this
module?If so, what is good name? itks? I think having
a separate namespace from itk would be nice. The
statistical modelling module should be a set of
general statistical tools. There are possible class
name conflicts. Grouping this module's class using a
namespace might help users extinguish it from other
parts of ITK. Since users are probably already using
more than one namespaces in their programs such as itk
and std, at least I do, there is no extra typing.

   * Do the class names make sense to users who have
basic statistical knowledge? I have never seen
"feature domain" in anyliterature.    

   * I will make the Label and DensityEstimate classes
internally use itk::MapContainer. The key type of the
map structure is InstanceIdentifier type and the value
type is label or density estimate values as map value
type. The problem is that the InstanceIdentifier can
be either unsigned long (PointSetTable) or itk::Index
(other FeatureDomain subclasses). Since MapContainer
requires less than operator (<) for the key type, I
need something like itk::Index with less than
operator. I am considering creating a subclass of
itk::Index. The name of the class can be
"itks"::ComparableIndex. Is this approach a good  
idea? Or any other options? 


=====
Jisung Kim
bahrahm@yahoo.com
106 Mason Farm Rd.
129 Radiology Research Lab., CB# 7515
Univ. of North Carolina at Chapel Hill
Chapel Hill, NC 27599-7515

__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com