Why Write-Ups?
| Purpose |
Description |
| Knowledge Base |
Accessible overview of methods and research from past competitions |
| Discussion |
Research direction and decision justification for supervisors and team |
| Planning |
Outline of action courses, reasoning, and consequences before coding |
Document Types
OV - Overview
Purpose: Set out goals, tools, and restrictions so anyone can understand the framework without reading 3 pages of competition rules.
| Contents |
|
| Competition objective |
Data available |
| Constraints and rules |
Timeline |
EX - Execution
Purpose: Overview of thought process during the whole competition.
| Section |
Description |
| Infrastructure |
Scripts for comparison, backtest, and key development/testing tools |
| Ideas |
Models, data treatment, agent behavior hypotheses, feature engineering |
| Implementation |
Hypothesis testing and course of action |
Implementation Process:
| Step |
Description |
| State Hypothesis |
e.g., “Data has well-defined regimes” or “Player exhibits behavior patterns” |
| Outline Testing |
Ways to test, implications if proven/disproved, course of action after |
| Why This Process |
Prevents untestable hypotheses, avoids wasted effort, maintains focus |
Takeaways
Purpose: Capture lessons learned after competition ends.
| Category |
Description |
| Framework |
Issues and improvements to project framework |
| Methods |
New methods learned during competition |
| Mistakes |
What went wrong and why |
| Successes |
What worked well |
| Future |
What to do differently next time |