Rules & FAQ.
Check the eight competition rules before submitting. For practical help, see the questions below or ask on Discord.
Eight binding rules.
Read these before submitting. They govern every track and take precedence over informal guidance elsewhere on the site.
Anyone can enter. Organisers cannot win prizes.
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.
One team may enter all four tracks.
Each participant submits through their own Codabench account and has an individual submission quota. For team entries, those submissions are attributed to the participant's Codabench organization and ranked as team submissions.
Five submissions a day in warm-up, one in the sealed final.
Warm-up (Sep 21 to Oct 25, 2026): 5 submissions per participant per day. Sealed final (Oct 28 to Nov 21, 2026, AoE): 1 per participant per day, so the prize roster reflects deliberate iteration rather than lottery search. The final NeurIPS ranking uses sealed submissions only.
Pre-train on any public dataset. Declare all of it.
Training data is suggested to stay within the track, but pre-training on any publicly available, redistributable dataset is allowed. The sealed test split is never allowed, and closed clinical datasets are not allowed. Original dataset and model licenses 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.
Training compute is uncapped. Inference is 60 minutes on one GPU. Submission size is capped.
Train on whatever you have. The scoring container must complete a full test pass in under 60 minutes on one A100 GPU, so that audit cost stays bounded and per-team runtime stays comparable. AWS, the compute partner, provides complimentary instance hours to finalists.
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 means immediate disqualification.
Any attempt to cheat, including but not limited to using closed 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.
The top three per track must replay within ±2σ.
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.
Reproducible top teams are announced during the NeurIPS workshop.
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. This opportunity is offered to teams with complete, reproducible artifacts.
Questions people ask.
Answers, not rules: nothing here overrides the eight rules above.
RegistrationWhere do I register and submit?
Registration stays open through October 24, including during warm-up. Use the track registration page to choose the Codabench competitions you want to enter. Submissions open September 21, 2026.
See the NeuralBench guides for preparation and Discord for help.
DatasetsWhen is the Track 3 Muse Sleep-Onset dataset available, and how do I access it?
The new public Muse Sleep-Onset training data will be released soon. Until the release announcement, use the public datasets listed on the Tracks & Data page. The Track 3 start kit and Codabench warm-up currently use Sleep-EDF as a proxy.
The private 2026 Muse evaluation cohort is reserved for the sealed phase and will not be released. Release and access instructions for the public training data will be published on the website and Discord.
Low participationWhat happens if a track has too few participants?
Low-participation tracks fold into the closest active analysis group for the post-competition report, but prizes are still awarded on that track's own leaderboard. Each track is scored independently, so low participation on one track never shrinks the field on another.
DelaysWhat if there's a delay?
Technical, data, or infrastructure delays shift all downstream deadlines by the same amount on the website and Discord. The reproducibility audit gate is the only milestone that can extend independently if a top submission needs more re-run time.
Data releaseWill the competition data be released?
After the challenge, new data is made publicly available in full or in part where consent, licensing, and provider policy allow. The hidden evaluation labels remain confidential indefinitely so the benchmark stays usable for future research.
Reach the organising team.
Contact the organising team on Discord.