REVIEW 1 cited by
LMC-driven anisotropic boosts in stream--subhalo interactions
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
Dark Matter (DM) subhalos are predicted to perturb stellar streams; stream morphologies and dynamics can constrain the mass distribution of subhalos. Using FIRE-2 simulations of Milky Way-mass galaxies, we show that presence of a Large Magellanic Cloud (LMC)--analog significantly changes stream-subhalo encounter rates. Three key factors drive these changes. First, the LMC--analog brings in many subhalos, increasing encounter rates for streams near the massive satellite by up to 20--40%. Second, the LMC--analog displaces the host from its center-of-mass (inducing reflex motion), causing a north-south asymmetry in the density and radial velocity distribution of subhalos. This asymmetry results in encounter rates varying by 50--70% across the sky at the same distance. Finally, the LMC--mass satellite induces a density wake in the host's DM halo, further boosting the encounter rates near the LMC--analog. We also explore the influence of stream orbital properties, finding a 50% increase in encounters for streams moving retrograde to the LMC--analog's orbit in the opposite hemisphere. The dependence of encounter rates on stream location and orbit has important implications for where to search for new streams with spurs and gaps in the Milky Way.
Forward citations
Cited by 1 Pith paper
-
Dancing Streams In Merging Halos: Stellar Streams in a MW--LMC-like merger
A systematic N-body experiment finds that a 1:5 dark-matter merger strongly perturbs nearly all stellar streams, with morphology and orbit changes driven by close encounters with the infalling satellite.
Discussion (0). Continue with ORCID to comment.