Metadata | Start Date | End Date | Comment |
---|---|---|---|
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 6 |
10/5/16, 12:00 AM | 10/15/16, 12:00 AM |
suspect data ranges By Leila Belabbassi, on 3/28/19 |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 5 |
8/3/16, 12:00 AM | 8/30/16, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/28/19 |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 5 |
9/14/16, 12:00 AM | 9/20/16, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/28/19 |
RS03ASHS-MJ03B-10-CTDPFB304 Deployment: 3 |
10/10/17, 12:00 AM | 10/11/17, 6:00 AM | |
RS03ASHS-MJ03B-10-CTDPFB304 Deployment: 3 |
3/14/18, 12:00 AM | 3/14/18, 12:00 PM | |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 2 |
3/10/15, 12:00 AM | 4/1/15, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/28/19 |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 2 |
1/11/15, 12:00 AM | 2/19/15, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/28/19 |
RS01SBPS-PC01A-4A-CTDPFA103 |
Annotation IDs 1243, 1245, 1254, 1261, and 1284 should be updated to indicate the causes of the data gaps. By Lori Garzio, on 3/28/19 |
||
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 2 |
12/16/14, 12:00 AM | 1/2/15, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/26/19 |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 3 |
10/9/15, 12:00 AM | 10/11/15, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/28/19 |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 3 |
9/20/15, 12:00 AM | 9/21/15, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/27/19 |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 3 |
7/30/15, 12:00 AM | 8/5/15, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/28/19 |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 3 |
6/30/15, 12:00 AM | 7/4/15, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/28/19 |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 3 |
5/23/15, 12:00 AM | 5/25/15, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/27/19 |
CE09OSSM-MFD37-03-CTDBPE000 Deployment: 4 |
9/21/16, 1:26 AM | 10/17/16, 12:00 AM |
According to asset management, this instrument was deployed at 542 m. The pressure at the beginning of the deployment is around 560 dbar, then jumps up to around 547 dbar (closer to the planned deployment depth). This requires investigation and an annotation - excluding the data from the beginning of the deployment from summary data ranges. By Lori Garzio, on 3/28/19 |
CE09OSSM-MFD37-03-CTDBPE000 Deployment: 1 |
8/28/15, 12:00 AM | 9/25/15, 5:45 PM | |
CE09OSSM-MFD37-03-CTDBPE000 Deployment: 7 |
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. The recovered_inst data will hopefully fill in the missing data at the end of the deployment (seen in the recovered_host data) By Lori Garzio, on 3/27/19 |
||
CE09OSSM-MFD37-03-CTDBPE000 Deployment: 2 |
There are no data from any delivery method available for deployment 2. This should be annotated in the system (according to the ingest csv, the instrument failed at deployment). By Lori Garzio, on 3/27/19 |
||
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 4 |
4/10/16, 12:00 AM | 4/28/16, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/27/19 |
CE09OSPM-WFP01-02-DOFSTK000 Deployment: 4 |
11/3/15, 12:00 AM | 11/5/15, 12:00 AM |
suspect data profiles By Leila Belabbassi, on 3/27/19 |