Notes

Sort by:
  • Reference Designator
  • First Name
  • Created
  • Modified  
  • Metadata Start Date End Date Comment
    GS03FLMA-RIM01-02-CTDMOH051
    Deployment: 3

    Data are not available for download from uFrame this deployment. According to asset management, the bottom portion of the mooring was left in an extra year due to weather. This instrument was recovered on 2018-12-10T10:11:00 so data either need to be ingested or annotated to indicate why the data aren't available.

    By Lori Garzio, on 1/23/19

    GS03FLMA-RIM01-02-CTDMOH050
    Deployment: 3

    Data are not available for download from uFrame this deployment. According to asset management, the bottom portion of the mooring was left in an extra year due to weather. This instrument was recovered on 2018-12-10T10:11:00 so data either need to be ingested or annotated to indicate why the data aren't available.

    By Lori Garzio, on 1/23/19

    GS03FLMA-RIM01-02-CTDMOG048
    Deployment: 3

    Data are not available for download from uFrame this deployment. According to asset management, the bottom portion of the mooring was left in an extra year due to weather. This instrument was recovered on 2018-12-10T10:11:00 so data either need to be ingested or annotated to indicate why the data aren't available.

    By Lori Garzio, on 1/23/19

    GS03FLMA-RIM01-02-CTDMOH049
    Deployment: 3

    Data are not available for download from uFrame this deployment. According to asset management, the bottom portion of the mooring was left in an extra year due to weather. This instrument was recovered on 2018-12-10T10:11:00 so data either need to be ingested or annotated to indicate why the data aren't available.

    By Lori Garzio, on 1/23/19

    GS03FLMA
    Deployment: 3

    Annotation ID 378 needs to be updated - according to asset management, the bottom portion of the mooring was recovered on 2018-12-10T10:11:00.

    By Lori Garzio, on 1/15/19

    CE06ISSM-RID16-06-PHSEND000
    Deployment: 5

    51 days missing at the end of the data record indicates that the ph sensor did not record internally. If this is correct, annotation ID 899 should be modified to indicate the final status of the instruments.

    By Leila Belabbassi, on 1/22/19

    CE06ISSM-RID16-06-PHSEND000
    Deployment: 2

    The following gaps are not annotated in the system:

    ['2015-04-29T03:30:37', '2015-05-02T10:30:39']
    ['2015-05-02T21:30:41', '2015-05-04T04:30:41']
    ['2015-05-19T22:32:38', '2015-05-22T16:30:50']

    By Leila Belabbassi, on 1/22/19

    CE06ISSM-RID16-06-PHSEND000
    Deployment: 8

    Why are recovered-inst data not in the system?

    The missing data in the recovered_host stream are found at the end of the record in the telemetered stream.

    By Leila Belabbassi, on 1/22/19

    CE06ISSM-RID16-06-PHSEND000

    pressure coordinate is missing in the NetCDF data files for all deployments.

    By Leila Belabbassi, on 1/22/19

    CE06ISSM-RID16-03-CTDBPC000

    Deployments 1 and 6: Data gaps at the end of the deployment are not annotated in the system. (deployment 6 figure shown is here)

    By Leila Belabbassi, on 1/16/19

    CE09OSSM-RID27-03-CTDBPC000

    The following gaps are not annotated in the system:
    Gap at the end of deployments 1, 2 and 7
    Gap ['2017-08-11T20:32:30', '2017-08-13T19:30:21'] during deployment 5
    Gap ['2017-10-24T16:33:12', '2017-10-25T17:30:15'] during deployment 6
    Gap ['2018-04-27T18:33:12', '2018-05-25T17:30:23'] during deployment 7

    By Leila Belabbassi, on 1/17/19

    CE09OSSM-RID27-03-CTDBPC000

    Timestamps do not match between recovered_inst and telemetered or recovered_host for the following deployments: 1 through 7.

    By Leila Belabbassi, on 1/17/19

    CE09OSSM-RID27-03-CTDBPC000
    Deployment: 7

    Why are the recovered_inst data for deployment 7 missing from the system?

    By Leila Belabbassi, on 1/17/19

    CE06ISSM-RID16-03-CTDBPC000
    Deployment: 8

    Pressure data record on deployment 8 show deeper measurements (closer to 8 than 7 db) than the previous deployments. Is this correct?

    By Leila Belabbassi, on 1/17/19

    CE06ISSM-RID16-03-CTDBPC000
    Deployment: 8

    Why are recovered-inst data not in the system?

    The missing data in the recovered_host stream are found at the end of the record in the telemetered stream.

    By Leila Belabbassi, on 1/10/19

    CE06ISSM-RID16-03-CTDBPC000

    Deployments 1, 4, and 6: The missing data in the recovered_inst stream are found at the end of the record in both the telemetered and recovered_host streams.

    Deployments 1, 2, 3, 4, 5, 6 and 7: The timestamps do not match exactly between the preferred stream and the recovered_host and telemetered streams.

    By Leila Belabbassi, on 1/10/19

    CE06ISSM-RID16-03-DOSTAD000
    Deployment: 8

    Why are recovered-inst data not in the system?

    The missing data in the recovered_host stream are found at the end of the record in the telemetered stream.

    By Leila Belabbassi, on 12/17/18

    GI01SUMO
    Deployment: 4
    10/12/17, 12:00 AM 6/14/18, 8:02 AM

    The surface buoy detached from the mooring and the subsurface portion of the mooring fell to the seafloor (see annotation ID 102). Excluding all mooring data for this time range from final statistics.

    By Lori Garzio, on 1/15/19

    GS01SUMO-RII11-02-DOSTAD031
    Deployment: 2

    There are no recovered_host or telemetered data available for download from this instrument for deployment 2. There should be an annotation in the system indicating why there are no data available.

    By Lori Garzio, on 1/15/19

    GS01SUMO-RII11-02-FLORDG031
    Deployment: 2

    There are no recovered_host or telemetered data available for download from this instrument for deployment 2. There should be an annotation in the system indicating why there are no data available.

    By Lori Garzio, on 1/15/19

    129 of 135