[Insight-developers] PointSet I/O
Parag Chandra
chandra@cs.unc.edu
Fri, 20 Apr 2001 13:21:45 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_010B_01C0C99C.D8E03F70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi,
I've written a set of classes that read and write pointsets in binary =
and ASCII formats. The class hierarchy looks like this:
ProcessObject -> PointSetSource -> PointSetReader
Writer -> PointSetWriter
so it fits in well with our existing classes. The file format is also =
very simple, consisting of a small ASCII header that defines the =
fileformat and the dimensionality of the pointset, followed immediately =
by the pointdata itself in either ASCII or binary format. Would anyone =
else find these classes useful, or should I keep them to myself? They're =
pretty simple, but no point in duplicating effort if others need this =
functionality.
The main reason I have held off on checking this work in is because it =
makes use of Unsupported/MetaImage, since that library provides a very =
convenient way to read in header information. Therefore, I'm not sure =
where to put the stuff, or if it belongs in there at all. Maybe the best =
way would be if I sent the source code to anyone interested in something =
like this, to see if it should be extended/rewritten. I'd appreciate any =
comments.
Thanks,
-Parag
------=_NextPart_000_010B_01C0C99C.D8E03F70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I've written a set of classes that read =
and write=20
pointsets in binary and ASCII formats. The class hierarchy looks like=20
this:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>ProcessObject -> PointSetSource =
->=20
PointSetReader</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Writer -> =
PointSetWriter</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>so it fits in well with our existing =
classes. The=20
file format is also very simple, consisting of a small ASCII header that =
defines=20
the fileformat and the dimensionality of the pointset, followed =
immediately by=20
the pointdata itself in either ASCII or binary format. Would anyone else =
find=20
these classes useful, or should I keep them to myself? They're pretty =
simple,=20
but no point in duplicating effort if others need this=20
functionality.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The main reason I have held off on=20
checking this work in is because it makes use of=20
Unsupported/MetaImage, since that library provides a very convenient way =
to read=20
in header information. Therefore, I'm not sure where to put the stuff, =
or if it=20
belongs in there at all. Maybe the best way would be if I sent the =
source code=20
to anyone interested in something like this, to see if it should be=20
extended/rewritten. I'd appreciate any comments.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>-Parag</FONT></DIV></BODY></HTML>
------=_NextPart_000_010B_01C0C99C.D8E03F70--