Notes

Sort by:
  • Reference Designator
  • First Name
  • Created
  • Modified  
  • Metadata Start Date End Date Comment
    CP04OSPM-WFP01-04-FLORTK000
    Deployment: 4
    2/1/16, 12:00 AM 5/19/16, 12:09 PM

    Suspect data during the second half of the deployment.

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01-04-FLORTK000
    Deployment: 2
    11/1/14, 12:00 AM 4/29/15, 12:00 AM

    Suspect data

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01-04-FLORTK000
    Deployment: 1
    9/1/14, 12:00 AM 10/4/14, 12:30 PM

    Suspect data at the end of the deployment.

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01-02-DOFSTK000
    Deployment: 8

    Suspect profile in Dec 2017

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01
    9/26/16, 12:00 AM 9/28/16, 1:25 PM

    Deployment 5: suspect data at 0 dbar at the very end of the deployment

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01-01-VEL3DK000
    Deployment: 4

    According to annotation ID 569, recovered_wfp data are missing for this deployment. The raw data files should be loaded to the raw data server and ingested, or the dataset should be annotated to explain why recovered data aren't available.

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01-01-VEL3DK000

    vel3d_k_pressure (dbar) is an array of all fill values for every deployment.

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01-01-VEL3DK000
    Deployment: 8

    Data were found in the telemetered data stream but were not in the recovered data stream from 2017-12-25T00:00:02 to 2017-12-30T21:31:11.

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01-01-VEL3DK000

    Annotation ID 1407 needs to be updated when the code is fixed

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01-01-VEL3DK000
    Deployment: 1

    Data were found in the telemetered data stream but were not in the recovered data stream for 2 time periods: 2014-04-15T20:00:00 to 2014-04-20T21:00:00 and 2014-07-14T00:00:00 to 2014-07-19T22:00:00.

    By Lori Garzio, on 8/26/19

    CP04OSPM-WFP01-03-CTDPFK000
    Deployment: 4

    Suspect profile in Nov 2015

    By Lori Garzio, on 8/26/19

    CP02PMUO-WFP01-05-PARADK000

    11% - 96% of parad_k_par values for deployments 3-10 are outside of global ranges. Zooming in shows that the majority of the values outside of global ranges are negative. This should be investigated.

    By Lori Garzio, on 8/23/19

    CP02PMUO-WFP01-05-PARADK000
    Deployment: 9

    Suspect data

    By Lori Garzio, on 8/23/19

    CP02PMUO-WFP01-05-PARADK000
    Deployment: 4

    Suspect data

    By Lori Garzio, on 8/23/19

    CP02PMUO-WFP01-04-FLORTK000
    Deployment: 3
    7/20/14, 12:00 AM 10/5/14, 12:11 PM

    Suspect data towards the end of the deployment.

    By Lori Garzio, on 8/23/19

    CP02PMUO-WFP01-04-FLORTK000
    Deployment: 10
    2/15/18, 12:00 AM 4/10/18, 10:15 AM

    Suspect data at the end of the deployment

    By Lori Garzio, on 8/23/19

    CP02PMUO-WFP01-04-FLORTK000
    Deployment: 9
    8/28/17, 12:00 AM 11/11/17, 12:45 PM

    Suspect data at the end of the deployment

    By Lori Garzio, on 8/23/19

    CP02PMUO-WFP01-04-FLORTK000
    Deployment: 8
    10/25/16, 12:00 AM 6/7/17, 12:08 PM

    Suspect backscatter

    By Lori Garzio, on 8/23/19

    CP02PMUO-WFP01-04-FLORTK000
    Deployment: 7
    8/20/16, 12:00 AM 10/1/16, 4:16 PM

    Suspect data towards the end of the deployment

    By Lori Garzio, on 8/23/19

    CP02PMUO-WFP01-04-FLORTK000
    Deployment: 8

    63% of total_volume_scattering_coefficient values are outside of global ranges for this deployment

    By Lori Garzio, on 8/23/19

    22 of 135