Slicer-3.6-QA

Return to Slicer 3.6 documentation

• This page contains our assessment of the Slicer 3.6 modules

• See also the module culling event at the end of April 2010

Testing Status

Core Modules

Slicer 3.6 Quality Assurance

Score	Name	Documentation	Help	Acknowledgment	Current Owner
??	Camera	complete	yes, no link	no	Sebastien Barre
??	Welcome	complete	yes and yes	yes and yes	Wendy Plesniak
??	Volumes	complete	yes and yes	yes and yes	Steve Pieper
??	Diffusion Editor	complete	yes and yes	no	CF Westin
??	Models	complete	yes and yes	yes and yes	Alex Yarmarkovich
??	Measurements	complete	yes and yes	yes and yes	Nicole Aucoin
??	Fiducials	complete	yes and yes	yes and yes	Nicole Aucoin
??	Data	complete	yes and yes	yes and yes	Steve Pieper
??	Slices	complete	yes and yes	yes and yes	Jim Miller
??	Colors	complete	yes and yes	yes and yes	Nicole Aucoin
??	Interactive Editor	complete	no and yes	yes and no	Steve Pieper
??	ROI Module	complete	no and yes	no and yes	Alex Yarmarkovich
??	Volume Rendering	complete	yes and yes	no and yes	Yanling Liu
??	PET/CT Fusion	complete	yes and yes	yes and yes	Wendy Plesniak

Application CLI Modules

Version of 04-29-2010

Slicer 3.6 QA table 2010 04 29

Version of 05-2010

Part A

Slicer 3.6 Quality Assurance

Score	Name	Documentation	Help	Acknowledgment	Test coverage	valgrind errors	Current Owner	Comments	3.6 Documentation Name
	ACPC Transform	complete	yes and yes	yes and yes	75%	1	Nicole Aucoin		same
	Add Images	complete	yes and yes	yes and yes	84.9%	0	Bill Lorensen		AddImages
	Affine registration (Fast Affine Registration ?)	complete	yes and no	yes and yes	68.4%	82	Daniel Blezek		same
	BRAINSDemonWarp	complete	yes and no	yes and no	78.4%	Unknown	Hans Johnson, Greg Harris		same
	BRAINSFit	complete	yes and yes	yes and yes	73.3%	Unknown	Eun Young Kim		same
	BRAINSResample	no	yes and yes	yes and no	76.7%	Unknown	Hans Johnson		n/a
	BRAINSROIAuto	no	yes and no	yes and no	xx	Unknown	Hans Johnson		n/a
	BRAINSVectorDemonWarping	no	yes and no	yes and no	xx	Unknown	Hans Johnson		n/a
	Cast Image	complete	yes and yes	yes and yes	24.1%	XX	Nicole Aucoin		Cast Image
	CheckerBoard Filter	complete	yes and yes	yes and yes	67.4%	xx	Bill Lorensen		CheckerBoard Filter
	Create a DICOM Series	complete	yes and yes	yes and yes	86.1%	xx	Bill Lorensen		Create a Dicom Series
	Curvature Anisotropic Diffusion	complete	yes and yes	yes and yes	64.3%	XX	Bill Lorensen		same
	Deformable BSpline registration	complete	yes and yes	yes and yes	82.3%	xx	Bill Lorensen		Fast Nonrigid BSpline Registration
	Dicom to Nrrd Converter				35.8%	xx	??	|n/a
	Diffusion Tensor Estimation	complete	yes and no	yes and yes	79.7%	9	CF Westin		same
	Diffusion Tensor Scalar Measurements	no	yes and no	yes and yes	56.2%	5	CF Westin		Diffusion Tensor Scalar Measurements
	EMSegment BatchMake				TBF	TBF	author	|n/a
	EMSegment Command-line				TBF	TBF	author	|n/a
	EMSegment Simple				TBF	TBF	author	|n/a
	Execution Model Tour				TBF	TBF	author	|n/a
	Extract Skeleton	no	yes and no	no and yes	0.0%	Unknown	Pierre Seroul, Martin Styner, Guido Gerig, Stephen Aylward		n/a
	Gaussian Blur BatchMake				TBF	TBF	author	|n/a
	Gaussian Blur	complete	yes and no	yes and yes	55.9%	0	Julien Jomier, Stephen Aylward		Gaussian Blur
	Gradient Anisotropic Diffusion	complete	yes and yes	yes and yes	63.4%	0	Bill Lorensen		GradientAnisotropicFilter
	Grayscale Fill Hole	complete	yes and yes	yes and yes	57.1%	0	Bill Lorensen		Grayscale Fill Hole
	Grayscale Grind Peak				TBF	TBF	author	|n/a
	Grayscale Model Maker				TBF	TBF	author	|n/a
	Histogram Matching				TBF	TBF	author	|n/a
	Image Label Combine				TBF	TBF	author	|n/a
	Joint Rician LMMSE Image Filter				TBF	TBF	author	|n/a
	Labelmap Seeding				TBF	TBF	author	|n/a
	Label Map Smoothing				TBF	TBF	author	|n/a
	Linear registration				TBF	TBF	author	|n/a

