2008 Winter Project Week:Astronomical Medicine - Revision history

Nessus: /* January 2008 Project Week */

2008-06-05T21:34:33Z

January 2008 Project Week

Mhalle: /* January 2008 Project Week */

2008-02-14T16:58:06Z

January 2008 Project Week

Mhalle: Added vtkCoordinateSystemManager description

2008-01-11T15:23:32Z

Added vtkCoordinateSystemManager description

Nessus: /* June 2006 Project Week */

2008-01-08T01:00:49Z

June 2006 Project Week

Nessus at 21:15, 2 January 2008

2008-01-02T21:15:21Z

Nessus at 21:14, 2 January 2008

2008-01-02T21:14:07Z

Nessus at 21:13, 2 January 2008

2008-01-02T21:13:34Z

Nessus: /* June 2007 Project Week */

2008-01-02T21:02:27Z

June 2007 Project Week

Nessus: /* References */

2008-01-02T21:00:21Z

References

Nessus: /* References */

2008-01-02T20:59:46Z

References

@@ Line 33: / Line 33: @@
 ====January 2008 Project Week====
-* Created vtkCoordinateSpaceManager, a container that manages multiple named coordinate spaces and the transforms between them. A reader can populate a coordinate space manager with all the coordinate spaces it knows about.  Registration tools can link otherwise unrelated coordinate spaces, and the manager can hand back a (possibly composite) transform between any to related spaces. This module hasn't been incorporated into Slicer3 yet.
+* Created vtkCoordinateSpaceManager, a container that manages multiple named coordinate spaces and the transforms between them. A reader can populate a coordinate space manager with all the coordinate spaces it knows about.  Registration tools can link otherwise unrelated coordinate spaces, and the manager can hand back a (possibly composite) transform between any two related spaces. This module hasn't been incorporated into Slicer3 yet.
 * With Wendy Plesniak's help, we now have the ability to recenter on data not located at the origin in Slicer. She's incorporating similar changes into the "look from" Slicer control. We'll need to look at autozooming as well for very small volumes.
 * Slicer3 volume rendering works reasonably well with astronomical data, but the world size of model seems to influence rendering appearance. Solved some performance issues on the Mac.
 * Experimental linearized celestial coordinate system implementation being tested now.
-* Still need standard way to deal with NaNs in ITK/VTK/Slicer3.
+* Prototyped Slicer3 plugin module adapter for fits2itk.
 ====June 2007 Project Week====

@@ Line 33: / Line 33: @@
 ====January 2008 Project Week====
-* Created vtkCoordinateSpaceManager, a container that manages multiple named coordinate spaces and the transforms between them. A reader can populate a coordinate space manager with all the coordinate spaces it knows about.  Registration tools can link otherwise unrelated coordinate spaces, and the manager can hand back a (possibly composite) transform between any to related spaces.
+* Created vtkCoordinateSpaceManager, a container that manages multiple named coordinate spaces and the transforms between them. A reader can populate a coordinate space manager with all the coordinate spaces it knows about.  Registration tools can link otherwise unrelated coordinate spaces, and the manager can hand back a (possibly composite) transform between any to related spaces. This module hasn't been incorporated into Slicer3 yet.
-* -- Execution model stuff --
+* With Wendy Plesniak's help, we now have the ability to recenter on data not located at the origin in Slicer. She's incorporating similar changes into the "look from" Slicer control. We'll need to look at autozooming as well for very small volumes.
-* -- NaN stuff --
+* Slicer3 volume rendering works reasonably well with astronomical data, but the world size of model seems to influence rendering appearance. Solved some performance issues on the Mac.
 ====June 2007 Project Week====

← Older revision		Revision as of 15:23, 11 January 2008
Line 31:		Line 31:

	<h1>Progress</h1>		<h1>Progress</h1>
		+	====January 2008 Project Week====
		+
		+	* Created vtkCoordinateSpaceManager, a container that manages multiple named coordinate spaces and the transforms between them. A reader can populate a coordinate space manager with all the coordinate spaces it knows about. Registration tools can link otherwise unrelated coordinate spaces, and the manager can hand back a (possibly composite) transform between any to related spaces.
		+	* -- Execution model stuff --
		+	* -- NaN stuff --
		+
	====June 2007 Project Week====		====June 2007 Project Week====

@@ Line 41: / Line 41: @@
 ====June 2006 Project Week====
-Implemented a prototype FITS reader for ITK.  We later released this as an open-source FITS-to-NRRD file converter, which is available [http://astromed.iic.harvard.edu/FITS-reader here].
+Implemented a prototype FITS reader for ITK.  We later released a subsequent version as an open-source FITS-to-NRRD file converter, which is available [http://astromed.iic.harvard.edu/FITS-reader here].
 </div><br style="clear: both;" /></div>

@@ Line 25: / Line 25: @@
 Our approach is summarized on the [http://astromed.iic.harvard.edu Astronomical Medicine web site].  The main challenge to this approach at the moment, is the impedance mismatch between celestial coordinates and medical imaging coordinates, and a lack of infrastructure within ITK and Slicer to allow for alternative coordinate systems.
-Our plan for the project week is to make further progress in integrating our ITK FITS reader into Slicer as a plug-in, and to begin work on Slicer GUI enhancements to support our FITS plug-in and to allow the display of astronomical coordinates in slicer viewers.
+Our plan for the project week is to make further progress in integrating our ITK FITS reader into Slicer as a plug-in, and to begin work on Slicer GUI enhancements to support our FITS plug-in and to allow the display of astronomical coordinates in slice viewers.
 </div>

@@ Line 23: / Line 23: @@
 <h1>Approach, Plan</h1>
-Our approach is summarized on the [http://astromed.iic.harvard.edu Astronomical Medicine web site].  The main challenge to this approach, at the moment, is the impedance mismatch between celestial coordinates and medical imaging coordinates, and a lack of infrastructure within ITK and Slicer to allow for alternative coordinate systems.
+Our approach is summarized on the [http://astromed.iic.harvard.edu Astronomical Medicine web site].  The main challenge to this approach at the moment, is the impedance mismatch between celestial coordinates and medical imaging coordinates, and a lack of infrastructure within ITK and Slicer to allow for alternative coordinate systems.
 Our plan for the project week is to make further progress in integrating our ITK FITS reader into Slicer as a plug-in, and to begin work on Slicer GUI enhancements to support our FITS plug-in and to allow the display of astronomical coordinates in slicer viewers.

@@ Line 57: / Line 57: @@
 <h1></h1><br>
 ====References====
-* [http://am.iic.harvard.edu Astronomical Medicine web site]
+* The [http://am.iic.harvard.edu Astronomical Medicine web site]
 * [http://am.iic.harvard.edu/FITS-reader Open-source release] of our ITK-based FITS file reader/converter.