/SCG.PROC/CRUISE.DATA
3.5kHz/ MET/ TRANS/
ADCP/ NAV/ TRKPLOTS/
CD_LABELS/ OS-75/ UWMRG/
CTD/ PDF/ UWPROF/
CruiseData.txt README.data XBT/
DEP/ SBDATA/ event.log
GRAV/ SBPLOTS/ s.i.'CRUISE'
LOGS/ SVPROFILES/
MAG/ T.files/
=================================================================
3.5Hz/
The 3.5Hz directory contains files of the single-beam depth data
from the Knudsen subbottom profiler. The data strings recorded are
configurable, but would at least include date and time, position
and depth. The data files can be in ascii, binary or SEGY formats,
whereby the SEGY format results in huge data files. The files are
written to the Knudsen host and ftp'd to the postprocessing machine
periodically for backup and archiving.
=================================================================
ADCP/pingdata.nn/
Pingdata.nnn files from the accoustic data current profiler (ADCP) are
in binary format and require special software for processing. Data
files are closed when they reach a size of about 320K.
Processing is normally done ashore with the CODAS software freely
available from the University of Hawaii.
The ADCP transducer well is located at plate 82, 96 feet forward of
the fantail and 4 feet to port of the centerline. Access is through a
hatch just inside the rear door of the lower computer lab.
(See also: OS-75 section later in this README)
=================================================================
CTD/
CTD data if included with the data set.
=================================================================
DEP/dep_uwts.yyymondd/
Depth on the minute is extracted from SBfixavg.yyyymondd SeaBeam files
and written to dep_uwts.yyyymondd files. Thus depth is only available
for periods of Simrad (Revelle) or SeaBeam (Melville) operation.
Note that dep_uwts.yyymondd files contain time and depth but no
navigation. Depth merged with navigation is found in the
UWMRG/list.uwmrg. file. It is also found in any Knudsen data
files.
The data format:
#yymmdd hhmmss Mtr hhmmss Mtr hhmmss Mtr hhmmss Mtr hhmmss Mtr
950926d000000 3555 000100 3554 000200 3554 000300 3556 000400 3555
For example:
### Program - swath_beamxtrct Version 1.2
### Input file name: /SCG.PROC/CRUISE.DATA/SBDATA/SBmrg.95sep26
### Extracted Center Beam
### Data was extracted every 1 minutes
### Day change
950925d235500 3495 235600 3508 235700 3530 235800 3541 235900 3553
### Day change
950926d000000 3555 000100 3554 000200 3554 000300 3556 000400 3555 ...
950926d000600 3556 000700 3557 000800 3563 000900 3567 001000 3566 ...
...
=================================================================
GRAV/GRAVinpf.yyyymondd
Raw gravity data, in units called counts, are written to
GRAVinpf.yyyymondd files, for example GRAVinpf.2000jun22:
Meter
# Unix secs Msecs Counts Error Code
961631701 255 023220 00
961631702 253 024121 00
961631703 255 025236 00
961631704 255 025051 00
Post-processed gravity data in the uwts format by date and minute are
collected in grav_uwts.yyyymondd files, for example
grav_uwts.2000jun22:
### grav.uwts. file produced by grav_filter
# BGM-3 meter serial #224 Scale factor 4.982796 mgal/count
# BGM-3 zero meter reading: Begin date: 960907 Begin reading: 855985.30 mgal
# BGM-3 zero meter reading: End date: 961021 End reading: 855985.30 mgal
# field formula type: 1967 GRS
# data bias: stored values = measured gravity in mgal*10 - 1200000
000621g23480023684 23490023692 23500023703 23510023711 23520023719 ...
000621g23540023866 23550024064 23560024242 23570024321 23580024312 ...
000622g00000024105 00010023947 00020023819 00030023741 00040023701 ...
...
For example, to derive the gravity value in milligals for the first
reading in the file, 23684, at time 23:48:00, multiply it by the scale
factor of 4.9827696 and add the result to the zero gravity meter value
(ZGMV) of 855985.30 mgal. Thus,
4.9827696 * 23684 = 118012
118012 + 855985.30 = 973997.84 mgals
Any meter drift would be factored in through linear interpolation from
the beginning and ending meter readings; here 855985.30 mgal for both
beginning and ending readings shows no drift and requires no
interpolation.
Note that GRAVinpf.yyymondd and grav_uwts.yyyymondd files contain time
and gravity but no navigation. Gravity merged with navigation is
found in the UWMRG/list.uwmrg. file.
Only Melville has a gravity meter. The data are routinely collected
and are made available by arrangement.
=================================================================
LOGS
Software, hardware and operator logs maintained by computer tech
during the cruise.
=================================================================
MAG/
MAG/MAG886inpf.yyyymondd, e.g., MAG886inpf.2000jul22
MAG/mag_uwts.yyyymondd, e.g., mag_uwts.2000jul22
MAG/MAG886inpf.yyyymondd:
- "MAG886inpf" file is ASCII, correct?
- Field 1 should be defined as the "total observed magnetic
field value".
- is the one minute-interval uwts file on the even minute or
at 60 second intervals since the start of recording?
- What does "Data Type: Earth total field magnetic data ?????" mean?
- "uwts" needs to be defined
- state that "uwts" files contain NO navigation, just (time,value).
Earth total field magnetic data are collected from a surgace-towed
Geometrics Mod. 801 Marine Proton magnetometer and logged on the
realtime computer. Data is received at about 4- to 6-seconds
intervals, converted from BCD to ASCII format, and written to a
MAGinpf.yyyymondd file on the realtime computer. The actual time
interval varies, and it is best computed by using the time difference
between adjacent records.
The data consist of time and magnetic total field value in nanoTesslas
(nT) from each magnetometer 5.5 second cyce.
The raw data file MAG886inpf.yyyymondd:
yymmdd hhmmss 1 2 3 4 5 6
000509m235500 = 40358.48 356 0 0 40.3 30.1
000509m235504 = 40359.40 360 0 0 40.3 30.1
1 total observed magnetic field value
2 signal strength, should be in area above 300
3 depth, always zero
4 altitude, always zero
5 tuning value, should correspond to first three digits of magfield
6 ????
Once each day the MAG886inpf file is timestamped and transferred to
the offline machine for postprocessing: the data are averaged over 1
minute intervals and written to a file, mag_uwts.yyyymondd. Each
mag_uwts file is then concatenated with the previous ones into a
cumulative file, mag_uwts.[CRUISE], which is then merged with
navigation, depth and gravity into a binary file, 'uwmrg.[CRUISE]'.
The magnetic anomaly is calculated during merging by subtracting
the International Geomagnetic Reference Field (IGRF) from the total
field value. (The IGRF is calculated by determining the IGRF values
at the corners of a one degree square centered on the first point
and then interpolating the IGRF on this plane as long as the location
of subsequent values stay within the one degree square.)
Processing: /UWDSYS/bin/mag886_uwts < MAG886inpf.$1 > mag_uwts.$1
Output: CRUISE.DATA/MAG/mag_uwts.yyyymondd in one minute intervals on
the minute.
Data Type: Earth total field magnetic data in nanoTessla (nT):
yymmdd hhmmssnT hhmmssnT hhmmssnT hhmmssnT hhmmss nT
000509m23550040359 23560040358 23570040355 23580040356 23590040355
000510m00000040354 00010040352 00020040351 00030040352 00040040351 ...
000510m00060040349 00070040349 00080040348 00090040347 00100040347 ...
All daily mag_uwts files are concatenated into a mag_uwts.
file of the same format:
000506m17370032061 17380032069 17390032082 17400032095 17410032108 ...
000506m17430032132 17440032146 17450032153 17460032168 17470032180 ...
000506m17490032209 17500032222 17510032236 17520032246 17530032257 ...
...
MAG886inpf.yyymondd and mag_uwts.yyyymondd files contain time and
magnetic values but no navigation. Magnetics merged with navigation
is found in the UWMRG/list.uwmrg. file.
=================================================================
MET/*.ps
Data printouts in postscript form are found under MET.
MET.yymmdd.dat.ps displays air temperature, barometric pressure,
humidy, precipitation, short wave and long wave readings over the
last 24 hours.
SSV.yymmdd.dat.ps displays water temperature, conductivity, salinity
and surface sound velocity over the last 24 hours.
WIND.yymmdd.dat.ps displays relative wind speed, relative wind
direction, true wind speed, true wind direction, ship speed and ship
direction over the last 24 hours.
WEEKLY.MET.yyyymondd.ps displays air temperature, barometric pressure,
humidty, precipitation, and short and long wave radiation for the past
week.
=================================================================
Navigation Files
NAV/PCODE
PCODE position:
Stern A-frame 44.2m @ 000 degs relative
Starboard A-frame 23.6m @ 333 degs relative
J-frame 11.0m @ 312 degs relative
Each second GPZDA, GPGGA and GPVTG NMEA strings are output from the
PCODE receiver and written to the ASCII file PCODEinpf.yyyymondd on
the real time host. At the end of the GMT day this file is copied to
the postprocessing computer and compressed (*.Z).
Here are examples and descriptions of each type:
1 2 3 4 5 6 7
$GPZDA,173112.00,17,06,2000,00,00,*4f
(1) hhmmss.ss
(2) day of month
(3) month
(4) year
(5) local zone description, -- to +/-13 hours
(6) local zone minutes description, same sign as local hours
(7) checksum
1 2 3 4 5 6 7 8 9 10 11 12 13
$GPGGA,173111.816,1403.2520,N,09645.2016,W,3,08,0.9,034.0,M,007.7,M,,*79
(1) hhmmss.sss
(2) latitude
(3) hemisphere n/s
(4) longitude
(5) hemisphere e/w
(6) gps quality, 3 = precise positioning service
(7) number of satellites in use 00-12
(8) horizontal dilution of precision
(9) antenna altitude above/below mean sea level (geoid)
(10) units of altitude, m = meters
(11) geoidal separation: the difference between the wgs-84 earth
ellipsoid and mean-sea-level (geoid), "-" - mean-sea-level below
ellipsoid.
(12) units of geoidal separation, m = meters
(13) checksum
1 2 3 4 5 6 7 8 9
$GPVTG,190.5,t,184.1,M,012.3,N,022.7,K*48
(1) track angle in degrees
(2) t = true track
(3) track angle in degrees
(4) m = magnetic
(5) speed over ground
(6) n = knots
(7) speed over ground
(8) k = kilometers per hour
(9) checksum
NAV/ASHTECH
Ashdata.yyyymondd.ps files contain graphic of Ashtech heading, pitch
and roll over the last 24 hours.
ASHinpf.yyyymondd files contain the Ashtech data of the last day. The
NMEA strings recorded are LGZDA, GPGGA, GPVTG and PASHR. LGZDA are
recorded on the minute, GPGGA and GPVTG on the second, and PASHR on
the half second or the second. At the end of the GMT day the ASHinpf
file is copied from to the postprocessing computer.
1 2 3 4 5
$LGZDA,000200.00,11,01,2000,,
1 Header
2 hhmmss.ss
3 dd
4 mm
5 yyyy
1 2 3 4 5 6 7 8 9 10
$GPGGA,hhmmss.ss,ddmm.mmmm,H,dddmm.mmmm,H,1,06,HDOP,
$GPGGA,230005.50,1120.2652,N,08934.0808,W,1,06,01.3,+00037,M,,M,,
1 Header
2 GMT time in hours, minutes, seconds and decimal seconds
3 Latitude
4 N north or S south
5 Longitude
6 E east or W west
7 GPS quality indicator, 1 = GPS Available
8 Number of GPS satellites in use
9 Horizontal dilution of precision HDOP
10 Antenna height in meters, M for meters
(1) (2) (3) (4) (5) (6) (7)
$GPVTG,ddd.dd,T,,,013.22,N,024.49,K
$GPVTG,293.17,T,,,013.22,N,024.49,K
(1) Header
(2) COG (course over ground) and
(3) T for true
(4) SOG (speed over ground)
(5) N for knots
(6) SOG (speed over ground)
(7) K for km/hr
1 2 3 4 5 6 7 8
$PASHR,ATT,ssssss.s,ddd.dd,-ddd.dd,+ddd.dd,m.mmmm,m.mmmm,F
$PASHR,ATT,428419.0,290.99,-000.17,-002.19,0.0013,0.0277,0
(1) Header
(2) GPS seconds-of-week
(3) Heading in degrees
(4) Pitch in degrees
(5) Roll in degrees
(6) MRMS in meters: the average double difference carrier phase residual.
(7) BRMS in meters: RMS error for the differences between calibrated
baseline magnitudes and coputed baseline magnitudes for the three
vectors forme by Anbtenna 1 to the other three antennas.
(8) Attitude reset flag with type of attitude output:
"0" : phase ambiguities solved, precise carrier phase attitude
computed.
"1" : phase ambiguities unsolved, codephase heading estimate
given, pitch and roll set to 0.0.
NAV/200D (Melville)
Output is collected in 200Dinpf.yyyymondd files on the realtime host.
At the end of the GMT day the files are copied to the postprocessing
host and compressed (*.Z). The GPZDA, GPVTG and GPGGA NMEA lines of
the files contain the same information as corresponding lines in the
NAV/PCODE/PCODEinpf.yyymondd.Z files, for example,
$GPZDA,235507.00,08,05,2000,,
$GPVTG,337,T,329,M,012.25,N,022.68
$GPGGA,235509,1248.8508,N,10146.6943,W,1,6,001.09,00028,M,-00011,M
$GPVTG,338,T,330,M,012.35,N,022.87
$GPGGA,235510,1248.8541,N,10146.6955,W,1,6,001.09,00028,M,-00011,M
$GPVTG,338,T,330,M,012.35,N,022.88
...
NAV/satdata.yyyymondd
At the end of the GMT day, NAV/PCODE/PCODEinpf.yyyymondd files are
copied to the postprocessing host and converted into satdata.yyyymondd
ASCII files with one-minute navigation. The files have the following
format:
LAT(1) LON(2)
mm dd yyyy hhmm d dd.dddd ddd mm.mmmm
05 04 2000 2356 3 24.3737-102 13.6108 pc08 1.0
05 04 2000 2357 3 24.3655-102 13.6211 pc08 1.0
05 04 2000 2358 3 24.3574-102 13.6309 pc08 1.0
05 04 2000 2359 3 24.3508-102 13.6391 pc08 1.0
06 04 2000 0000 3 24.3424-102 13.6490 pc08 1.0
06 04 2000 0001 3 24.3353-102 13.6576 pc08 1.0
...
(1) -Lat = Southern Hemisphere
(2) -Lon = Western Hemisphere
NAV/navbin."CRUISE"
The sorted satdata.EXTENT files are catted into a binary
navbin. file. This file is then used to update the navigation
in the contour track (SBmrg.yyyymondd) and sidescan (SSmrg.yyyymondd)
files (Melville).
===========================================================================
OS-75
Contains data from the RD Instruments Ocean Surveyor 75 ADCP
===========================================================================
SBDATA
Contains the SeaBeam 2000 contour and sidescan files collected during
the cruise.
SBPLOTS
Under SBPLOTS are automatically generated *.cmd scripts which produce
compressed postscript files of the SeaBeam contour track and the
sidescan for each six-hour period across the day. On Melville, for
example:
SBfixavg.2000mar25.0000-0600.cmd => SBfixavg.2000mar25.0000-0600.ps.Z
SSmed.2000mar25.0000-0600.cmd => SSmed.2000mar25.0000-0600.ps.Z.
===========================================================================
SVPROFILES
An edited XBT/*.edf file is converted to a sound velocity file named
.svp., for example, NEMO03MV.svp.04. This
file includes a header including time and position followed by
depth/sound-velocity pairs. Sample values of depth (meters) and sound
velocity (meters/sec) are:
0.0 1540.0
31.4 1540.3
46.3 1537.2
77.6 1508.8
110.8 1500.0
...
Also created is a plot of the resultant curve of depth versus sound
velocity, for example, NEMO03MV.svp.04.ps.
===========================================================================
T.files
The T.files directory contains log files with the standard ouput from
the daily postprocessing scripts in directory sproc.
DOcron.list.yyyymondd: Master log file with standard outputs of many
of the postprocessing script commands in CRUISE.DATA/sproc.
Tuwchek.dep_uwts.yyyymondd: standard output of DOuwchek.dep which
runs uwchek program on dep.uwts file
Tuwchek.mag_uwts.yyyymondd: standard output of DOuwchek.mag which
runs uwchek program on mag.uwts file
Tuwchek.grav_uwts.yyyymondd: std output of DOuwchek.grav which
runs uwchek program on grav.uwts file
Tswath.mer.fix.box.yyyymondd: main log file of standard ouput for
postprocessing of SeaBeam files. This includes the track start
and endtimes as well as the latitude/longitude bounds of the area
covered, for example:
2-17.796N
101-21.018W 97-31.519W
1-58.379N
=================================================================
TRANS/yyyymondd.COR -- Water, meteo and navigation data
Meteorological data is collected from sensors on the forward MET mast
located on the bow. The mast sensors are from 13.5 to 14.7 meters
above the water line. Seawater sensors are mounted in the bow some 13
feet below water line depending on the ship's load and its distribution.
Every 30 seconds air, water and navigation data are written to file:
TRANS/yymmdd.UCR (raw, uncorrected)
TRANS/yymmdd.COR (corrected)
and
TRANS/yymmdd.MET (corrected subset of *.COR file as configured)
Data analysis should be done on either *.COR or *.MET files.
yymmdd.COR files
The format for the corrected data in *.COR files is:
$WICOR,030103,000112,13.7,WS3,340.8,WD3,8.7,TW3,182.3,TI3,1018.07,BP3,
1017.54,BP3,63.76,RH3,18.64,RT3,11.76,DP3,19.00,AT3,0.0,PR3,292.09,LD3,
291.98,LB3,302.4,LT3,493.7,LW3,-3.8,SW3,20.746,TT3,47.336,TC3,33.920,SA3,
23.740,SD3,1522.320,SV3,75.9,FM3,2.786,OC3,20.738,OT3,4.979,OX3,5.1285,
OS3,20.74,WT3,4.7,FI3,3.279,FL3,-99.0,BT9,-99,TS9,-35.121470,LA3,
16.995683,LO3,222.0,CR3,11.4,SP3,50,GT3,217.6,GY3,-99.0,SH9*32
The convention is for data designators to follow their corresponding
values. Thus, in the line above, after "$WICOR" and two time values
of form yymmdd,hhmmss, there comes a series of data values and
designators, the values preceding. Here, WS3 (relative wind speed)
follows its corresponding value 13.7. Also, -99 indicates an absent
or invalid value. The designators are as follows:
AT Air Temperature Deg C
AX Auxiliary Air Temperature Deg C
BC Barometric Pressure Temp Deg C
BP Barometric Pressure mb
BT Bottom Depth Meters
CR Ships Course (GPS) Deg
DP Dew Point Deg C
FI USW Flow Meter LPM
FL Fluorometer ug/l
FM USW Flow Meter GPM
GT GPS Time Secs
GY Ships Course (Gyro) Deg
LA Latitude Decimal format Deg
LB LWR Body Temperature Deg K
LD LWR Dome Temperature Deg K
LO Longitude Decimal format Deg
LT LWR Thermopile Volts
LW LWR W/M^2
MA Current m/a
OC Oxygen Current ua
OG Oxygen mg/l
OS Oxygen Saturation value ml/l
OT Oxygen Temperature Deg C
OX Oxygen ml/l
PA Surface PAR uE/Second/Meter^2
PM Precipitation mm/mm
PR Precipitation mm
PS Pressure PSI
PT Precipitation mm/hr
RH Relative Humidity %RH
RT Air Temp (RH module) Deg C
SA Salinity PSU
SD Sigma-t Kg/m^3
SH Ashtech Heading Deg
SL Ships Speed (Speed Log) Knts
SP Ships Speed (GPS) Knts
ST Sea Surface Temperature Deg C
SV Sound Vel (Chen/Millero) M/S
SW Short Wave Radiation W/M^2
TB Turbidity NTU
TC SBE21 Conductivity mS/m
TI True Wind Direction Deg
TK True Wind Speed Knots
TR Transmissometer %
TS Time Server Time Secs
TT SBE21 Temperature Deg C
TW True Wind Speed M/S
VT Volts Volts
WD Rel Wind Direction Deg
WK Rel Wind Speed Knots
WS Rel Wind Speed M/S
WT Auxiliary water Temp Deg C
XX Unspecified
ZO Winch Wire Out Meters
ZS Winch Speed MPM
ZT Winch Tension LBS
=================================================================
yymmdd.MET files
Yymmdd.MET files contain corrected data. Their first line displays
designators in the sequence of the data values on subsequent lines:
#Time WS WD TW TI BP BP-2 RH RT DP AT PR LD LB LT LW SW TT TC SA SD SV
FM OC OT OX OS WT FI-2 FL BT TS LA LO CR SP GT GY SH
000009 5.8 40.7 5.7 180.0 1014.78 1014.70 83.92 20.21 17.46 20.44 0.0
292.92 292.80 285.7 493.6 -4.1 20.578 47.521 34.204 24.001 1522.176
15.7 2.800 20.696 5.000 5.1239 20.70 7.3 1.609 -99.0 -99 -34.123825
14.583165 135.0 0.1 10 -99.0 -99.0
...
In the line above, WS (relative wind speed) is 5.8, BP (barometric
pressure) is 1014.78. -99 indicates an absent or invalid value.
See the list of designators just above.
=================================================================
TRKPLOTS
Under TRKPLOTS, the DR1hour file includes Julian day with date, time,
position, speed, and timestamp of the
Julian File
Day day dd mon dd hh mm ss Lat Lon Knt Hdg time
[DR Thu 283 10-Oct-02 21:00:20 9 58.12 N 84 50.25 W 0.1 214 2100 ]
[DR Thu 283 10-Oct-02 22:00:20 9 58.11 N 84 50.25 W 0.2 214 2200 ]
[DR Thu 283 10-Oct-02 23:00:21 9 58.12 N 84 50.25 W 0.1 214 2300 ]
[DR Fri 284 11-Oct-02 00:00:20 9 58.12 N 84 50.25 W 0.1 214 0000 ]
[DR Fri 284 11-Oct-02 01:00:20 9 58.09 N 84 50.22 W 0.1 168 0100 ]
[DR Fri 284 11-Oct-02 02:00:20 9 58.12 N 84 50.17 W 0.1 160 0200 ]
...
A track plot of the cruise to date is created from the DR1hour file:
MV.dd-mon-yy.ps (Melville) or RV.dd-mon-yy.ps
(Revelle).
=================================================================
UWMRG/list.uwmrg."CRUISE"
list.uwmrg. is an ASCII file containing a compilation of data
at 60 second intervals (on the minute) from SeaBeam, magnetics, and
gravity data (Melville) files, all merged with navigation (PCODE). It
is recreated at the end of each GMT day when the data files of the
previous day are copied to the postprocessing host. E.g.,
Do the "CORRECTED METERS" come from Carter corrections or from SVP
ray-bending calculations?
#DAY TIME LATITUDE LONGITUDE COURSE SPEED CUM.DIST 1500M CORRECTED MAGNETICS GRAVITY RECORD
# (GMT) DEG MIN DEG MIN DEG KTS N.MILES MTR METERS OBSV ANOM OBSV ANOM IN FILE
990915 0004 11 58.9449 S 163 5.1617 W 25.6 8.0 997.3 3122 3113 36536.0 -57.4 8665
990915 0005 11 58.8254 S 163 5.1031 W 25.8 7.9 997.5 3105 3096 36536.0 -56.4 8666
990915 0006 11 58.7068 S 163 5.0455 W 24.5 7.8 997.6 3103 3094 36536.0 -55.5 8667
990915 0007 11 58.5887 S 163 4.9896 W 26.2 7.8 997.7 3103 3094 36538.0 -52.6 8668
Depth, magnetics, and gravity only have values for the periods of
SeaBeam, magnetometer and gravity meter operation. Depth 1500M MTR
shows depth computed at a sound velocity of 1500 meters/second.
CORRECTED METERS has depth corrected for sound velocity. Revelle has
no gravity meter and will never show gravity data.
=================================================================
UWPROF
summary.data.yyyymondd.ps files include 24-hour plots of ship's
heading and speed, gravity in milligals, free air in milligals, and
depth, mag field (nT) and mag anomaly
plot.NEMO04MV.page06.ps incudes gravity free air (mgals), magnetic
anomaly (nT) and depth (meters) over last 250 nautical miles.
=================================================================
XBT
With each XBT, the MK12 XBT software produces a *.rdf binary file of
the raw XBT data, and a corresponding *.edf ASCII file. An XBT/*.edf
file contains header infomation--time, position and ID number--and
depth/temp (meters/centigrade) values, for example:
0.68 26.559
1.37 27.317
2.05 27.678
2.73 27.812
3.41 27.893
4.10 27.923
4.78 27.927
5.46 27.937
... ...
A graph of the depth/temp curve is created in a postscript file, e.g.,
t5_00138.edf.ps, whereby t5 is the XBT type and 138 is the sequence
number.
Later processing then creates a .svp.nn file (see SVPROFILES)
with depth/sound-velocity pairs for entry into SeaBeam.
=================================================================
event.log
The bridge records events pertaining to science in the event.log file,
e.g.,
Time Date Lat Lon Event
1316z 06/13/100 09 34.71N. 086 02.28W. Recovered OBS S2 CC
1632z 06/13/100 09 30.00N. 086 11.61W. OBS S1 Recovered GZ
2024z 06/13/100 09 45.06N. 085 33.11W. O.B.S. S14 on deck RW
...
=================================================================
sample_index, e.g., KIMO04_sample_index
The sample_index is the resident technician's (restech's) record of
the science party and the significant events of the cruise, e.g.,
KIMO EXPEDITION LEG 04 RV MELVILLE
PECS MPL BERMAN, L. CHIEF SCIENTIST SCRIPPS INSTITUTION KIMO04MV
PEST IGPP GEHREN, R. GRADUATE STUDENT SCRIPPS INSTITUTION KIMO04MV
PESP MPL EICHER, S. PROG. ANALYST SCRIPPS INSTITUTION KIMO04MV
PECT STS JACKSON, D. COMPUTER TECH SCRIPPS INSTITUTION KIMO04MV
PESP MPL KANTOR, N. SCIENTIST SCRIPPS INSTITUTION KIMO04MV
PEAT STS MOYER, S. AIRGUN TECHNICIAN SCRIPPS INSTITUTION KIMO04MV
PERT STS POLAND, G. RESIDENT TECH SCRIPPS INSTITUTION KIMO04MV
PEPS MPL SANDER, A. SCIENTIST SCRIPPS INSTITUTION KIMO04MV
Time Date Event Cruise
2300 120600 LGPT B PUNTARENAS, COSTA RICA g KIMO04MV
1430 280600 LGPT E SAN DIEGO, CA USA g KIMO04MV
0238 130600 DPR3 B 3.5 RECORD GDC g KIMO04MV
1200 280600 DPR3 E R0LL 01 GDC g KIMO04MV
0209 130600 MBSR B SEABEAM RECORD GDC g KIMO04MV
1200 280600 MBSR E ROLL 01 GDC g KIMO04MV
...