Part B

Slicer 3.6 Quality Assurance

Score	Name	Documentation	Help	Acknowledgment	Test coverage	valgrind errors	Current Owner	Comments	3.6 Documentation Name
	Mask Image				82%	TBF	author	|n/a
	Median Filter				57%	TBF	author	|n/a
	Merge Models				87%	TBF	author	|n/a
	Mesh Contour Segmentation				TBF	TBF	author	|n/a
	Model Maker				41%	TBF	author	|n/a
	MRI Bias Field Correction				TBF	TBF	author	|n/a
	Multiple models example				2.5%	TBF	author	|n/a
	Multiply Images				80%	TBF	author	|n/a
	N4ITK MRI Bias correction				TBF	TBF	author	|n/a
	Orient Images				88%	TBF	author	|n/a
	Otsu Threshold Segmentation				91%	TBF	author	|n/a
	Otsu Threshold				100%	TBF	author	|n/a
	PolyData To Label Map				89%	TBF	author	|n/a
	Register Images BatchMake				TBF	TBF	author	|n/a
	Register Images MultiRes (Experimental)				TBF	TBF	author	|n/a
	Register Images				TBF	TBF	author	|n/a
	Resample DTI Volume				100%	TBF	author	|n/a
	Resample Scalar/Vector/DWI Volume				43%	TBF	author	|n/a
	Resample Scalar Volume BatchMake				TBF	TBF	author	|n/a
	Resample Scalar Volume				TBF	TBF	author	|n/a
	Rician LMMSE Image Filter				TBF	TBF	author	|n/a
	Rigid registration				61%	TBF	author	|n/a
	Robust Statistics Segmentation				TBF	TBF	author	|n/a
	ROISelect				TBF	TBF	author	|n/a
	Simple DWI IO Test				TBF	TBF	author	|n/a
	Simple IO Test				TBF	TBF	author	|n/a
	Simple region growing				TBF	TBF	author	|n/a
	Subtract Images				76%	TBF	author	|n/a
	Test GridTransform registration				100	TBF	author	|n/a
	Threshold Image				59%	TBF	author	|n/a
	Transform From Fiducials				TBF	TBF	author	|n/a
	Unbiased Non Local Means filter for DWI				TBF	TBF	author	|n/a
	Voting Binary Hole Filling				100%	TBF	author	|n/a

Testing Partition

Most Slicer modules have a GUI component and a Data Processing component.

Testing GUI components is still a challenge, so we will focus here on testing the Data Processing components. This can be done in most cases by partitioning the module into a GUI section and a Data Processing section, where the second one usually takes the form of a C++ class (although that is not a requirement).

The data processing section can be tested by using standard CTest/CMake mechanisms. Basically by adding ADD_TEST() entries to the CMakeLists.txt file of the module.

Luis Ibanez' scoring system

The following scoring will be applied to the data processing sections of all modules:

Slicer 3.6 Quality Assurance Scoring

Score	Code Coverage	Valgrind Errors	Documentation	Tutorial
1Gold	> 80%	0	yes	yes
2Silver	> 70%	< 10	yes	yes
3Bronze	> 60%	< 50	yes	yes
4Clay	> 50%	< 100	yes	yes
5Coal	< 50%	> 100	yes	yes
6Hazard	unknown	unknown	no	no

The code coverage and Valgrind error must be the ones reported on the Nightly Slicer Dashboard. Anecdotal data is not acceptable.