Documentation/Labs/FiberTractMeasurementAndVisualization - Revision history

Alexy at 18:35, 24 February 2015

2015-02-24T18:35:22Z

Alexy at 17:56, 24 February 2015

2015-02-24T17:56:45Z

Alexy: /* To be tested */

2015-02-24T17:56:04Z

To be tested

Alexy at 17:55, 24 February 2015

2015-02-24T17:55:43Z

Alexy: /* To be tested */

2015-02-20T18:59:55Z

To be tested

Alexy: /* Fiber Tract Measurements */

2015-02-20T18:59:33Z

Fiber Tract Measurements

Lauren: /* Fiber Tract Measurements */

2015-02-07T17:27:32Z

Fiber Tract Measurements

Alexy at 19:17, 16 January 2015

2015-01-16T19:17:28Z

Lauren: /* To do lists for features and bugs */

2015-01-08T23:02:24Z

To do lists for features and bugs

Lauren: /* Design and implementation */

2015-01-08T23:01:05Z

Design and implementation

@@ Line 26: / Line 26: @@
 * 9. BUG: Only the first hierarchy added to the scene can be measured from.
 * 12. Bug: select multiple clusters with Ctrl and move into a child of the top-level hierarchy. Then, toggle visibility using the eye next to this hierarchy child node. Two bugs happen. Clusters will “jump out” of the hierarchy. Also, the visibility of the multiple clusters is not updated. [Note: at Project week this was found to be a general bug with hierarchies that MRML does not get updated with multiple nodes, only one node is actually moved.] '''Status''': multi-nodes selection is currently disabled. A slicer bug filed for support of multiple node re-parenting: http://www.na-mic.org/Bug/view.php?id=3936
 ==Hierarchies==
-* 10. When you move nodes within the hierarchy and then save it, the mrml file is not checked to be saved. This means slicer is not always aware that the mrml file has been modified.
 ==Visualization==

@@ Line 25: / Line 25: @@
 * 8. fixed: Large numbers are reported in scientific notation with rounding. 1.51e+06 = 1514700, but the actual number of points was 1514703. Please don't round the integers because we want the number of points measured to be consistent.
 * 9. BUG: Only the first hierarchy added to the scene can be measured from.
-* 12. Bug: select multiple clusters with Ctrl and move into a child of the top-level hierarchy. Then, toggle visibility using the eye next to this hierarchy child node. Two bugs happen. Clusters will “jump out” of the hierarchy. Also, the visibility of the multiple clusters is not updated. [Note: at Project week this was found to be a general bug with hierarchies that MRML does not get updated with multiple nodes, only one node is actually moved.] Status: multi-nodes selection is currently disabled. A slicer bug filed for support of multiple node re-parenting: http://www.na-mic.org/Bug/view.php?id=3936
+* 12. Bug: select multiple clusters with Ctrl and move into a child of the top-level hierarchy. Then, toggle visibility using the eye next to this hierarchy child node. Two bugs happen. Clusters will “jump out” of the hierarchy. Also, the visibility of the multiple clusters is not updated. [Note: at Project week this was found to be a general bug with hierarchies that MRML does not get updated with multiple nodes, only one node is actually moved.] '''Status''': multi-nodes selection is currently disabled. A slicer bug filed for support of multiple node re-parenting: http://www.na-mic.org/Bug/view.php?id=3936
 ==Hierarchies==

@@ Line 25: / Line 25: @@
 * 8. fixed: Large numbers are reported in scientific notation with rounding. 1.51e+06 = 1514700, but the actual number of points was 1514703. Please don't round the integers because we want the number of points measured to be consistent.
 * 9. BUG: Only the first hierarchy added to the scene can be measured from.
