Data and Code Availability

Every research article should include a Data and Code Availability Statement. Authors should identify the observations, simulations, catalogues, calibration files and software needed to understand and assess the results.

Public data and code should be deposited in a stable disciplinary or general repository when practical and cited with a persistent identifier. Proprietary mission or observatory data may remain restricted for the stated access period; the statement should identify the source and conditions.

Methods should report software names and versions, major parameters, uncertainty treatment and enough workflow detail for an informed researcher to reproduce the analysis. Editors or reviewers may request underlying material for confidential assessment.