The Tarantula Massive Binary Monitoring
Bibliographic record
Abstract
Context. A high fraction of massive stars are found to be binaries but only a few of them are reported as photometrically variable. By studying the populations of double-lined spectroscopic binaries in the 30 Doradus region, we found a subset of them that have photometry from the OGLE project and that display variations in their light curves related to orbital motions. Aims. The goal of this study is to determine the dynamical masses and radii of the 26 binary components in order to investigate the mass-discrepancy problem and to provide an empirical mass-luminosity relation for the Large Magellanic Cloud (LMC). Methods. We use the PHOEBE programme to perform a systematic analysis of the OGLE V and I light curves obtained for 13 binary systems in the 30 Doradus region. We adopt the effective temperatures, and orbital parameters derived previously to obtain the inclinations of the systems and the parameters of the individual components. Results. Three systems display eclipses in their light curves, while the others only display ellipsoidal variations. We classify two systems as over-contact, five as semi-detached, and four as detached. The two remaining systems have uncertain configurations due to large uncertainties on their inclinations. The fact that systems display ellipsoidal variations has a significant impact on the inclination errors. From the dynamical masses, luminosities, and radii, we provide LMC-based empirical mass-luminosity and mass-radius relations, and we compare them to other relations given for the Galaxy, the LMC, and the Small Magellanic Cloud. These relations differ for different mass ranges, but do not seem to depend on the metallicity regimes. We also compare the dynamical, spectroscopic, and evolutionary masses of the stars in our sample. While the dynamical and spectroscopic masses agree with each other, the evolutionary masses are systematically higher, at least for stars in semi-detached systems. This suggests that the mass discrepancy can be partly explained by past or ongoing interactions between the stars.
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.001 | 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".