Skip to main content
Sandbox Physics
Stellar streams, encounters and observed projections

Stellar streams · L1

Why does a stellar stream develop a gap?

A gap usually means the stars have moved, not vanished. A brief gravitational encounter can alter their orbital clocks just enough that a sparse region appears hundreds of millions of years later. Immediately after the encounter, the same region may actually be more crowded.

A tug together can become a drift apart

Picture stars moving around the Galaxy in a narrow band. A massive object passes nearby and pulls stars on both sides toward the encounter. At first those stars converge. Counting them in a short segment can show an enhancement.

Their subsequent motion is not straight-line travel. A small forward kick can put a star on an orbit with a larger mean radius. In a host with nearly constant circular speed, the larger circuit takes longer. That star initially moves forward, yet eventually falls behind. A backward kick can reduce the guiding radius and shorten the orbital clock.

The useful question is therefore not simply which star is faster now. Ask which orbit it occupies and how long each circuit takes. Small differences in those clocks accumulate until stars move away from the original encounter region.

Reading: Erkal & Belokurov (2015), Forensics of Subhalo-Stream Encounters, arXiv:1412.6035v2 · Sandbox Physics standalone stellar-stream scientific reader v1

One thin stream contains many orbits

The Galaxy pulls differently on the near and far sides of a cluster or dwarf galaxy. Those tidal differences can gradually remove stars and produce a stream. Escaping stars have slightly different positions and velocities. They spread along their orbits into a long band rather than following one identical path.

Our experiment starts later in that story, with an imposed warm segment of 192 tracers. Warm means a small initial spread of positions and velocities. Every tracer follows its own three-dimensional trajectory, but the calculation does not release stars from a progenitor or include their mutual gravity. It asks what a passing force does to an existing ensemble.

Fresh finite tracer counts and same-star angular offsets
Top: counts at encounter, about 83 million years and 483 million years later. Bottom: same-star angular offsets from the host-only reference at about 533 million years. The numerical example contains 192 equal-weight tracers and fixed bins; each plotted time unit is about 66.7 million years.
Open the scalable figure

Reading: Erkal & Belokurov (2015), Forensics of Subhalo-Stream Encounters, arXiv:1412.6035v2 · Sandbox Physics standalone stellar-stream scientific reader v1

Put a number on the long memory

Two nearly circular orbital periods differing by one percent accumulate a phase difference of about a tenth of a turn, roughly thirty-six degrees, over ten circuits. Small clock differences become appreciable position differences. The time for an actual gap to develop also depends on how the kick varies along the stream.

For a more familiar scale, a velocity difference of one kilometre per second sustained for a hundred million years corresponds to about 102 parsecs of free straight-line travel. Galactic gravity bends the actual motion, so this is not a gap-width formula. It does explain why a modest disturbance can leave an extended trace.

Reading: Erkal & Belokurov (2015), Forensics of Subhalo-Stream Encounters, arXiv:1412.6035v2 · Sandbox Physics standalone stellar-stream scientific reader v1

Does the gap identify dark matter?

A small clump of dark matter bound within the Galaxy, called a dark subhalo, can perturb a stream without producing an obvious patch of light. That makes streams attractive probes of unseen mass. Ordinary massive objects also exert gravity, however, and variations in stellar release, smooth-potential orbital pile-ups and observational selection can change a count profile.

Position offsets, velocities, distances and chemistry add information. They need to be compared through the same observational selection. A striking gap, or an attractive fitted orbit, is not a unique verdict about the perturber. The thin stream and broad cocoon of GD-1 make that distinction particularly interesting.

Reading: Erkal & Belokurov (2015), Forensics of Subhalo-Stream Encounters, arXiv:1412.6035v2 · Valluri et al. (2025), GD-1 Stellar Stream and Cocoon in the DESI Early Data Release, arXiv:2407.06336v2

Make a prediction before changing the scene

Compare the compact and diffuse encounters at the same saved time. They use the same mass but distribute it differently; a more extended object produces a weaker nearby force gradient. Look at the saved counts and displacement diagnostics as well as the stars.

Then inspect the unperturbed reference. Losing a single tracer from a bin containing only a few stars can make a large ratio change. Counts outside the plotted range and the valid-ratio mask matter. These finite samples are not a continuous luminosity map.

Reading: Erkal & Belokurov (2015), Forensics of Subhalo-Stream Encounters, arXiv:1412.6035v2 · Sandbox Physics standalone stellar-stream scientific reader v1

Exercises and explanations

  1. The encounter region becomes denser at first. Is the simulation reversed?

    Read the explanation

    Not necessarily. Stars on both sides are initially pulled toward the encounter. Later orbital-period differences can reverse that compression. Inspect the full saved sequence rather than deciding from one frame.

  2. Would an extremely precise gap width give a precise perturber mass?

    Read the explanation

    Not by itself. Mass, size, velocity, impact geometry, elapsed time and the host potential all affect the width. Greater precision on one observable does not remove those physical degeneracies.

Try the prediction

Watch a gap develop

  1. Predict the early, middle and late count changes before inspecting the default complete record.
  2. At one saved time compare compact and diffuse presets, including physical vertical displacement; the scene discloses its vertical display enlargement.
  3. Export a record and connect the star positions to the counts and valid ratios at the same physical settings and saved time.

Sources and calculation scope

  1. Erkal & Belokurov (2015), Forensics of Subhalo-Stream Encounters, arXiv:1412.6035v2

    All 14 pages actually read. Sections 2–3 and equations 1–23 derive the short-encounter circular-stream model; sections 4–6 compare simulations and physical degeneracies. Printed pages 3/9 actually viewed. The imposed warm ensemble is not the paper’s tidal-release calculation.

  2. Valluri et al. (2025), GD-1 Stellar Stream and Cocoon in the DESI Early Data Release, arXiv:2407.06336v2

    Fixed 30 January 2025 v2, 25 pages fully read; original pages 7/12/14/21 actually viewed. Sections 3–5, Figures 2/7–12, Table 3 and Appendix A are distinguished from our conditional orbit exercise. DOI 10.3847/1538-4357/ada690; no original paper, figure or observed row redistributed.

  3. Sandbox Physics standalone stellar-stream scientific reader v1

    Own Python integrates 25 finite cases anew, checks an independent high-order reference, half steps, analytic limits and saved-record counts. Default zero network. Optional exact-source galpy exercise retains poor fit/nonconvergence/no-coverage failures. No App/Engine, completed tracks, originals or observed-derived figures in the ZIP.

FeedbackSomething broken, confusing, or missing on this page?Tell us
What kind of feedback?

Sent with this page’s address, its Lab ID, the site language and your device type. Please leave out personal details. Feedback is kept for up to 12 months.Privacy policy