Pith. sign in

REVIEW 3 major objections 5 minor 4 references

Ambiente de Simula\c{c}\~oes Utilizando Tra\c{c}ado de Raios com Ondas Milim\'etricas e MIMO Para VANTs

T0 review · 3 major / 5 minor · reviewed 2026-08-14 · deepseek-v4-flash

Pith's one-line read The paper claims that an integrated pipeline of traffic, flight, and ray-tracing simulators can generate large datasets of 60 GHz MIMO propagation between ground transmitters and UAVs.

desk verdict A modest but real extension of the authors' earlier mmWave ray-tracing pipeline to UAV scenarios; the environment works, but the claim that the generated data can guide system design needs validation it doesn't currently provide. read the letter →

arxiv 1908.07933 v1 pith:SU4572J2 submitted 2019-08-06 eess.SP

classification eess.SP
keywords UAVmmWaveMIMOraytracing5Gchanneldatasimulationenvironmentdronecommunications
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

To design 5G links for drones, engineers need channel data at millimeter-wave frequencies, but collecting it from real flights is slow and expensive. This paper tries to establish that an integrated simulation environment—a traffic simulator feeding positions to a flight simulator, then a ray-tracing engine computing the 60 GHz channel—can produce large volumes of such data in a repeatable way. In a case study, ten UAVs fly at 50, 100, and 150 meters over an urban street canyon, and the system records per-ray received power, departure and arrival angles, delay, and propagation events into a database. If the environment works, it gives researchers a flexible, low-cost source of aerial mmWave MIMO channel data for 5G system design.

What carries the argument

The central mechanism is an orchestration loop that connects simulators: the traffic simulator determines where the UAVs are on the map; the flight model adds their altitude (here 50, 100, or 150 m); and the ray tracer redraws the scene with those positions and computes the channel. The ray tracer is configured with X3D propagation, 60 GHz carrier, concrete buildings, metal drones, half-wave dipole antennas, 1° ray spacing, up to 25 analyzed rays per link, and Lambertian diffuse scattering with coefficients 0.4 for concrete and 0.2 for metal. For every ray, the tool writes received power, angles of departure and arrival, delay, and event type into a SQL database, which is the reusable output.

What would settle it

A 60 GHz channel sounder flown on a drone over a street canyon at 50, 100, and 150 m, compared with the simulator's database, would settle the matter: large systematic differences in median received power, delay spread, or angular spread would show the uncalibrated ray-tracing parameters misrepresent the channel.

Watch

Extended reading notes

Core claim

The authors' central claim is that the orchestrated simulation environment generates large amounts of propagation data for links between terrestrial transmitters and aerial vehicles, and that it is flexible enough to support several 5G investigations. Their case study places ten metal UAVs at three altitudes over a concrete urban canyon with a 5 m-tall transmitter, using the X3D ray-tracing model at 60 GHz, one-degree ray spacing, and Lambertian diffuse scattering with up to two bounces. The output is a SQL database organized by episodes, scenes, receivers, and rays; each ray carries received power, angles of departure and arrival, propagation delay, and interaction events such as reflections and diffractions. The authors present the environment as a tool for later channel modeling, and they do not compare the generated data against measurements.

Load-bearing premise

The paper's value rests on the assumption that its ray-tracing choices—concrete buildings, metal UAVs, 1° ray spacing, Lambertian scattering—produce channel data that reflects real 60 GHz UAV-to-ground propagation, yet no validation against measurements is provided.

Editorial extensions

If this is right

  • If the pipeline works as described, researchers can generate UAV-to-ground mmWave channel databases for arbitrary routes and city geometries without flight campaigns.
  • The per-ray records are directly usable for machine-learning tasks such as beam selection, extending the ground-vehicle data methodology in the paper's reference [1] to aerial users.
  • By repeating the simulation at different altitudes—50, 100, and 150 m—the environment can reveal how received power and delay spread change with UAV height.
  • Because UAV models, building materials, and routes can be edited in the simulator, the same environment can cover delivery, surveillance, and rural use cases.

Reading between the lines

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

  • The paper leaves unstated that the database's usefulness for system design depends on how faithfully the chosen ray-tracing parameters mimic real urban propagation; a calibration step against measured air-to-ground channels would strengthen that link.
  • One testable extension is to train a beam-selection policy on the UAV database and compare its accuracy with models trained on ground-level data; performance differences would quantify how much altitude changes the beam-choice problem.
  • The environment could be expanded to include moving ground traffic, weather losses, or 3D antenna patterns, all of which would change the angular spread and blockage statistics of the generated channels.
  • Because scattering coefficients are fixed without measurement, data generated for other cities or building materials should be treated as exploratory until re-tuned for that scenario.
