Rules & FAQ.

Industry, academia, students, and independents are all eligible, and cross-institution teams are encouraged. Organisers and their direct team members may submit, but their entries appear as Organizers on the leaderboard and are ineligible for cash prizes.

Each participant submits through their own Codabench account and has an individual submission quota for each track. For team entries, submissions are attributed to the participant's Codabench organization. Solo participants count as one-person teams. See how the best team score is selected automatically.

Both phases have separate quotas per participant and per track:

• Warm-up: 10 submissions per participant per day per track, with 100 submissions total per participant per track.
• Sealed: 1 submission per participant per day per track, with 5 submissions total per participant per track.

The five-submission sealed cap limits repeated tuning against hidden test data. Sealed evaluation measures generalization, not blind trial-and-error optimization on the test set.

See what counts toward your quota and which score is retained. Warm-up closes Sunday, Nov 1 at 23:59 CET (UTC+01:00). Sealed runs Thursday, Nov 5 at 00:01 through Saturday, Nov 21 at 23:59 CET (UTC+01:00).

Training data is suggested to stay within the track. Public datasets may be used when their original terms permit competition use. This includes NSRR datasets under an active licence, as clarified in the Track 03 Scientific FAQ. The sealed test split and non-permitted closed clinical datasets are not allowed. Original dataset and model licences remain in force. Declare every external corpus, and a compute estimate, in the method description that ships with your final submission. The audit cross-checks it against a re-run of your submitted training pipeline and declared configuration.

Train on whatever you have. The evaluation container must complete its test pass within 80 minutes on one A100 GPU. Evaluations that exceed this execution limit time out.

Codabench also limits each profile to 15 GB of submission storage shared across all tracks and uploads. This makes 15 GB the theoretical maximum for one submission, but your practical limit is the space remaining in your profile. If needed, delete unused archived submissions under Profile → Resources. A submission displayed on a leaderboard cannot be deleted.

Any attempt to cheat, including but not limited to using non-permitted clinical data, accessing the sealed test split, or modifying the scoring harness, results in immediate disqualification from the competition. This decision is made by the organising committee and is final.

After the sealed final closes, the top-3 of every track go through a reproducibility audit: we re-run your training pipeline from the committed config and re-score the resulting weights against the sealed split. Scores within ±2σ of your submitted number stay on the prize roster. Scores outside the tolerance drop off the prize roster but remain on the public board for context. The organising committee chairs the audit.

Participants retain the intellectual property rights they hold in their submitted code, models, and related materials. Finalists must provide the materials required for the audit and grant the auditing committee permission to access and run them solely to verify the submission and detect cheating. This limited audit permission does not allow the organisers to publish, share, modify, commercialise, or otherwise use those materials outside the audit. Open-source release after the competition is encouraged, but remains entirely the participant's choice.

Top-ranked teams that pass the audit and submit a method description, training and inference code, and pre-training disclosures are announced during the NeurIPS workshop. Winner notifications are targeted for Dec 1, ahead of the Dec 11-12 workshop. This opportunity is offered to teams with complete, reproducible artifacts.