2-Wavelength Fluorometer

Reference Designator
GP05MOAS-GL276-01-FLORDM000
Start Depth
0
End Depth
1,000
Location
Current Status
Review Complete
Class
FLORD (2-Wavelength Fluorometer)
Series
FLORD-M
Science Discipline
Biological
Make
WET Labs
Model
ECO Puck FLBB-SLC
M2M Example
https://ooinet.oceanobservatories.org/api/m2m/12576/sensor/inv/GP05MOAS/GL276/01-FLORDM000/metadata
Method Data Stream Content Type
recovered_host flort_m_sample Data Products Report M2M Stats Science
telemetered flort_m_sample Data Products Report M2M Stats Science
Deployment Cruise Start Date Stop Date Mooring Asset Node Asset Sensor Asset Latitude Longitude Deployment Depth Water Depth
1 Review MV-1404 06/15/2014 06/02/2015 CGVGP-05MOAS-00000 CGVEH-GLDROO-00276 CGINS-FLORTM-03260 49.9965 -144.255 1000 1000
2 Review SR1811 07/23/2018 02/12/2019 CGVGP-05MOAS-00000 CGVEH-GLDROO-00276 CGINS-FLORTM-03260 50.1295 -144.542 1000 1000
Metadata Start Date End Date Comment
GP05MOAS

Glider optodes typically exhibit a sensor lag of 20-25 seconds. Example attached of several segments with consecutive down and up casts for CP05MOAS-GL335-04-DOSTAM000 on 10/26/2015 showing a typical measurement time lag. Profiles should be analyzed for individual time lags and data should be adjusted. OOI doesn't necessarily need to make the adjustment but users should be aware of the issue.

By Lori Garzio, on 5/31/19

GP05MOAS-GL276-01-FLORDM000

Deployments 1 and 2: Data streams for this instrument will not match what we have in the database!! A FLORT was deployed (not a FLORD). The data had to be ingested using the FLORTM driver/parser, meaning the data streams are flort_sample.

By Lori Garzio, on 8/20/18
Redmine Issue #13507

GP05MOAS-GL276
Deployment: 1

I downloaded data for this glider for automated analysis on March 3, 2020. There are a substantial amount of gaps in the CTD, DOSTA, and FLORD data that were not there when I had previously downloaded the data on Apr 12, 2019. There are now 103 days of missing CTD data, 91 days of missing DOSTA data, and 59 days of missing FLORD data that were available on Apr 12, 2019. See Redmine ticket 14654 for details.

By Lori Garzio, on 3/13/20

New Note

Metadata Start Date End Date Comment
GP05MOAS-GL276
6/15/14, 1:30 AM 6/1/15, 8:00 PM

Deployment 1: Deployed on 6/15/2014, recovered on 6/18/2014 for ballast correction and re-deployed at 07:36 UTC.

Id: 590 By: lgarzio

GP05MOAS-GL276-01-FLORDM000
6/15/14, 1:30 AM 6/1/15, 8:00 PM

Deployment 1: A 3-wavelength fluorometer (instrument series FLORTM) was deployed in place of the customary 2-wavelength fluorometer (instrument series FLORDM) for global gliders.

Id: 1476 By: lgarzio

GP05MOAS-GL276-01-FLORDM000
7/23/18, 2:35 AM 7/31/18, 4:00 PM

Deployment 2: At the beginning of the deployment, the glider didn't send any valid fluorometer data. Issue was resolved and fluorometer data should be available for the remainder of the deployment.

Id: 1475 By: lgarzio

GP05MOAS-GL276-01-FLORDM000
7/23/18, 2:35 AM

Deployment 2: A 3-wavelength fluorometer (instrument series FLORTM) was deployed in place of the customary 2-wavelength fluorometer (instrument series FLORDM) for global gliders.

Id: 1477 By: lgarzio

GP05MOAS-GL276
1/27/19, 8:00 AM 2/12/19, 5:00 PM

Glider 276 was suspected to be showing early signs of battery failure so it was set adrift on 1/27/19 and successfully recovered on 2/12/19. No science data is expected after 1/27/19.

Id: 1561 By: cdobson