Data Releases

Please cite Kriek et al. (2015) for any publications using the MOSDEF data products

December 7, 2014:
MOSDEF Spectroscopic redshifts (Ascii; Fits; Readme)
Based on 8 masks from the 2012B-2013A observing runs
October 1, 2015:
MOSDEF Spectroscopic redshifts (Ascii; Fits; Readme)
Based on 21 masks from the 2012B-2014A observing runs (full sample from Kriek et al. 2015)
August 16, 2016:
MOSDEF Spectroscopic redshifts (Ascii; Fits; Readme)
Based on 30 masks from the 2012B-2015A observing runs
March 11, 2018:
MOSDEF Spectroscopic redshifts (Ascii; Fits; Readme)
Based on final MOSDEF sample of 54 masks from the 2012B-2016A observing runs

January 2021:
MOSDEF 2D and 1D Spectra
This data release includes both 2D and 1D spectra for galaxies in the MOSDEF survey, as well as a catalog required for matching each spectrum with a v4.1 ID in the 3D-HST survey.

2D spectra: For each field (AEGIS, COSMOS, GOODS-N, GOODS-S, and UDS) there is a corresponding gzipped tarfile containing all of the individual 2D MOSDEF slitlets. The slitlet files have the following filename conventions: <field-abbreviation><redshift-abbreviation>_<mask#>.<filter>.<SLIT-ID>.2d.fits. The “field-abrreviation” codes are: ae, co, gn, gs, ud for AEGIS, COSMOS, GOODS-N, GOODS-S, and UDS, respectively. The “redshift-abbreviation” codes are: 1, 2, and 3, for z~1.5, z~2.3, and z~3.4 redshift ranges, respectively. The “mask#” indicates the pointing area in each field that is targeted by the mask (see Kriek et al. 2015, Figure 2). The “filter” is Y, J, H, or K, and “SLIT-ID” is the targeting ID for the slitlet (the 3D-HST v2.1 for the ~35% of the targets and 3D-HST v4.1 for ~65% of the targets). For z~2 masks (mask prefixes starting, e.g., “gn2”), there are J, H, and K spectra. For z~3 masks (mask prefixes starting, e.g., “gn3”), there are H and K spectra. For z~1.5 masks (mask prefixes starting, e.g., “gn1”), there are either Y, J, and H spectra, or else just J and H. These spectra are flux calibrated but not corrected for slit losses. The file readme_2ddata describes the headers of the 2D spectra.

1D spectra: For each field, (AEGIS, COSMOS, GOODS-N, GOODS-S, and UDS) there is a corresponding gzipped tarfile containing all of the 1D extractions from the 2D slitlets above. The spectrum filenames have the following filename conventions <field-abbreviation><redshift-abbreviation>_<mask#>.<filter>.<ID>.ell.1d.fits for objects that were the main target of a given slit. For objects serendipitously detected on the slit, the filename conventions are <field-abbreviation><redshift-abbreviation>_<mask#>.<filter>.<SLIT-ID>.<ap-no>.ell.1d.fits. The same field and redshift abbreviations apply to the 1D spectra. In addition, “ap-no” refers to the aperture number (2, 3, 4) extracted for the serendipitous object. Serendipitous objects were extracted in order from top to bottom along the slit. Since in some cases multiple objects were extracted from the same 2D slitlet, there are more 1D than 2D spectra. These spectra are flux-calibrated and have been corrected for slit-losses. The file readme_1ddata describes the headers of the 1D spectra.

ID+redshift catalog: fits and ascii redshift catalogs for the full MOSDEF survey, (similar to the redshift catalog that can be retrieved from this site, above, but with a few additional useful columns included). The file readme_mosdef_zcat.final_slitap explains the columns of this catalog.

Below we describe how to interpret filenames for the case of additional serendipitous objects extracted from a given 2D slitlet, with reference to the MOSDEF ID+redshift catalog. We note that there are some subtleties to the MOSDEF object naming conventions to be aware of in order to use the spectra properly:

First, when the MOSDEF survey began, we used the 3D-HST v2.1 catalog for targeting purposes. Midway through the survey, the targeting ID system was updated to 3D-HST v4.1, and all the target IDs changed. However, the object IDs in all MOSDEF spectra refer to the ID at the time of targeting. Accordingly, 19/54 masks are on the v2.1 system, and 35/54 are on the v4.1 system. The catalogs above include columns ID_v2.1, ID_v4.1, and ID. ID_V2.1 and ID_V4.1 refer to the v2.1 and v4.1 IDs of an object, while ID refers to the ID used for targeting (and the ID in the spectrum filename).