-* 12. Bug: select multiple clusters with Ctrl and move into a child of the top-level hierarchy. Then, toggle visibility using the eye next to this hierarchy child node. Two bugs happen. Clusters will “jump out” of the hierarchy. Also, the visibility of the multiple clusters is not updated. [Note: at Project week this was found to be a general bug with hierarchies that MRML does not get updated with multiple nodes, only one node is actually moved.] Status: multi-nodes selection is currently disabled. A slicer bug filed for support of multiple node re-parenting:
+* 12. Bug: select multiple clusters with Ctrl and move into a child of the top-level hierarchy. Then, toggle visibility using the eye next to this hierarchy child node. Two bugs happen. Clusters will “jump out” of the hierarchy. Also, the visibility of the multiple clusters is not updated. [Note: at Project week this was found to be a general bug with hierarchies that MRML does not get updated with multiple nodes, only one node is actually moved.] Status: multi-nodes selection is currently disabled. A slicer bug filed for support of multiple node re-parenting: http://www.na-mic.org/Bug/view.php?id=3936
 ==Hierarchies==

@@ Line 25: / Line 25: @@
 * 8. fixed: Large numbers are reported in scientific notation with rounding. 1.51e+06 = 1514700, but the actual number of points was 1514703. Please don't round the integers because we want the number of points measured to be consistent.
 * 9. BUG: Only the first hierarchy added to the scene can be measured from.
 ==Hierarchies==
 * 10. When you move nodes within the hierarchy and then save it, the mrml file is not checked to be saved. This means slicer is not always aware that the mrml file has been modified.

@@ Line 24: / Line 24: @@
 * 3. Put num fibers and num points at the beginning of the list again.
 * 8. fixed: Large numbers are reported in scientific notation with rounding. 1.51e+06 = 1514700, but the actual number of points was 1514703. Please don't round the integers because we want the number of points measured to be consistent.
 ==Hierarchies==

@@ Line 14: / Line 14: @@
 ==Fiber Tract Measurements==
 * 2. some values are nan and some are #NAN. The nan values seem to come from the scalar measures that look incorrect in visualization, and the other values are present for those tracts. There is a bug in vtkDiffusionTensorScalarMeasurements.cxx.
 * 4. If all models in a particular hierarchy have no points (have NAN values), the overall output value should be NAN.

@@ Line 14: / Line 14: @@
 ==Fiber Tract Measurements==
-* tab delimited please
+* 2. some values are nan and some are #NAN. The nan values seem to come from the scalar measures that look incorrect in visualization, and the other values are present for those tracts. There is a bug in vtkDiffusionTensorScalarMeasurements.cxx.
-* some values are nan and some are #NAN. The nan values seem to come from the scalar measures that look incorrect in visualization, and the other values are present for those tracts. There is a bug in vtkDiffusionTensorScalarMeasurements.cxx.
+* 4. If all models in a particular hierarchy have no points (have NAN values), the overall output value should be NAN.
-* Put num fibers and num points at the beginning of the list again.
+* 5. We need a test dataset with known output to make sure this is working. Lauren will make this dataset.
-* If all models in a particular hierarchy have no points (have NAN values), the overall output value should be NAN.
+* 6. Output Text File must exist already or the module won't run. Work around: we created the text file first outside of slicer.  Would be great if the module created its own new output text file.
-* We need a test dataset with known output to make sure this is working. Lauren will make this dataset.
+* 7. A nightly test is needed. This should be improving the test of vtkDiffusionTensorMathematics in vtkTeem
 ==To be tested ==
-* fixed: Large numbers are reported in scientific notation with rounding. 1.51e+06 = 1514700, but the actual number of points was 1514703. Please don't round the integers because we want the number of points measured to be consistent.
+* 1. tab delimited please: Added Tab/Comma/Space option to the module. Use --separator Tab/Comma/Space on the command line
 ==Hierarchies==
