Seawater pH

Reference Designator
GP03FLMB-RIS01-04-PHSENF000
Start Depth
30
End Depth
30
Location
Sensor cage
Current Status
Review Complete
Class
PHSEN (Seawater pH)
Series
PHSEN-F
Science Discipline
Chemical
Make
Sunburst
Model
SAMI-pH
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/GP03FLMB/RIS01/04-PHSENF000/metadata
Method Data Stream Content Type
recovered_host phsen_abcdef_imodem_control_recovered Control Data Report M2M Engineering
recovered_host phsen_abcdef_imodem_instrument_recovered Data Products Report M2M Stats Science
recovered_host phsen_abcdef_imodem_metadata_recovered Metadata Report M2M Engineering
recovered_inst phsen_abcdef_instrument Data Products Report M2M Stats Science
recovered_inst phsen_abcdef_metadata Metadata Report M2M Engineering
telemetered phsen_abcdef_sio_mule_instrument Data Products Report M2M Stats Science
telemetered phsen_abcdef_sio_mule_metadata Metadata Report M2M Engineering
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 Review MV-1309 07/24/2013 06/18/2014 CGMGP-03FLMB-00001 CGINS-PHSENF-P0081 50.3317 -144.401 30 4145
2 Review MV-1404 06/20/2014 06/07/2015 CGMGP-03FLMB-00002 CGINS-PHSENF-P0102 50.3313 -144.398 31 4145
3 Review TN-323 06/08/2015 07/03/2016 CGMGP-03FLMB-00003 CGINS-PHSENF-P0105 50.3303 -144.398 47 4145
4 Review RB-16-05 07/04/2016 07/17/2017 CGMGP-03FLMB-00004 CGINS-PHSENF-P0143 50.3293 -144.398 4146
5 Review SR17-10 07/14/2017 07/25/2018 CGMGP-03FLMB-00005 CGINS-PHSENF-P0105 50.3777 -144.515 4169
6 Review SR1811 07/24/2018 09/27/2019 CGMGP-03FLMB-00006 CGINS-PHSENF-P0079 50.3295 -144.398 4145
7 Review SKQ201920S 09/27/2019 CGMGP-03FLMB-00007 CGINS-PHSENF-P0147 50.3755 -144.514 4176
Metadata Start Date End Date Comment
GP03FLMB-RIS01-04-PHSENF000

pressure coordinate are missing in the data files

By Leila Belabbassi, on 5/30/19

GP03FLMB-RIS01-04-PHSENF000
7/24/13, 12:00 AM 6/18/14, 12:00 AM

suspect data

By Leila Belabbassi, on 5/30/19

GP03FLMB-RIS01-04-PHSENF000
9/25/15, 12:00 AM 10/25/15, 12:00 AM

suspect data

By Leila Belabbassi, on 5/30/19

GP03FLMB
7/4/16, 11:07 PM 7/25/18, 5:11 PM

Deployments 4 and 5 don't have deployment depths defined in asset management.

By Lori Garzio, on 1/3/19

GP03FLMB-RIS01-04-PHSENF000
7/14/16, 12:00 AM 8/5/18, 12:00 AM

suspect data

By Leila Belabbassi, on 5/30/19

GP03FLMB-RIS01-04-PHSENF000
Deployment: 4

recovered data are missing in the system

By Leila Belabbassi, on 5/30/19

GP03FLMB-RIS01-04-PHSENF000
Deployment: 4
7/4/16, 12:00 AM 7/1/17, 12:00 AM

Deployment 4 - instrument not telemetering data. Issue under investigation. UPDATE 11/15/2016: Either this instrument is having issues, or the entire secondary controller is malfunction. There are multiple low battery warnings that appear to originate from the SSIOC. The issue is under investigation.

By Lori Garzio, on 8/1/16
Redmine Issue #10853

GP03FLMB
Deployment: 5

Annotation ID 1531: recovered_host data are not available for download (Redmine 13628). Issue should be addressed and annotation needs be updated.

By Lori Garzio, on 1/10/19

GP03FLMB
Deployment: 5
7/14/17, 10:49 PM 7/25/18, 5:11 PM

The mooring was deployed 9 - 10 km from the location of the previous 4 deployments of this mooring. If this location is correct, the platform should be annotated to inform the users as to why the deployment location changed.

By Lori Garzio, on 1/4/19

New Note

Metadata Start Date End Date Comment
GP03FLMB
7/24/13, 2:32 AM 6/17/14, 8:00 PM

Deployment 1: Mooring was deployed 5-10m shallower than planned.

Id: 154 By: lgarzio

GP03FLMB
6/19/14, 10:00 PM 6/6/15, 8:00 PM

Deployment 2: Mooring was deployed 10-15m shallower than planned. Upon recovery of platform, biofouling was apparent on shallow CTDs.

Id: 155 By: lgarzio

GP03FLMB
6/8/15, 5:25 PM 7/3/16, 2:35 PM

Deployment 3: Mooring was deployed 10m deeper than planned.

Id: 156 By: lgarzio

GP03FLMB
7/4/16, 7:07 PM 7/17/17, 11:02 AM

Deployment 4: Mooring was deployed 10m deeper than planned.

Id: 157 By: lgarzio

GP03FLMB-RIS01-04-PHSENF000
7/14/17, 6:49 PM 7/25/18, 1:11 PM

Deployment 5: it was discovered upon recovery that the secondary controller did not log any data for this instrument between 2017-09-24 and 2017-12-07 or after 2017-12-31. No recovered host data are available after this date. Due to the fact that gliders were not deployed at Papa this year no telemetered data are available for the deployment. Recovered instrument data are available for the entire deployment.

Id: 2178 By: cdobson
Flag: not_operational Exclude: No

GP03FLMB
7/14/17, 6:49 PM 7/25/18, 1:11 PM

Deployment 5: Telemetered data are not available for this deployment because gliders were not deployed.

Id: 142 By: lgarzio

GP03FLMB-RIS01-04-PHSENF000
Method: telemetered
7/24/18, 7:01 PM 9/27/19, 7:55 PM

Deployment 6: There will be no telemetered data from this instrument due to issues between the instrument and controller. The instrument is logging internally and data should be available at recovery.

Id: 1498 By: cdobson