Next, the main target of a slit was always extracted as aperture #1 (APERTURE_NO=1). Any serendips were extracted from top to bottom of the slit as aperture 2, 3, and so on. The catalogs above list which aperture an object can be found in if it is not the main target of a slit.

We now provide two examples for finding the spectra corresponding to a given 3D-HST v4.1 ID that is in the MOSDEF survey.

First, a straightforward example. The simplest case is if you are looking for the spectrum of a galaxy targeted on a v4.1 mask, which is the main target of its slit (i.e., not a serendipitously detected galaxy):

Here is the relevant line from the ID+redshift catalog:

# FIELD ID_V2.1D ID_V4.1 RA DEC Z_MOSFIRE Z_QUAL MASKNAME TARGET SLITOBJNAME ID APERTURE_NO
GOODS-N 8736 19658 189.349122 62.238069 2.2109 7 gn2_deep 1 19658 19658 1

GOODS-N 19658 (v4.1) was targeted on mask gn2_deep, which was on the v4.1 system. It was the main target on the slit, and you can find its 1D spectra here:
gn2_deep.H.19658.ell.1d.fits
gn2_deep.J.19658.ell.1d.fits
gn2_deep.K.19658.ell.1d.fits

The 2D spectra will be on these slitlets:
gn2_deep.H.19658.2d.fits
gn2_deep.J.19658.2d.fits
gn2_deep.K.19658.2d.fits

Second, a more complex example. This is the case of a serendipitously detected galaxy, which was targeted on a mask that used 3D-HST v2.1 IDs at the time of observation:

Here is the relevant line from the ID+redshift catalog:

# FIELD ID_V2.1D ID_V4.1 RA DEC Z_MOSFIRE Z_QUAL MASKNAME TARGET SLITOBJNAME ID APERTURE_NO
GOODS-N 2944 6336 189.276575 62.172466 3.4123 7 gn2_04 0 2959 2944 3

The spectrum of object GOODS-N 6336 (v4.1 ID) was extracted on a v2.1 mask (gn2_04). This galaxy (v2.1 ID=2944) was in aperture 3 on the slit targeting 2959 (v2.1 ID). So, to find the 1D spectra of GOODS-N 6336 (v4.1 ID) look for the files:
gn2_04.J.2959.3.ell.1d.fits
gn2_04.H.2959.3.ell.1d.fits
gn2_04.K.2959.3.ell.1d.fits

The 2D spectra will be on these slitlets:
gn2_04.J.2959.2d.fits
gn2_04.H.2959.2d.fits
gn2_04.K.2959.2d.fits

This second example comprises a most-complicated scenario, mixing version numbers, and for the spectrum of a serendipitously detected galaxy, not the main target of a slit. Most cases will be simpler.

MOSDEF Spectra:

2D Spectra (README)

AEGIS (ae_2dspec.tar.gz)

COSMOS (co_2dspec.tar.gz)

GOODS-N (gn_2dspec.tar.gz)

GOODS-S (gs_2dspec.tar.gz)

UDS (ud_2dspec.tar.gz)

1D Spectra (README)

AEGIS (ae_1dspec.tar.gz)

COSMOS (co_1dspec.tar.gz)

GOODS-N (gn_1dspec.tar.gz)

GOODS-S (gs_1dspec.tar.gz)

UDS (ud_1dspec.tar.gz)

ID+Redshift Catalog (Ascii; Fits; Readme)

May 2021:

MOSDEF Emission-Line Catalogs

This data release includes measurements of slit-loss-corrected, rest-optical emission lines from MOSDEF spectra, as generally described in Kriek et al. (2015) and Reddy et al. (2015). Please note that the field “ID” in the linemeas catalogs linked below refers to the target ID at the time of observation. This “ID” field can be found in the “ID+Redshift Catalog” linked just above, and can therefore be matched unambiguously to a 3D-HST v4.1 catalog ID.

The following catalog contains emission-line measurements where the Balmer features are uncorrected for underlying stellar absorption (linemeas_nocor.fits, Readme).

The following catalog contains emission-line measurements where the Balmer features are corrected for underlying stellar absorption based on the best-fitting FAST model fits to the broadband photometry (linemeas_cor.fits, Readme).