Swarm-in-Blocks: Simplifying Drone Swarm Programming with Block-Based Language

Agnes Bressan de Almeida; Joao Aires Correa Fernandes Marsicano

REVIEW 3 major objections 2 minor 18 references

Swarm-in-Blocks: Simplifying Drone Swarm Programming with Block-Based Language

T0 review · 3 major / 2 minor · reviewed 2026-08-05 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗

Pith's one-line read Swarm-in-Blocks is presented as a high-level, block-based interface that lets users program drone swarms by assembling loops and conditional structures, without requiring deep ROS or programming knowledge.

desk verdict The submission is not a coherent paper: the abstract advertises a block-based drone swarm tool, but the full text is an unrelated higher-spin physics paper, so there is nothing to evaluate. read the letter →

arxiv 2508.11498 v1 pith:DHWFCC6N submitted 2025-08-15 cs.RO

Agnes Bressan de Almeida , Joao Aires Correa Fernandes Marsicano This is my paper

classification cs.RO

keywords droneswarmsblock-basedprogrammingvisualCloverplatformROSabstractionswarmmanagementeducationalroboticsCopterHack

verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

Swarm-in-Blocks is presented as a high-level, block-based programming interface for drone swarms, built on the Clover platform. The paper's central claim is that a user can create swarm behaviours — loops, conditionals, coordinated actions — by dragging and assembling code blocks, without needing deep knowledge of ROS or text-based programming. The motivation is practical: as swarms move into delivery, agriculture, and surveillance, the people who deploy them may not be robotics programmers, and a visual language would widen who can write swarm logic. The abstract asserts the tool exists, originated in CopterHack 2022, and was refined in 2023 as Swarm-in-Blocks 2.0. Note: the full text supplied with this record is a different manuscript, so this summary rests on the abstract alone.

What carries the argument

The central object is the block-based language itself: a drag-and-drop visual language in which each block represents a control or action unit, and assembling blocks constructs program logic such as loops and conditionals. The machinery's role is to translate those block assemblies into commands for the Clover drone platform, replacing hand-written ROS code as the user-facing programming surface, and thereby claiming to lower the entry barrier for swarm programming.

What would settle it

Run a controlled study in which novice users program a fixed swarm mission (takeoff, formation loop, conditional landing) with Swarm-in-Blocks and with text-based ROS, measuring completion time, errors, and help needed. If block-based beginners are no faster or need similar support, the simplification claim fails. Separately, verify that the submitted record actually contains the tool's code or documentation; the text currently attached is an unrelated physics manuscript.

Watch

Extended reading notes

Core claim

The discovery claimed is that a block-based visual language can serve as a high-level interface for drone swarm programming. On the Clover platform, the interface lets users assemble loops and conditional structures from blocks rather than writing ROS nodes, and this is said to make swarm handling accessible without extensive programming knowledge. The paper positions Swarm-in-Blocks 2.0 as the refinement of the original 2022 CopterHack project, with the refinement aimed at reducing the complexity of swarm management in a user-friendly way.

Load-bearing premise

The load-bearing premise is that assembling code blocks genuinely reduces the programming burden of drone swarms for beginners; the abstract asserts this, but the record supplies no implementation details, documentation, simulator demo, or user data to support it.

Editorial extensions

If this is right

Beginners could author swarm loops and conditionals without writing ROS code.
The Clover platform would become a low-entry environment for classroom swarm robotics.
Swarm use cases in delivery, agriculture, and surveillance could see faster prototyping by non-specialists.
Swarm-in-Blocks 2.0 would position the 2022 CopterHack tool as a maintained educational interface.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

If the block semantics are faithful to Clover's command set, a block-assembled mission should compile to the same ROS-level commands as a hand-written script; comparing command traces would test the abstraction without needing human subjects.
The accessibility claim could be tested directly: have first-time users program a fixed mission in block form and in text; the paper gives no such data, so this is the immediate next experiment.
Educational value would follow only if the visual language also exposes the underlying logic; a useful extension would be a 'show the code' view that reveals the generated ROS structure, turning blocks into a scaffold for learning text programming.

Share X Bluesky LinkedIn Reddit HN

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Desk Editor's Note

