Copyright © German Cancer Research Center (DKFZ), Division of Medical Image Computing (MIC). Please make sure that your usage of this code is in compliance with the code license:
This tasks focuses on how segmentation methods can learn from multi-institutional datasets how to be robust to distribution shifts at test-time, effectively solving a domain generalization problem. In this repository, you can find information on the container submission and ranking for task 2 of the FeTS challenge 2021. It is structured as follows:
singularity_example
: Guide how to build the container submission with examplesscripts
: Scripts for running containers, both in the participant's environment and in the federated testing environmentranking
: Code for performing the final ranking
In the FeTS challenge task 2, participants can submit their solution in the form of a singularity container. Note that we do not impose restrictions on the participants how they train their model nor how they perform inference, as long as the resulting algorithm can be built into a singularity container with the simple interface described in singularity_example
. Hence, after training a model, the following steps are required to submit it:
- Write a container definition file and an inference script.
- Build a singularity container for inference using above files and the final model weights.
- Upload the container to the submission platform.
Details for steps 1 and 2 are given in the guide in the singularity_example. Instructions for step 3 will follow soon.
Singularity has to be installed to create a container submission (instructions).
Python 3.6 or higher is required to run the scripts in scripts
.
The examples in this repo assume the following data folder structure, which will also be present at test-time:
data/ # this should be passed for inference
│
└───Patient_001 # case identifier
│ │ Patient_001_brain_t1.nii.gz
│ │ Patient_001_brain_t1ce.nii.gz
│ │ Patient_001_brain_t2.nii.gz
│ │ Patient_001_brain_flair.nii.gz
│
└───Pat_JohnDoe # other case identifier
│ │ ...
Furthermore, predictions for test cases should be placed in an output directory and named like this: <case-identifier>_seg.nii.gz