Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Data products of the survey of eclipses at the conjunctions predicted by Gaia DR3 single-lined spectroscopic orbits in TESS light curves, accompanying the paper "Eclipsing spectroscopic binaries from Gaia DR3 orbits and TESS: 93 systems at periods of 13–119 days". 9 389 orbits searched in up to three TESS sectors each; 227 stars with two consistent primary dips and 561 with one; 425 candidates absent from the variability catalogues vetted on every available sector; 93 eclipsing systems established at periods of 13–119 days (21 beyond 30 d), 90 of them never identified as eclipsing before, 54 with companion masses and radii from detached-binary fits. The record includes an integrity and reproduction check (check_z4.py) that recomputes the paper's funnel from the deposited files without a network connection. Contents: the selection of Gaia DR3 SB1 orbits observed by TESS with a conjunction predictable to one day (selection_v2.parquet); every predicted conjunction tested, with the depth and significance of the deepest dip and the control level (conjunctions.jsonl); the candidate stars with their star-level evidence and automatic catalogue checks (candidate_stars.jsonl); the batch vetting of the candidates absent from the variability catalogues — difference imaging, dips at predicted conjunctions in every sector, eclipse ephemerides, Gaia primary parameters, companion masses, verdicts (vetting_summary.csv, vet_*.json); and the eclipse fits of the confirmed systems (fits_table.csv, fit_*.json). Light curves are not included: they are the SPOC, TESS-SPOC and QLP products on MAST. Access is embargoed until the acceptance of the paper; the DOI can be cited meanwhile. CC BY 4.0. Version 1.1.0 supersedes 1.0.0 (doi:10.5281/zenodo.22998329): the funnel counts only the 9 389 selected stars (788 flagged, 561 single-dip); the candidate file has one line per source with grades recomputed from the conjunction rows; Table 3 uses the DR3 eccentricity for four partial eclipses whose free fit departs from it by more than 3σ; the software is lctriage 1.2.0 (doi:10.5281/zenodo.21916566, all versions). The data rows are unchanged. Version 1.1.1 changes only the software reference inside README.md and CITATION.cff: version 1.1.0 (doi:10.5281/zenodo.23003140) cited lctriage 1.2.0 by a version DOI that was never registered. Version 1.2.0 supersedes 1.1.1 (doi:10.5281/zenodo.23003581). The mass–radius sample of the paper now requires a reduced chi-square of the detached-binary fit of at most 10: six fits above it, previously counted as partial eclipses, are counted as poorly fitted, and the sample has 54 systems (34 full and 20 partial eclipses) instead of 60; check_z4.py applies the rule. Table 3 is regenerated accordingly: three partial eclipses are computed with the DR3 eccentricity, with a/R1 printed rescaled together with R2; K1 is given in km s−1. Figures 4 and A.1 are redrawn. The data rows are unchanged.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 2, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.