Slicer-3.6-QA

From Slicer Wiki
Jump to: navigation, search
Home < Slicer-3.6-QA

Return to Slicer 3.6 documentation

  • This page contains our assessment of the Slicer 3.6 modules

Testing Status

Core Modules

Slicer 3.6 Quality Assurance
Score Name Documentation Help [1] Acknowledgment [2] Test coverage [3] valgrind errors Current Owner Comments [4]
Gold my module complete yes and yes yes, yes, yes 80% 0 DNK
?? Camera complete yes, no link no 75% unknown Sebastien Barre
?? Volumes complete yes and yes yes and yes 44% unknown Steve Pieper
?? Diffusion Editor complete yes and yes no 65%* unknown CF Westin Files found under svn.slicer.org/Slicer3/trunk/Modules/Volumes/
?? Models complete yes and yes yes and yes 12% unknown Alex Yarmarkovich
?? Measurements complete yes and yes no and yes 46% unknown Nicole Aucoin
?? Fiducials complete yes and yes no 7% unknown Nicole Aucoin
?? Data complete yes and yes yes and yes 10% unknown Steve Pieper
?? Slices complete no no 40% unknown Jim Miller
?? Colors complete yes and no yes and no 8% unknown Nicole Aucoin
?? Interactive Editor complete no and yes yes and no unknown unknown Steve Pieper
?? ROI Module complete no and yes no and yes 22% unknown Alex Yarmarkovich
?? Volume Rendering complete yes and yes no and yes 22% unknown Yanling Liu
  1. including link to website documentation
  2. including name of author and of supervisor
  3. in % for non-interactive part
  4. Unless otherwise noted, Test coverage percentage determined by: [# lines code covered / total # lines of code (covered and non-covered) *100] of relevant .cxx and .h files

Application CLI Modules

Slicer 3.6 Quality Assurance
Score Name Documentation Help [1] Acknowledgment [2] Test coverage [3] valgrind errors Current Owner
Gold my module complete yes and yes yes, yes, yes 80% 0
?? DiffusionWeightedTest no no yes and yes 69.8% 0 Raul San Jose Estepar
?? DiffusionTensorEstimation complete yes and no yes and yes 79.7% 9 Raul San Jose Estepar
?? DiffusionTensorMathematics no yes and no yes and yes 56.2% 5 Raul San Jose Estepar
?? OrientImage complete yes and yes yes and yes 85.7% 0 Bill Lorensen
?? LinearRegistration complete yes and no yes and yes 66.7% 4 Daniel Blezek
?? RigidRegistration no yes and no yes and yes 1.0% 92 Daniel Blezek
?? AffineRegistration complete yes and no yes and yes 1.4% 82 Casey Goodlett
?? BSplineDeformableRegistration complete yes and yes yes and yes 82.3% 6 Bill Lorensen
?? TestGridTransformRegistration no no yes and yes 90.7% 0 Yinglin Lee
?? CheckerBoard complete yes and yes yes and yes 67.4% 0 Bill Lorensen
?? ResampleScalarVolume complete yes and yes yes and yes 57.1% 0 Bill Lorensen
?? PolyDataToLabelmap no yes and yes yes and yes 87.9% 0 Nicole Aucoin, Xiaodong Tao
?? GaussianBlurImageFilter complete yes and no yes and yes 55.9% 0 Julien Jomier, Stephen Aylward
?? ConfidenceConnected/SimpleRegionGrowing no yes and no yes and yes 87.5% 0 Jim Miller
?? ExecutionModelTour no yes and yes yes and yes 87.2% 0 Daniel Blezek, Bill Lorensen
?? ImageReadDicomWrite no yes and yes yes and yes 86.1% 0 Bill Lorensen
?? CurvatureAnisotropicDiffusion complete yes and yes yes and yes 64.3% 0 Bill Lorensen
?? GradientAnisotropicDiffusion complete yes and yes yes and yes 63.4% 0 Bill Lorensen
?? MedianImageFilter complete yes and yes yes and yes 51.1% 0 Bill Lorensen
?? DWIDicomLoad complete yes and yes yes and yes 0% (disabled) Kerstin Kessel
?? HistogramMatching complete yes and yes yes and yes 65.0% 0 Bill Lorensen
?? OtsuThresholdImageFilter no yes and yes yes and yes 100% 0 Bill Lorensen
?? OtsuThresholdSegmentation complete yes and no yes and yes 90.9% 0 Bill Lorensen
?? Subtract complete yes and yes yes and yes 71.7% 0 Bill Lorensen
?? Multiply no yes and no yes and yes 77.6% 0 Bill Lorensen
?? Add complete yes and yes yes and yes 84.9% 0 Bill Lorensen
?? Threshold no yes and no yes and yes 55.8% 0 Nicole Aucoin
?? Mask complete yes and no yes and yes 80.0% 0 Nicole Aucoin
?? Cast complete yes and no yes and yes 14.6% 0 Nicole Aucoin
?? VotingBinaryHoleFillingImageFilter complete yes and yes yes and yes 100% 0 Bill Lorensen
?? ModelMaker complete yes and yes yes and yes 57.4% 1 Nicole Aucoin
?? MultipleModelsExample no yes and no yes and yes 1.9% 50 Nicole Aucoin
?? GrayscaleModelMaker no yes and no yes and yes 82.1% 1 Bill Lorensen
?? MergeModels no yes and yes yes and yes 62.7% 0 Nicole Aucoin, Daniel Haehn
?? GrayscaleFillHoleImageFilter complete yes and yes yes and yes 57.1% 0 Bill Lorensen
?? GrayscaleGrindPeakImageFilter complete yes and yes yes and yes 64.5% 0 Bill Lorensen
?? LabelMapSmoothing no yes and no yes and yes 87.9% 0 Dirk Padfield, Josh Cates, Ross Whitaker
?? ImageLabelCombine complete yes and no yes and no 7.5% 50 Alex Yarmarkovich
?? ResampleVolume2 no yes and yes yes and yes 46.8% 0 Francois Budin
?? ZeroCrossingBasedEdgeDetectionImageFilter no yes and no yes and yes 62.5% 0 Elliot Uvero
?? FreesurferSurfaceSectionExtraction no yes and no yes and yes 60.0% 62 Katharina Quintus
  1. including link to website documentation
  2. including name of author and of supervisor
  3. in % for non-interactive part

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
Gold > 80% 0 yes yes
Silver > 70% < 10 yes yes
Bronze > 60% < 50 yes yes
Clay > 50% < 100 yes yes
Coal < 50% > 100 yes yes
Hazard 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.