ITK/Release 4/Testing Data: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
| Line 24: | Line 24: | ||
contains a CMake function that will download specific files and put them in a given directory. | contains a CMake function that will download specific files and put them in a given directory. | ||
==== How to find Checksum files ==== | |||
* Go to the MIDAS page of the image of your interest | |||
* Check the checkbox "Advanced View" | |||
** 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 | |||
Revision as of 18: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.
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.
How to find Checksum files
- Go to the MIDAS page of the image of your interest
- Check the checkbox "Advanced View"
- 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
