R/V Tioga Calliope metadata file Mon 14/May/2012 19:39:16 Current time zone: GMT Standard Time ================================================== Air temperature ( TMP1) Format: xxx.xx degrees Celsius __________________________________________________ Air temperature (aux) ( TMP2) Format: xx.x degrees Celsius This is a rough air temperature value obtained from the barometric pressure sensor located in a junction box on the ship's mast. Values are likely to be high during the daylight hours of sunny days. __________________________________________________ Aux air temperature (raw) ( TMP2_Raw) Format: xx.x degrees Celsius This is a rough temperature value obtained from the barometric pressure sensor located in a junction box on the ship's mast. Values are likely to be high during the daylight hours of sunny days. Note, there will be a space between a leading minus sign and the value. __________________________________________________ Barometric Pressure (BPR) Format: Barometric pressure (milli-bars) Calibration - Jan 2003 __________________________________________________ Sound velocity ( SSV) Format: Sound_Velocity (meters/sec) Surface sound velocity calculated from sea surface temperature and conductivity data values. Intermediate salinity values are calculated in accordance with UNESCO 44. __________________________________________________ Decimal Latitude ( deg_lat) Example: 42.220669 Format: dd.dddddd __________________________________________________ Decimal Longitude ( deg_lon) Example: -71.119579 Format: ddd.dddddd __________________________________________________ Furuno GPS DBT (GPDBT_Furuno) __________________________________________________ Furuno RMC ( GPRMC_Furuno) NMEA RMC position data obtained from the Furuno NAVnet system. __________________________________________________ Furuno Heading Ref GGA (GPGGA_Com4) __________________________________________________ GPS Date ( GPS_DA) Format: ddmmyy Example 300908 = Sept. 30, 2008 Data obtained from GPS RMC NMEA data sentence. __________________________________________________ GPS Time ( GPS_UT) Format: hhmmss Example: 142258 Data obtained from GPS RMC NMEA data sentence. __________________________________________________ GPS course over ground (COG) Course over ground (true) obtained from Garmin GPRMC data sentence. Format: Course, degrees true ddd __________________________________________________ GPS Navigation data (GPS) Garmin 17N GPS receiver The datum used by receiver is WGS84. Caution - SOG is in km/hr rather than knots NMEA PGRMF data sentence: Header $PGRMF 1 GPS week number (0 - 1023) 2 GPS seconds (0 - 604799) 3 UTC date of position fix: ddmmyy 4 UTC time of position fix: hhmmss 5 GPS leap second count 6 Latitude: ddmm.mmmm (including leading zeros) 7 Latitude hemisphere, N/S 8 Longitude: ddmm.mmmm (including leading zeros) 9 Longitude, E/W 10 Mode (2d, 3d), M=manual, A=automatic 11 Fix type, 0 = no fix, 1 = 2d fix, 2 = 3d fix 12 Speed Over Ground (SOG), 0 - 1851 kilometers/hour 13 Course Over Ground (COG), 0 - 359 degrees, true 14 Position dilution of precision, 0 - 9 15 Time dilution of precision, 0 - 9 16 checksum NMEA GPVTG data sentence: Header $GPVTG 1 Course, T (degrees true) 2 Course, M (magnetic) 3 Speed, N (knots) 4 Speed, K (km/hr) 5 * checksum . __________________________________________________ GPS speed over ground (SOG) Speed over ground (knots) obtained from Garmin GPRMC data sentence. Format: Speed Raw data from Garmin GPS receiver $GPRMF sentence provides SOG in km/hr. This can be converted to Knots using km/hr * .5399568 = knots (Note - most GPS receivers provide SOG in Knots) __________________________________________________ Humidity (HRH) Format = xxx.x % relative humidity __________________________________________________ Humidity (raw) (HRH_Raw) __________________________________________________ Knudsen bathymetry ( KND) Knudsen 33 & 200 kHz bathymetry system NMEA output Format: $PKEL99,xx.xx,yy.yy,zzzz*cs $PKEL99 Header xx.xx Depth in meters (200 kHz) yy.yy Depth in meters (33 kHz) zzzz Speed of sound value use for depth determination (m/sec) cs Checksum S/N K2K-04-0143 __________________________________________________ Max Wind Sped ( WIND_Max) meters/second Maximum 5 second wind speed sample over past minute. __________________________________________________ Min Wind Sped ( WIND_Min) meters/second Minimum 5 sec wind speed sample over past minute. __________________________________________________ NMEA Gyro (GPHDT) Ship's heading obtained from Furno GPS receiver array. Format: Header ($GPHDT), Heading (degrees), T (true),* checksum. __________________________________________________ SBE45 MicroTSG ( SBE45) Data format: ttt.tttt, cc.ccccc, sss.ssss, vvvv.vvv t = temperature (degrees Celsius, ITS-90) c = conductivity (S/m) s = salinity (psu) v = sound velocity (meters/second) Conductivity units 10*S/m = mS/cm = mmho/cm __________________________________________________ Sea surface conductivity ( SBE45C) Format: cc.ccccc Conductivity mS/cm Data obtained from Seabird SBE45 MicroTSG This value is 10 times the raw value returned by the SBE45 in order to have units consistant with the FSI thermosalinograph. __________________________________________________ Sea surface fluorometer (FLR) __________________________________________________ Sea surface salinity ( SBE45S) Format: sss.ssss Salinity, psu Data obtained from Seabird SBE45 MicroTSG __________________________________________________ Sea surface sound velocity ( SBE45SV) Format: vvvvv.vvv Sound velocity, meters/second Data obtained from Seabird SBE45 MicroTSG __________________________________________________ Sea surface temperature ( SBE45T) Format: ttt.tttt Temperature, degrees Celsius Data obtained from Seabird SBE45 MicroTSG __________________________________________________ Ship's heading (Gyro) Ship's heading (degrees true) obtained from the Furuno GPS based heading reference (NMEA GPHDT sentence). Format: xxx.x (degrees true) __________________________________________________ True Wind Spd & Dir ( TWND_SD) 5 sec average, m/sec, 0-359 degrees Raw data corrected for ship heading, COG & SOG __________________________________________________ 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 __________________________________________________ WX Wind direction (ship relative) (WXWnd_dir) __________________________________________________ WX Wind speed & direction (WXWND) Format: E.E N.N S.S X.X M.M Wind E (m/sec), Positive for a stbd to port wind Wind N (m/sec), Positive for a bow to stern wind Wind S, (m/sec), Averaged over previous 5 sec. Wind X, (m/sec), max of 5 sec samples for past minute. Wind M (m/sec), min of 5 sec samples for past minute. Calibration - Jul 2003 __________________________________________________ Wind spd & dir (raw data reformated) ( WND_SD) Values are not corrected for vessel heading and motion (see TWND_SD). Speed (m/s), Direction (0-359 degrees) __________________________________________________ Wind Direction ( WND_DIR) Wind direction (0-359 degrees) corrected for ship's heading and motion. Value is averaged over 5 seconds. __________________________________________________ Wind Speed ( WND_SPD) Format: WndSpd (meters/sec) corrected for ship's heading and motion. Value is averaged over 5 seconds. __________________________________________________ __________________________________________________ Defined constants: UPD = Mag_Dev = 18.0 WindSensorOffset = +180 WXWindOffset = 000 __________________________________________________ __________________________________________________ Auxiliary information: Calliope Data Files September 2, 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) synchronous, 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 consistant local time 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.