Review History


All reviews of published articles are made public. This includes manuscript files, peer review comments, author rebuttals and revised materials. Note: This was optional for articles submitted before 13 February 2023.

Peer reviewers are encouraged (but not required) to provide their names to the authors when submitting their peer review. If they agree to provide their name, then their personal profile page will reflect a public acknowledgment that they performed a review (even if the article is rejected). If the article is accepted, then reviewers who provided their name will be associated with the article itself.

View examples of open peer review.

Summary

  • The initial submission of this article was received on October 28th, 2020 and was peer-reviewed by 2 reviewers and the Academic Editor.
  • The Academic Editor made their initial decision on November 25th, 2020.
  • The first revision was submitted on December 9th, 2020 and was reviewed by the Academic Editor.
  • A further revision was submitted on January 16th, 2021 and was reviewed by the Academic Editor.
  • The article was Accepted by the Academic Editor on January 20th, 2021.

Version 0.3 (accepted)

· Jan 20, 2021 · Academic Editor

Accept

The author has met all the comments provided by all reviewers and the the paper is in very good standard for publishing in PeerJ computer science journal.

Version 0.2

· Jan 11, 2021 · Academic Editor

Minor Revisions

The math equations must be explained in how will be used in your study. No further comments

Version 0.1 (original submission)

· Nov 25, 2020 · Academic Editor

Minor Revisions

This paper presents a novel control scheme for a swarm of UAVs, this paper should be revised aligned with the reviewer's comments.

[# PeerJ Staff Note: It is PeerJ policy that additional references suggested during the peer-review process should only be included if the authors are in agreement that they are relevant and useful #]

[# PeerJ Staff Note: Please ensure that all review comments are addressed in a rebuttal letter and any edits or clarifications mentioned in the letter are also inserted into the revised manuscript where appropriate.  It is a common mistake to address reviewer questions in the rebuttal letter but not in the revised manuscript. If a reviewer raised a question then your readers will probably have the same question so you should ensure that the manuscript can stand alone without the rebuttal letter.  Directions on how to prepare a rebuttal letter can be found at: https://peerj.com/benefits/academic-rebuttal-letters/ #]

Reviewer 1 ·

Basic reporting

no comment

Experimental design

no comment

Validity of the findings

no comment

Additional comments

This paper proposes a novel control scheme for a swarm of UAVs that
employs the original Reynolds rules but adopts an adaptive weight allocation
mechanism based on the current context than being fixed at the beginning.

This paper contains some interesting results. Please find the following comments that may help improve the paper.

(1) It is suggested to highlight the challenges of the investigated problem.

(2) The significance of using an adaptive weight allocation mechanism needs to be explained.

(3) What is the meaning of step 3 in algorithm 1?

(4) Please explain the steps 6-9 in algorithm 2.

(5) The simulation is done on Pygame. What is the advantage and disadvantage compared to other software?

(6) This paper is about flocking control. The following three references should be included in the introduction section to present readers a complete literature review. B. Shucker, T. D. Murphey, and J. K. Bennett, “Convergence-preserving switching for topology-dependent decentralized systems,” IEEE Trans. Robot., vol. 24, no. 6, pp. 1405-1415, Dec. 2008. B. Ning, Q.-L. Han, Z. Zuo, J. Jin, and J. Zheng, “Collective behaviors of mobile robots beyond the nearest neighbor rules with switching topology,” IEEE Trans. Cybern., vol. 48, no. 5, pp. 1577-1590, May 2018. R. Olfati-Saber, “Flocking for multi-agent dynamic systems: Algorithms and theory,” IEEE Trans. Autom. Control, vol. 51, no. 3, pp. 401-420, Mar. 2006.

(7) In figure 2, the decrease of average distance from 4.4 to 4.8 looks strange, please explain the reason.

(8) The language of this paper needs to be improved.

Reviewer 2 ·

Basic reporting

The paper has been written in reasonably good English. Introduction and background may be enough for the specialist. In general, it would be nice to have a bit more details. There are over 20 relatively recent references. Also, major work from the past is pointed out. Figures are generally well together with the text. Perhaps a more rigorous usage of the units on axis, whenever applicable, would be relevant. For example, distance should have units, even if it is just “unit” (explained in the text).

Experimental design

The experiment is purely software-based, which may be enough for the current paper, but some real-life validation would enhance the value. So far the impact of factors (external forces) making it closer to the real-life is proposed only in upcoming works.

Validity of the findings

Better comparison with state of the art would be in order. No doubt that the results are interesting and useful, should the findings be verified in real life and against competing solutions.

Additional comments

It may be that the notation used in line68 is acceptable in the specialist circles (if time is taken as unity for example), but generally adding space coordinates in m, “unit” or similar (position vector) to the speed (velocity vector) in m/s, “unit”/s or similar should be avoided. There seems to be some problem with indexes - ws (line 168) seems to be alone.

All text and materials provided via this peer-review history page are made available under a Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.