MaNGA provides three primary catalogs: the targeting catalog, the DRPall file, and the DAPall file. The targeting catalog is a survey input and is described here as part of the discussion of MaNGA's parent target selection. The DRPall and DAPall catalogs are products of the survey that provide information about the observations, consolidates salient photometric properties of the observed galaxies, and provides global derived properties pulled from the data analysis results.
This is the final summary FITS binary table for the MaNGA Data Reduction Pipeline (DRP). It merges together information taken from
mangacore (the repository containing all MaNGA metadata), and various header information taken from the output MaNGA data cubes. It contains no actual spectra from MaNGA cubes, but all of the information required to find a given set of spectra. It can be used to search for galaxies matching a given set of selection criteria. The naming convention is
[drpver] is the version of the DRP used to produce the data and this summary file. Note that in DR17 the MaNGA and MaSTAR data (which we previously included in the same FITS extension) have now been split between extensions 1 and 2 respectively.
In particular, the DRPALL file provides two identifiers for MaNGA targets: MANGAID and PLATEIFU.
PLATEIFUis composed of the plate ID (
PLATE) and the IFU design ID (
IFUDSGN) in the format of
"PLATE-IFUDSGN". It uniquely identifies an observation of a target. The same object drilled on two different plates will have different
PLATEIFUidentifiers. This is analogous to the way of using
FIBERIDto identify targets in the original SDSS spectroscopy survey.
MANGAIDis composed of a catalog ID number and an object number with a hyphen in between. Within the same input catalog (e.g., the NSA
v1_0_1catalog), it uniquely identifies each object. The same galaxy from the same catalog always have the same
MANGAIDis in the format of "CatalogID-LineNumber". For instance, the NSA
v1_0_1catalog has a catalog ID of 1. The number after the hyphen is the 0-indexed line number of the object in that catalog. For example,
MANGAID'1-113567' is the object in the 113568th row of the NSA catalog. If the same galaxy appears in two different input catalogs (e.g., the NSA catalog and the input catalog of an ancillary project), it could have different
For the MaNGA commissioning plates the galaxies are selected from an older version of the NSA catalog, which has a catalog ID of 12.
A tutorial for how to interact with the DRPall file can be found here. The DRPall catalog is also uploaded as a CAS table called mangadrpall. You can find the schema for this table in the mangaDrpAll table description - go to the SkyServer Schema Browser, click to expand Tables, and select
The DAPall file provides final summary tables of the MaNGA Data Analysis Pipeline (DAP) results. It provides collated summary information about the DAP methods and global metrics derived from the DAP analysis products useful for sample selection.
Similar to the DRPall file, the DAPall file contains no resolved maps or model spectra, but a set of data that can be useful for selecting subsets of
MAPS and model
LOGCUBE files for further analysis.
The DAP analyzes each observation (
PLATEIFU) once per analysis method (
DAPTYPE). However, not all datacubes provided by the DRP are analyzed by the DAP. In DR17, the DAPall file has multiple extensions, one for each
DAPTYPE analysis (unlike in previous data releases when all
DAPTYPEs were listed in a single extension). There is a row in each extension for all attempted analyses of the available
DAPTYPE combinations. Some of the attempted analyses faulted, and these are listed among the known issues. The purpose of the
DAPDONE column in the DAPall file is to select those
DAPTYPE combinations where the DAP was successful in its analysis of the data.
For more information see the discussion of MaNGA catalogs in the data-release documentation and the relevant MaNGA DAP ReadTheDocs page.
A tutorial for how to interact with the DAPall file can be found here. The DAPall catalog is also uploaded as a CAS table called mangadapall. You can find the schema for this table in the mangaDapAll table description in the Schema Browser.