The disc origin of the Milky Way bulge
Bibliographic record
Abstract
Previous studies of the chemo-kinematic properties of stars in the Galactic bulge have revealed a puzzling trend. Along the bulge minor axis, and close to the Galactic plane, metal-rich stars display a higher line-of-sight velocity dispersion compared to metal-poor stars, while at higher latitudes metal-rich stars have lower velocity dispersions than metal-poor stars, similar to what is found in the Galactic disc. In this work, we re-examine this issue, by studying the dependence of line-of-sight velocity dispersions on metallicity and latitude in APOGEE Data Release 17, confirming the results of previous works. We then analyse an N-body simulation of a Milky Way-like galaxy, also taking into account observational biases introduced by the APOGEE selection function. We show that the inversion in the line-of-sight velocity dispersion-latitude relation observed in the Galactic bulge - where the velocity dispersion of metal-rich stars becomes greater than that of metal-poor stars as latitude decreases – can be reproduced by our model. We show that this inversion is a natural consequence of a scenario in which the bulge is a boxy or peanut-shaped structure, whose metal-rich and metal-poor stars mainly originate from the thin and thick disc of the Milky Way, respectively. Due to their cold kinematics, metal-rich, thin disc stars are efficiently trapped in the boxy, peanut-shaped bulge, and at low latitudes show a strong barred morphology, which – given the bar orientation with respect to the Sun-Galactic centre direction – results in high velocity dispersions that are larger than those attained by the metal-poor populations. Extremely metal-rich stars in the Galactic bulge, which have received renewed attention in the literature, do follow the same trends as those of the metal-rich populations. The line-of-sight velocity-latitude relation observed in the Galactic bulge for metal-poor and metal-rich stars are thus both an effect of the intrinsic nature of the Galactic bulge (i.e. mostly secular) and of the angle at which we observe it from the Sun.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".