read the letter

The first thing you should know: this submission cannot be reviewed as-is. The metadata and abstract describe "Swarm-in-Blocks," a block-based programming interface for drone swarms. The full text is Vasiliev and Vereitin's "Differential Contracting Homotopy in the Linearized 3d Higher-Spin Theory" (arXiv:2508.11500). That is not a minor formatting glitch; it is an authentication failure. Every downstream claim—that the tool simplifies swarm programming, that it works for beginners without ROS knowledge, that version 2.0 improved on version 1.0—is unsupported by any accessible manuscript content. I can no more evaluate the drone tool than I can evaluate a recipe by reading a car manual.

To give credit where it is due: the abstract's stated goal is sensible. Visual, block-based programming for robotics is an established approach, and applying it to drone swarms could be a useful educational contribution. The authors mention a CopterHack 2022 origin and a 2023 2.0 iteration, which suggests the tool has had real use. But none of that appears in the supplied text. There is no architecture, no block semantics, no implementation details, no user study, no benchmark, no comparison with prior block-based drone tools (e.g., Scratch, Blockly, or Clover's own ecosystem). The abstract's claims about delivery, agriculture, and surveillance are contexts, not demonstrated outcomes.

The physics paper that actually appears in the full text may be mathematically competent—I am not judging it—but it is not the paper under review. The mismatch makes the submission incoherent on its own terms: the title and abstract claim one thing, the body is about something else entirely.

Who is this for? A reader interested in drone swarm education might find the abstract a useful pointer to a project that may exist on GitHub or in the CopterHack archives. But that is not peer-reviewed literature; it is a project blurb. The physics paper is for readers of hep-th, and it should be submitted to the appropriate venue, not grafted onto a cs.RO abstract.

My recommendation: desk reject. Do not send this to reviewers. Ask the authors to resubmit the correct manuscript—the actual Swarm-in-Blocks paper—and, if it is a serious tool paper, require that it include an evaluation against existing block-based systems and a clear description of what the interface actually does. As submitted, there is no evidence to referee.

Referee Report

3 major / 2 minor

Summary. The manuscript announces 'Swarm-in-Blocks', a block-based programming interface for drone swarms built on the Clover platform, and claims that it simplifies swarm programming for beginners by removing the need for deep ROS or programming knowledge. The abstract describes two versions, the original CopterHack 2022 tool and a 2023 'Swarm in Blocks 2.0' refinement. However, the full text supplied with this submission is not the Swarm-in-Blocks paper. It is arXiv:2508.11500, a theoretical physics paper by M.A. Vasiliev and V.A. Vereitin titled 'Differential Contracting Homotopy in the Linearized 3d Higher-Spin Theory'. That text contains no description of the drone-swarm tool, no system overview, no block semantics, no implementation details, no user study, and no benchmark. As submitted, the manuscript therefore consists only of an abstract making an unsupported central claim plus an unrelated physics paper. No scientific content of the claimed contribution can be evaluated from the provided document.

Significance. If the tool exists and delivers what the abstract claims, it could be a useful educational contribution to drone-swarm programming, particularly for beginners and classroom use. The block-based approach and the Clover integration are plausible design choices, and the claimed support for loops and conditionals is a sensible feature set for a visual programming interface. However, significance cannot be assessed from the submitted material. There is no machine-checked proof, no reproducible code, no demonstration, no user evaluation, and no technical narrative connecting the abstract's claims to any artifact. The supplied full text is not even the same paper. Consequently, the manuscript in its current form provides no evidence that the central claim is true, and it does not permit the usual refereeing checks of novelty, correctness, or usability.

major comments (3)

