🤖Freshcollected in 24m

Should AAAI Reviewers Penalize Missing Code?

PostLinkedIn
🤖Read original on Reddit r/MachineLearning

💡See why missing code is becoming a serious concern in ML peer review.

⚡ 30-Second TL;DR

What Changed

A reviewer reports seeing a low number of AAAI 2027 submissions with accompanying code.

Why It Matters

If adopted more broadly, code availability could become a stronger informal or formal signal in ML peer review. However, penalizing papers without code may disadvantage work involving proprietary data, safety restrictions, or genuinely difficult-to-release implementations.

What To Do Next

Add a reproducibility checklist to your next paper and prepare a sanitized code release with environment files, training commands, and evaluation scripts.

Who should care:Researchers & Academics

Key Points

  • A reviewer reports seeing a low number of AAAI 2027 submissions with accompanying code.
  • The post suggests code availability could be considered when assigning initial review scores.
  • The author argues that publishing code after peer review reduces concerns about idea theft.
  • The discussion links missing implementations to reproducibility risks and potentially fabricated empirical results.

🧠 Deep Insight

AI-generated analysis for this event.

🔑 Enhanced Key Takeaways

  • The AAAI Association for the Advancement of Artificial Intelligence has historically maintained a 'Reproducibility Checklist' for submissions, which asks authors to explicitly state if code is available, though it has not historically mandated code as a strict acceptance criterion.
  • Major AI conferences like NeurIPS and ICML have moved toward mandatory 'Reproducibility Reports' and artifact evaluation tracks, which AAAI has been slower to adopt as a standardized, incentivized requirement compared to its peers.
  • The rise of 'LLM-assisted research' has increased concerns regarding 'paper mills' and the generation of synthetic, non-reproducible empirical data, leading to calls for automated verification of code-to-results pipelines.
  • Academic research indicates that papers with open-source code receive significantly higher citation counts, creating a natural incentive that often conflicts with the 'publish or perish' pressure to submit incomplete work early.
  • Reviewer fatigue and the massive scale of AAAI submissions (often exceeding 10,000 papers) make manual code verification logistically difficult for the volunteer peer-review pool.

🔮 Future ImplicationsAI analysis grounded in cited sources

AAAI will implement a mandatory 'Code Availability' flag in the submission portal by 2028.
Increasing pressure from the community regarding reproducibility and the threat of AI-generated fake results necessitates stricter submission standards.
Automated artifact evaluation tools will become a standard part of the peer-review process.
Manual verification is unscalable, forcing conferences to adopt containerized or automated testing environments to validate empirical claims.

Timeline

2019-05
AAAI introduces a reproducibility checklist for all conference submissions.
2021-02
AAAI 2021 emphasizes reproducibility by encouraging authors to provide code, though it remains optional.
2023-06
NeurIPS formalizes the 'Reproducibility Program' with mandatory artifact evaluation for selected papers.
2025-02
AAAI 2025 faces criticism regarding the high volume of submissions and the difficulty of verifying empirical claims.
📰

Weekly AI Recap

Read this week's curated digest of top AI events →

👉Related Updates

AI-curated news aggregator. All content rights belong to original publishers.
Original source: Reddit r/MachineLearning