Bibliographic record
Abstract
Context. The origin of massive runaway stars is an important unsolved problem in astrophysics. Two main scenarios have been proposed, namely: dynamical ejection or release from a binary at the first core collapse. However, their relative contribution remains heavily debated. Aims. Taking advantage of two large spectroscopic campaigns towards massive stars in 30 Doradus, we aim to provide observational constraints on the properties of the O-type runaway population in the most massive active star-forming region in the Local Group. Methods. We used radial velocity measurements of the O-type star populations in 30 Doradus obtained by the VLT-FLAMES Tarantula Survey and the Tarantula Massive Binary Monitoring to identify single and binary O-type runaways. Here, we discuss the rotational properties of the detected runaways and qualitatively compare the observations with expectations of ejection scenarios. Results. We identified 23 single and one binary O-type runaway objects, most of them located outside the main star-forming regions in 30 Doradus. We find an overabundance of rapid rotators (ve sin i > 200 km s−1) among the runaway population, thus providing an explanation for the observed overabundance of rapidly rotating stars in the 30 Doradus field. Considerations of the projected rotation rates and runaway line-of-sight velocities reveal a conspicuous absence of rapidly rotating (ve sin i > 210 km s−1), fast-moving (vlos > 60 km s−1) runaway stars in our sample, strongly suggesting the presence of two different populations of runaway stars: a population of rapidly spinning but slowly moving runaway stars and a population of fast-moving but slowly rotating ones. These are detected with a ratio close to 2:1 in our sample. Conclusions. We argue that slowly moving but rapidly spinning runaway stars result from binary ejections, while rapidly moving but slowly spinning runaways could result from dynamical ejections. Given that detection biases will more strongly impact the slow-moving runaway population, our results suggest that the binary evolution scenario dominates the current massive runaway star population in 30 Doradus.
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.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".