Share X Bluesky LinkedIn Reddit HN

Signed reviews

No signed human review yet.

Editorial analysis

A structured set of objections, weighed in public.

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

Referee Report

3 major / 5 minor

Summary. The paper proposes a simulation environment for generating large amounts of UAV-to-ground propagation data at 60 GHz for 5G MIMO systems. The workflow combines SUMO for UAV mobility and Wireless InSite for ray tracing, with AirSim mentioned as a flight simulator. An urban case study with 10 UAVs at heights of 50, 100, and 150 m, 20 concrete buildings, and metal UAV bodies is defined; Table 1 lists the simulation parameters. Preliminary results are shown as received-power and propagation-delay plots for one UAV at 100 m, and the conclusion states that the environment is flexible and can support channel-model studies.

Significance. The contribution is an integration/orchestration layer rather than a new algorithm or model. If the generated data were validated, the environment would be useful for creating synthetic UAV mmWave channel data, e.g., for machine-learning-based beam selection. Strengths of the paper are the explicit parameter table, the previously established data model referenced in [1], and a pipeline description that is reproducible from the text. However, the paper presents no quantitative database statistics and no validation of the ray-tracing output against measurements or prior channel soundings; the stress-test concern about this gap is well-founded. The current significance is therefore limited to a work-in-progress report.

major comments (3)
  1. [§III-A (Banco de Dados); Figs. 4-5] The central claim that the environment "gera grandes quantidades de dados de propagação" is not supported by the evidence. The manuscript reports only two plots for a single UAV at 100 m and gives no quantitative description of the generated database: no number of episodes, scenes, receivers, or rays, no total sample count, and no statistics such as path-loss distributions, delay spreads, or angular spreads. Please add a quantitative characterization of the database and describe the output schema, so that the claim about "large amounts of data" can be assessed.
  2. [Table 1 and §II-B] The ray-tracing configuration is used without calibration or validation. At 60 GHz the channel is highly sensitive to the propagation model (X3D), the ray spacing (1 degree), the maximum number of rays per link (L=25), the diffuse-scattering coefficients (S=0.4 for concrete and 0.2 for metal), and the material parameters, all fixed in Table 1. The manuscript does not compare any simulated output with the measurements in [3] or any other UAV mmWave data, and no sensitivity analysis is provided. Because the stated purpose is to generate data for channel modeling and system design, the absence of validation leaves open the possibility that the database is self-consistent but physically unrepresentative. Please add a validation or calibration step, even a qualitative comparison to [3] or a sensitivity study, or explicitly restrict the abstract and title to "demonstration of the pipeline".
  3. [§I and §II-A] The introduction and abstract state that the environment combines traffic, flight, and ray-tracing simulators, naming AirSim, but the workflow described in Section II-A uses only SUMO and Wireless InSite. AirSim does not appear in the pipeline diagram or in the case-study description. Please either document how AirSim is integrated, including its role, interface, and outputs, or remove the claim that a flight simulator is part of the environment.
minor comments (5)
  1. [Title, Table 1, §II-B] The Portuguese text contains typographical and grammatical errors, e.g., "Trac ¸ado" in the title, "paiodo" instead of "período" in Table 1, and "antenas receptoras foram s ˜ao posicionadas" in Section II-B; a language revision is recommended.
  2. [Figs. 4-5] The captions indicate plots for "um VANT a 100 M", but the text states that three heights were simulated; please clarify how many UAVs and heights are included in these preliminary results.
  3. [§III-A and references] Section III-A refers to the database organization "como detalhado em [1]", but the references list gives no arXiv identifier or publication venue for [1]; please provide a complete reference.
  4. [§IV] The conclusion states that the base scenarios are obtained from CAD websites, but Section II does not describe this source and no reference is given; please add a description or citation.
  5. [Table 1] The table lists the transmitter antenna as a half-wave dipole at 5 m height, but it is not specified whether the receiver antennas are also half-wave dipoles and what their height relative to the UAV is; please clarify.

Circularity Check

0 steps flagged · score 1.0 of 10

No significant circularity: the paper reports a simulation environment and its generated database; no fitted parameter, equation, or uniqueness claim reduces the conclusion to its inputs.

full rationale

