http://lod.bco-dmo.org/id/dataset/2395
eng; USA
utf8
dataset
Highest level of data collection, from a common set of sensors or instrumentation, usually within the same research project
Biological and Chemical Oceanography Data Management Office (BCO-DMO)
Unavailable
508-289-2009
WHOI MS#36
Woods Hole
MA
02543
USA
info@bco-dmo.org
http://www.bco-dmo.org
Monday - Friday 8:00am - 5:00pm
For questions regarding this resource, please contact BCO-DMO via the email address provided.
pointOfContact
2009-11-25
ISO 19115-2 Geographic Information - Metadata - Part 2: Extensions for Imagery and Gridded Data
ISO 19115-2:2009(E)
Broad-scale hydrography from CTDs deployed from 30 cruises on the R/V Albatross IV, R/V Endeavor, and R/V Oceanus in the Gulf of Maine and Georges Bank from 1995-1999 (GB project)
2004-11-19
publication
2004-11-19
revision
Marine Biological Laboratory/Woods Hole Oceanographic Institution Library (MBLWHOI DLA)
2020-01-29
publication
https://doi.org/10.1575/1912/bco-dmo.2395.2
Dr David Mountain
National Marine Fisheries Service
principalInvestigator
Biological and Chemical Oceanography Data Management Office (BCO-DMO)
Unavailable
508-289-2009
WHOI MS#36
Woods Hole
MA
02543
USA
info@bco-dmo.org
http://www.bco-dmo.org
Monday - Friday 8:00am - 5:00pm
For questions regarding this resource, please contact BCO-DMO via the email address provided.
publisher
Cite this dataset as: Mountain, D. (2004) Broad-scale hydrography from CTDs deployed from 30 cruises on the R/V Albatross IV, R/V Endeavor, and R/V Oceanus in the Gulf of Maine and Georges Bank from 1995-1999 (GB project). Biological and Chemical Oceanography Data Management Office (BCO-DMO). (Version 2) Version Date 2004-11-19 [if applicable, indicate subset used]. doi:10.1575/1912/bco-dmo.2395.2 [access date]
Georges Bank Broad-scale hydrography, 1995 - 1999 Dataset Description: <h2>Broad-scale Hydrography, 1995 - 1999</h2>
<p><strong>If you encounter any questionable values or have other questions, contact:</strong> David Mountain National Marine Fisheries Servce, NEFC Woods Hole, MA 02540 voice: 508 495 2000 fax: 508 495 2258 email: <a href="mailto:David.Mountain@noaa.gov">David.Mountain@noaa.gov</a></p>
<h2>File Descriptions:</h2>
<p>At level 1 in the comments field, the user has three options for selecting CTD profile data available from this cruise:</p>
<p>mark5CTD link - Links the user to the Neil Brown Mark-5 CTD profiles. The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations.</p>
<p>seabirdCTD link - Links the user to the SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. Users working with the plankton data may want to work with this data set exclusively.</p>
<p>primary link - Links the user to the best hydrography coverage available for the cruise. The "primary version", in most cases, is a composite of both the Mark-5 and SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).</p>
<p><em>Prepared by: Maureen Taylor, NMFS/Woods Hole, 2/7/1996<br />
last updated: 19 Nov. 2004; gfh </em></p> Methods and Sampling: <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations.</li>
<li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and</li>
<li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).</li>
</ul>
Funding provided by National Science Foundation (NSF) Award Number: unknown GB NSF
Funding provided by National Oceanic and Atmospheric Administration (NOAA) Award Number: unknown GB NOAA
completed
Dr David Mountain
National Marine Fisheries Service
508-495-2271
Woods Hole
MA
02543
USA
David.Mountain@noaa.gov
pointOfContact
asNeeded
Dataset Version: 2
Unknown
year
ship
cruiseid
si
eventno
site
comments
month_local
day_local
time_local
cast
station
station_std
depth_w
lon
lat
yrday_gmt
yrday_local
press
temp
sal
flvolt
light_tran_v
numb_obs
object
object_year
par_scalar_v
Mark 5 CTD
SeabirdCTD
Sea-Bird Seacat CTD
theme
None, User defined
year
ship
cruise id
investigator
event
brief description
comments
month_local
day_local
time_local
cast
station
station_std
depth_w
longitude
latitude
day of year and decimal time (time zone GMT)
day of year and decimal time (local time zone)
water pressure
water temperature at measurement depth
salinity
flvolt
light transmission (volts)
numb_obs
No BCO-DMO term
par_scalar_v
featureType
BCO-DMO Standard Parameters
CTD Neil Brown Mark 5
CTD Sea-Bird
CTD Sea-Bird SEACAT
instrument
BCO-DMO Standard Instruments
AL9505
AL9506
AL9508
EN261
EN263
EN265
AL9605
AL9607
EN276
EN278
EN282
OC275
AL9701
AL9705
AL9707
OC298
OC300
OC302
AL9801
AL9806
AL9808
OC317
OC319
OC322
AL9901
AL9904
AL9906
EN320
OC336
OC341
service
Deployment Activity
Gulf of Maine and Georges Bank
place
Locations
otherRestrictions
otherRestrictions
Access Constraints: none. Use Constraints: Please follow guidelines at: http://www.bco-dmo.org/terms-use Distribution liability: Under no circumstances shall BCO-DMO be liable for any direct, incidental, special, consequential, indirect, or punitive damages that result from the use of, or the inability to use, the materials in this data submission. If you are dissatisfied with any materials in this data submission your sole and exclusive remedy is to discontinue use.
U.S. GLOBal ocean ECosystems dynamics
http://www.usglobec.org/
U.S. GLOBal ocean ECosystems dynamics
U.S. GLOBEC (GLOBal ocean ECosystems dynamics) is a research program organized by oceanographers and fisheries scientists to address the question of how global climate change may affect the abundance and production of animals in the sea.
The U.S. GLOBEC Program currently had major research efforts underway in the Georges Bank / Northwest Atlantic Region, and the Northeast Pacific (with components in the California Current and in the Coastal Gulf of Alaska). U.S. GLOBEC was a major contributor to International GLOBEC efforts in the Southern Ocean and Western Antarctic Peninsula (WAP).
U.S. GLOBEC
largerWorkCitation
program
U.S. GLOBEC Georges Bank
http://globec.whoi.edu/globec_program.html
U.S. GLOBEC Georges Bank
<p>The U.S. GLOBEC <a href="http://globec.whoi.edu/globec-dir/about_georges_bank.html">Georges Bank</a> Program is a large multi- disciplinary multi-year oceanographic effort. The proximate goal is to understand the population dynamics of key species on the Bank - Cod, <a href="http://globec.whoi.edu/images/haddock103.07.gif">Haddock</a>, and two species of zooplankton (<a href="http://globec.whoi.edu/images/calanus-finmarchicus.html"><em>Calanus finmarchicus</em></a> and <a href="http://globec.whoi.edu/images/pseudocalanus.html"><em>Pseudocalanus</em></a>) - in terms of their coupling to the physical environment and in terms of their <a href="http://globec.whoi.edu/images/targetpp.gif">predators and prey</a>. The ultimate goal is to be able to predict changes in the distribution and abundance of these species as a result of changes in their physical and biotic environment as well as to anticipate how their populations might respond to climate change.</p>
<p>The effort is substantial, requiring broad-scale surveys of the entire Bank, and process studies which focus both on the links between the target species and their physical environment, and the determination of fundamental aspects of these species' life history (birth rates, growth rates, death rates, etc).</p>
<p>Equally important are the modelling efforts that are ongoing which seek to provide realistic predictions of the flow field and which utilize the life history information to produce an integrated view of the dynamics of the populations.</p>
<p>The U.S. GLOBEC Georges Bank <a href="http://globec.whoi.edu/globec-dir/EXCO.html">Executive Committee (EXCO)</a> provides program leadership and effective communication with the funding agencies.</p>
GB
largerWorkCitation
project
eng; USA
oceans
Gulf of Maine and Georges Bank
-69.268
-65.647
40.285
42.343
1995-05-09
1999-06-23
Georges Bank, Gulf of Maine, Northwest Atlantic Ocean
0
BCO-DMO catalogue of parameters from Broad-scale hydrography from CTDs deployed from 30 cruises on the R/V Albatross IV, R/V Endeavor, and R/V Oceanus in the Gulf of Maine and Georges Bank from 1995-1999 (GB project)
Biological and Chemical Oceanography Data Management Office (BCO-DMO)
Unavailable
508-289-2009
WHOI MS#36
Woods Hole
MA
02543
USA
info@bco-dmo.org
http://www.bco-dmo.org
Monday - Friday 8:00am - 5:00pm
For questions regarding this resource, please contact BCO-DMO via the email address provided.
pointOfContact
http://lod.bco-dmo.org/id/dataset-parameter/8112.rdf
Name: year
Units: unknown
Description: <p>4-digit year (i.e. 1992)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8113.rdf
Name: ship
Units: unknown
Description: <p>ship name (i.e. Albatross)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8114.rdf
Name: cruiseid
Units: unknown
Description: <p>originator's cruise identification</p>
http://lod.bco-dmo.org/id/dataset-parameter/8115.rdf
Name: si
Units: unknown
Description: <p>name of scientist responsible for data</p>
http://lod.bco-dmo.org/id/dataset-parameter/8116.rdf
Name: eventno
Units: dimensionless
Description: <p>event number assigned to a suite of sampling events</p>
http://lod.bco-dmo.org/id/dataset-parameter/8117.rdf
Name: site
Units: unknown
Description: <p>designated site (Broadscale)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8118.rdf
Name: comments
Units: unknown
Description: <p>comments (free text)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8119.rdf
Name: month_local
Units: unknown
Description: <p>month of year, local time (as 01-12)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8120.rdf
Name: day_local
Units: unknown
Description: <p>day of month, local time (as 01-31)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8121.rdf
Name: time_local
Units: decimal min.
Description: <p>time of day, local time </p>
http://lod.bco-dmo.org/id/dataset-parameter/8122.rdf
Name: cast
Units: dimensionless
Description: <p>CTD cast number</p>
http://lod.bco-dmo.org/id/dataset-parameter/8123.rdf
Name: station
Units: dimensionless
Description: <p>station number, not always consecutive</p>
http://lod.bco-dmo.org/id/dataset-parameter/8124.rdf
Name: station_std
Units: unknown
Description: <p>standard station no., (Globec assigned)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8125.rdf
Name: depth_w
Units: meters
Description: <p>water depth</p>
http://lod.bco-dmo.org/id/dataset-parameter/8126.rdf
Name: lon
Units: decimal degrees
Description: <p>longitude, negative = west</p>
http://lod.bco-dmo.org/id/dataset-parameter/8127.rdf
Name: lat
Units: decimal degrees
Description: <p>latitude, negative = south</p>
http://lod.bco-dmo.org/id/dataset-parameter/8128.rdf
Name: yrday_gmt
Units: decimal
Description: <p>gmt yearday (Julian Calendar)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8129.rdf
Name: yrday_local
Units: decimal
Description: <p>local yearday (Julian Calendar)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8130.rdf
Name: press
Units: decibars
Description: <p>depth of sample reported as pressure</p>
http://lod.bco-dmo.org/id/dataset-parameter/8131.rdf
Name: temp
Units: deg. C ITS68
Description: <p>temperature, in 1996 NMFS CTD temps. switch to ITS90 scale</p>
http://lod.bco-dmo.org/id/dataset-parameter/8132.rdf
Name: sal
Units: PSU
Description: <p>salinity (CTD)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8133.rdf
Name: flvolt
Units: volts
Description: <p>fluorescence (mk5ctd only)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8134.rdf
Name: light_tran_v
Units: volts
Description: <p>light transmission (mk5ctd only)</p>
http://lod.bco-dmo.org/id/dataset-parameter/8135.rdf
Name: numb_obs
Units: unknown
Description: <p>number of observations per bin</p>
http://lod.bco-dmo.org/id/dataset-parameter/23109.rdf
Name: object
Units: unknown
Description: <p>name of the data object</p>
http://lod.bco-dmo.org/id/dataset-parameter/23110.rdf
Name: object_year
Units: unknown
Description: <p>a duplicate year variable with a different name</p>
http://lod.bco-dmo.org/id/dataset-parameter/788862.rdf
Name: par_scalar_v
Units: volts
Description: <p>photosynthetically available radiation, 400-700nm wave length, with scalar sensor response (PAR), reported in conjunction with a water depth</p>
GB/NERC/BODC > British Oceanographic Data Centre, Natural Environment Research Council, United Kingdom
Biological and Chemical Oceanography Data Management Office (BCO-DMO)
Unavailable
508-289-2009
WHOI MS#36
Woods Hole
MA
02543
USA
info@bco-dmo.org
http://www.bco-dmo.org
Monday - Friday 8:00am - 5:00pm
For questions regarding this resource, please contact BCO-DMO via the email address provided.
pointOfContact
77582181
https://darchive.mblwhoilibrary.org/bitstream/1912/25282/1/dataset-2395_ctdhydrography__v2.tsv
download
https://doi.org/10.1575/1912/bco-dmo.2395.2
download
onLine
dataset
<ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations.</li>
<li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and</li>
<li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).</li>
</ul>
from Cruise: AL9505 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9506 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9508 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: EN261 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: EN263 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: EN265 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9605 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9607 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: EN276 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: EN278 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: EN282 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: OC275 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9701 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9705 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9707 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: OC298 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: OC300 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: OC302 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9801 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9806 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9808 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: OC317 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: OC319 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: OC322 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9901 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: AL9904 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations.</li>
<li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and</li>
<li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).</li>
</ul>
from Cruise: AL9906 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: EN320 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: OC336 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
from Cruise: OC341 <ul>
<li>The Mark-5 profiler, has a higher sampling rate then the SeaBird SEACAT, was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations. <li>SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. The upcast portion of the tow is the most reliable and that is what is reported here. These profiles do not contain the parameters: light transmission, fluorescence, and scalar par. The primary version, in most cases, is a composite of both the Mark-5 and <li>SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. As a result, the reported cast and station numbers are frequently duplicated and random in order. When present, SeaBird profiles are identified with a one hundred series cast number to distinguish from a Mark-5 profile, however, this convention is inconsistent and does not always appear in all cruises (primary link only).
</ul>
Specified by the Principal Investigator(s)
<p><strong>Procedure for processing primary CTD data:</strong></p>
<p>The following is an outline of the methods used to process the "primary" CTD data from the 1995 Broad scale surveys.</p>
<ol>
<li>Upon completion of each broad scale cruise, preliminary processing of the MK5 data was carried out:
<ol>
<li><strong>"first differencing"</strong> (called from within CTDPOST) of the Raw cast files was completed. This program flags any data where the difference between sequential scans exceed some preset limit.</li>
<li><strong>"smart editor"</strong> used to interpolate over any flagged values from "first differencing"</li>
<li><strong>ENDCAST XXX</strong> (a dos batch routine where xxx=cast#) runs MK5PROC.EXE which creates pressure averaged, pressure centered 1 db files (.PRE files). These routines (pressure averaging and pressure centering) were developed by Bob Millard at WHOI and were modified for the Mk5. "ENDCAST" also updates a cruise header file, and backs up the data to floppy)</li>
<li><strong>CTDPLOT</strong> (visual basic program by David Mountain) was run at each station to plot out the cast profile and to visually inspect the data.</li>
<li><strong>MK5BOT.EXE</strong> This routine (again, developed by Bob Millard) extracts and averages 30 data scans around the data scan number (as identified in the cast .BTL file) at which bottles were fired during a cast and appends to a cruise bottle file. These files were reviewed after each cruise to ensure that each btl fired had a corresponding observation record in the btl file. If we forgot to record a btl fired (forgot to press [CTRL] F3), we used an observation from the .PRE files.</li>
</ol>
</li>
<li>Salinity samples (btm) collected on each cruise were analyzed on a guildline autosal
<ul>
<li><strong>tstslt.bas</strong> was used to compare the cruise btl file with the autosal output file</li>
<li><strong>mk5xxxx.m</strong> (where xxxx=4 digit cruise id) was used to calculate the mean conductivity offset</li>
</ul>
<ol>
<li>any single comparison that was greater than -0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were calculated</li>
<li>any single comparison that was greater than +/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to insure that a time dependant trend was not evident and that using a mean offset was appropriate.<br />
&nbsp;</li>
</ol>
</li>
<li>The mean conductivity offsets were applied to each cruise data set using <strong>MK5final.bas</strong>. <strong>MK5cru.fin</strong> was read in as input containing the necessary information for cruise id, directory, and most importantly conductivity offset. The output was pressure averaged, pressure centerred .PRS files.
<ul>
<li>During EN261 and ALB9506, seabird data was used to supplement for primary hydro data when there were problems with the MK5 (or winch). Seabird CTD data were processed to pressure averaged, 1 db files using the manufacturer's software <strong>DATCNV, ALIGNCTD, BINAVG, DERIVE,</strong> and <strong>ASCIIOUT</strong>. When Seabird data were used as "primary" data, the casts were numbered &gt;100. The same steps outlined in 2a)--2e) were followed in the quality controlling of the seabird salinity data except that the comparison was done with salinity (rather than conductivity). The seabird cast data have also been processed to NODC formatted files and are available in this format in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.<br />
&nbsp;</li>
</ul>
</li>
<li>Final data checking was accomplished with a matlab program called <strong>dchkXX.m</strong> (where xx is the cruise code) that did the following:
<ol>
<li>read in the cruise .h3 file (output of <strong>ENDCRUIS.FOR</strong>) and calculated the distance and time between consecutive casts and wrote the results to headchk.xx (where xx is the cruise code). Any speed that was &gt;= 10 knots was verified with the original cruise logs and if found in error, was corrected.</li>
<li>read in the cast files and went through a series of allowable "range checking" of T, S, Sigma-t, and fluorescence. Profiles of these 4 parameters are plotted to the screen for visual inspection.
<pre>
RANGES
0 &lt;--- T ---&gt; 25
30 &lt;--- S ---&gt; 37
0 &lt;--- Fl ---&gt; 5
-0.05 &lt;--- ST---&gt; 0.1
</pre>
The above flagged values were written out to <strong>datachk.xx</strong></li>
</ol>
</li>
</ol>
<p>** note: in most instances, the positive sigma-t differences were O.K. and occurred when stratification had developed or when the MK5 sampled through strong gradients like the shelf / slope front. However, there were cases of "hysteresis" (sp?) when the MK5 or seabird sampled through sharp t/s gradients. In these instances, I had to delete the records.</p>
<p>** On a number of occasions, there were negative fluorescence values for the sfc observation. (These were also observed in the raw data...A consultant with Sea-tech said that this is probably "noise" associated with its equilibrating when just powered up). For these casts, I looked in the raw data files, and chose a substitute fluorescence value.</p>
<p>The output listing of the flagged observations from "datachk.m" are kept on file (and can be made available). Any record deletions are noted.</p>
from Cruise: AL9505 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9506 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9508 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: EN261 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: EN263 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: EN265 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9605 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9607 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: EN276 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: EN278 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: EN282 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: OC275 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9701 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9705 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9707 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: OC298 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: OC300 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: OC302 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9801 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9806 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9808 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: OC317 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: OC319 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: OC322 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9901 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: AL9904 <p>The following is an outline of the methods used to process the "primary" CTD data from the 1995 Broad scale surveys.</p>
<ol>
<li>Upon completion of each broad scale cruise, preliminary processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of the Raw cast files was completed. This program flags any data where the difference between sequential scans exceed some preset limit.</li>
<p> </p>
<li><b>"smart editor"</b> used to interpolate over any flagged values from "first differencing"</li>
<p> </p>
<li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#) runs MK5PROC.EXE which creates pressure averaged, pressure centered 1 db files (.PRE files). These routines (pressure averaging and pressure centering) were developed by Bob Millard at WHOI and were modified for the Mk5. "ENDCAST" also updates a cruise header file, and backs up the data to floppy)</li>
<p> </p>
<li><b>CTDPLOT</b> (visual basic program by David Mountain) was run at each station to plot out the cast profile and to visually inspect the data.</li>
<p> </p>
<li><b>MK5BOT.EXE</b> This routine (again, developed by Bob Millard) extracts and averages 30 data scans around the data scan number (as identified in the cast .BTL file) at which bottles were fired during a cast and appends to a cruise bottle file. These files were reviewed after each cruise to ensure that each btl fired had a corresponding observation record in the btl file. If we forgot to record a btl fired (forgot to press [CTRL] F3), we used an observation from the .PRE files.</li>
<p> </p>
</ol>
</li>
<li>Salinity samples (btm) collected on each cruise were analyzed on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was used to calculate the mean conductivity offset</li>
</ul>
<p> </p>
<ol>
<li>any single comparison that was greater than -0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were calculated</li>
<li>any single comparison that was greater than +/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to insure that a time dependant trend was not evident and that using a mean offset was appropriate.</li>
<p> </p>
</ol>
<p> </p>
</li>
<li>The mean conductivity offsets were applied to each cruise data set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input containing the necessary information for cruise id, directory, and most importantly conductivity offset. The output was pressure averaged, pressure centerred .PRS files.
<p> </p>
<ul>
<li>During EN261 and ALB9506, seabird data was used to supplement for primary hydro data when there were problems with the MK5 (or winch). Seabird CTD data were processed to pressure averaged, 1 db files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG, DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary" data, the casts were numbered >100. The same steps outlined in 2a)--2e) were followed in the quality controlling of the seabird salinity data except that the comparison was done with salinity (rather than conductivity). The seabird cast data have also been processed to NODC formatted files and are available in this format in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul>
<p> </p>
</li>
<li>Final data checking was accomplished with a matlab program called <b>dchkXX.m</b> (where xx is the cruise code) that did the following:
<p> </p>
<ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and calculated the distance and time between consecutive casts and wrote the results to headchk.xx (where xx is the cruise code). Any speed that was >= 10 knots was verified with the original cruise logs and if found in error, was corrected.</li>
<p> </p>
<li>read in the cast files and went through a series of allowable "range checking" of T, S, Sigma-t, and fluorescence. Profiles of these 4 parameters are plotted to the screen for visual inspection.
<p> </p>
<pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b>
<p> </p>
</li>
</ol>
</li>
</ol>
<p>** note: in most instances, the positive sigma-t differences were O.K. and occurred when stratification had developed or when the MK5 sampled through strong gradients like the shelf / slope front. However, there were cases of "hysteresis" (sp?) when the MK5 or seabird sampled through sharp t/s gradients. In these instances, I had to delete the records.</p>
<p> </p>
<p>** On a number of occasions, there were negative fluorescence values for the sfc observation. (These were also observed in the raw data...A consultant with Sea-tech said that this is probably "noise" associated with its equilibrating when just powered up). For these casts, I looked in the raw data files, and chose a substitute fluorescence value.</p>
from Cruise: AL9906 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: EN320 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: OC336 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
from Cruise: OC341 The following is an outline of the methods used to process the
"primary" CTD data from the 1995 Broad scale surveys.
<ol>
<li>Upon completion of each broad scale cruise, preliminary
processing of the MK5 data was carried out:
<ol>
<li><b>"first differencing"</b> (called from within CTDPOST) of
the Raw cast files was completed. This program flags
any data where the difference between sequential
scans exceed some preset limit. </li> <p>
</p><li><b>"smart editor"</b> used to interpolate over any flagged
values from "first differencing"</li><p>
</p><li><b>ENDCAST XXX</b> (a dos batch routine where xxx=cast#)
runs MK5PROC.EXE which creates pressure averaged,
pressure centered 1 db files (.PRE files). These
routines (pressure averaging and pressure centering)
were developed by Bob Millard at WHOI and were
modified for the Mk5. "ENDCAST" also updates a
cruise header file, and backs up the data to floppy) </li><p>
</p><li><b>CTDPLOT</b> (visual basic program by David Mountain)
was run at each station to plot out the cast
profile and to visually inspect the data.</li><p>
</p><li><b>MK5BOT.EXE</b> This routine (again, developed by Bob
Millard) extracts and averages 30 data scans around
the data scan number (as identified in the cast .BTL
file) at which bottles were fired during a cast and
appends to a cruise bottle file. These files were
reviewed after each cruise to ensure that each btl
fired had a corresponding observation record in the
btl file. If we forgot to record a btl fired
(forgot to press [CTRL] F3), we used an observation
from the .PRE files.</li><p>
</p></ol>
</li><li>Salinity samples (btm) collected on each cruise were analyzed
on a guildline autosal
<ul>
<li><b>tstslt.bas</b> was used to compare the cruise btl
file with the autosal output file</li>
<li><b>mk5xxxx.m</b> (where xxxx=4 digit cruise id) was
used to calculate the mean conductivity offset</li>
</ul>
<p>
</p><ol>
<li>any single comparison that was greater than
-0.1 or +0.1 was ignored.</li>
<li>the mean offset and standard deviation (std) were
calculated</li>
<li>any single comparison that was greater than
+/- 2 std's was discarded as an outlier</li>
<li>the mean and std were re-calculated</li>
<li>The offset series for each cruise were inspected to
insure that a time dependant trend was not evident
and that using a mean offset was appropriate.</li><p>
</p></ol> <p>
</p></li><li>The mean conductivity offsets were applied to each cruise data
set using <b>MK5final.bas</b>. <b>MK5cru.fin</b> was read in as input
containing the necessary information for cruise id, directory,
and most importantly conductivity offset. The output was
pressure averaged, pressure centerred .PRS files.
<p></p><ul>
<li>During EN261 and ALB9506, seabird data was used to supplement
for primary hydro data when there were problems with the MK5 (or
winch). Seabird CTD data were processed to pressure averaged, 1 db
files using the manufacturer's software <b>DATCNV, ALIGNCTD, BINAVG,
DERIVE,</b> and <b>ASCIIOUT</b>. When Seabird data were used as "primary"
data, the casts were numbered >100. The same steps outlined in
2a)--2e) were followed in the quality controlling of the seabird
salinity data except that the comparison was done with salinity
(rather than conductivity). The seabird cast data have also been
processed to NODC formatted files and are available in this format
in a NEFSC anonymous ftp account ftp: ftp/pub/hydro.</li>
</ul><p>
</p></li><li>Final data checking was accomplished with a matlab program
called <b>dchkXX.m</b> (where xx is the cruise code) that did the
following:
<p>
</p><ol>
<li>read in the cruise .h3 file (output of <b>ENDCRUIS.FOR</b>) and
calculated the distance and time between consecutive casts
and wrote the results to headchk.xx (where xx is the cruise
code). Any speed that was >= 10 knots was verified
with the original cruise logs and if found in error,
was corrected.</li><p></p>
<li>read in the cast files and went through a series of
allowable "range checking" of T, S, Sigma-t, and
fluorescence. Profiles of these 4 parameters are plotted to
the screen for visual inspection.<p>
</p><pre>
RANGES
0 <--- T ---> 25
30 <--- S ---> 37
0 <--- Fl ---> 5
-0.05 <--- ST---> 0.1
</pre>
The above flagged values were written out to <b>datachk.xx</b> <p>
</p></li></ol></li>
</ol>
<p>
** note: in most instances, the positive sigma-t differences were
O.K. and occurred when stratification had developed or when the MK5
sampled through strong gradients like the shelf / slope front.
However, there were cases of "hysteresis" (sp?) when the MK5 or
seabird sampled through sharp t/s gradients. In these instances,
I had to delete the records.</p><p>
</p><p>
** On a number of occasions, there were negative fluorescence
values for the sfc observation. (These were also observed in the
raw data...A consultant with Sea-tech said that this is probably
"noise" associated with its equilibrating when just powered up).
For these casts, I looked in the raw data files, and chose a
substitute fluorescence value.</p>
Specified by the Principal Investigator(s)
asNeeded
7.x-1.1
Biological and Chemical Oceanography Data Management Office (BCO-DMO)
Unavailable
508-289-2009
WHOI MS#36
Woods Hole
MA
02543
USA
info@bco-dmo.org
http://www.bco-dmo.org
Monday - Friday 8:00am - 5:00pm
For questions regarding this resource, please contact BCO-DMO via the email address provided.
pointOfContact
Mark 5 CTD
Mark 5 CTD
PI Supplied Instrument Name: Mark 5 CTD PI Supplied Instrument Description:Mark 5 CTD. Instrument Name: CTD Neil Brown Mark 5 Instrument Short Name:CTD NBIS MK5 Instrument Description: The Neil Brown Instrument Systems Mark 5 CTD is used to measure conductivity, temperature, and depth of sea water. The MK5 profiler has a higher sampling rate then the SeaBird SEACAT. (For the GLOBEC Georges Bank project the Mark 5 was instrumented with an expanded suite of sensors and deployed almost exclusively at GLOBEC Standard stations.) Community Standard Description: http://vocab.nerc.ac.uk/collection/L05/current/130/
SeabirdCTD
SeabirdCTD
PI Supplied Instrument Name: SeabirdCTD PI Supplied Instrument Description:SeaBird SEACAT profiler deployed with the bongo plankton net tow system at Standard and Intermediate stations. Instrument Name: CTD Sea-Bird Instrument Short Name:CTD Sea-Bird Instrument Description: A Conductivity, Temperature, Depth (CTD) sensor package from SeaBird Electronics. This instrument designation is used when specific make and model are not known or when a more specific term is not available in the BCO-DMO vocabulary. Refer to the dataset-specific metadata for more information about the specific CTD used. More information from:Â http://www.seabird.com/ Community Standard Description: http://vocab.nerc.ac.uk/collection/L05/current/130/
Sea-Bird Seacat CTD
Sea-Bird Seacat CTD
PI Supplied Instrument Name: Sea-Bird Seacat CTD PI Supplied Instrument Description:CTD measurements taken by Seabird Seacat CTD instrument package..
The primary version, in most cases, is a composite of both the Mark-5 and SEACAT CTD casts. These casts have been extracted from their respective cruise files and sorted by time. Instrument Name: CTD Sea-Bird SEACAT Instrument Short Name:CTD SEACAT Instrument Description: The CTD SEACAT recorder is an instrument package manufactured by Sea-Bird Electronics. The first Sea-Bird SEACAT Recorder was the original SBE 16 SEACAT developed in 1987. There are several model numbers including the SBE 16plus (SEACAT C-T Recorder (P optional))and the SBE 19 (SBE 19plus SEACAT Profiler measures conductivity, temperature, and pressure (depth)). More information from Sea-Bird Electronics. Community Standard Description: http://vocab.nerc.ac.uk/collection/L05/current/350/
Cruise: AL9505
AL9505
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9505
Dr David Mountain
Northeast Fisheries Science Center - Woods Hole
http://globec.whoi.edu/globec-dir/reports/al9505/al9505rot.pdf
Report describing AL9505
Cruise: AL9506
AL9506
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9506
Ann Bucklin
University of New Hampshire
http://globec.whoi.edu/globec-dir/reports/al9506/al9506new.html
Report describing AL9506
Cruise: AL9508
AL9508
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9508
Peter H. Wiebe
Woods Hole Oceanographic Institution
http://globec.whoi.edu/globec-dir/reports/al9508/a9508rp2.HTM
Report describing AL9508
Cruise: EN261
EN261
R/V Endeavor
Community Standard Description
International Council for the Exploration of the Sea
R/V Endeavor
vessel
EN261
Peter H. Wiebe
Woods Hole Oceanographic Institution
Cruise: EN263
EN263
R/V Endeavor
Community Standard Description
International Council for the Exploration of the Sea
R/V Endeavor
vessel
EN263
Dr Charles B. Miller
Oregon State University
http://globec.whoi.edu/globec-dir/reports/en263/EN263.pdf
Report describing EN263
Cruise: EN265
EN265
R/V Endeavor
Community Standard Description
International Council for the Exploration of the Sea
R/V Endeavor
vessel
EN265
Dr John Sibunka
Northeast Fisheries Science Center - Sandy Hook
Cruise: AL9605
AL9605
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9605
Dr John Green
Northeast Fisheries Science Center - Narragansett
http://globec.whoi.edu/globec-dir/reports/al9605/al9605.html
Report describing AL9605
Cruise: AL9607
AL9607
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9607
Dr David Mountain
Northeast Fisheries Science Center - Woods Hole
http://globec.whoi.edu/globec-dir/reports/al9607/AL9607.pdf
Report describing AL9607
Cruise: EN276
EN276
R/V Endeavor
Community Standard Description
International Council for the Exploration of the Sea
R/V Endeavor
vessel
EN276
Dr Charles B. Miller
Oregon State University
http://globec.whoi.edu/globec-dir/reports/en276/EN276.pdf
Report describing EN276
Cruise: EN278
EN278
R/V Endeavor
Community Standard Description
International Council for the Exploration of the Sea
R/V Endeavor
vessel
EN278
Dr Peter Garrahan
University of Rhode Island
Cruise: EN282
EN282
R/V Endeavor
Community Standard Description
International Council for the Exploration of the Sea
R/V Endeavor
vessel
EN282
Dr John Sibunka
Northeast Fisheries Science Center - Sandy Hook
Cruise: OC275
OC275
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel
OC275
Peter H. Wiebe
Woods Hole Oceanographic Institution
Cruise: AL9701
AL9701
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9701
Dr John Sibunka
Northeast Fisheries Science Center - Sandy Hook
http://globec.whoi.edu/globec-dir/reports/al9701/cral9701.htm
Report describing AL9701
Cruise: AL9705
AL9705
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9705
Dr David Mountain
Northeast Fisheries Science Center - Woods Hole
http://globec.whoi.edu/globec-dir/reports/al9705/al9705.html
Report describing AL9705
Cruise: AL9707
AL9707
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9707
Dr John Green
Northeast Fisheries Science Center - Narragansett
http://globec.whoi.edu/globec-dir/reports/al9707/al9707.html
Report describing AL9707
Cruise: OC298
OC298
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel
OC298
Mr Erich Horgan
Woods Hole Oceanographic Institution
http://globec.whoi.edu/globec-dir/reports/oc298/cruisereport.html
Report describing OC298
Cruise: OC300
OC300
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel
OC300
Peter H. Wiebe
Woods Hole Oceanographic Institution
http://globec.whoi.edu/globec-dir/reports/oc300/oc300rpt.mr7.html
Report describing OC300
Cruise: OC302
OC302
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel
OC302
Ann Bucklin
University of New Hampshire
http://globec.whoi.edu/globec-dir/reports/oc302/oce302.html
Report describing OC302
Cruise: AL9801
AL9801
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9801
Dr John Sibunka
Northeast Fisheries Science Center - Sandy Hook
http://globec.whoi.edu/globec-dir/reports/al9801/al9801.html
Report describing AL9801
Cruise: AL9806
AL9806
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9806
Dr John Green
Northeast Fisheries Science Center - Narragansett
http://globec.whoi.edu/globec-dir/reports/al9806/al9806.html
Report describing AL9806
Cruise: AL9808
AL9808
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9808
Ann Bucklin
University of New Hampshire
http://globec.whoi.edu/globec-dir/reports/al9808/al9808.html
Report describing AL9808
Cruise: OC317
OC317
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel
OC317
Dr David Mountain
Northeast Fisheries Science Center - Woods Hole
Cruise: OC319
OC319
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel
OC319
Peter H. Wiebe
Woods Hole Oceanographic Institution
http://globec.whoi.edu/globec-dir/reports/oc319/oc319new/oc319rpt.8april98.htm
Report describing OC319
Cruise: OC322
OC322
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel
OC322
Dr Charles B. Miller
Oregon State University
http://globec.whoi.edu/globec-dir/reports/oc322/oc322.html
Report describing OC322
Cruise: AL9901
AL9901
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9901
Dr John Sibunka
Northeast Fisheries Science Center - Sandy Hook
http://globec.whoi.edu/globec-dir/reports/al9901/al9901.html
Report describing AL9901
Cruise: AL9904
AL9904
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9904
Dr John Green
Northeast Fisheries Science Center - Narragansett
Cruise: AL9906
AL9906
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
AL9906
Peter H. Wiebe
Woods Hole Oceanographic Institution
http://globec.whoi.edu/globec-dir/reports/al9906/al9906rpt.html
Report describing AL9906
Cruise: EN320
EN320
R/V Endeavor
Community Standard Description
International Council for the Exploration of the Sea
R/V Endeavor
vessel
EN320
Ann Bucklin
University of New Hampshire
http://globec.whoi.edu/globec-dir/reports/en320new/en320mda.htm
Report describing EN320
Cruise: OC336
OC336
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel
OC336
Ms Maureen Taylor
Northeast Fisheries Science Center - Woods Hole
http://globec.whoi.edu/globec-dir/reports/oc336/oc336cruise-report.html
Report describing OC336
Cruise: OC341
OC341
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel
OC341
Dr Charles B. Miller
Oregon State University
http://globec.whoi.edu/globec-dir/reports/oc341/reptoc341.html
Report describing OC341
Community Standard Description
International Council for the Exploration of the Sea
R/V Albatross IV
vessel
R/V Endeavor
Community Standard Description
International Council for the Exploration of the Sea
R/V Endeavor
vessel
R/V Oceanus
Community Standard Description
International Council for the Exploration of the Sea
R/V Oceanus
vessel