I have three remaining questions before pushing my final image: **1. Image name and tag convention.** Besides the mandatory docker.synapse.org// prefix, is there any required convention for the image name or tag? For example, I plan to use: ``` docker.synapse.org//brats-goat-2026:v1 ``` Is a versioned tag like :v1 fine, or should it be something specific (e.g., latest)? **2. Expected output filename for GoAT.** The example in the instructions uses the METs naming format, and the note says to use the correct naming format for the GoAT task. Could you confirm that, for BraTS-GoAT, each prediction must be named exactly after its input case folder? That is: /input/BraTS-GoAT-02489/ -> /output/BraTS-GoAT-02489.nii.gz (I used this convention during the validation phase and the submissions were scored successfully, but I would like to confirm it for the hidden test set.) **3. Hidden test input structure.** Will the hidden test set follow the same structure as the GoAT validation data, i.e.: ``` /input/ ├── BraTS-GoAT-02489/ │ ├── BraTS-GoAT-02489-t1c.nii.gz │ ├── BraTS-GoAT-02489-t1n.nii.gz │ ├── BraTS-GoAT-02489-t2f.nii.gz │ └── BraTS-GoAT-02489-t2w.nii.gz ├── BraTS-GoAT-02490/ │ └── ... ``` Is there any difference in folder or file naming that my container should be prepared to handle? Thank you very much for your help!

Created by Henrique Zan Henrique_Zan
Hi @Henrique_Zan , > Is a versioned tag like :v1 fine, or should it be something specific (e.g., latest)? For the best reproducibility, we strongly recommend using explicit version tags rather than relying on `latest` (since `latest` will update every time you rebuild without a tag). That said, we do not enforce strict naming or tagging conventions for your Docker images. > Could you confirm that, for BraTS-GoAT, each prediction must be named exactly after its input case folder? Correct. Just like in the validation phase, you should parse the input folder names to derive the subject IDs and generate your output filenames accordingly. **One important note:** because this is a generalizability challenge, your model should not hardcode for "BraTS-GoAT". Case folders could use "BraTS-GoAT", "BraTS-GLI", or some other variations, so we recommend that your logic handles varying folder prefixes dynamically. > Will the hidden test set follow the same structure as the GoAT validation data Yes, the structure will be similar to the validation dataset, where each case folder in `/input` contains 4 files. Hope that helps!

Docker (BraTS-GoAT) final submission questions page is loading…