TIMEDOMES data are part of the italian in-kind contribution to the LSST community
As such, while the raw data of legacy surveys are available through the ESO data portal, for the time being all reduced data, masks, diagnostic plots, catalogs and lightcurves will be distributed only to LSST data-right holders following the in-kind policy.
Once the in-kind proprietary period is over the access will be made public to the entire astronomical community and reduced images will be uploaded on the ESO portal.
Data releases: the data are distributed through periodic releases as the survey progresses.
DR1: was released in September 2025. It containes reduced images for the first 5 years (2011-2016) of the Cosmos and CDF-S fields (README).
DR2: has been released in March 2026. It contains reduced images acquired over the first 11 years (2011-2022) of the Cosmos and CDF-S fields. It also contains masks and source catalogs for the all Cosmos observations of the first 3 years (2011-2013) as well as lightcurves (README).
DR3: to be released in summer 2026, will likely extend the Cosmos data products and lightcurves to the first 11 years (2011-2022), as well as include masks, catalogs and lightcurves for the CDF-S fields up to 2016.
DR4: planned for the end of 2026, will extend the data release to the new TIMEDOMES data including ELAIS-S1 and XMM-LSS.
DR5: planned for the first half of 2027 will release the full dataset, catalogs and lightcurves of all fields.
Data access
The data and a Readme file with all the relevant information can be downloaded in two ways:
NAS access (slow): using a direct link that can be provided upon request. The connection relies on an external service so it is relatively slow and should be used for inspection or download of moderate amount of data. It requires an access to the NAS service that can be requested to the Timedomes team (maurizio.paolillo@unina.it).
Data center (faster): through the Naples AdHoc data center. The access requires an account, which can be requested through this form, specifying that you need access to the in-kind TIMEDOMES data.