[Full text (arXiv:2508.11500)] The full text supplied with the submission is a high-energy physics paper by Vasiliev and Vereitin, not the Swarm-in-Blocks paper announced in the title and abstract. There is no architecture description, block-language specification, Clover integration discussion, example programs, or evaluation of any kind for the drone-swarm tool. This is a load-bearing submission-integrity failure: the existence of the described tool cannot be verified from the provided document, and no downstream claim can be checked. This issue cannot be repaired by local revisions; the correct manuscript would need to be supplied.
[Abstract] The central claim that Swarm-in-Blocks 'simplifies drone swarm programming' and makes swarm handling accessible 'without requiring extensive knowledge of ROS or programming' is unsupported by any evidence in the submitted material. No user study, usability metric, task-completion benchmark, feature comparison against existing ROS or block-based tools, or even a demonstration video is provided. Even if the full text had been the correct paper, this evaluative claim would need supporting material or at least a clearly scoped system description before it could be accepted as more than an assertion.
[Abstract (version claim)] The abstract asserts that 'Swarm in Blocks 2.0' further refined the platform to address swarm-management complexity, but no details of the differences between versions 1.0 and 2.0 are given, and no change log or design rationale is present. The version claim is therefore not assessable. This is a secondary issue compared with the full-text mismatch, but it would need to be addressed in any revised submission.

minor comments (2)

[Abstract] The abstract would be easier to evaluate if it included a project repository URL, a demonstration link, or a citation to the CopterHack 2022 entry; currently there is no pointer to any artifact.
[Full text] The manuscript title, abstract, and full text are inconsistent at the level of subject area. This should be caught by the submission process before review; in a revised submission the authors should confirm that the correct PDF is attached.

Circularity Check

0 steps flagged · score 0.0 of 10

No circularity: the supplied full text is a different arXiv paper, so no Swarm-in-Blocks derivation chain exists to reduce; the mismatch is an integrity issue, not circular reasoning.

full rationale

The abstract for 'Swarm-in-Blocks' makes a software-description claim: it 'simplifies drone swarm programming using a block-based language' and 'enables users to create functionalities like loops and conditional structures by assembling code blocks.' There is no derivation, fit, or equation, so there is nothing that could be self-definitional or a renamed prediction. The supplied full text is an unrelated higher-spin theory paper (arXiv:2508.11500), not the Swarm-in-Blocks manuscript. A missing or mismatched full text prevents evaluation of the abstract's claims, and it may be a serious correctness/authentication problem, but it is not circularity: the abstract does not obtain its conclusion from its own assumptions via a self-citation or a fitted parameter. No passage in the provided text asserts a limitation that reveals a circular step, and no load-bearing derivation chain is present to walk. Under the hard rule that circularity must be exhibited by quoting a specific reduction, none can be exhibited here. Score 0.

Assumptions & free parameters 0 free parameters · 0 assumptions · 0 invented entities

The drone paper's abstract introduces no free parameters, axioms, or invented entities. The mismatched full text is a separate physics paper; its assumptions are not assessed here.

how reviews work

0 comments

Cite this review

Pith. "Pith review of Swarm-in-Blocks: Simplifying Drone Swarm Programming with Block-Based Language." pith.science (2026). https://pith.science/paper/DHWFCC6N

@misc{pith2026250811498,
  author       = {Pith},
  title        = {Pith review of: Swarm-in-Blocks: Simplifying Drone Swarm Programming with Block-Based Language},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/DHWFCC6N}},
  note         = {Machine review of arXiv:2508.11498}
}

read the original abstract

Swarm in Blocks, originally developed for CopterHack 2022, is a high-level interface that simplifies drone swarm programming using a block-based language. Building on the Clover platform, this tool enables users to create functionalities like loops and conditional structures by assembling code blocks. In 2023, we introduced Swarm in Blocks 2.0, further refining the platform to address the complexities of swarm management in a user-friendly way. As drone swarm applications grow in areas like delivery, agriculture, and surveillance, the challenge of managing them, especially for beginners, has also increased. The Atena team developed this interface to make swarm handling accessible without requiring extensive knowledge of ROS or programming. The block-based approach not only simplifies swarm control but also expands educational opportunities in programming.

Discussion (0). Sign in to comment.

Reference graph

Works this paper leans on

18 extracted references · 4 canonical work pages

[1]

A. V. Korybut, A. A. Sevostyanova, M. A. Vasiliev and V. A. Vereitin, Phys. Lett. B838, 137718 (2023) [arXiv:2211.15778 [hep-th]]

arXiv 2023
[2]

M. A. Vasiliev, Mod. Phys. Lett. A7, 3689-3702 (1992)

work page 1992
[3]

