Difference between revisions of "2014 Winter Project Week:CIP Infrastructure Testing and SuperBuild"
From NAMIC Wiki
Line 12: | Line 12: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
− | * | + | * We have developed a library of tools (Chest Imaging Platform) for the processing and the analysis of chest images. The main objective is to make the tools available to the public by providing a common infrastructure that in turn can be incorporated into Slicer by means of the Slicer CIP library. The goals for this week are twofold: 1) set up a software testing framework to improve code quality control, and 2) create a simplified mechanism for downloading and building the CIP and the packages on which it depends. |
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
Line 20: | Line 20: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
− | * | + | * Use CTest to orchestrate CIP testing |
+ | * Set up infrastructure / directory structure within CIP to execute one or two initial tests | ||
+ | * Explore the use of CDash to display testing results | ||
+ | * The CIP depends on several software packages: (ITK, VTK, FLTK, Teem, and boost. We will mimic the Super-Build approach taken with Slicer4 to automatically retrieve and build these packages as part of the overall CIP build process | ||
</div> | </div> | ||
</div> | </div> |
Revision as of 15:40, 5 January 2014
Home < 2014 Winter Project Week:CIP Infrastructure Testing and SuperBuildKey Investigators
James Ross, Raul San Jose
Project Description
Objective
- We have developed a library of tools (Chest Imaging Platform) for the processing and the analysis of chest images. The main objective is to make the tools available to the public by providing a common infrastructure that in turn can be incorporated into Slicer by means of the Slicer CIP library. The goals for this week are twofold: 1) set up a software testing framework to improve code quality control, and 2) create a simplified mechanism for downloading and building the CIP and the packages on which it depends.
Approach, Plan
Progress
- Use CTest to orchestrate CIP testing
- Set up infrastructure / directory structure within CIP to execute one or two initial tests
- Explore the use of CDash to display testing results
- The CIP depends on several software packages: (ITK, VTK, FLTK, Teem, and boost. We will mimic the Super-Build approach taken with Slicer4 to automatically retrieve and build these packages as part of the overall CIP build process