CTD, regional temperature and Icthyoplankton catch data collected from the eastern Bering Sea from 1997 to 2017

This dataset includes three components. The first component is physical data. The dataset includes depth, temperature, conductivity, and salinity (ppt) collected by the EcoFOCI program based out of the Alaska Marine Fisheries Science Center. The data were collected concurrently with ichthyoplankton...

Full description

Bibliographic Details
Main Authors: Lorenzo Ciannelli, Lauren Rogers
Format: Dataset
Language:unknown
Published: Research Workspace
Subjects:
Online Access:https://search.dataone.org/view/10.24431_rw1k7do_20230516T233214Z
Description
Summary:This dataset includes three components. The first component is physical data. The dataset includes depth, temperature, conductivity, and salinity (ppt) collected by the EcoFOCI program based out of the Alaska Marine Fisheries Science Center. The data were collected concurrently with ichthyoplankton collected by using either a 19plus version 2 SeaCAT or a Sea-Bird Scientific 49 FastCAT profilers. The cruise, station, and hauls at which the sensors were deployed are included as well as the date and time. These data were collected to obtain vertical profiles of abiotic parameters in the eastern Bering Sea in situ. Regional temperature data are regional sea surface temperature values, by year, for the eastern Bering Sea, from 1979 to 2017. Data are used as input for the JMA Climate Data Assimilation System and the Japanese 25-year re-analyses. The second component is biological (catch) data. These data were collected on seasonal cruises between February and October from 1979 to 2017 in the eastern Bering Sea (51.6 degrees N to 66.5 degrees N and east of -180 degrees W). These data contain ichthyoplankton catch records for Alaska plaice (eggs and larvae), flathead sole (eggs and larvae), Pacific cod (larvae), walleye pollock (eggs and larvae), rex sole (eggs), northern rock sole (larvae), and yellowfin sole (larvae). These data were collected by the Ecosystems and Fisheries-Oceanography Coordinated Investigations (EcoFOCI) program of the NOAA Alaska Fisheries Science Center with bongo nets with either a 333 or 505 micrometer mesh size. This is a .csv file, with each row pertaining to a specific haul of the bongo net at a specific station (identified by HAUL_ID and CRUISE as well as date and time (GMT_DATE_TIME) and geographical position (LAT and LON). Other variables are included, such as bottom depth, mesh size, species name and life stage, and the cruise name and haul number. The third component is modeling results. These data are the model output for the Bering10K ROMS simulations, which is a 10-km grid over the Bering Sea with 30 vertical layers. This was derived from the larger Northeast Pacific ROMS model (NEP5). The downscaled variable output is available as daily, weekly, or monthly values, of which only temperature and salinity were used for this research. Three Earth System Models (ESM) and two emission scenarios were used for the six dynamically downscaling runs of the Bering10K that provide forecast and historical outputs. These ESMs are the CESM version 2 with Community Atmospheric Model version 6, GFDL Earth System Model version 4.1, and MIROC Earth System version 2. The two emission scenarios are the Shared Socio-economic Pathways for a low carbon mitigation scenario (SSP5-8.5) and a high carbon mitigation scenario (SSP1-2.6). These ESMs and scenarios are from Phase 6 of the Coupled Model Intercomparison Project (CMIP6). Forecasts are bias corrected using the historical data, with a reference period of 1980 - 2014, and centered to the hindcasts. Output is available on the THREDDS data server hosted by NOAA ACLIM as netCDF files. All files begin with B10K-K20P19, indicating the Bering10K. The hindcast for the CMIP6 is then labeled as CORECFS. The CMIP6 outputs are labeled as such, followed with the ESM used (cesm, gfdl, miroc) and the scenario (ssp126, ssp585, historical). Outputs are split into folders labeled Level 1, 2, and 3. Files for this project were pulled from folder Level 1 for each ESM and scenario.