For the latest Slicer developers documentation, visit the Nightly page.
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:
Test data are expected to be stored in folders like:
<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
Create an account on the extension server: http://slicer.kitware.com by clicking on the
Registerlink in the top right corner
Go to NA-MIC community and click on
- 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 the
Datafolder and sub-folders.
- Create a sub folder for your Module.
- Create a
- Upload data in folders
This image shows the top portion of http://slicer.kitware.com after it has been expanded by clicking the
What happen when Slicer is released ?
Each time a release of Slicer is done, for both the
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. We will have to coordinate with the development of the release script allowing to version the Data tree. See here
It means if you develop an extension named
Salad bundling two modules respectively named
Mozzarella, the following folders would have to be created:
Consider also monitoring issue #2722: Think about organization of Data/Modules directory on midas to accomodate extension relationship