S. F. Prokushkin and M. A. Vasiliev, Nucl. Phys. B545, 385 (1999) [arXiv:hep-th/9806236 [hep-th]]

arXiv 1999
[4]

M. A. Vasiliev, Int. J. Mod. Phys. D5, 763-797 (1996) [arXiv:hep-th/9611024 [hep-th]]

arXiv 1996
[5]

M. P. Blencowe, Class. Quant. Grav.6, 443 (1989)

work page 1989
[6]

V. E. Didenko, O. A. Gelfond, A. V. Korybut and M. A. Vasiliev, J. Phys. A51, no.46, 465202 (2018) [arXiv:1807.00001 [hep-th]]

arXiv 2018
[7]

M. A. Vasiliev, JHEP11, 048 (2023) [arXiv:2307.09331 [hep-th]]

arXiv 2023
[8]

M. A. Vasiliev, Class. Quant. Grav.11, 649-664 (1994)

work page 1994

Show all 18 references

[9]

V. E. Didenko, N. G. Misuna and M. A. Vasiliev, JHEP03, 164 (2017) [arXiv:1512.07626 [hep-th]]

2017 arXiv
[10]

Giombi and X

S. Giombi and X. Yin, JHEP09, 115 (2010) [arXiv:0912.3462 [hep-th]]

2010 arXiv
[11]

Boulanger, P

N. Boulanger, P. Kessel, E. D. Skvortsov and M. Taronna, J. Phys. A49, no.9, 095402 (2016) [arXiv:1508.04139 [hep-th]]

2016 arXiv
[12]

O. A. Gelfond and M. A. Vasiliev, Phys. Lett. B786, 180-188 (2018) [arXiv:1805.11941 [hep-th]]

2018 arXiv
[13]

M. A. Vasiliev, Annals Phys.190, 59-106 (1989)

1989
[14]

M. A. Vasiliev, Phys. Lett. B834, 137401 (2022) [arXiv:2208.02004 [hep-th]]

2022 arXiv
[15]

A. V. Barabanshchikov, S. F. Prokushkin and M. A. Vasiliev, Teor. Mat. Fiz.110N3, 372-384 (1997) [arXiv:hep-th/9609034 [hep-th]]

1997 arXiv
[16]

P. T. Kirakosiants, D. A. Valerev and M. A. Vasiliev, Nucl. Phys. B1023, 117290 (2026) [arXiv:2506.16634 [hep-th]]

2026
[17]

V. E. Didenko, O. A. Gelfond, A. V. Korybut and M. A. Vasiliev, JHEP12, 086 (2019) [arXiv:1909.04876 [hep-th]]

2019 arXiv
[18]

M. A. Vasiliev, JHEP10, 111 (2017) [arXiv:1605.02662 [hep-th]]. 23

2017 arXiv

Pith tools

Reviewed August 5, 2026 · model on record in the stance chip above.

[1] [1]

A. V. Korybut, A. A. Sevostyanova, M. A. Vasiliev and V. A. Vereitin, Phys. Lett. B838, 137718 (2023) [arXiv:2211.15778 [hep-th]]

arXiv 2023

[2] [2]

M. A. Vasiliev, Mod. Phys. Lett. A7, 3689-3702 (1992)

work page 1992

[3] [3]

S. F. Prokushkin and M. A. Vasiliev, Nucl. Phys. B545, 385 (1999) [arXiv:hep-th/9806236 [hep-th]]

arXiv 1999

[4] [4]

M. A. Vasiliev, Int. J. Mod. Phys. D5, 763-797 (1996) [arXiv:hep-th/9611024 [hep-th]]

arXiv 1996

[5] [5]

M. P. Blencowe, Class. Quant. Grav.6, 443 (1989)

work page 1989

[6] [6]

V. E. Didenko, O. A. Gelfond, A. V. Korybut and M. A. Vasiliev, J. Phys. A51, no.46, 465202 (2018) [arXiv:1807.00001 [hep-th]]

arXiv 2018

[7] [7]

M. A. Vasiliev, JHEP11, 048 (2023) [arXiv:2307.09331 [hep-th]]

arXiv 2023

[8] [8]

M. A. Vasiliev, Class. Quant. Grav.11, 649-664 (1994)

work page 1994