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 |
||
GS03FLMB-RIM01-02-CTDMOG068 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-10T17:57: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 |
||
GS03FLMB-RIM01-02-CTDMOH069 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-10T17:57: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 |
||
GS03FLMB-RIM01-02-CTDMOH070 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-10T17:57: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 |
||
GS03FLMB-RIM01-02-CTDMOH071 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-10T17:57: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-CTDMOG045 Deployment: 2 |
3/8/16, 12:00 PM | 3/9/16, 12:00 PM |
Conductivity (and salinity and density) dropped suddenly for several hours, then quickly returned to reasonable values. Excluding data from final statistics. By Lori Garzio, on 1/23/19 |
GS03FLMA-RIM01-02-CTDMOG047 Deployment: 1 |
5/12/15, 12:00 PM | 5/13/15, 12:00 PM |
Conductivity (and salinity and density) dropped suddenly for several hours, then quickly returned to reasonable values. Excluding data from final statistics. By Lori Garzio, on 1/23/19 |
GS03FLMA-RIM01-02-CTDMOG047 Deployment: 1 |
5/16/15, 6:00 PM | 5/18/15, 12:00 AM |
Conductivity (and salinity and density) dropped suddenly for several hours, then quickly returned to reasonable values. Excluding data from final statistics. By Lori Garzio, on 1/23/19 |
GS03FLMB-RIM01-02-CTDMOG066 Deployment: 2 |
12/25/15, 12:00 AM | 1/20/16, 12:00 AM |
Conductivity (and salinity and density) dropped suddenly for several days, then returned to reasonable values. This should be investigated. Excluding data from final statistics. By Lori Garzio, on 1/29/19 |
GS03FLMB-RIM01-02-CTDMOG066 Deployment: 2 |
2/23/16, 12:00 PM | 2/27/16, 12:00 PM |
Conductivity (and salinity and density) dropped suddenly for several days, then returned to reasonable values. Excluding data from final statistics. By Lori Garzio, on 1/29/19 |
GS03FLMB-RIM01-02-CTDMOG067 Deployment: 2 |
2/23/16, 12:00 PM | 2/25/16, 12:00 PM |
Conductivity (and salinity and density) dropped suddenly, then quickly returned to reasonable values. Excluding data from final statistics. By Lori Garzio, on 1/29/19 |
GA01SUMO-RII11-02-CTDMOQ014 Deployment: 3 |
10/27/16, 1:47 AM | 1/14/18, 10:24 AM |
Density and salinity gradually drifted higher towards the end of the deployment. A similar pattern isn't observed in surrounding CTDs and annotation ID 391 says that the temperature probe was bent. It's unclear when the issue started, so excluding the entire deployment from the final stats. By Lori Garzio, on 1/29/19 |
GA01SUMO-RII11-02-CTDMOQ014 Deployment: 2 |
Annotation ID 666 should be updated to indicate which sensor was bent. By Lori Garzio, on 1/30/19 |
||
GA01SUMO-RII11-02-CTDMOQ014 Deployment: 3 |
12/31/17, 10:52 PM | 1/1/18, 1:00 AM | |
GA01SUMO-RII11-02-CTDMOQ015 Deployment: 2 |
1/30/16, 12:00 AM | 2/1/16, 12:00 AM |
Salinity and density dropped suddenly, then returned to reasonable values. UPDATE: This appears to be a real event as it was captured by other CTDs on this mooring (GA01SUMO-RII11-02-CTDBPP031, 32, and 33) By Lori Garzio, on 1/31/19 |
GA01SUMO-RII11-02-CTDMOQ031 Deployment: 1 |
Suggestion: add an annotation to explain why this reference designator only has 1 deployment. By Lori Garzio, on 1/31/19 |
||
GA01SUMO-RII11-02-CTDMOQ033 Deployment: 1 |
Suggestion: add an annotation to explain why this reference designator only has 1 deployment. By Lori Garzio, on 1/31/19 |
||
GI01SUMO-RII11-02-CTDMOQ031 Deployment: 1 |
Suggestion: add an annotation to explain why this reference designator only has 1 deployment. By Lori Garzio, on 1/31/19 |
||
GI01SUMO-RII11-02-CTDMOQ033 Deployment: 1 |
Suggestion: add an annotation to explain why this reference designator only has 1 deployment. By Lori Garzio, on 1/31/19 |
||
GS01SUMO-RII11-02-CTDMOQ031 Deployment: 1 |
Suggestion: add an annotation to explain why this reference designator only has 1 deployment. By Lori Garzio, on 1/31/19 |