<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff background=""><FONT face=Arial size=2>Hi,
Andinet,<BR><BR>Kevin asked me to give some comments on the IGSTK Tutorial, and
below are some quick ones:<BR><BR>It is a great job and give a very helpful
information on the first sight of IGSTK! Just some minor comments:<BR><BR>1. "
Image I/O classes: These classes provide the ability to read and display medical
images including CT and MRI in DICOM format. " <BR><BR>Should we specify the
medical images as only CT and MRI? Or we should say more, such as CT, MR, DR/CR,
PET .... Technically speaking, no difference of CT and MRI images in DICOM
format and implementation, which has internal tags to indicate number of bits,
pixel type and so on;<BR><BR>2. Viewer classes: probably we should mention
although the current version is tightly associated and implemented with FLTK,
the future version would be GUI-indepent. (It is not a good idea to tie viewer
classes with FLTK from my opinion and it is not hard to implement GUI-indepent
ones.) Some other toolkits, such as two MITKs, have already provided this
mechanic. Those would be better for other users not facing FLTK.<BR><BR>3. In
the SpatialObject section. I think spatial objects are a very nice part for
IGSTK for it provides a high-level and easy to use tool-kit than basic spatial
shapes, and these components are more attractive to the end-user's eyes. How
about adding some pictures, such as that well-designed ultrasound
probe.<BR><BR>4. Registration class: Registration is an important part in the
surgical tools. But from the tutorial, our IGSTK registration's introduction is
simple. For the reason that we only have basic rigid-body algorithm here, we can
speak some on the great error handling part recently added. The error handling
part is one distinguished part compared with other toolkits. We probably should
mention our registration module provied error handling functions, such as TRE,
FRE analysis, to get a better safety control.<BR><BR>5. Did we forget
calibration part? The reason I implement some calibration parts is to add to
IGSTK some new features which don't appear in other toolkits. And also this part
is essential in using tracked tools in CAS, although we currently only use
pre-defined parameters inside.<BR><BR>6. The tutorial on how to implement the
helloworld is a nice and straightforward part. Just one place to misspell FLTK
to FLK.<BR><BR>Nice work!<BR><BR>James<BR><BR>> <BR>> -------- Original
Message --------<BR>> Subject: [IGSTK-Developers] IGSTK-Tutorial<BR>>
Date: Mon, 06 Feb 2006 14:31:14 -0600<BR>> From: Andinet Enquobahrie
<andinet.enqu@kitware.com><BR>> To: 'IGSTK-developers'
<igstk-developers@public.kitware.com><BR>> <BR>> Dear all,<BR>>
<BR>> The IGSTK-tutorial is looking better. Please, take a look at it and
make<BR>> your comments.<BR>> <BR>>
http://public.kitware.com/IGSTKWIKI/index.php/IGSTK:Tutorial<BR>> <BR>>
thank you<BR>> <BR>> -Andinet<BR>> <BR>> <BR>> PS: The SPIE demo
is around the corner and it would be great if I can<BR>> get everybody's
comments as soon as possible. This tutorial will be a<BR>> good
document to hand out to demo participants in addition to the paper.<BR>>
Thank you.<BR>> <BR>>
_______________________________________________<BR>> IGSTK-Developers mailing
list<BR>> IGSTK-Developers@public.kitware.com<BR>>
http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers<BR>>
<BR>> <BR>> </FONT></BODY></HTML>