REVIEW 1 cited by
Origins of Very Low Helium Abundance Streams Detected in the Solar Wind Plasma
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
abstract
The abundance of helium ($A_{He}$) in the solar wind exhibits variations typically in the range from 2-5% with respect to solar cycle activity and solar wind velocity. However, there are instances where the observed $A_{He}$ is exceptionally low ($<$ 1%). These low-$A_{He}$ occurrences are detected both near the Sun and at 1 AU. The low $A_{He}$ events are generally observed near the heliospheric current sheet. We analyzed 28 low-$A_{He}$ events observed by the Wind spacecraft and 4 by Parker Solar Probe (PSP) to understand their origin. In this work, we make use of the ADAPT-WSA model to derive the sources of our events at the base of the solar corona. The modeling suggests that the low-$A_{He}$ events originated from the boundaries of coronal holes, primarily from large quiescent helmet streamers. We argue that the cusp above the core of the streamer can produce such very low helium abundance events. The streamer core serves as an ideal location for gravitational settling to occur as demonstrated by previous models, leading to the release of this plasma through reconnection near the cusp, resulting in low $A_{He}$ events. Furthermore, observations from Ulysses provide direct evidence that these events originated from coronal streamers.
Forward citations
Cited by 1 Pith paper
-
Statistical insights on the decorrelation lengths of solar wind parameters at L1 point under varying conditions
Using ACE and Wind measurements, the authors report decorrelation lengths from ~270 RE (Bz in stream interaction regions) to ~8700 RE (bulk speed), with composition the least coherent parameter.
Discussion (0). Continue with ORCID to comment.