1 min readfrom Machine Learning

AAAI 2027 Review: No code submission? [D]

Our take

AAAI 2027 paper reviews have revealed a concerning trend: a surprisingly low number of submissions include accompanying code. This deviates from AAAI's explicit emphasis on reproducibility and raises questions about the rigor of some submissions. While initial scoring will reflect this omission, we seek community input. Providing code fosters transparency and allows for validation – a practice we strongly advocate, as evidenced by our own consistent code sharing on ArXiv.

The recent Reddit post from a reviewer at AAAI 2027, highlighting the surprisingly low number of submissions with accompanying code, strikes at a core tension within the AI research community. It’s a signal that the drive toward demonstrable reproducibility, a principle increasingly vital for validating AI advancements, isn’t universally embraced. This echoes concerns raised in discussions around practical AI applications, such as the search for real-world examples of predictive analytics in mortgage lending [Looking for real-world examples of predictive analytics in mortgage lending], where the ability to scrutinize underlying methodologies is paramount. The ease with which AI coding startups like Cognition [AI coding startup Cognition reportedly already in talks to raise at $40B valuation] can now generate seemingly plausible, yet potentially flawed, research papers further underscores the need for rigorous verification and, crucially, open access to the code that produced those results.

The reviewer’s point about the diminishing excuse for omitting code is particularly poignant. While concerns about intellectual property theft were once a common barrier, the reality is that the risk is minimal, and the benefits of transparency far outweigh the perceived drawbacks. The ability for others to replicate, extend, and build upon research findings is fundamental to scientific progress. Moreover, the proliferation of AI assistants capable of generating empirical results in short order – as the reviewer wryly notes – amplifies the importance of verifying those results through accessible code. A lack of code implementation casts immediate doubt on the rigor of the work, regardless of the quality of the appendices. It suggests a reluctance to open the methodology to scrutiny, potentially masking underlying weaknesses or biases. This isn't about preventing idea theft; it's about ensuring the integrity of the research itself. The increasing sophistication of AI notetaking hardware [Why Stream ring-maker Sandbar says the future of AI wearables is voice] demonstrates the growing accessibility of tools that can both generate and analyze data, making code accessibility even more critical for discerning genuine insights.

The AAAI’s explicit emphasis on reproducibility is a welcome step, but it requires more than just a statement of intent. Reviewers, like the one on Reddit, are clearly taking this seriously, and it's reasonable to expect that code availability will increasingly become a significant factor in evaluating submissions. This shift isn't just about academic rigor; it’s about building trust in AI systems. As AI continues to permeate various aspects of our lives, from financial decisions to healthcare diagnoses, the ability to understand and validate the underlying algorithms becomes increasingly essential. A culture of open code and reproducible research fosters this trust, allowing for greater scrutiny and ultimately leading to more robust and reliable AI solutions. The trend towards increased transparency aligns with a broader movement towards explainable AI (XAI), which seeks to make AI decision-making processes more understandable to humans.

Looking ahead, the challenge will be to incentivize code sharing and provide support for researchers who may lack the resources or expertise to properly document and distribute their code. Perhaps AAAI and other conferences could explore mechanisms like pre-publication code reviews or provide templates for code documentation. Ultimately, the move towards greater code transparency represents a necessary evolution in AI research, one that prioritizes verifiable results and fosters a collaborative environment where knowledge can be freely shared and built upon. The question remains: will this shift become the norm, or will a significant portion of the AI research community continue to resist the call for open and reproducible practices?

I am now reviewing a bunch of papers for AAAI 2027 and it has surprised me the low amount of submissions with no code implementation. I don’t know if it has been only in my batch or it is common, but I was expecting very detailed appendices + code submission since AAAI is very explicit with the topic of reproducibility. I was planning to take this into consideration when assigning my initial scores, but I would like to hear your opinions. I have always submitted my code: it gives a very good impression and after reviewing process finishes we just publish it on ArXiv, so no one “tries to stole the idea” (although I think that this is very very unlikely). So I cannot find any excuse for those submissions that do not have code implementation, specially in today’s times where AI assistants can just write an empirical paper with artificial results within a couple of hours

submitted by /u/wontonut
[link] [comments]

Read on the original site

Open the publisher's page for the full experience

View original article