-*Bug: select multiple clusters with Ctrl and move into a child of the top-level hierarchy. Then, toggle visibility using the eye next to this hierarchy child node. Two bugs happen. Clusters will “jump out” of the hierarchy. Also, the visibility of the multiple clusters is not updated. [Note: at Project week this was found to be a general bug with hierarchies that MRML does not get updated with multiple nodes, only one node is actually moved.]
+* 9. Bug: select multiple clusters with Ctrl and move into a child of the top-level hierarchy. Then, toggle visibility using the eye next to this hierarchy child node. Two bugs happen. Clusters will “jump out” of the hierarchy. Also, the visibility of the multiple clusters is not updated. [Note: at Project week this was found to be a general bug with hierarchies that MRML does not get updated with multiple nodes, only one node is actually moved.]
-*When you move nodes within the hierarchy and then save it, the mrml file is not checked to be saved. This means slicer is not always aware that the mrml file has been modified.
+* 10. When you move nodes within the hierarchy and then save it, the mrml file is not checked to be saved. This means slicer is not always aware that the mrml file has been modified.
 ==Visualization==
-*There are bugs with scalar measures that are due either to a) incorrect computation (likely with the nan issue in the measurements) and/or b) scalar range not updating.
+* 11. There are bugs with scalar measures that are due either to a) incorrect computation (likely with the nan issue in the measurements) and/or b) scalar range not updating.
 ==Finished==

← Older revision		Revision as of 23:02, 8 January 2015
Line 31:		Line 31:
	==Visualization==		==Visualization==
	*There are bugs with scalar measures that are due either to a) incorrect computation (likely with the nan issue in the measurements) and/or b) scalar range not updating.		*There are bugs with scalar measures that are due either to a) incorrect computation (likely with the nan issue in the measurements) and/or b) scalar range not updating.
		+
		+	==Finished==
		+	* QNAN output in cluster is ok but propagated to hierarchy is not
		+	* Please call Num_Polylines Num_Fibers instead so users can understand.
		+	* what is the category of the module> should be under diffusion tractography
		+	* Don’t skip clusters even if they have no points/lines. Put NAN at the cluster level for the measures, 0 for the points/lines, and then don’t propagate to the hierarchy level (skip it then)

← Older revision		Revision as of 23:01, 8 January 2015
Line 10:		Line 10:

	= Design and implementation =		= Design and implementation =
		+
		+	= To do lists for features and bugs =
		+
		+	==Fiber Tract Measurements==
		+	* tab delimited please
		+	* some values are nan and some are #NAN. The nan values seem to come from the scalar measures that look incorrect in visualization, and the other values are present for those tracts. There is a bug in vtkDiffusionTensorScalarMeasurements.cxx.
		+	* Put num fibers and num points at the beginning of the list again.
		+	* If all models in a particular hierarchy have no points (have NAN values), the overall output value should be NAN.
		+	* We need a test dataset with known output to make sure this is working. Lauren will make this dataset.
		+	* Output Text File must exist already or the module won't run. Work around: we created the text file first outside of slicer. Would be great if the module created its own new output text file.
		+	* A nightly test is needed. This should be improving the test of vtkDiffusionTensorMathematics in vtkTeem
		+
		+	==To be tested ==
		+	* fixed: Large numbers are reported in scientific notation with rounding. 1.51e+06 = 1514700, but the actual number of points was 1514703. Please don't round the integers because we want the number of points measured to be consistent.
		+
		+	==Hierarchies==
		+	*Bug: select multiple clusters with Ctrl and move into a child of the top-level hierarchy. Then, toggle visibility using the eye next to this hierarchy child node. Two bugs happen. Clusters will “jump out” of the hierarchy. Also, the visibility of the multiple clusters is not updated. [Note: at Project week this was found to be a general bug with hierarchies that MRML does not get updated with multiple nodes, only one node is actually moved.]
		+	*When you move nodes within the hierarchy and then save it, the mrml file is not checked to be saved. This means slicer is not always aware that the mrml file has been modified.
		+
		+	==Visualization==
		+	*There are bugs with scalar measures that are due either to a) incorrect computation (likely with the nan issue in the measurements) and/or b) scalar range not updating.