Will I be desk rejected for this[R]

The anxiety expressed by /u/Gold_You_6594 on the MachineLearning subreddit regarding a potential desk rejection due to a minor page limit transgression is surprisingly relatable. We’ve all been there – meticulously crafting a submission, only to realize a last-minute detail might jeopardize the entire effort. The core concern highlights a surprisingly rigid aspect of academic publishing: adherence to formatting guidelines. It’s a reminder that even groundbreaking research can be sidelined by seemingly trivial technicalities. This situation underscores a broader tension within the machine learning community – the desire to push boundaries in algorithms and models versus the often-inflexible requirements of presenting that work to the wider academic world. It’s a process that often feels divorced from the innovative spirit it’s meant to evaluate. Relatedly, the discussions surrounding documentation and supplementary materials, as seen in [Some new updates to Papers with Code [P]], demonstrate a constant evolution and refinement of how research is presented and disseminated.

The likelihood of a desk rejection over a half-line overage is, thankfully, relatively low, but the user's paranoia is understandable. Conference committees often have a significant workload, and while a blatant disregard for guidelines might trigger an immediate rejection, a minor overshoot, especially if the paper appears otherwise promising, is less likely to result in such a swift dismissal. The fact that the submission status has been updated recently suggests at least some level of review is underway, offering a glimmer of hope. It’s worth noting that many conferences are moving toward more flexible submission processes, acknowledging that the focus should be on the content of the research rather than strict adherence to formatting rules. However, the prevalence of discussions like [WACV supp. mat. video [R]] demonstrates the ongoing challenges in navigating the complexities of conference submissions, particularly regarding supplementary materials and format requirements. Preparing effectively for these types of submissions is crucial, as highlighted in [Just landed a Computer Vision internship, here’s the preparation list I used [D]], where a thorough checklist helps researchers avoid common pitfalls.

The incident also reveals a broader trend: the increasing reliance on automated systems for initial screening of submissions. These systems often flag papers that deviate from specified formatting requirements, potentially leading to desk rejections even when the transgression is minor. While such systems aim to streamline the review process, they can also introduce unintended biases and disproportionately impact researchers who may not have access to sophisticated formatting tools or who are submitting from contexts where adherence to these conventions is less emphasized. This raises questions about the fairness and inclusivity of the academic publishing system. It also reinforces the importance of carefully reviewing submission guidelines and utilizing tools that can automatically format papers to meet those requirements. The potential for these automated checks to inadvertently filter out valuable research is a growing concern that the community needs to address.

Ultimately, /u/Gold_You_6594’s experience serves as a cautionary tale and a reminder of the often-unseen anxieties that accompany the publishing process. While the chances of a desk rejection over such a minor infraction are slim, the incident prompts a larger reflection on the rigidity of academic publishing and the potential for automated systems to exacerbate existing inequalities. The question becomes: how can we move toward a more equitable and efficient review process that prioritizes the quality and impact of research over adherence to increasingly granular formatting rules? It’s a challenge that requires ongoing dialogue and a willingness to reconsider established norms within the machine learning community.