REVIEW 1 cited by
The thermal-radiative wind in the neutron star low mass X-ray binary GX 13+1
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
read the original abstract
We fit the observed high ionisation X-ray absorption lines in the neutron star binary GX13+1 with a full simulation of a thermal-radiative wind. This uses a radiation hydrodynamic code coupled to Monte Carlo radiation transfer to compute the observed line profiles from Hydrogen and Helium-like iron and Nickel, including all strong K{\alpha} and K{\beta} transitions. The wind is very strong as this object has a very large disc and is very luminous. The absorption lines from Fe K{\alpha} are strongly saturated as the ion columns are large, so the line equivalent widths (EWs) depend sensitively on the velocity structure. We additionally simulate the lines including isotropic turbulence at the level of the azimuthal and radial velocities. We fit these models to the Fe xxv and xxvi absorption lines seen in the highest resolution Chandra third order HETGS data. These data already rule out the addition of turbulence at the level of the radial velocity of ~500 km/s. The velocity structure predicted by the thermal-radiative wind alone is a fairly good match to the observed profile, with an upper limit to additional turbulence at the level of the azimuthal velocity of ~100 km/s. This gives stringent constraints on any remaining contribution from magnetic acceleration.
Forward citations
Cited by 1 Pith paper
-
Why do massive stars form bow shocks? Bulk ISM motion as the main driver of bow shock formation and geometry
Bulk interstellar gas motion, not stellar motion, dominates most massive star bow shocks; only about 21% are classical aligned bow shocks.
Discussion (0). Continue with ORCID to comment.