Home » Conferences & Workshops » Financially Co-sponsored RAS Conferences » International Conference on Intelligent Robots and Systems (IROS) » Information for IROS Editors
| 2 March | Submission deadline |
| 7 March | Video submission deadline |
| 9 March | Papers placed in profiles and initial AE assignments available for Editors to review |
| 11 March | Deadline for Editors to check papers in profile and AE assignments to papers |
| 13 March | Papers assigned to AEs |
| 20 March | Deadline for AEs to assign papers to reviewers |
| 20 March | Deadline for AEs to summarily reject papers |
| 24 March | Deadline for Editors to endorse/revise AE summary rejection recommendations |
| 18 April | Deadline for reviewers to submit reviews |
| 30 April | Deadline for AE final reports |
| 9 May | Deadline for Editor endorsements of AE reports |
The IROS Conference Paper Review Board (ICPRB) is organized with one Editor-in-Chief (EiC), 27 Senior Editors (SE’s), roughly 400 Associate Editors (AE’s), and several hundred Reviewers. Each paper to be reviewed will be assigned one Editor and to one of the AEs that that Editor supervises. The AE will be responsible for obtaining a minimum of two high quality reviews for each paper they handle, and for preparing an AE recommendation that explains the recommended decision regarding the paper acceptance and presentation type. The AEs will also help to identify papers to be considered for awards. The Editors will be responsible for reviewing and endorsing the work done by the AEs on the papers for which they are responsible.
This page focuses on issues for Editors. The process from the perspective of AEs is noted on the IROS CPRB: Information for Associate Editors page.
The process from the perspective of Reviewers is noted on the IROS CPRB: Information for Reviewers.
Assignment of Papers to Editors and AEs. For IROS, the keywords are partitioned into sets, each of which is the responsibility of one Editor. When a paper is submitted to the conference (via PaperPlaza), the author’s choice of keywords will be used to determine to which Editor and AE the paper will initially be assigned. This initial assignment, which is done automatically by the system, is then reviewed by the Editor-in-Chief and the Editors to avoid conflicts of interest (COIs), to improve the matching of the expertise of the AE with the paper, and to provide load balancing across the AEs. Finally, the AEs must review the papers assigned to them and inform the supervising Editor of any COI they may have with their assigned papers.
Editor Tasks and Responsibilities.
Editors will also overview and endorse the identification of award candidates by the AEs.
The review process for IROS is managed using the PaperPlaza system. PaperPlaza provides a wide variety of tools to help AEs manage the review process. Reviewer assignments, review entry, AE reporting, and final decisions are all managed using PaperPlaza.
To access the system, go to the PaperPlaza page, click Start and then Log in. If you have forgotten your login information, you can retrieve it using the PIN management page.
It may be useful to spend a few minutes looking over the help pages, and in particular the Associate Editor’s FAQ at the PaperPlaza site: PaperPlaza Help Page.
(Re)Assigning Papers to AEs: A simple way to (re)assign a paper to one of your AEs or change the assignement is as follows:
Monitoring the Review Process: A useful way to monitor the review process and see the ratings and text for the reviews and the AE report is to use “Digests” as follows:
Tools > Program > Digests
After you have the digest page, select the items of information you are interested in and then hit the “submit” button at the bottom of the page. The spreadsheet resulting from your work will show up at the top of the page.
The Editor needs to review and endorse all AE recommendations. The Editor is responsible for checking that the quality standards of the review process (including number and depth of reviews, significance of AE’s reports, avoiding undecisiveness, etc.) have been met.
Support has been added to paper plaza so that the Editor reports can be done in the system. For each paper you handle, you can submit a report by clicking on the “Report” link in next to the paper’s information in your workspace. The report has similar format to the AE report. You will be required to complete the following parts of the report.
If you have already submitted your Editor report for a paper and wish to change it, please send the Editor-in-Chief the paper number and ask them to change the status of the paper to be under review so you can re-edit it.
Plagiarism cases involve serious accusations, which should be dealt with carefully. IEEE has clear policies to follow. IEEE defines plagiarism as the reuse of someone else’s prior ideas, processes, results, or words without explicitly acknowledging the original author and source. It is important for all IEEE authors to recognize that plagiarism in any form, at any level, is unacceptable and is considered a serious breach of professional conduct, with potentially severe ethical and legal consequences (source: Section “8.2 Publication Guidelines” of the IEEE PSPB Operations Manual, “Guidelines for Adjudicating Different Levels of Plagiarism.” )
IROS has access to the CrossCheck database, and initiative to prevent scholarly and professional plagiarism. Every submission will receive a plagiarism similarity score. The score and scan reports are generated by an external provider (iThenticate) and the scan reports are stored on the iThenticate servers and not downloaded to the conference submission system servers. Eventually the reports are deleted from the iThenticate servers at a time determined by conference and provider policy, after which they are no longer available.
IMPORTANT: It is very important to note that it is not possible to draw any conclusion from the iThenticate numerical score alone. Unfortunately, due to the output from iThenticate algorithms, there will be a number of false positives. One issue is that it represents a cumulative score so that, e.g., a 1% similarity with 40 papers is shown as 40% similarity. Another issue is that there may be large similarity, but still not plagiarism. For example, if an author has a version of their paper as an technical report or in a public dropbox someplace, it might get a very high (e.g., 99% or 100% similarity score). Hence, it is necessary that the detailed report be scanned to make sure that there is indeed a case of plagiarism. Also, some of the papers will not scan properly due to font problems.
The iThenticate reports are available to you as Editor and to your AE but they are NOT available to reviewers. You can access the reports for a particular paper, or prepare a digest containing the reporst for all the papers in your profile as follows.
To see the report on a particular paper:
To create a digest for all the papers in your profile:
This will give you a summary of all the papers in your profile which you can process as you wish, e.g., sort by similarity score, identify flags, etc., that will allow you to easily identify the papers that have scores 40 or higher, which should all get an inspection by you (and the AEs).
Self-plagiarism. The definition of self-plagiarism is that the paper includes substantial overlap with another of the authors published paper(s) and that the previously published paper is not cited in the references and/or the contribution of the current paper over that other papers is not described in the current submission, both of which are required by IEEE policy.
The AE should be able to determine if self-plagiarism is a concern by reviewing the paper and the plagiarism report. If this is considered to be the case, then the AE should set one of the plagiarism flags and inform their managing Editor. If the Editor agrees, then they should inform the Editor-in-Chief who will also review the paper and the report. If the EiC concurs, then they will inform the Editor and AE that the paper is a candidate for summary rejection and will request that the AE prepare a report describing the reason for the summary rejection.
Notes:
AE Procedures:
Plagiarism may also be spotted/reported by reviewers (recall, they don’t have access to the iThenticate report). If a reviewer detects a potential case of plagiarism, then they should document their concerns in the confidential comments portion of their review and should alert their AE. It is important that the Reviewer is factual in their remarks, and that as much and detailed evidence is provided as possible. For instance, this could be a copy of the supposedly plagiarized paper with the copied parts highlighted. It should also be noted that there exist freely available software that can detect plagiarism automatically: if this was used, details on the query and its outcomes would also be useful. Based on this information, the AE should use the information provided by the reviewer in the same fashion in which they would have if the alert was prompted by the iThenticate report.
Editor Procedures:
Share this page