The central claim is that the proposed environment integrates SUMO and Wireless InSite (with AirSim mentioned as intended) to generate propagation data for UAV-mmWave-MIMO studies. This claim is supported by running a commercial ray tracer under the Table 1 configuration and storing the output in a database; there is no derived numerical prediction that is then compared back to an input. No parameter is fitted to a subset of data and later renamed a prediction. The paper does invoke the authors' prior work [1] for the general methodology and the database organization ('...está sendo desenvolvido com base na metodologia proposta em [1]' and 'como detalhado em [1]'), and that citation is a self-citation because Aldebaro Klautau is a co-author of both works. However, the self-citation is not load-bearing in the sense of forcing the paper's conclusion: the environment's functionality is demonstrated by the executed simulator runs and the resulting database, and [1] is used for bookkeeping conventions (episodes, scenes, receivers, rays) rather than as an unverified uniqueness theorem or as the source of the channel data. The concrete mmWave modeling choices (X3D propagation model, 60 GHz ITU concrete, metal UAVs, 1 degree ray spacing, Lambertian scattering) are arbitrary inputs to the ray tracer, not outputs of the paper's derivation, so they cannot make the derivation circular; whether they are realistic is a correctness/validation concern, not a circularity concern. The narrative also names AirSim as a flight simulator, while Section II-A describes a SUMO-to-Wireless-InSite workflow; this is an internal consistency gap, but it does not create a circular dependency. Because no step in the paper equates a claimed result with an input by construction, the circularity score is minimal.

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

The simulation environment is a tool, so the burden is on realism of the propagation model and the representativeness of the drone scenarios. The parameters are hand-picked configuration choices, not fitted constants, but they shape the output data.

free parameters (4)
  • Diffuse scattering coefficients S = 0.4 (concrete), 0.2 (metal)
    Chosen from Wireless InSite material models, not fit to UAV-specific measurements; affects reflected and diffuse ray powers.
  • Ray spacing = 1 degree
    Angular resolution of ray search; hand-picked, affects number of rays and accuracy.
  • Number of analyzed rays L = 25
    Maximum number of rays stored per receiver; arbitrary cutoff that may drop weaker paths.
  • Maximum diffuse scattering reflections = 2
    Limits simulation complexity; chosen by hand.
assumptions (3)
  • domain assumption Ray tracing with X3D model provides accurate propagation at 60 GHz in urban environments
    The paper uses Wireless InSite with X3D model and ITU concrete materials (Table 1) without validation against real UAV channel measurements.
  • domain assumption Buildings are homogeneous concrete and UAVs are metal boxes
    Material simplification in Section II.B ignores windows, roughness, and drone geometry details.
  • domain assumption SUMO-generated routes represent realistic UAV flight patterns
    The paper adds UAV routes in SUMO but does not compare to actual drone trajectories or aerodynamics.

how reviews work

0 comments
Cite this review

Pith. "Pith review of Ambiente de Simula\c{c}\~oes Utilizando Tra\c{c}ado de Raios com Ondas Milim\'etricas e MIMO Para VANTs." pith.science (2026). https://pith.science/paper/SU4572J2

@misc{pith2026190807933,
  author       = {Pith},
  title        = {Pith review of: Ambiente de Simula\cc\~oes Utilizando Tra\ccado de Raios com Ondas Milim\'etricas e MIMO Para VANTs},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/SU4572J2}},
  note         = {Machine review of arXiv:1908.07933}
}
read the original abstract

The use of UAVs tends to increase in the coming years, it is of great importance to study forms of communication with these aerial models. This paper presents a simulations environment that combines simulators of traffic, flight and ray tracing, to generates a large amounts of propagation data between terrestrial transmitters and aerial vehicles in 5G networks.

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

4 extracted references · 4 canonical work pages

  1. [1]

    Klautau, P

    A. Klautau, P. Batista, N. Gonz \'a lez-Prelcic, Y. Wang, and R. W. Heath Jr, ``5g mimo data for machine learning: Application to beam-selection using deep learning.''

  2. [3]

    UAV Air-to-Ground Channel Characterization for mmWave Systems

    W. Khawaja, O. Ozdemir, and I. Guvenc, ``Uav air-to-ground channel characterization for mmwave systems,'' arXiv preprint arXiv:1707.04621, 2017

  3. [2]

    Job Selection in a Network of Autonomous UAVs for Delivery of Goods

    P. Grippa, D. A. Behrens, C. Bettstetter, and F. Wall, ``Job selection in a network of autonomous uavs for delivery of goods,'' CoRR, vol. abs/1604.04180, 2016. [Online]. Available: http://arxiv.org/abs/1604.04180

  4. [4]

    11em plus .33em minus .07em @technote 4000 4000 100 4000 4000 500 `\.=1000 = #1 #1 #1 0pt [0pt][0pt] #1 * \| ** #1 \@IEEEauthorblockNstyle \@IEEEauthorblockAstyle \@IEEEauthordefaulttextstyle \@IEEEauthorblockconfadjspace -0.25em \@IEEEauthorblockNtopspace 0.0ex \@IEEEauthorblockAtopspace 0.0ex \@IEEEauthorblockNinterlinespace 2.6ex \@IEEEauthorblockAinte...

Pith tools

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