ITK/Release 4/Testing Data

The Challenge

• Data used for testing can be large.
  • ITK has three types of Data (Input, Baselines and "Large Data"). At this point, neither Baselines or Input are very large (subjective remark). "Large Data" would benefit from the MIDAS solution.
• Data should not be stored along with the source code
  • Lorensen comment: This is an opinion, not a fact.
• 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
  • This was possible with ITK 3.x.
• There must be a way to pull down the testing data corpus as a whole. You must be able to run CTest without an Internet connection.

MIDAS Proposal

• Store ITK Testing Data in MIDAS
  • Lorensen Proposal: Keep Input and Baseline data in the ITK repository. Store Large data in MIDAS.
• Download it at run time during ITK testing.

Data on MIDAS

At:

• http://midas.kitware.com/community/view/7

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
• 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