View source for Documentation/4.10/Developers/Tutorials/UploadTestData

<noinclude>{{documentation/versioncheck}}</noinclude>
= Introduction =

Slicer has adopted [http://slicer.kitware.com/midas3 MIDAS] to store testing and algorithm validation dataset. For this purpose, we have created a dedicated [http://slicer.kitware.com/midas3/community/23 NA-MIC MIDAS community]

In the NA-MIC community [http://slicer.kitware.com/midas3/folder/301 <code>Slicer/Data</code>] folder, you will find:
* [http://slicer.kitware.com/midas3/folder/302 Application]
* [http://slicer.kitware.com/midas3/folder/310 Modules]

To organize the test data based on Slicer major release, you will find sub folders like:
* <code>Nightly</code>
* <code>4.2</code>
* <code>4.3</code>

Test data are expected to be stored in folders like:

* <code>Data/Application/Nightly/Testing/Baseline</code>
* <code>Data/Application/Nightly/Testing/Input</code>
* <code>Data/Modules/&lt;NameOfYourModule&gt;/Nightly/Testing/Baseline</code>
* <code>Data/Modules/&lt;NameOfYourModule&gt;/Nightly/Testing/Input</code>

* <code>Data/Application/X.Y/Testing/Baseline</code>
* <code>Data/Application/X.Y/Testing/Input</code>
* <code>Data/Modules/&lt;NameOfYourModule&gt;/X.Y/Testing/Baseline</code>
* <code>Data/Modules/&lt;NameOfYourModule&gt;/X.Y/Testing/Input</code>

where 

* <code>&lt;NameOfYourModule&gt;</code>: name of the folder in the source repository, it should also match the module pages created on the slicer wiki.
* <code>Input</code>: Used to store testing input data.
* <code>Baseline</code>: Used to store the baseline images for regression tests.

= Upload test data =

<ol start="1" style="list-style-type: decimal;">

{{:Documentation/{{documentation/version}}/Developers/Tutorials/CreateMidasAccount/steps}}

<li>Send an email on the developer list asking to be added to the <code>DataManager</code> group on NA-MIC community. That will grant you read/write permissions to the <code>Data</code> folder and sub-folders.</li>
<li>Create a sub folder for your Module.</li>
<li>Create a <code>Nightly</code> sub-folder.</li>
<li>Upload data in folders <code>Nightly/Testing/Baseline</code> and <code>Nightly/Testing/Input</code></li>

</ol>

<gallery widths=330px heights=220px perrow=4>
File:Midas-test-data-upload-1.png|Browse, select the destination folder (1) and click on View (2)
File:Midas-test-data-upload-2.png|Select an item (3) and click "Upload here" (4)
File:Midas-test-data-upload-3.png|Select one or more files (5) and click "Upload" button (6)
</gallery>

= FAQ =

== What happen when Slicer is released ? ==

Each time a  release of Slicer is done, for both the <code>Application</code> and <code>Modules/&lt;NameOfYourModule&gt;</code> folders, the current <code>Nightly</code> is copied into an <code>X.Y</code> folders where X and Y corresponds to the major and minor release number of Slicer.

== Should data for extension be organized differently ? ==

For now, let's keep all of them at the same level. We will have to coordinate with the development of the release script allowing to version the Data tree. See [http://slicer-devel.65872.n3.nabble.com/Versioning-of-test-data-tree-on-slicer-kitware-com-What-does-this-mean-for-you-tt4026608.html here]

It means if you develop an extension named <code>Salad</code> bundling two modules respectively named <code>Tomato</code> and <code> Mozzarella</code>, the following folders would have to be created:

* <code>Data/Modules/Tomato/Nightly/Testing/Baseline</code>
* <code>Data/Modules/Tomato/Nightly/Testing/Input</code>
* <code>Data/Modules/Mozzarella/Nightly/Testing/Baseline</code>
* <code>Data/Modules/Mozzarella/Nightly/Testing/Input</code>

Consider also monitoring issue [http://www.na-mic.org/Bug/view.php?id=2722 #2722]: Think about organization of Data/Modules directory on midas to accomodate extension relationship