|
|
(15 intermediate revisions by 2 users not shown) |
Line 1: |
Line 1: |
| = Introduction =
| |
| Tubetk has adopted [http://midas3.kitware.com/midas/ MIDAS] to store testing and algorithm validation dataset.
| |
|
| |
|
| For this purpose, we have created a dedicated [http://midas3.kitware.com/midas/community/7 tubetk MIDAS community]
| |
|
| |
| In the tubetk community, we have two main types of folders
| |
|
| |
| #Input data folder: Where all input data for testing will be stored
| |
| #Baseline dataset folder: These are individual folders that will be used to store the baseline images for tests in each "module"/CLI application in slicer.
| |
|
| |
| = How to add a new tubetk test =
| |
|
| |
| #If the input data is not already in Midas,
| |
| ##Upload the data to the "Data" folder
| |
| ##
| |
| 2) Modify cmake list files in the Testing directory to "add" unit
| |
| tests to use the data from MIDAS. ( The MIDAS tests will run in
| |
| parallel with the current unit tests for about a week or so. )
| |
| 3) After a week, if everything looks solid ( MIDAS server doesn't
| |
| crash nor we don't run into a lot of authentication issues, we can
| |
| then remove all the testing data from tubetk code base and continue
| |
| using the MIDAS tests.
| |
|
| |
| Any thoughts on this? we can chat about it during our 2pm stand-up
| |
| meeting as well.
| |
|
| |
| = MIDAS macro =
| |
| The following are the key MIDAS cmake macro that will be used
| |
| #MIDAS_ADD_TEST
| |
| #[http://www.kitware.com/midaswiki/index.php/MIDAS%2BCTest#MIDAS_FETCH_ONLY_option MIDAS_FETCH ONLY]
| |
| #[http://www.kitware.com/midaswiki/index.php/MIDAS%2BCTest#MIDAS_DIRECTORY_option MIDAS_DIRECTORY]
| |