Submission Guidelines
Make sure to use the same team name as in the registration form when submitting your predictions.
Predictions must be in the ascending order of filenames (from 0000.wav to 0159.wav).
The best segment-level result (selected from the five predictions) will determine the final segment-level score.
Majority voting will be applied to this result to derive the subject-level score.
Submission Format
Participants must submit their predictions as a .txt file adhering to the following format:
The file should include five prediction lines, one prediction per line.
Each prediction line consists of 160 binary digits (0 or 1), separated by commas:
0 represents Wild Type.
1 represents ASD.
Example of a prediction line: 0,1,0,1,0,1,...,1,0
Ranking Rules
Submission and Selection
Each participating team is allowed to submit multiple entries before the deadline, with each submission containing up to five predictions.
The highest segment-level result among the five predictions in a submission will be considered the best result for that submission.
Leaderboard Updates
If a new submission achieves a better segment-level result than the team’s previous best, it will replace the previous result on the leaderboard.
This update occurs even if the previous best result had a higher subject-level performance.
Final Rankings
After the evaluation phase ends, two separate rankings will be established:
a) Segment-Level Ranking: Based on the best segment-level results of all teams.
b) Subject-Level Ranking: Based on the best subject-level results of all teams.
The Overall Ranking is determined by averaging each team’s segment-level and subject-level rankings.
Determining the Winner
The team with the lowest overall ranking wins the challenge.
In case of a tie:
a) The team with the lower segment-level ranking wins the challenge.
b) If still tied, the team that submitted their best segment-level result earlier wins the challenge.
Important Notes
Ensure that your .txt file strictly follows the formatting guidelines to avoid evaluation failure.
Every team is allowed to submit the prediction file ten times per day.
For queries or issues, contact us at info@maduv.org.
(c) 2025 - Educational Physiology Laboratory,
Graduate School of Education, The University of Tokyo