Slicer3:TimeSeries and Multi-Volume Data - Revision history

Marianna: /* Hierarchical Management of Large Data Sets */

2008-05-20T17:57:19Z

Hierarchical Management of Large Data Sets

Marianna: /* Data format testing */

2008-05-20T17:56:13Z

Data format testing

Marianna: 28 revisions

2008-05-15T17:53:26Z

28 revisions

Pieper: /* Feature ideas */

2008-03-31T17:55:34Z

Feature ideas

Blezek: /* Data format testing */

2008-03-08T03:43:27Z

Data format testing

Blezek: /* Data format testing */

2008-03-02T02:36:27Z

Data format testing

Blezek: /* Data format testing */

2008-02-25T05:13:05Z

Data format testing

Blezek: /* Data format testing */

2008-02-25T05:10:05Z

Data format testing

Blezek: /* Use Cases */

2008-02-25T05:06:11Z

Use Cases

Blezek: /* Use Cases */

2008-02-03T03:11:01Z

Use Cases

← Older revision		Revision as of 17:57, 20 May 2008
Line 100:		Line 100:
	''I'd like to see a project to implement this approach inside VTK (and, possibly, ITK). There have been a few attempts in the past (DataCutter at OSU, is similar, I believe, but the code doesn't appear to be available and so far the people I've been asking at BWH, GE, Kitware don't know the details -- this is something I can research more).''		''I'd like to see a project to implement this approach inside VTK (and, possibly, ITK). There have been a few attempts in the past (DataCutter at OSU, is similar, I believe, but the code doesn't appear to be available and so far the people I've been asking at BWH, GE, Kitware don't know the details -- this is something I can research more).''

−	''What I have in mind is four related tools: ~~(1)~~ a preprocessor to build a hierarchical volume datastructure/database~~, (2)~~ a server that will take requests for a given extent at a given resolution and provide back the volume data~~, (3)~~ a demo web site that will allow interactive browsing through large data sets~~, and (4)~~ an implementation in slicer to load and display these multi-resolution volumes for interactive visualization.''	+	''What I have in mind is four related tools:
		+	# a preprocessor to build a hierarchical volume datastructure/database
		+	# a server that will take requests for a given extent at a given resolution and provide back the volume data
		+	# a demo web site that will allow interactive browsing through large data sets
		+	# an implementation in slicer to load and display these multi-resolution volumes for interactive visualization.''

@@ Line 48: / Line 48: @@
 Results
 {| border="1"
-|- bgcolor="#abcdef"
+|- bgcolor="#ccccff"
 ! Software !! Write performance (256x256x10x16) !! Read performance (256x256 slice, averaged over 1000 slices)
 |-

@@ Line 12: / Line 12: @@
 ** Volume by volume
 ** Slice by Slice (would require a "block of bytes" format like NRRD, Analyze, or NIFTI)
 === Potentially useful codes ===

@@ Line 47: / Line 47: @@
 ! Software !! Write performance (256x256x10x16) !! Read performance (256x256 slice, averaged over 1000 slices)
 |-
-| SQLite || 1.3sec || 0.017sec
+| SQLite
-| HDF5   || 2.6sec ||  0.017sec
+| 1.3sec
-| Raw    || 0.6sec || 0.004sec
+| 0.017sec
 |}

@@ Line 45: / Line 45: @@
 {| border="1"
 |- bgcolor="#abcdef"
-! Software !! Write performance (256x256x10x16) !! Read performance (average per 256x256 slice)
+! Software !! Write performance (256x256x10x16) !! Read performance (256x256 slice, averaged over 1000 slices)
 |-
-| Coming soon || Entry2 || Entry3
+| SQLite || 1.3sec || 0.017sec
 |}
 === Mock-ups and ideas ===

← Older revision	Revision as of 17:53, 15 May 2008
(No difference)

← Older revision		Revision as of 05:10, 25 February 2008
Line 43:		Line 43:

	Results		Results
		+	{\| border="1"
		+	\|- bgcolor="#abcdef"
		+	! Software !! Write performance (256x256x10x16) !! Read performance (average per 256x256 slice)
		+	\|-
		+	\| Entry1 \|\| Entry2 \|\| Entry3
		+	\|-
		+	\| Entry1 \|\| Entry2 \|\| Entry3
		+	\|}

	=== Mock-ups and ideas ===		=== Mock-ups and ideas ===

@@ Line 33: / Line 33: @@
 # Process one volume at a time through all volumes (same as previous?)
 # Render dynamic time series, e.g. cardiac data
 === Mock-ups and ideas ===

@@ Line 26: / Line 26: @@
 # User pages through same slice from all volumes in acquisition orientation
-# User pages through reformatted slice from all volumes in acquisition orientation
+# User pages through reformatted slice from all volumes
 # Process one pixel at a time through all volumes
 ## Process in an "accumulator" mode
 ## Process by analyzing whole time course of voxel (could possibly be done slice at a time?)
 # Process one slice at a time through all volumes
-# Process one volume at a time through all volumes
+# Process one volume at a time through all volumes (same as previous?)
 # Render dynamic time series, e.g. cardiac data