<div><p>Data were collected using a Brooke-Ocean Technology Laser Optical Plankton Counter model LOPC-660. Instrument was deployed in individual, vertical casts < 200m in depth. The LOPC was calibrated prior to deployment; however, the data have not been examined in depth for quality control or assurance.</p>
<p>Data have not been analyzed beyond the initial collection.</p>
<p>Samples were taken in two locations:<br />
near the Macondo-1 well site: 28.736669 N, 88.387161 W<br />
offshore location bounded by 27.377-28.866667 N and 90.57366667-88.06766667 W</p></div>
Laser Optical Plankton Counter
<div><p>Data consist of particle counts and sizes measured using a Brooke Ocean Technology Laser Optical Plankton Counter (LOPC) and were collected from vertical casts of up to 200 m in depth.<br />
<br /><strong>Parameter names, definitions and units:</strong><br />
The following information is from the LOPC Software Operation Manual (see related files and references). The LOPC data files are written as binary files and converted to ASCII during a minimal processing step. Each file contains a set of header information:<br />
<br /><strong>Header 1:</strong> PC DATE-TIME: contains Date and Time as recorded from the logging computer.<br />
<br /><strong>Header 2:</strong> USER SUPPLIED HEADER: contains any information provided by the user about the data<br />
<br /><strong>Header 3:</strong> LOPC SOFTWARE CONFIG: contains information about how the LOPC hardware was configured.<br />
<br /><strong>Header 4:</strong> LOPC FIRMWARE CONFIG: contains information about how the LOPC software was configured.<br />
<br />
Following the header information, the data stream begins as single lines of information, the file format description is as follows:<br />
<br /><strong>L1-L4:</strong> these four lines contain the 128 bins (32 bins per line) of single element plankton counted during this half-second sample.<br />
L1 0 0 0 0 0 0 6 8 8 7 4 2 3 2 2 7 3 4 5 6 5 3 3 2 1 2 5 7 8 0 0 4<br />
L2 3 2 0 3 0 1 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0<br />
L3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0<br />
L4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0</p>
<p><strong>L5</strong>: system status/engineering data<br />
L5 0 100 31 7 116 0 2550 0 0 2247<br />
Description of the L5 line from the sample above (from left to right)<br />
0 = Snapshot number<br />
100 = Threshold<br />
31 = Sample Number<br />
7 = Flow Counts<br />
116 = Delta Time<br />
0 = Buffer Overrun<br />
2550 = Laser Monitor (LMon in A/D counts)<br />
0 = Electronic Counts<br />
0 = Count Period<br />
2247 = Laser Voltage (LVolt in A/D counts)</p>
<p><strong>C</strong>: indicates a line of instrument data from any attached serial instruments. The rate at which this is transmitted by the LOPC, the data it contains, and the data string format is determined by the instrument in use. Typically, this represents a stream of CTD data.<br />
C +20.06602 2.35579 -0.056 0.2600 3.8046</p>
<p>This example shows the output from a CTD.<br /><strong>M</strong>: indicates a portion of Multi-Element Plankton (MEP) data, where the form is ‘M Element-Number Scan-Number Scan-Length Peak-Laser Monitor. The MEP data is sent whenever the opportunity is available. Both the binned data (<strong>L1-L5</strong> lines) and the Instrument data (<strong>C</strong> lines) take precedence over MEP data.<br />
M 26 20845 1 32869<br />
M 25 20826 30 291<br />
M 24 20831 21 186<br />
M 4 23768 7 33251<br />
M 3 23760 23 1403<br />
M 2 23761 22 1092</p>
<p><strong>Description of file fields:</strong><br /><strong>Snapshot Indicator:</strong> This value indicates whether a snapshot is in progress. A 1 indicates a snapshot is in progress, 0 indicates no snapshot is in progress [Found on L5 lines – position 1]</p>
<p><strong>Threshold:</strong> The threshold is used to set a lower limit on signal level detection, which ensures that the LOPC is operating above the “noise level” of internal active components. This improves the accuracy and reliability of detection data. [Found on L5 lines – position 2]</p>
<p><strong>Sample Number:</strong> A counter indicating number of samples taken by the LOPC at 2 Hz [Found on L5 lines – position 3]</p>
<p><strong>Flow Counts:</strong> The Flow Counts indicate the number of counts within a pre-determined size range within current 0.5-second sample (can be used in combination with Delta Time for flow calculations) [Found on L5 lines – position 4]</p>
<p><strong>Delta Time:</strong> Delta Time is the accumulated time for all counts detected in the Flow Counts window to pass through the beam (can be used in combination with Flow Counts for flow calculations) [Found on L5 lines – position 5]</p>
<p><strong>Buffer Overrun:</strong>Used to indicate an internal buffer overrun. ”1” if a buffer overrun occurs, “0” otherwise [Found on L5 lines – position 6]</p>
<p><strong>Laser Monitor (LMon):</strong> Laser Monitor is the mean laser intensity detected by all 35 elements of the photo-diode array during this 0.5-second sample [Found on L5 lines – position 7]</p>
<p><strong>Laser Voltage (LVolt):</strong> Laser Voltage is the input voltage to the laser. This value is a monitor of a laser control circuit that will increase or decrease the laser input voltage as required to maintain a preset level (LMon) [Found on L5 lines – position 10]</p>
<p><strong>Element-Number:</strong> Indicates the element within the 35-element photo-diode array to which this line of MEP data pertains [Found on M lines – position 1]</p>
<p><strong>Scan-Number:</strong> The Scan-Number is read from a 16-bit internal counter (0-65535) that is incremented every 35 µs to provide a measure of time. The Scan-Number indicates the “time” at which the MEP entered the beam for this element [Found on M lines – position 2]</p>
<p><strong>Scan-Length:</strong> Scan-Length indicates the number of scans, or the “length of time,” a portion of a MEP was detected on the element of question [Found on M lines – position 3]</p>
<p><strong>Peak Laser Level:</strong> The maximum level of laser light detected on this element during passage of a MEP [Found on M lines – position 4]</p>
<p>
<strong>Related files and references:</strong><br />
Laser Optical Plankton Counter Operation and Maintenance Manual. 2010. Brooke Ocean Technology <strong>(<a href="http://www.brooke-ocean.com/">www.brooke-ocean.com</a>).</strong></p>
<p>Herman AW. LOPC post-processing page: <a href="http://www.alexherman.com/lopc_post.php"><strong>http://www.alexherman.com/lopc_post.php.</strong></a> Contains software designed to enable first-time users of the LOPC to process data.</p>
<p>Herman AW, M Harvey. 2006. Application of normalized biomass size spectra to laser optical plankton counter net intercomparisons of zooplankton distributions. Journal of Geophysical Research-Oceans. 111(C5): C05S05.</p>
<p>Herman AW, B Beanlands, EF Phillips. 2004. The next generation of Optical Plankton Counter: the Laser-OPC. Journal of Plankton Research. 26(10): 1135-1145.</p></div>
Laser Optical Plankton Counter
<div><p>The data have been processed only by converting the original binary data into an ASCII format.<br />
Otherwise the data have not been processed.<br />
<br /><strong>PI Note:</strong><br />
These date are processed enough so that people can follow the instructions to further analysis listed in the metadata.<br />
Any further processing would be specific to any users direction questions.<br />
<br /><strong>BCO-DMO Processing Notes</strong><br />
Generated from original text file "LOPC_Locations.txt" contributed by David Kimmel</p>
<p><strong>BCO-DMO Edits</strong><br />
- Date reformatted to YYYYMMDD<br />
- Time reformatted to HHMM<br />
- Longitude values signed negative for West Longitude<br />
- "nd" (no data) value inserted in blank cells<br />
- Parameter names modified to conform to BCO-DMO convention</p></div>
3540
Laser Optical Plankton Counter
2011-09-15T08:23:08-04:00
2011-09-15T08:23:08-04:00
2023-07-07T16:10:26-04:00
urn:bcodmo:dataset:3540
Laser Optical Plankton Counter from R/V Oceanus cruise OC468-02 in the Gulf of Mexico in 2010 (GoMX - Hypoxia and Oil Effects project)
false
Kimmel, D. G., Roman, M. R., Boicourt, W. C., Pierson, J. J., Brandt, S. E. (2011) Laser Optical Plankton Counter from R/V Oceanus cruise OC468-02 in the Gulf of Mexico in 2010 (GoMX - Hypoxia and Oil Effects project). Biological and Chemical Oceanography Data Management Office (BCO-DMO). (Version 16 September 2011) Version Date 2011-09-16 [if applicable, indicate subset used]. http://lod.bco-dmo.org/id/dataset/3540 [access date]
false
16 September 2011
false
2011-09-16
HTML
https://www.bco-dmo.org/dataset/3540
text/html
Datapackage.json
Frictionless Data Package
https://www.bco-dmo.org/dataset/3540/datapackage.json
application/vnd.datapackage+json
PDF
https://www.bco-dmo.org/dataset/3540/Dataset_description.pdf
application/pdf
JSON-LD
https://www.bco-dmo.org/dataset/3540.json
application/ld+json
Turtle
https://www.bco-dmo.org/dataset/3540.ttl
text/turtle
RDF/XML
https://www.bco-dmo.org/dataset/3540.rdf
application/rdf+xml
ISO 19115-2 (NOAA Profile)
https://www.bco-dmo.org/dataset/3540/iso
application/xml
http://www.isotc211.org/2005/gmd-noaa
Dublin Core
https://www.bco-dmo.org/dataset/3540/dublin-core
application/xml
http://purl.org/dc/elements/1.1/
3540
http://lod.bco-dmo.org/id/dataset/3540
<http://www.opengis.net/def/crs/OGC/1.3/CRS84> POLYGON ((-90.5736667 27.377, -88.0676667 27.377, -88.0676667 28.8666667, -90.5736667 28.8666667, -90.5736667 27.377))
JGOFS
http://www.opengis.net/def/crs/OGC/1.3/CRS84
-90.5736667
27.377
-88.0676667
28.8666667
28.121833349999
-89.320666699998