For users

Using the data

Who may use 7DT data, on what terms, and what to know before working with it.

Policy

Data rights and publication

The 7DS publication policy governs authorship, data rights and the acknowledgment of 7DT observations in refereed work. It is being prepared by the collaboration and will be posted here once ratified. In the meantime, anyone intending to publish results based on 7DT data is asked to contact the principal investigator so that the appropriate collaboration authors and funding acknowledgments can be agreed in advance.

Until the policy is ratified, anyone intending to publish results based on 7DT data should contact the principal investigator in advance so that collaboration authorship and funding acknowledgments can be agreed. Observations obtained as target-of-opportunity follow-up carry the same expectation.

Acknowledgment

Publications using 7DT data should acknowledge the 7-Dimensional Telescope and its funding bodies. The current wording is on the funding page, and the instrument and pipeline should be cited from publications.

Before you start

Four things to know

  • 01

    Every image carries its own quality flags

    Check SANITY before using a frame: false means the pipeline judged the image unusable and recorded the stage at which it did so. Measured seeing, depth, ellipticity and astrometric precision are in the header of every product.

  • 02

    Coadd pixels are already in flux units

    Coadds are scaled to a zero point of 23.9 AB, which puts pixel values directly in microjansky — convenient for the pixel-based analysis that medium-band data invite, but a departure from the counts other archives deliver.

  • 03

    Not every band is calibrated to the same standard

    The original twenty medium bands are the calibrated set. The fifteen filters added in late 2025 are in operational use but their spectrophotometric calibration is still in preparation. Measured depths per band are on the performance page.

  • 04

    Products can be traced back to their inputs

    A dependency record links each output to the coadds, processed singles and master frames it was built from, and the pipeline version that produced it is recorded with the product.

Next

Where the rest is

What the pipeline produces, in what units, with what recorded alongside it — and how to obtain it in the first place — are on the data access page. How to reprocess it yourself is under available software.