Notes

Sort by:
  • Reference Designator
  • First Name
  • Created
  • Modified  
  • Metadata Start Date End Date Comment
    CE06ISSM-SBD17-06-CTDBPC000
    Deployment: 1

    Deployment 1 recovered_inst data should be available for download (according to the ingest csv, the raw data file was never ingested because there wasn't a parser). If the recovered_inst data aren't available, the dataset should be annotated.

    By Lori Garzio, on 3/27/19

    CE04OSSM-RID27-04-DOSTAD000

    A substantial percentage of data for all deployments is outside of global ranges. It looks like the instruments biofouled shortly after each deployment (1-2 months) - the suspect data should be annotated for all deployments, and further analysis should be done using shipboard bottle data (which is outside the scope of this project).

    By Lori Garzio, on 3/27/19

    CE02SHSM-RID27-04-DOSTAD000

    A substantial percentage of data for all deployments is outside of global ranges. It looks like the instruments biofouled shortly after each deployment (1-2 months) - the suspect data should be annotated for all deployments, and further analysis should be done using shipboard bottle data (which is outside the scope of this project).

    By Lori Garzio, on 3/26/19

    CE04OSSM-RID27-04-DOSTAD000
    Deployment: 1

    Deployment 1 files are missing a pressure coordinate.

    By Lori Garzio, on 3/27/19

    CE04OSSM-RID27-04-DOSTAD000
    Deployment: 1

    int_ctd_pressure has units=no_units for deployment 1 (this variable has units=dbar for all other deployments).

    By Lori Garzio, on 3/27/19

    CE04OSSM-RID27-03-CTDBPC000
    Deployment: 1

    The data gap at the end of deployment 1 should be annotated.

    By Lori Garzio, on 3/27/19

    CE09OSPM-WFP01

    Deployment 6 for all instruments:
    Update annotation ID # 925 to indicate that the profiler was lost at sea and no recovered data are expected.
    Two other issues with telemetered data need to be mentioned:
    (1) the gaps in the data.
    (2) the change in the sampling rate.

    Are the gaps in the data as a result of a change in the sampling rate?

    By Leila Belabbassi, on 3/26/19

    CE04OSSM-RID27-03-CTDBPC000
    Deployment: 6

    Deployment 6 recovered_inst data should be available for download (the raw data file is available according to the ingest csv) or annotated to indicate why recovered_inst data are not available.

    By Lori Garzio, on 3/26/19

    CE02SHSM-RID27-02-FLORTD000
    Deployment: 5

    The missing data for deployment 5 should be annotated.

    By Lori Garzio, on 3/26/19

    CE02SHSM-RID27-03-CTDBPC000
    Deployment: 7

    Deployment 7 data gaps should be annotated: [['2018-04-20T18:48:18', '2018-05-18T21:30:23'], ['2018-05-23T16:48:11', '2018-05-25T17:30:24'], ['2018-05-30T15:18:11', '2018-06-01T19:30:22']]

    By Lori Garzio, on 3/26/19

    CE02SHSM-RID27-03-CTDBPC000
    Deployment: 6
    10/10/17, 2:21 AM 4/4/18, 1:57 PM

    Deployment 6 should be annotated to indicate why recovered_inst data aren't available.

    By Lori Garzio, on 3/26/19

    CE01ISSM-MFD37-03-CTDBPC000
    Deployment: 8
    11/25/17, 12:00 AM 1/19/18, 12:00 AM

    Conductivity, salinity, and density drop suddenly - this should be investigated and annotated if an issue is found. Excluding from summary data ranges.

    By Lori Garzio, on 3/26/19

    CE01ISSM-MFD37-03-CTDBPC000
    Deployment: 7
    8/24/17, 8:00 PM 10/12/17, 8:00 PM

    There are recovered_host and telemetered data available at the end of deployment 7 (2017-08-24T20:00:00 to 2017-10-12T20:00:00), and the same data are not available in the recovered_inst data stream. These data should be available in the recovered_inst data stream (or annotated if there was an issue with internally recording data).

    By Lori Garzio, on 3/26/19

    CE01ISSM-MFD37-03-CTDBPC000
    Deployment: 6
    2/4/17, 10:15 PM 4/17/17, 7:45 PM

    The missing data at the end of deployment 6 should be annotated.

    By Lori Garzio, on 3/26/19

    CE01ISSM-RID16-03-CTDBPC000
    Deployment: 7
    4/19/17, 4:18 AM 10/12/17, 9:50 PM

    Deployment 7 recovered_inst data should be available for download (the raw data file is available according to the ingest csv) or annotated to indicate why recovered_inst data are not available.

    By Lori Garzio, on 3/26/19

    CE01ISSM-RID16-03-CTDBPC000
    Deployment: 5
    5/18/16, 3:44 PM 10/2/16, 8:15 PM

    Deployment 5 should be annotated to indicate why no recovered_inst data are available. According to the ingest csv, "No Data on instrument. Did not start logging."

    By Lori Garzio, on 3/26/19

    CE01ISSM-RID16-03-CTDBPC000
    Deployment: 6
    1/15/17, 3:00 AM 2/1/17, 12:00 PM

    There are recovered_host and telemetered data available at the end of deployment 6 (2017-01-15T03:00:00 to 2017-02-01T12:00:00), and the same data are not available in the recovered_inst data stream. These data should be available in the recovered_inst data stream (or annotated if there was an issue with internally recording data).

    By Lori Garzio, on 3/26/19

    CE01ISSM-RID16-03-CTDBPC000
    Deployment: 1
    7/27/14, 9:50 PM 8/16/14, 10:30 PM

    The data gap at the end of deployment 1 should be annotated.

    By Lori Garzio, on 3/26/19

    CE01ISSM-RID16-03-CTDBPC000
    Deployment: 2
    12/13/14, 12:00 PM 4/12/15, 12:00 AM

    There are recovered_host and telemetered data available for the second half of deployment 2 (2014-12-13T12:00:00 to 2015-04-12T00:00:00), and the same data are not available in the recovered_inst data stream. These data should be available in the recovered_inst data stream (or annotated if there was an issue with internally recording data).

    By Lori Garzio, on 3/26/19

    CE01ISSM-SBD17-06-CTDBPC000
    Deployment: 6
    12/12/16, 5:00 AM 2/1/17, 5:00 PM

    There are sparse recovered_host and telemetered data available for the second half of deployment 6 (2016-12-12T05:00:00 to 2017-02-01T17:00:00), and the same data are not available in the recovered_inst data stream. These data should be available in the recovered_inst data stream (or annotated if there was an issue with internally recording data).

    By Lori Garzio, on 3/26/19

    108 of 135