R/V Knorr Calliope metadata file Fri 12/Sep/2008 04:37:02 Current time zone: GMT Standard Time ================================================== 12kHz depth (Depth12) Format: xxxx.x (meters) Depth in meters obtained from the 12 kHz channel of the Knudsen bathymetry system. 5 meter transducer depth correction has been applied (see Knudsen bathymetry data string). __________________________________________________ 3.5kHz depth (Depth35) Format: xxxx.x (meters) Depth in meters obtained from the Knudsen 3.5 kHz channel. 5 meter transducer depth correction has been applied (see Knudsen bathymetry data string). __________________________________________________ Air Temperature (Air_Temp) Format: xx.xxx (degrees C) Data is obtained from IMET_HRH primary sensor. __________________________________________________ Air temperature; WXT (WXT5_Ta) Abient air temperature (C) from Vaisala WXT510 sensor. __________________________________________________ Barometric Pressure; WXT (WXT5_Pa) Barometric pressure (hPa) from Vaisala WXT510 sensor. __________________________________________________ Decimal Latitude (dec_lat) Latitude in decimal degrees obtained from primary GPS receiver. __________________________________________________ Decimal Latitude 1850 (DecLat_1850) Decimal latitude from Furuno 1850 GPS receiver. __________________________________________________ Decimal Longitude (dec_lon) Longitude in decimal degrees obtained from primary GPS receiver. __________________________________________________ Decimal Longitude 1850 (DecLon_1850) Decimal Longitude from Furuno 1850 GPS receiver. __________________________________________________ Distance to waypoint; RMB (WP_Dist) Distance to next waypoint reported by Furuno 1850 GPS receiver (GPRMB data sentence). __________________________________________________ Sea Surface Conductivity (SSCND) Falmouth Scientific TSG (OCM-S-212) sea surface conductivity Format: xx.xxxx (mmho/cm or milli-Siemens/cm) OCM sensor is mounted in the bow chamber on the suction side of the clean sea water distribution pump, approximately 5 feet from the forward facing inlet at a depth of 15 feet. __________________________________________________ Sea Surface Temperature (SSTMP) Falmouth Scientific TSG (OTM-S-212) sea surface temperature Format: xx.xxxx (degrees C) OTM sensor is mounted in the bow chamber on the suction side of the clean sea water distribution pump approximately 5 feet from the forward facing inlet at a depth of 15 feet. __________________________________________________ Furuno Speedlog NMEA (VDVBW) NMEA output from the Furuno speedlog (4800,N,8,1) Format: $VDVBW,a.a,b.b,A,c.c,d.d,A,e.e,A,f.f,A,*hh a.a = Longitudial water speed, knots b.b = Transverse water speed, knots A = Status - "A" data valid, "V" data invalid c.c = Longitudial ground speed, knots d.d = Transverse ground speed, knots A = Status e.e = Stern transverse water speed, knots A = Status f.f = Stern transverse ground speed, knots A = Status hh = checksum __________________________________________________ GPS 1850 RMB (GPRMB_1850) Furuno 1850 GPS waypoint data string. Format: $GPRMB,A,x.x,d,c1,c2,dlat,h,dlon,h,r.r,b.b,v.v,AS*xx A=Status (A=valid, V=Warning) x.x=Cross track error d=Direction to steer (Left/Right) c1=Origin waypoint ID c2=Destination waypoint ID dlat,h=Destination waypoint Latitude,N/S dlon,h=Destination waypoint Longitude,E/W r.r=Range to destination, NM (max value = 999.9) b.b=Bearing to destination, degrees true v.v=Destination closing velocity, knots AS=Arrival status (A=arrival circle entered/passed, V=not entered/passed) *xx=Checksum __________________________________________________ GPS 1850 RMC (GPRMC_1850) Furuno 1850 GPS data Format: Header, UTC of position fix, Status (A=valid, V=warning), Latitude, N/S, Longitude, E/W, Speed over ground (knots), Course over ground (True), Date (ddmmyy), Magnetic variation (degrees), E/W (Easterly variation subtracts from True course) *xx is checksum Example: $GPRMC,141818,A,4131.4373,N,07040.3363,W,0.1,259.1,050808,15.9,W*47 __________________________________________________ GPS course over ground (GPS_COG) Course over ground (true) obtained from primary GPS VTG data sentence. Format: xxx.x (degrees) __________________________________________________ Latitude (GPS_Lat) Latitude from primary GPS GGA data sentence formatted for display. Format: dd mm.mmm, N/S __________________________________________________ Longitude (GPS_Lon) Longitude from primary GPS GGA data sentence formatted for display. Format: ddd mm.mmm, E/W __________________________________________________ GPS Navigation data (GPS) Complete NMEA data output from the primary GPS receiver. WGS84 datum. The single digit following the position information in the GPGGA data string indicates the type of GPS fix as follows: 0=No valid fix; 1=Standard; 2=Differential; 3=P-Code NMEA GPGGA data sentence: Header, UTC of position, Latitude, N/S, Longitude, E/W, Quality indicator, Number of satellites in use, Horizontal dilution, Altitude, M (meters), Geoidal separation, M (meters), Age of differential data (secs), Differential reference station I.D. * checksum. (Lat & Lon values are "degrees minutes.decimal_minutes") NMEA GPVTG data sentence: Header, Course, T (degrees true), Course, M (magnetic), Speed, N (knots), Speed, K (km/hr) * checksum. NMEA GPZDA data sentence: Header, UTC, Day, Month, Year, LTZ (Hrs), LTZ (Min) * checksum LTZ(hrs) + LTZ(Min) + Local Time = UTC NMEA GPRMC data sentence - not always available: Header, UTC of position fix, Status (A=valid, V=warning), Latitude, N/S, Longitude, E/W, Speed over ground (knots), Course over ground (True), Date (ddmmyy), Magnetic variation (degrees), E/W (Easterly variation subtracts from True course) NMEA GPRMB data sentence - not always available Format: $--RMB,DA,x.x,L/R,OID,DID,Lat,N/S,Lon,E/W,r.r,b.b,v.v,AS*hh DA = Data Status ("A" = valid, "V" = receiver warning) x.x = Cross trtack error (nautical miles) L/R = Direct to steer (left/right) OID = Origin waypoint ID DID = Destination waypoint ID Lat,N/S = Destination Latitude Lon,E/W = Destination Longitude r.r = Range to destination (nautical miles) b.b = Bearing to destination (degrees true) v.v = Destination closing veliocity (knots) AS = Arrival status (A=Arrival circle entered, V=not entered) hh = checksum This string allows calculation of time and distance to next waypoint. __________________________________________________ GPS speed over ground (GPS_SOG) Speed over ground obtained from primary GPS VTG data sentence. Format: xx.xx (knots) __________________________________________________ GPS type (GPS_TYPE) GPS position type (Std, Diff, P-Code) GPS position type indicator is obtained from the "quality indicator" included as part of the primary GPS GGA data sentence. __________________________________________________ Gyro heading (Gyro) Ship's heading obtained from the Gyro NMEA HEHDT data sentence. Format: xxx.x (degrees true) __________________________________________________ IMET Wind (IMET_WND) Format: X, Y, Total, Max, Min, LastVane, LastCompass, C1, C2 Wind X (m/sec), Positive for a stbd to port wind Wind Y (m/sec), Positive for a bow to stern wind Wind Total (m/sec), Averaged over previous minute Wind Max (m/sec, 15 sec interval), Wind Min (m/sec, 15 sec interval), Last Vane Reading (deg), Last Compass Reading (deg), Counter1 ("0"), Counter2 ("4") Note - Wind direction is not provided as a single quantity. Direction values are ship relative. The wind sensor does not have a compass installed (value should always be 0.0). __________________________________________________ IMET Barometric Pressure (IMET_BPR) Format: xxxx.xx (millibars) __________________________________________________ IMET longwave radiation ( IMET_LWR) __________________________________________________ IMET Precipation (IMET_PRC) Format: Last minute (mm/min), Last hour (mm/hr), Present level (mm) __________________________________________________ IMET Shortwave Radiation (IMET_SWR) Format: xxxx.x (watts/square meter) Sensor is manufactured by Eppley Laboratory Inc. The wavelength range is 0.3 to 3 um __________________________________________________ IMET Humidity & Temperature (IMET_HRH) Format: xx.xxx (%RH), xx.xxx (C) Note - Relative humidity (HRH) and Air temperature (Air_Temp) data are both obtained from this instrument. __________________________________________________ Knudsen bathymetry (PKEL99) Depth data obtained from the Knudsen bathymetry system. Values have been corrected for transducer depth (5 meters). Format: Header ($PKEL99), 12 kHz depth (meters), 3.5 kHz depth (meters), Speed of sound (m/s), Lat (dd mm.mmm N/S), Lon (ddd mm.mmm E/W) Speed of sound is the value used by the Knudsen. It is entered manually and therefore is not necessarily correct. __________________________________________________ Latitude (Lat) Latitude obtained from the primary GPS receiver expressed in degrees & minutes. 4131.436,N is 41 degrees 31.436 minutes North Latitude. __________________________________________________ Longitude (Lon) Longitude obtained from the primary GPS receiver expressed as degrees and minutes. 07040.336, W is 70 degrees 40.336 minutes West Longitude. __________________________________________________ MetraByte #1 (MByte1) __________________________________________________ NMEA Gyro (HEHDT) Ship's heading obtained from the Sperry Gyro. NMEA format: Header ($HEHDT), Heading (degrees), T (true), Heading (degrees), M (magnetic) * checksum. Version 2.20 (1/1/97) of the NMEA 0183 standard does not show magnetic heading in this data sentence and the validity of this item is questionable. __________________________________________________ NMEA depth (SDDBS) Format: $SDDBS,xx.xx,f,xx.xx,M,xx.xx,F*hh Water depth below the surface: feet, meters, fathoms. *hh is checksum __________________________________________________ Position from primary GPS receiver (Lat_Lon) Latitude & Longitude in decimal degrees. Format: +/-dd.dddddd +/-ddd.dddddd (N & E are "+") __________________________________________________ QSR_2200 (QSR_2200) Quantum Reference Sensor by Biospherical Instruments, Inc. Model Number QSR-2200 Serial Number 20313 Cal date 3/24/2008 __________________________________________________ Rain Intensity; mm/hr (WXT5_Ri) Rain intensity (mm/hr) from Vaisala WXT510 sensor. Data Format: x.x This value is calculated over 10 second intervals. __________________________________________________ Rain accumulation; WXT (WXT5_Rc) Rain accumulation (mm) from Vaisala WXT510 sensor. Data Format: xx.xx This value continues to increase until the sensor is reset as the result of power cycling (data polling does not reset the count). __________________________________________________ Relative humidity (HRH) Format: xx.xxx (%RH) Data is obtained from IMET_HRH primary sensor. __________________________________________________ Relative Humidity; WXT (WXT5_Ua) Relative humidity (%) from Vaisala WXT510 sensor. __________________________________________________ Relative wind direction (WXT5_Dm) Ship relative wind direction (degrees) from Vaisala WT510 sensor. Data has not been corrected for sensor mounting alignment error - see "defined constants". Data Format: xxx Wind direction is given in meteorological terms: a “0” degree wind comes from the bow; a “90” degree wind comes from the Stbd side. Wind sampling is done at 2 Hz and averaged over 10 seconds – new data is available at 10 sec intervals. __________________________________________________ Relative wind speed (WXT5_Sm) Ship relative wind speed (m/s) from Vaisala WXT510 sensor. Data Format: xx.x Wind sampling is done at 2 Hz and averaged over 10 seconds – new data is available at 10 sec intervals. __________________________________________________ SBE45 conductivity (SBE45C) Surface conductivity from SBE45 Format: cc.ccccc (mS/cm) (Note - raw data is S/m; S/m*10 = mS/cm) __________________________________________________ SBE45 salinity (SBE45S) Surface Salinity from SBE45 Format: sss.ssss (psu) __________________________________________________ SBE45 sound velocity (SBEV) Surface sound velocity from SBE45 Format: xxxxx.xxx (m/sec) __________________________________________________ SBE45 temperature (SBE45T) Sea surface temperature from SBE45 Format: ttt.tttt (degrees C, ITS-90) __________________________________________________ SBE45 thermosalinograph (SBE45) Data Output Format: ttt.tttt, cc.ccccc, sss.ssss, vvvvv.vvv t = temperature (degrees Celsius, ITS-90) c = conductivity (S/m) s = salinity (psu) v = sound velocity (meters/second) All data is separated with a comma and a space. This sensor is mounted in the clean seawater piping at the aft end of the Main Laboratory. __________________________________________________ SBE48 sea surface temperature (SBE48T) Format xx.xxxx Sea surface temperature (C) measured through the hull with a magnetically coupled SBE48. Sensor is located in the bow chamber at a depth of about 5 meters. Sensor housing is contained in an insulation jacket to limit effect of ambient bow chamber air. __________________________________________________ Salinity (Salinity) Format: xx.xxxx Salinity (psu) calculated from sea surface temperature and conductivity data values in accordance with UNESCO 44. __________________________________________________ Sea surface conductivity ( SSCND) Best sea surface conductivity value. This value is used to calculate dependent data items (i.e. salinity). March 13, 2008; Value obtained from SBE45 in Main Lab (SBE45C) __________________________________________________ Sea surface fluorometer (Fluorometer) WetLabs Wet-Star fluorometer located in the clean seawater system. Value reported in millivolts. Calibration must be done by interested science parties. A MetraByte A/D converter is used to convert the 0-5 vdc fluorometer output to serial data. This device sets the output decimal point as necessary for best resolution which results in a 1 vdc fluorometer value being represented as +01000.00 in the raw MetraByte serial stream. WetLabs Wet-Star fluorometer Specifications Response time: 0.17 sec (analog); 0.125 sec (digital, optional) Input: 7-15 VDC Output: 0-5 VDC (analog); 0-4095 counts (digital, optional) Current draw: < 40 mA (analog); < 80 mA (digital, optional) Linearity: = 99% R2 Optical Chlorophyll Dynamic ranges: 0.03 -75 \uffffg/l (standard); 0.06-150 \uffffg/l (optional) Sensitivity: = 0.03 \uffffg/l Excitation: 460 nm Emission: 695 nm CDOM Dynamic ranges: 1000 ppb (estuarine waters) 250 ppb (near-coastal waters) 100 ppb (open ocean waters) Sensitivity: 0.100 ppb quinine sulfate dihydrate Excitation: 370 nm (10 nm FWHM) Emission: 460 nm (120 nm FWHM) Uranine Dynamic range: 0-4000 \uffffg/l uranine Sensitivity: 1 \uffffg/l uranine Excitation: 485 nm Emission: 590 nm Phycoerythrin Excitation: 525 nm Emission: 575 nm __________________________________________________ Sea surface temperature ( SSTMP) Degrees C Best sea surface temperature value. This value is used for calculating dependent data items (i.e. salinity). March 13, 2008; SSTMP obtained from SBE48 in bow chamber (SBE48T) __________________________________________________ Sound velocity ( SSV) Format: xxxx.xxxx (meters/sec) Surface sound velocity calculated from sea surface temperature and conductivity data values. Intermediate salinity values are calculated in accordance with UNESCO 44. __________________________________________________ Speed over ground - 1850 (SOG_1850) Speed over ground (Knots) from Furuno 1850 GPS receiver. __________________________________________________ Surface Irradiance ( SPAR) Surface Irradiance in uE/cm2sec is calculated by (((QSR_2200*.001)-.0019)/5.8731) Following cal sheet: "To calculate irradiance, divide the net voltage reading in Volts by the Calibration Scale Factor" First convert raw sensor value from millivolts to volts Subtract .0019 - Probe Dark output voltage in volts from cal sheet Divide by the Calibration Scale Factor, 5.8731 V/(uE/cm2sec) __________________________________________________ Time to waypoint; RMB (WP_time) Time (hrs) to next waypoint reported by Furuno 1850 GPS receiver ($GPRMB data sentence) __________________________________________________ True wind direction; IMET (Wnd_Dir) Format: xxx.x (degrees) Wind direction obtained from the IMET wind sensor and corrected for sensor alignmaent, ship heading (gyro) and ship course and speed (GPS SOG & COG). A 0 degree wind comes from the north. __________________________________________________ True wind direction; WXT ( TWD5) True wind direction (degrees) Values are calculated from the Vaisala WXT510 Weather Transmitter raw data corrected for sensor alignment error and combined with the ship’s gyro heading and GPS SOG and COG values. __________________________________________________ True wind speed; IMET (Wnd_Spd) Format: xx.xxxx (meters/sec) Wind speed obtained from the IMET wind sensor and corrected for ship heading (gyro) plus ship course and speed (GPS SOG & COG). __________________________________________________ True wind speed & direction (TWind) Format: Speed, Direction (meters/sec, degrees) Values are calculated from the IMET wind xy raw data. Wind direction is given in meteorological terms; a 0 degree wind comes from the north. Ship speed and direction of travel are obtaned from GPS data (GGA SOG & COG). Sensor mounting orientation is corrected using the direction the ship is pointing obtained from the gyro (the ship is not necessarily moving in the direction its pointing). __________________________________________________ True wind speed & direction; WXT ( TWnd5) True wind speed (m/s) and direction (degrees) Data Format xx.x, xxx Values are calculated from the Vaisala WXT510 Weather Transmitter raw data corrected for sensor alignment error and combined with the ship’s gyro heading and GPS SOG and COG values. Wind direction is given in meteorological terms; a 0 degree wind comes from the north. Ship speed and direction of travel are obtaned from GPS data (GGA SOG & COG). Sensor mounting orientation is corrected using the direction the ship is pointing obtained from the gyro (the ship is not necessarily moving in the direction its pointing). __________________________________________________ True wind speed; WXT ( TWS5) True wind speed (m/sec) Data Format xx.x Values are calculated from the Vaisala WXT510 Weather Transmitter raw data corrected for sensor alignment error and combined with the ship’s gyro heading and GPS SOG and COG values. __________________________________________________ Turner fluorometer data (TF10_data) Fluorometer data from Turner Designs Model 10. Full scale = 1 volt (1000.00 from MetraByte A/D module). Exact value is not in agreement with instrument front panel meter due to the characteristics of the calibration resistor. Science party is responsible for recording comparative readings during the cruise if needed. __________________________________________________ Turner fluorometer range (TF10_Range) Fluorometer range setting from Turner Designs Model 10 (full scale = 1 volt). Actual values reported by the MetraByte A/D module (1000.00=1 volt) are not in agreement with the value indicated in the Turner manual due to the accuracy of the calibration resistor. Actual readings are per the following table (science party should check these values at some point during the cruise): Range Expected Actual X0 0.0v 000.10 X3.16 0.4v 488.60 X10 0.7v 831.00 X31.6 1.0v 9999.99 __________________________________________________ WXT510 #5 ( WXT5) Vaisala WXT510 Weather Transmitter Data Format: WXT5 39240.67178 16:07:22 5R0,Dm=048D,Sn=0.0M,Sm=0.1M, Sx=0.2M,Ta=24.5C,Ua=35.7P,Pa=1018.2H,Rc=0.00M,Ri=0.0M WXT5 39240.67178 16:07:22 = Calliope designator and time values (time stamps are GMT) 5R0 = Instrument's polled data request cmd (“5” is inst address) Dm = Wind direction, deg (2 Hz samples, 10 sec average) 0 deg wind comes over the bow Sn = Wind speed min, m/sec (2 Hz, 10 sec sample period) Sm = Wind speed average, m/sec (2 Hz, 10 sec sample period) Sx = Wind speed max, m/sec (2 Hz, 10 sec sample period) Ta = Air temperature, degrees C Ua = Relative humidity, % Pa = Barometric pressure, hPa Rc = Rain accumulation, mm (accumulation is updated in 10 sec intervals) The accumulation value is reset only when the sensor power is reset. Ri = Rain intensity, mm/hour Wind speed and direction are given in meteorological terms: a “0” degree wind comes from the bow; a “90” degree wind comes from the Stbd side. Wind speed and direction values are ship relative and direction has not been corrected for mounting alignment error. Wind sampling is done at 2 Hz and averaged over 10 seconds - new data is available at 10 sec intervals. __________________________________________________ Wind XY velocities; IMET ( WND_XY) Meters/second - not corrected for sensor alignment or ship motion. This data item is utilized by the IMET true wind speed and direction calculations. __________________________________________________ Wyse (data) ( Wyse_data) __________________________________________________ __________________________________________________ Defined constants: IMETSensorOffset = 0.0 WXT5SensorOffset = 0.0 WS425SensorOffset = 0.0 __________________________________________________ __________________________________________________ Auxiliary information: Calliope Data Files August 8, 2008 General considerations - The Calliope system does not normally log all the data available or all the data it obtains and uses internally; it logs a subset on a timed basis individually specified for each data item. Data is frequently obtained and used for calculations without being logged due to a difference between the data collection interval and the log cycle. If the log file recording rate was not the same as the data collection rate, post-processing calculations may not give the same answers as the originals even though all calculations are done correctly. This is because the original calculations would have new data available at the collection rate whereas post-processing would only have the logged data subset. The true wind calculation provides a good example; determining true wind speed and direction requires the wind sensor data plus heading from a compass or gyro and COG and SOG from a GPS. Normally heading data is obtained at a rapid rate compared to wind data but they are both recorded at about the same interval. This means that when the Calliope code makes the true wind calculation it is likely to use newly obtained heading data, which may not be logged. Clearly, attempting to check the Calliope calculations using the logged data will be difficult but, if the logging rates have been chosen reasonably, post-processing will provide valid, useful results. Log Files - The Calliope system generates data files of two types: 1) asynchronous, single-item-per-line, time stamped ASCII and 2) aynchronous, multi-item-per-line, comma delimited (CSV). A single file of the first type is always created containing data items logged at the time interval specified by the Calliope configuration. Each line starts with a data identifier followed by the date and time given in the form used by Visual Basic (number of days since Dec. 31, 1899; the 31st is day #1) and then the time in normal human readable form. These values are followed by the data terminated with a . Log files are normally created at midnight GMT and the name of the file provides ship and creation date information with a “.dat” extension. The date value within the file name is always based on GMT. The first line of the file provides ship, date and initialization local time information. The second line indicates the local time zone and the third provides a reminder that Calliope data timestamps are always GMT. This is followed by a line containing “****” indicating the start of recorded data. The Calliope data collection application always uses GMT timestamp values regardless of the time zone setting of the application computer. However, the start time for new data files is controlled by an entry in the configuration file. Regardless of when a file is started, the date information used to construct the file name is based on GMT. Note however that any date and time information included in the data file headers is local time. If date or time values are included in data files as logged values, these will also be local values (with GMT timestamps). Time values are handled in this manner to allow more convenient use of local time for controlling Calliope’s activities if desired. As an example, starting new files at a particular local time can be preferable to midnight GMT when instrumentation deployment activities are scheduled on a daily basis. Note that GMT will be used exclusively if the computer’s time is set to GMT. All lines after the header’s “****” contain data as shown in the following example taken from an Oceanus file named “OC020915.dat”. For this example, most items are being logged at 1-minute intervals; HEHDT, PKEL99, Salinity, and SSV are exceptions. The header indicates that the Calliope computer was set to Azores Standard Time, which is one hour behind GMT. The file was started at approximately midnight local time and the timestamps reflect the 1 hour difference between local and GMT. R/V Oceanus Calliope data file, Sun 15/Sep/2002 00:00:11 Current time zone: Azores Standard Time (GMT-1) Data timestamps are GMT **** IMET_WND 37514.00031 01:00:26 1.14 –2.55 2.8 3.3 2.4 161.2 0 4 IMET_HRH 37514.00031 01:00:26 99.253 19.819 IMET_SWR 37514.00031 01:00:26 0.1 IMET_BPR 37514.00031 01:00:26 1021.66 IMET_PRC 37514.00032 01:00:27 -0.00 0.00 7.69 SSTMP 37514.00032 01:00:27 +24.6322 SSCND 37514.00032 01:00:27 +50.0594 HEHDT 37514.00032 01:00:27 $HEHDT,025.7,T PKEL99 37514.00034 01:00:29 $PKEL99,15.01,00.00,1500 Salinity 37514.04216 01:00:42 33.0489 SSV 37514.04216 01:00:42 1531.3961 TWind 37514.04216 01:00:43 2.7932 181.6 GPS 37514.04217 01:00:44 $GPGGA,010043.043,4131.4319,N, 07040.3348,W,3,08,1.0,026.0,M,034.4,M,,*75,$GPGXP,010043,4131.4319,N,07 040.3348,W*5D,$GPGLL,4131.4319,N,07040.3348,W,010043.043,A*21,$GPVTG,34 1.5,T,357.1,M,000.0,N,000.0,K*4D HEHDT 37514.04228 01:00:58 $HEHDT,025.7,T IMET_WND 37514.04249 01:01:11 1.14 -2.55 2.8 3.3 2.4 161.2 0.0 0 4 IMET_HRH 37514.04266 01:01:26 99.253 19.818 IMET_SWR 37514.04266 01:01:26 0.1 IMET_BPR 37514.04267 01:01:26 1021.71 IMET_PRC 37514.04267 01:01:27 0.00 0.00 7.69 SSTMP 37514.04268 01:01:27 +24.6304 SSCND 37514.04268 01:01:28 +50.0560 HEHDT 37514.04268 01:01:28 $HEHDT,025.6,T TWind 37514.04286 01:01:43 2.8356 183.7 GPS 37514.04286 01:01:43 $GPGGA,010142.043,4131.4306,N, 07040.3343,W,3,08,1.0,028.3,M,034.4,M,,*7D,$GPGXP,010142,4131.4306,N,07 040.3343,W*58,$GPGLL,4131.4306,N,07040.3343,W,010142.043,A*24,$GPVTG,34 1.5,T,357.1,M,000.0,N,000.0,K*4D HEHDT 37514.04306 01:01:58 $HEHDT,025.7,T IMET_WND 37514.04318 01:02:11 1.06 -2.63 2.8 3.5 2.4 165.3 0.0 0 4 IMET_HRH 37514.04336 01:02:26 99.253 19.804 IMET_SWR 37514.04336 01:02:26 0.0 IMET_BPR 37514.04336 01:02:26 1021.70 IMET_PRC 37514.04336 01:02:26 0.00 0.00 7.70 SSTMP 37514.04337 01:02:27 +24.6314 SSCND 37514.04337 01:02:27 +50.0593 HEHDT 37514.04337 01:02:27 $HEHDT,025.7,T PKEL99 37514.04339 01:02:29 $PKEL99,15.02,00.00,1500 Salinity 37514.04354 01:02:42 33.0511 SSV 37514.04354 01:02:42 1531.3987 TWind 37514.04354 01:02:42 2.5863 181.0 Note that the GPS data in the above example contains line-formatting characters that are not normally present in the real data files. The GPS data item above was defined as four NMEA sentences and the Calliope program concatenates multi-line data, replacing line termination characters with commas. characters are only present at the end of each data item. The “CSV” format file uses the same naming convention except that an underscore and two-digit number follow the date/time. The extension is always “csv”. CSV files are normally started at midnight GMT but the start time can be delayed by an amount specified in the configuration file. CSV files begin with a header line that identifies the ship and a line that identifies the data items in each of the following comma delimited columns. The last item in this second line is always the header line’s checksum. The content of these files can be changed by a number of methods and if this is done, a new file is created having a new file name; the two-digit number following the underscore is incremented. The header line identifying the file’s data items is also corrected. The rate at which data is added to a CSV file is normally once per minute but this can be changed by an entry in the Calliope configuration file. Each line begins with a date and GMT time stamp and contains the most recent data available at the time of the entry. Data is not repeated; if new data is not available when a line is to be added, the corresponding column is left blank. The final item in each line is the checksum of the data identifier header line - not the data line’s checksum. This is included so that when data lines of this type are broadcast to other applications, it is possible for these applications to determine if the correct header is being used. The following is an example taken from the file “OC020915_00.csv”. R/V Oceanus Calliope CSV data file (timestamps are GMT) Date, Time, SSTMP, SSCND, Gyro, Salinity, Wnd_Spd, Wnd_Dir, Depth, HdChkSum=OF 2002/09/15, 00:00:25, +24.630, +50.058, 025.7, 33.049, 2.67, 185.4, 115.01, 0F 2002/09/15, 00:01:25, +24.631, +50.060, 025.6, 33.050, 2.79, 181.5, 115.02, 0F 2002/09/15, 00:02:25, +24.631, +50.059, 025.7, 33.050, 2.83, 183.7, 115.01, 0F 2002/09/15, 00:03:25, +24.633, +50.057, 025.7, 33.047, 2.58, 181.0, 115.03, 0F 2002/09/15, 00:04:25, +24.633, +50.060, 025.7, 33.049, 2.43, 181.8, 115.06, 0F 2002/09/15, 00:05:25, +24.633, +50.057, 025.6, 33.046, 2.66, 178.1, 115.01, 0F 2002/09/15, 00:06:25, +24.633, +50.057, 025.7, 33.047, 2.49, 179.5, 115.01, 0F 2002/09/15, 00:07:25, +24.632, +50.060, 025.6, 33.050, 2.71, 181.5, 115.01, 0F 2002/09/15, 00:08:25, +24.632, +50.061, 025.7, 33.051, 3.02, 179.2, 115.03, 0F 2002/09/15, 00:09:25, +24.632, +50.058, 025.7, 33.048, 2.76, 180.6, 115.04, 0F 2002/09/15, 00:10:25, +24.630, +50.058, 025.7, 33.049, 3.03, 178.9, 115.03, 0F 2002/09/15, 00:11:25, +24.632, +50.058, 025.7, 33.048, 3.47, 178.2, 115.02, 0F Special Files - A Calliope file entry transaction definition can define special files having a specified name and data content. The data format will be as described above for the asynchronous .dat file. Files of this type are generally used to record a limited amount of data, possibly triggered by an “event” of some nature. Raw Data Files - The Calliope data input code can be configured to time stamp (GMT) and log all data received on a particular port. The same file name can be specified for more than one port allowing a single raw data file to hold a number of different data items. Raw data file names are specified when the files are activated; Calliope appends the yymmdd date and will always use a ".dat" extension (i.e. Pitch_080415.dat). Metadata The Calliope system generates a metadata file (Metadata.txt - possibly this file). This is a simple text file containing information on the various data sources listed by sensor name and the designator used in the header information of the primary data file types. The file also lists the constants defined by files in the Constants directory (i.e. calibration constants) and includes a copy of the file Metadata2.txt (located in the Calliope/Metadata directory), which can contain addition information entered by the application user. Hopefully, the resulting Metadata file contains enough information to make effective use of the data contained in the other files (i.e. format, units, sensor type, calibration dates, etc.). In addition, there may be a second metadata file in the primary data directory named MetaDataAux.txt. This file is intended to provide a location for initialization and other functions to store useful but non-data information obtained from sensor interrogations (such as the calibration date of an IMET sensor). Timestamp formats The Calliope data collection application always uses GMT timestamp values regardless of the time zone setting of the application computer. Also, the date used to generate the name of a data file is based on GMT. However, new files are not necessarily started at midnight GMT (file start times are controlled by an entry in the Calliope configuration file) and any date and time information included in data file headers is local time. If date or time values are included as logged values in data files, these will also be local values. The Calliope ".dat" data file headers indicate the local time zone setting when the file was started. Individual items in Calliope ".dat" data files are time stamped with two different formats. The first timestamp value is in the format used by Microsoft Visual Basic: the number of days since December 31, 1899 (Dec. 31 is day 1, not day 0). Its primary purpose is to provide a continuously increasing date and time indicator for use in data graphing applications. The VB format facilitates this for some applications but converting the number to the normal human readable form can be painful. The second timestamp value (hh:mm:ss format) in combination with the date in the file header may eliminate the need for this conversion. If not, the following may be helpful: 00.00 is 00:00:00 on Dec. 30, 1899. 00.50 is 12:00:00 (noon) on the same day. 35390.58333 is 14:00:00 May 15, 1998.