1 min readfrom Machine Learning

ECCV reviewer wants me to compare and contrast to my own paper. [D]

Our take

In response to the ECCV reviewer's request, it is essential to address the potential overlap between our current submission and the older arXiv version. While the title and method name have changed, the core results and figures remain consistent, with minor additions in the latest iteration. The reviewer’s use of specific language from our previous work, though not cited, suggests they may be referencing our earlier paper.

The peer review process exists to uphold scholarly rigor, yet situations like this reveal the human complexities that can emerge when institutional protocols intersect with practical realities. When a researcher discovers that a reviewer has identified their previously published arXiv work during a double-blind review cycle, they face a delicate balancing act between transparency and compliance. This scenario speaks to broader questions about how we manage intellectual lineage in an age where preprints circulate widely before formal publication. Much like troubleshooting technical challenges such as Having issues printing a document or optimizing workflows like Simplifying a task assignment process, where 2000 tasks are broken up among 10 workers, navigating academic publishing requires both strategic thinking and clear communication protocols that serve the ultimate goal of advancing knowledge.

The core tension here revolves around the fundamental purpose of double-blind review: protecting both authors and reviewers from bias while maintaining rigorous evaluation standards. However, the reality of modern academic workflows means that researchers naturally iterate on their work, refining methodologies and improving presentation through multiple versions. When a reviewer encounters recognizable intellectual fingerprints across different versions of the same work, they are not necessarily failing to uphold blind review standards—they may simply be demonstrating the kind of scholarly engagement that makes peer review valuable. The challenge lies in creating systems that acknowledge this reality without compromising the integrity of the review process itself.

What makes this situation particularly nuanced is the reviewer's apparent use of specific language from the earlier work without proper citation. This raises important questions about academic attribution and the evolving nature of scholarly communication in digital spaces. Researchers working with data visualization challenges, such as those seeking to Only show Yes percentages in their analyses, understand the importance of clear labeling and proper credit assignment. Similarly, academic work deserves transparent acknowledgment of its evolution and influences, even when that acknowledgment must navigate institutional constraints.

Looking forward, this scenario suggests we need more sophisticated approaches to handling iterative research in peer review systems. The emergence of persistent identifiers, version tracking, and clearer guidelines for preprint citations could help bridge the gap between traditional blind review expectations and contemporary research practices. How might academic communities develop more adaptive frameworks that honor both the spirit of blind review and the reality of iterative scholarship? The answer may lie in creating more transparent pathways for authors to acknowledge their intellectual journey while maintaining fair evaluation processes that focus on the quality and contribution of the current work.

Bascially title.

A reviewer found the arxiv of our paper, which is an older version, before we changed the title and name of the method for this submission. The results, figures and all that are the same minus some additions for the current version, a even small reading of what they are referncing should make it clear its the same paper by the same people.

They use the very specific language of our previous writing without citing it so we cant be 100% sure they are but we are fairly certain.

We are planning to write a little note to the AC and say we cant address it in our rebuttal for double-blind so we did not refute that issue raised.

What would you do in this situation?

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

Read on the original site

Open the publisher's page for the full experience

View original article