Difference between revisions of "Documentation/Nightly/Developers/Tutorials/UploadTestData"
m (→Introduction) |
m |
||
| Line 29: | Line 29: | ||
* <code>Input</code>: Used to store testing input data. | * <code>Input</code>: Used to store testing input data. | ||
* <code>Baseline</code>: Used to store the baseline images for regression tests. | * <code>Baseline</code>: Used to store the baseline images for regression tests. | ||
| − | |||
| − | |||
| − | |||
= Upload test data = | = Upload test data = | ||
| Line 39: | Line 36: | ||
# Create a <code>Nightly</code> sub-folder. | # Create a <code>Nightly</code> sub-folder. | ||
# Upload data in folders <code>Nightly/Testing/Baseline</code> and <code>Nightly/Testing/Input</code> | # Upload data in folders <code>Nightly/Testing/Baseline</code> and <code>Nightly/Testing/Input</code> | ||
| + | |||
| + | = FAQ = | ||
| + | |||
| + | == What happen when Slicer is released ? == | ||
| + | |||
| + | Each time a release of Slicer is done, for both the <code>Application</code> and <code>Modules/<NameOfYourModule></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 ? == | ||
| + | |||
| + | {{note}} For now, let's keep all of them at the same level. I will have to coordinate with the development of the release script allowing to version the Data tree. See [1] | ||
| + | |||
| + | I created a feature request to keep track of it. See http://www.na-mic.org/Bug/view.php?id=2722 | ||
| + | |||
| + | [1] http://slicer-devel.65872.n3.nabble.com/Versioning-of-test-data-tree-on-slicer-kitware-com-What-does-this-mean-for-you-tt4026608.html | ||
Revision as of 14:43, 7 November 2012
Home < Documentation < Nightly < Developers < Tutorials < UploadTestDataContents
Introduction
Slicer has adopted MIDAS to store testing and algorithm validation dataset. For this purpose, we have created a dedicated NA-MIC MIDAS community
In the NA-MIC community Slicer/Data folder, you will find:
To organize the test data based on Slicer major release, you will find sub folders like:
Nightly4.24.3
Test data are expected to be stored in folders like:
Data/Application/Nightly/Testing/BaselineData/Application/Nightly/Testing/InputData/Modules/<NameOfYourModule>/Nightly/Testing/BaselineData/Modules/<NameOfYourModule>/Nightly/Testing/Input
Data/Application/X.Y/Testing/BaselineData/Application/X.Y/Testing/InputData/Modules/<NameOfYourModule>/X.Y/Testing/BaselineData/Modules/<NameOfYourModule>/X.Y/Testing/Input
where
<NameOfYourModule>: name of the folder in the source repository, it should also match the module pages created on the slicer wiki.Input: Used to store testing input data.Baseline: Used to store the baseline images for regression tests.
Upload test data
- Send an email on the developer list asking to be added to the
DataManagergroup on NA-MIC community. That will grant you read/write permissions to theDatafolder and sub-folders. - Create a sub folder for your Module.
- Create a
Nightlysub-folder. - Upload data in folders
Nightly/Testing/BaselineandNightly/Testing/Input
FAQ
What happen when Slicer is released ?
Each time a release of Slicer is done, for both the Application and Modules/<NameOfYourModule> folders, the current Nightly is copied into an X.Y 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. I will have to coordinate with the development of the release script allowing to version the Data tree. See [1]
I created a feature request to keep track of it. See http://www.na-mic.org/Bug/view.php?id=2722
