In most ilastik workflows, such as the Pixel Classification Workflow, the user interactively trains a classifier on a representative set of images. The trained classifier can be applied to more data by using batch processing.
The following tutorial demonstrates the batch prediction for the pixel classification workflow. The procedure is the same in the other workflows (with the exception of Carving, where there is no batch processing available).
Before getting to the batch processing part, you first have to set up the file export settings.
Batch processing uses the same settings as in the Prediction Export step.
Here, it is crucial to use the “magic” placeholders, denoted by curly braces (e.g. {nickname}
): this ensures a unique export filename for each file.
Also make sure to configure the export source, file format, and other properties.
You can add files either by drag-and-drop from your file browser, or use the Select Raw Data Files… button.
When clicking on the Select Raw Data Files… button, you can choose between adding single or multiple files from the File selection dialog.
The next step is the actual batch processing itself.
After clicking on the Process all files button, ilastik begins batch processing all images, and writes the resulting classification result to the specified output files.
With default export settings, the output files are stored as hdf5 files in the same directory where the input file is located.
Their file names will be the same as the original files, plus one or two words indicating the export source (e.g. “Probabilities”) and the file extension .h5
.
The exported .h5
files contain the resulting prediction as a multidimensional dataset inside the file.
Further details on this versatile file format (that is easily accessible from Matlab and Python) can be found in the hdf5 documentation.
Stacks with one image file per slice are currently not supported in batch. If your image is spread across multiple files, you can use the headless mode, or the Fiji plugin to process those. Alternatively you could also convert your stack to a single file and use the batch processing graphical user interface in ilastik.
.hdf5
/.z5
-file?It is currently not possible to specify the internal dataset with the graphical user interface, use the headless mode, or Fiji plugin to process that data.
In batch processing, ilastik processes only one file at a time. If you have the resources in your machine (number of cores » 8), you could run multiple instances of ilastik in headless mode and have each instance process a subset of the images.