ITK/Release 4/Testing Data: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
Line 5: | Line 5: | ||
* Data files change along with the evolution of the code | * Data files change along with the evolution of the code | ||
** So we have to track their specific versions. | ** So we have to track their specific versions. | ||
* Adding new files should be quick and easy, ideally with a single command line | |||
* There should be a way to pull down the testing data corpus as a whole. You should be able to run CTest without an Internet connection. | |||
= MIDAS Proposal = | = MIDAS Proposal = |
Revision as of 19:28, 4 November 2010
The Challenge
- Data used for testing can be large.
- Data should not be stored along with the source code
- Data files change along with the evolution of the code
- So we have to track their specific versions.
- Adding new files should be quick and easy, ideally with a single command line
- There should be a way to pull down the testing data corpus as a whole. You should be able to run CTest without an Internet connection.
MIDAS Proposal
- Store ITK Testing Data in MIDAS
- Download it at run time during ITK testing.
Data on MIDAS
At:
MIDAS - CMake
The file
MIDAS.cmake
contains a CMake function that will download specific files and put them in a given directory.
This file will be in the directory
ITK/CMake
How to find Checksum files
- Go to the MIDAS page of the image of your interest
- From: http://midas.kitware.com/community/view/7
- For example, the image "cthead1.png" can be found at: http://midas.kitware.com/item/view/258
- From: http://midas.kitware.com/community/view/7
- Click on the check-box "Advanced View" at the top of the page.
- The checksums of individual files will be displayed under the filenames
- A "Download MD5 Key File" link will be shown in front of the checksum number
- Click on the "Download MD5 Key File" and save the file in the directory
- ITK/Testing/MIDAS_Keys