Epoch photometry. This table contains light curve data points. Each entry is a photometric flux-time pair for a given object, band and time. It follows the (evolving) VO convention for time series as much as possible. At the time of writing, a VO recommendation has not yet been released. It can be obtained selecting the INDIVIDUAL or COMBINED data structure options. A compact version using arrays and storing the full G, BP and RP bands light curve can be obtained using the RAW option. The corresponding data model is described in class epoch_photometry.
Note this table is not available through the main archive TAP interface, but via the Massive Data service, indexed by the VO Datalink protocol, described in Section 13.2.3.
Columns description:
A unique single numerical identifier of the source obtained from gaia_source.
For a given object, a transit comprises the different Gaia observations (SM, AF, BP, RP and RVS) obtained for each focal plane crossing.
Values: G (per-transit combined SM-AF flux), BP (blue photometer integrated flux) and RP (red photometer integrated flux).
Different times are defined for each band. For G, it is the field-of-view transit averaged observation time. For BP and RP, it is the observation time of the BP CCD transit. The units are Barycentric JD (in TCB) in days computed as follows. First the observation time is converted from On-board Mission Time (OBMT) into Julian date in TCB (Temps Coordonnee Barycentrique). Next a correction is applied for the light-travel time to the Solar system barycentre, resulting in Barycentric Julian Date (BJD). Finally, an offset of 2,455,197.5 days is applied (corresponding to a reference time at 2010-01-01T00:00:00) to have a conveniently small numerical value. Although the centroiding time accuracy of the individual CCD observations is (much) below 1 ms (e.g. in BP and RP), the G band observation time is averaged over typically 9 CCD observations taken in a time range of about 44 seconds.
Vega magnitude. It is computed from the flux applying the DR2 zero-point defined in https://www.cosmos.esa.int/web/gaia/iow_20180316
For G band, it is a combination of individual SM-AF CCD fluxes. For BP and RP bands, it is an integrated CCD flux.
The uncertainty flux_error on flux depends on the passband band as follows:
band G: the uncertainty on the weighted mean G flux of the set of SM/AF individual CCD observations for the transit. This accounts for intrinsic scatter in the data. The exact formula and further details are given in Carrasco, J. M. et al. (2017);
band BP: the uncertainty on the BP flux. This is the uncertainty associated with the single BP CCD transit available for a FoV transit. It includes photon noise and all applicable calibration errors. If the BP flux has been rejected or is unavailable, the value will be set to NaN (in VOTable and FITS formats) and an empty string (in plain text CSV format);
band RP: the uncertainty on the RP flux. This is the uncertainty associated with the single RP CCD transit available for a FoV transit. It includes photon noise and all applicable calibration errors. If the RP flux has been rejected or is unavailable, the value will be set to NaN (in VOTable and FITS formats) and an empty string (in plain text CSV format).
Mean flux in the band divided by its error.
Unavailable or rejected by DPAC photometric processing, or negative (unphysical) flux. When true, these rows are not provided in the default output because they are considerd only useful for debugging purposes.
rejected_by_variability : Rejected by DPAC variability processing (or variability analysis) (boolean)
Rejected by DPAC variability processing (or variability analysis), or negative (unphysical) flux.
This field contains extra information on the data used to compute the fluxes and their quality. It provides debugging information that may be safely ignored for many general purpose applications. The field is a collection of binary flags, whose values can be recovered applying bit shifting and masking operations. Each band has different binary flags in different positions, as shown below. Bit numbering is as follows: least significant bit = 1 and most significant bit = 64
G band:
Bit 1: SM transit rejected by photometry processing.
Bit 2: AF1 transit rejected by photometry processing.
Bit 3: AF2 transit rejected by photometry processing.
Bit 4: AF3 transit rejected by photometry processing.
Bit 5: AF4 transit rejected by photometry processing.
Bit 6: AF5 transit rejected by photometry processing.
Bit 7: AF6 transit rejected by photometry processing.
Bit 8: AF7 transit rejected by photometry processing.
Bit 9: AF8 transit rejected by photometry processing.
Bit 10: AF9 transit rejected by photometry processing.
Bit 13: G band flux scatter larger than expected by photometry processing (all CCDs considered).
Bit 14: SM transit unavailable by photometry processing.
Bit 15: AF1 transit unavailable by photometry processing.
Bit 16: AF2 transit unavailable by photometry processing.
Bit 17: AF3 transit unavailable by photometry processing.
Bit 18: AF4 transit unavailable by photometry processing.
Bit 19: AF5 transit unavailable by photometry processing.
Bit 20: AF6 transit unavailable by photometry processing.
Bit 21: AF7 transit unavailable by photometry processing.
Bit 22: AF8 transit unavailable by photometry processing.
Bit 23: AF9 transit unavailable by photometry processing.
BP band:
Bit 11: BP transit rejected by photometry processing.
Bit 24: BP transit photometry rejected by variability processing.
RP band:
Bit 12: RP transit rejected by photometry processing.
Bit 25: RP transit photometry rejected by variability processing.
All Gaia data processed by the Data Processing and Analysis Consortium comes tagged with a solution identifier. This is a numeric field attached to each table row that can be used to unequivocally identify the version of all the subsystems that where used in the generation of the data as well as the input data used. It is mainly for internal DPAC use but is included in the published data releases to enable end users to examine the provenance of processed data products. To decode a given solution ID visit https://gaia.esac.esa.int/decoder/solnDecoder.jsp