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
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
?? Models complete yes and yes yes and yes 12% unknown Alex Yarmarkovic
?? Measurements complete yes and yes no and yes 46% unknown Nicole Aucoin
?? Fiducials complete yes and yes no 7% unknown Nicole
?? Data complete yes and yes yes and yes 0% unknown Steve Pieper
?? Slices complete no no 0% unknown Jim Miller
?? Colors complete yes and no yes and no 0% unknown Nicole Aucoin
?? Interactive Editor complete no and yes yes and no 0% unknown Steve Pieper
?? ROI Module complete no and yes no and yes 0% unknown Alex Yarmarkovic
?? Volume Rendering complete yes and yes no and yes 0% unknown Yanling Liu
  1. including link to website documentation
  2. including name of author and of supervisor
  3. in % for non-interactive part

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 69.8% 0 Raul San Jose Estepar
?? DiffusionTensorEstimation complete 79.7% 9 Raul San Jose Estepar
?? DiffusionTensorMathematics no 56.2% 5 Raul San Jose Estepar
?? OrientImage complete 85.7% 0 Bill Lorensen
?? LinearRegistration complete 66.7% 4 Daniel Blezek
?? RigidRegistration no 1.0% unknown Daniel Blezek
?? AffineRegistration complete 1.4% unknown Casey Goodlett
?? BSplineDeformableRegistration complete 82.3% unknown Bill Lorensen
?? TestGridTransformRegistration no no yes and yes 90.7% unknown Yinglin Lee
?? CheckerBoard complete 67.4% unknown Bill Lorensen
?? ResampleVolume complete 57.1% unknown Bill Lorensen
?? PolyDataToLabelmap no 87.9% unknown Nicole Aucoin, Xiaodong Tao
?? GaussianBlurImageFilter complete 55.9% unknown Julien Jomier, Stephen Aylward
?? ConfidenceConnected no 87.5% unknown Jim Miller
?? ExecutionModelTour no 87.2% unknown Daniel Blezek, Bill Lorensen
?? ImageReadDicomWrite no 86.1% unknown Bill Lorensen
?? CurvatureAnisotropicDiffusion complete 64.3% unknown Bill Lorensen
?? GradientAnisotropicDiffusion complete 63.4% unknown Bill Lorensen
?? MedianImageFilter complete 51.1% unknown Bill Lorensen
?? DWIDicomLoad complete 0% unknown Kerstin Kessel
?? HistogramMatching complete 65.0% unknown Bill Lorensen
?? OtsuThresholdImageFilter no 100% unknown Bill Lorensen
?? OtsuThresholdSegmentation complete 90.9% unknown Bill Lorensen
?? Subtract complete 71.7% unknown Bill Lorensen
?? Multiply no 77.6% unknown Bill Lorensen
?? Add complete 84.9% unknown Bill Lorensen
?? Threshold no 55.8% unknown Nicole Aucoin
?? Mask complete 80.0% unknown Nicole Aucoin
?? Cast complete 14.6% unknown Nicole Aucoin
?? VotingBinaryHoleFillingImageFilter complete 100% unknown Bill Lorensen
?? ModelMaker complete 57.4% unknown Nicole Aucoin
?? MultipleModelsExample no 1.9% unknown Nicole Aucoin
?? GrayscaleModelMaker no 82.1% unknown Bill Lorensen
?? MergeModels no 62.7% unknown Nicole Aucoin, Daniel Haehn
?? GrayscaleFillHoleImageFilter complete 57.1% unknown Bill Lorensen
?? GrayscaleGrindPeakImageFilter complete 64.5% unknown Bill Lorensen
?? LabelMapSmoothing no 87.9% unknown Dirk Padfield, Josh Cates, Ross Whitaker
?? ImageLabelCombine complete 7.5% unknown Alex Yarmarkovich
?? ResampleVolume2 no 46.8% unknown Francois Budin
?? ZeroCrossingBasedEdgeDetectionImageFilter no 62.5% unknown Elliot Uvero
?? FreesurferSurfaceSectionExtraction no 60.0% unknown 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.