NeurIPS openreview - can I upload paper pdf after abstract deadline or should I upload something first to be able to update it later? [D]
Our take
The annual NeurIPS submission cycle inevitably surfaces a wave of procedural questions from first-time submitters, and this year's cohort is no exception. A recent inquiry on Reddit captures the essence of what many researchers grapple with: the tension between strict deadlines and the practical realities of preparing complex submissions. The question of whether one can upload a paper PDF after the abstract deadline, or must first submit something to preserve the ability to update later, speaks to a fundamental anxiety among submitters—fear of missing a technicality that could derail months of work. Understanding these procedural nuances matters because the difference between a valid submission and a disqualified one often hinges on timing and technical compliance, not on the quality of the research itself.
The related discussions in our archive, such as "[Neurips : Pushing anonymous repo after rebuttal [D]](post/neurips-pushing-anonymous-repo-after-rebuttal-d-cmoyanvr70i53jfqbdzdmtvrf)," reveal that these concerns extend well beyond initial submission deadlines. Researchers are asking similar questions about code repositories and the integrity of the anonymous review process, suggesting a broader need for clearer communication from conference organizers about what is permitted and what is enforced.
The code submission question is particularly revealing because it touches on the honor system underlying open review processes. When submitters ask whether they can update a URL later or whether they must input something initially to preserve flexibility, they are implicitly asking about the boundaries of acceptable behavior. More importantly, the question about how NeurIPS prevents people from pushing code after deadlines reflects a deeper concern: if some researchers exploit loopholes while others play by the rules, the competitive balance of the review process is compromised. The honest answer is that conference systems can only do so much to enforce integrity. Technical measures like locking repositories after certain dates help, but the system ultimately relies on researcher ethics and the vigilance of reviewers who may notice suspicious timing discrepancies between paper submissions and repository activity.
What makes these questions worth examining is what they reveal about the culture of academic publishing in AI. The NeurIPS openreview system was designed to increase transparency and enable community feedback, but it also places significant burden on submitters to navigate complex procedures without clear guidance. For first-time submitters especially, the learning curve can be steep and the stakes couldn't be higher. The fact that these questions appear year after year suggests that the community would benefit from more proactive education from conference organizers, not just in the form of detailed guidelines but in the form of clear, accessible explanations of the reasoning behind specific deadlines and restrictions.
As AI conferences continue to grow in scale and importance, the tension between rigorous process and accessibility will only intensify. The question worth watching is whether the community can find ways to maintain the integrity of the review process while reducing the anxiety that accompanies every submission. Perhaps the answer lies not in stricter enforcement but in better communication—helping researchers understand not just what the rules are, but why they exist and how they serve the collective goal of advancing scientific discourse fairly.
Hi,
I have a question about openreview procedure as in the title. It’s my first time submitting to neurips so I’m unsure.
Also for code URL submission can I do the same or should I put an URL in first? And side question, but does anyone know how neurips prevent people from pushing codes after paper deadline?
Thank you in advance!
[link] [comments]
Read on the original site
Open the publisher's page for the full experience