Papers › Streamer propagation in humid air

Streamer propagation in humid air

11 Apr 2023arXiv:2304.05160links table onlyarchive 2025-07-28

A. Malagón-Romero, A. Luque

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

We investigate the effect of humidity on the propagation of streamers in air. We present a minimal set of chemical reactions that takes into account the presence of water in a nonthermal air plasma and considers ionization, attachment, detachment, recombination and ion conversion including water cluster formation. We find differences in streamer propagation between dry and humid air that we attribute mostly to an enhanced effective attachment rate in humid air, leading to higher breakdown electric field and threshold field for propagation. This higher effective attachment rate in humid conditions leads to a faster decay of the conductivity in the streamer channel, which hinders the accumulation of charge in the streamer head. In some cases a propagating streamer solution still exists at the expense of a smaller radius and lower velocity. In other cases a high humidity leads to the stagnation of the streamer. We finally discuss how all these statements may affect streamer branching and the dimensions and lifetime of a streamer corona.

PaperPDFCode

Code

gitlab.com/MD-CWI-NL/afivo-streamer officialmentioned in paper report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

Not run by Syntology. Nothing on this page verifies that the listed code works.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections