Difference between revisions of "2014 Winter Project Week:CIP Infrastructure Testing and SuperBuild"
From NAMIC Wiki
(Created page with '__NOTOC__ <gallery> Image:PW-SLC2014.png|Projects List </gallery> ==Key Investigators== ==Project Description== <div style="margin: 20px;…') |
|||
(5 intermediate revisions by the same user not shown) | |||
Line 5: | Line 5: | ||
==Key Investigators== | ==Key Investigators== | ||
+ | James Ross, Raul San Jose | ||
==Project Description== | ==Project Description== | ||
Line 11: | 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%;"> | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</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 style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
− | * | + | * Successfully created testing infrastructure; ran an submitted an initial test to newly created CDash dashboard |
+ | * We were able to use superbuild to download and build ITK, VTK, teem, and boost. We also got components of the CIP to build, although there are a few remaining issues to iron out. | ||
</div> | </div> | ||
</div> | </div> | ||
+ | [[File:CIP_CDash.jpg]] |
Latest revision as of 05:20, 10 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
- 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
Progress
- Successfully created testing infrastructure; ran an submitted an initial test to newly created CDash dashboard
- We were able to use superbuild to download and build ITK, VTK, teem, and boost. We also got components of the CIP to build, although there are a few remaining issues to iron out.