Read the documentation on the overall data format first!
The data format for inference must match the one used for the raw data (specifically, the images must be in exactly the same format as in the imagesTr folder). As before, the filenames must start with a unique identifier, followed by a 4-digit modality identifier. Here is an example for two different datasets:
Task005_Prostate:
This task has 2 modalities, so the files in the input folder must look like this:
input_folder
├── prostate_03_0000.nii.gz
├── prostate_03_0001.nii.gz
├── prostate_05_0000.nii.gz
├── prostate_05_0001.nii.gz
├── prostate_08_0000.nii.gz
├── prostate_08_0001.nii.gz
├── ...
_0000 has to be the T2 image and _0001 has to be the ADC image (as specified by 'channel_names' in the dataset.json), exactly the same as was used for training.
Task002_Heart:
imagesTs
├── la_001_0000.nii.gz
├── la_002_0000.nii.gz
├── la_006_0000.nii.gz
├── ...
Task002 only has one modality, so each case only has one _0000.nii.gz file.
The segmentations in the output folder will be named {CASE_IDENTIFIER}.nii.gz (omitting the modality identifier).
Remember that the file format used for inference (.nii.gz in this example) must be the same as was used for training (and as was specified in 'file_ending' in the dataset.json)!
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。