-
Notifications
You must be signed in to change notification settings - Fork 31
OtherMakes
This page lists the rest of the instrument Makes and Models which are supported by the toolbox, and the data formats required for each of them. If you have some data from an unsupported instrument or format, submit an issue with details and files examples, and I'll look into adding support for this new instrument/format.
The toolbox is able to parse a .txt ASCII file from an Aaderaa MCR-8 and Seaguard RCM. It uses the RCM parser.
The toolbox is able to parse a .csv ASCII file from a JFE Infinity logger model ACLW2-USB produced by firmware v1.57 or JFE siftware v1.06. It uses the infinitySDLogger parser. A file produced by firmware v1.57 looks like:
//Infinity SDlogger
//Ver1.57
[Head]
SondeName=ACLW-USB
SondeNo=0341
SensorType=T0K0U3B0
Channel=4
DelayTime=0
PreHeat=10000
MeasMode=0
BurstTime=1
BurstCnt=1
Interval=1000
WiperInterval=0
SampleCnt=168
StartTime=2016/01/12 04:19:00
EndTime=2016/01/12 04:21:47
CHLA=0
CHLB=1
CoefDate=2015/08/24
Ch1=-6.844049e+00,+1.098076e-03,-9.044546e-09,+1.195099e-13,+0.000000e+00,+0.000000e+00,+0.000000e+00,+0.000000e+00,
Ch2=-5.783819e+00,+8.066693e-03,+0.000000e+00,+0.000000e+00,+0.000000e+00,+0.000000e+00,+0.000000e+00,+0.000000e+00,
Ch3=-8.747382e+00,+1.326119e-02,+8.063878e-08,-9.240077e-14,+0.000000e+00,+0.000000e+00,+0.000000e+00,+0.000000e+00,
Ch4=0.000000000e00,1.152000000e-04,0.000000000e00,0.000000000e00,0.000000000e00,0.000000000e00,0.000000000e00,0.000000000e00,
BuzzerEN=0
BuzzerInterval=1
COMMENT=eyer
SensorType2=03020202
BuzzerNumber=3
[Item]
Date,Temp.[deg C],Chl-Flu.[ppb],Chl-a[ug/l],Turb. -M[FTU],Batt.[V],
2016/01/12 04:19:00,23.418,18.75,18.75,0.45,3.27,
2016/01/12 04:19:01,23.418,18.72,18.72,0.48,3.27,
2016/01/12 04:19:02,23.419,18.73,18.73,0.48,3.27,
2016/01/12 04:19:03,23.420,18.71,18.71,0.47,3.27,
2016/01/12 04:19:04,23.420,18.71,18.71,0.48,3.27,
2016/01/12 04:19:05,23.421,18.73,18.73,0.45,3.27,
2016/01/12 04:19:06,23.422,18.72,18.72,0.47,3.27,
2016/01/12 04:19:07,23.422,18.71,18.71,0.48,3.27,
2016/01/12 04:19:08,23.423,18.73,18.73,0.47,3.27,
2016/01/12 04:19:09,23.423,18.69,18.69,0.45,3.27,
2016/01/12 04:19:10,23.424,18.71,18.71,0.45,3.27,
2016/01/12 04:19:11,23.425,18.72,18.72,0.47,3.27,
All of the entries in the header starting from [Head] are read as well as the data starting from [Item]. So far the following data columns are supported:
- Date
- Temp.[deg C]
- Chl-a[ug/l]
- Turb. -M[FTU]
- Batt.[V]
The toolbox is able to read the data from a .csv file retrieved from a VEMCO Minilog-II-T Temperature Recorder using the Vemco parser. The supported .csv format is produced via an export option of the Vemco Logger Vue software. The parser reads specific instrument header format and converts the data. The files consist of two sections:
- processed header : header information generated by Logger Vue software. Typically first 8 lines. Header information name and value are separated by a colon ":".
Example :
Source File: \\aims.gov.au\home\user\My Documents\Vemco\LoggerVUE\Minilog-II-T_354350_20140213_1.vld
Source Device: Minilog-II-T-354350
Study Description: TAN100
Minilog Initialized: 2013-08-04 05:02:17 (UTC+10)
Study Start Time: 2013-08-05 00:00:00
Study Stop Time: 2014-02-13 11:12:00
Sample Interval: 00:01:00
Date(yyyy-mm-dd),Time(hh:mm:ss),Temperature (°C)
The following header information is read:
-Source Device -Study Start Time -Study Stop Time -Sample Interval
It is assumed that the last line of the header is the one starting with "Date".
- data : Rows of comma seperated data.
It is assumed that date and time would always be the first and second column.
Example :
2013-08-05,00:00:00,22.05
2013-08-05,00:01:00,22.06
2013-08-05,00:02:00,22.06
2013-08-05,00:03:00,22.06
2013-08-05,00:04:00,22.07
2013-08-05,00:05:00,22.07
2013-08-05,00:06:00,22.07
2013-08-05,00:07:00,22.08
The toolbobx is able to read the data from a .DAT file retrieved from a Starmon mini Temperature Recorder using the StarmonMini parser. The supported ASCII file format is the .DAT file described in the Starmon mini user manual. % The files consist of two sections:
- file headerContent : Each header item is contained in one line, and all header lines start with a '#' (bookmark) and a number. Then follows a description of the header item, and then 1-4 directives, all separated by tabs. Eventually a comment trails the directives, preceded by a ';' (semicolon).
Example :
#0 Date-time: 9/06/2013 1:18:40
#1 Recorder: 3T4098
#2 File type: 1
#3 Columns: 3
#4 Channels: 1
#5 Field separation: 0
#6 Decimal point: 0
#7 Date def.: 0 0
#8 Time def.: 0
#9 Channel 1: Temperature(°C) Temp(°C) 2 1
#11 Reconvertion: 0
#19 Line color: 1 2 3 4; comment
#30 Trend Type Number: 1
#33 Limit Temp. Corr. OTCR: 0
- data : The first column is the measurement number, the second column the date and the time, depending on the set-up. The third column is the time or the first measured parameter, depending on set-up. The following column(s) contain the converted measured parameters with units and number of decimals according to set-up. Number of parameters can range from 1-3, and number of columns 3-6 accordingly.
Example :
1 01.04.12 00:00:00 25,22
2 01.04.12 00:04:00 25,30
3 01.04.12 00:08:00 25,32
4 01.04.12 00:12:00 25,51
5 01.04.12 00:16:00 25,24
6 01.04.12 00:20:00 25,15
7 01.04.12 00:24:00 25,51
8 01.04.12 00:28:00 25,49
9 01.04.12 00:32:00 25,25
The toolbobx is able to read the data from a .DAT file retrieved from a Starmon DST Tilt or Starmon DST CTD, using the StarmonDST parser. DST Tilt format consists in:
#0 Date-time: 29/10/2013 12:55:14 AM
#1 Recorder: 3X1010
#2 File type: 1
#3 Columns: 6
#4 Channels: 4
#5 Field separation: 0
#6 Decimal point: 1
#7 Date def.: 0 0
#8 Time def.: 0
#9 Channel 1: Temperature(°C) Temp(°C) 3 1
#10 Channel 2: Depth(m) Depth(m) 3 2
#11 Reconvertion: 0
#14 Channel 3: Pitch(°) Pitch(°) 1 1
#18 Channel 4: Roll(°) Roll(°) 1 1
#19 Line color: 1 2 3 4
#30 Trend Type Number: 1
#33 Limit Temp. Corr. OTCR: 0
1 14.07.12 00:00:00 6.146 -46.861 -6.3 -0.2
2 14.07.12 00:10:00 6.216 -46.706 -1.2 -0.2
3 14.07.12 00:20:00 6.287 -46.552 1.9 -1.9
4 14.07.12 00:30:00 6.357 -47.344 0.2 -2.9
5 14.07.12 00:40:00 6.462 -46.640 -2.3 -0.7
6 14.07.12 00:50:00 6.602 -46.808 3.4 -4.0
7 14.07.12 01:00:00 6.706 -47.052 -2.3 -1.2
8 14.07.12 01:10:00 6.846 -47.222 3.2 -3.3
9 14.07.12 01:20:00 6.950 -46.996 2.4 -3.3
10 14.07.12 01:30:00 7.088 -47.168 0.1 -1.0
...
While DST CTD format is:
#B Created: 12/12/2016 15:49:24
#5 Field separation: 0
#2 Date & Time: 1
#6 Decimal point: .
#7 Date def.: dd/mm/yyyy /
#8 Time def.: :
## Axis 0 Temperature(°C) clRed False
## Series 0 Temp(°C) clRed 0 Temp(°C) 2
## Axis 1 Pressure(Bar) clBlue False
## Series 1 Press(Bar) clBlue 1 Press(Bar) 2
## Axis 2 Salinity(psu) clGreen False
## Series 2 Salinity(psu) clGreen 2 Salinity(psu) 2
## Axis 3 Conductivity(mS/cm) $00FF80FF False
## Series 3 Conduct(mS/cm) $00FF80FF 3 Conduct(mS/cm) 2
## Axis 4 Sound Velocity(m/sec) $00404080 False
## Series 4 Sound Velocity(m/sec) $00404080 4 Velocity(m/sec) 2
## Recorder 2 DST CTD 8171
## Chart 2S8171DAT
#D Data: 87216 02/03/2016 00:00:00 29/12/2016 19:55:00
1 02/03/2016 00:00:00 15.33 -0.06 0.00 0.00 1466.34
2 02/03/2016 00:05:00 15.46 -0.06 0.00 0.00 1466.77
3 02/03/2016 00:10:00 15.61 -0.06 0.00 0.00 1467.29
4 02/03/2016 00:15:00 15.82 -0.06 0.00 0.00 1468.03
5 02/03/2016 00:20:00 16.00 -0.06 0.00 0.00 1468.65
6 02/03/2016 00:25:00 16.18 -0.06 0.00 0.00 1469.27
7 02/03/2016 00:30:00 16.36 -0.06 0.00 0.00 1469.89
8 02/03/2016 00:35:00 16.54 -0.06 0.00 0.00 1470.50
9 02/03/2016 00:40:00 16.72 -0.06 0.00 0.00 1471.11
10 02/03/2016 00:45:00 16.93 -0.07 0.00 0.00 1471.81
The toolbobx is able to read the data from a .csv file retrieved from a ReefNet Sensus Ultra logger using the sensusUltra parser. The supported file has no header and consists in a comma separated list of values with columns ordered as follow :
-
dive id(integer) -
instrument serial number(string) -
unknown(string) -
start year(integer, time - required) -
start month(integer, time - required) -
start day(integer, time - required) -
start hour(integer, time - required) -
start minute(integer, time - required) -
start second(integer, time - required) -
ellapsed millisecond(integer, time - required) -
pressure(integer, absolute pressure, mbar) -
temperature(floating point, temperature, Kelvin)
The toolbox is able to parse raw data file retrieved from an Aquatec AQUAlogger 520 using the aquatec parser. The AQUAlogger 520 range of sensors provide logging capability for temperature and pressure. The following variants on the AQUAlogger 520 exist:
- 520T: temperature
- 520P: pressure
- 520PT: pressure and temperature
The raw data file format for all loggers is identical; every line in a file, including sample data, is a key-value pair, separated by a comma. The following lines are examples:
VERSION,3.0
LOGGER TYPE,520PT Pressure & Temperature
LOGGER,23-502,SYD100 T2
DATA,23:00:01 24/06/2008,29412,16.310779,26345,1.025358,
DATA,23:00:02 24/06/2008,29411,16.312112,26346,1.025938,
If the logger was configured to use burst mode, the bursts are averaged.
Pressure values equal to 65535bar are ignored (happens when a T logger feeds its P channel with rubbish) and set to NaN.
The toolbox is able to import raw (.ctd) files retrieved from an NXIC CTD instrument, and parse the conductivity, temperature and depth data contained within it using the NXICBinary parser. A specification for the .ctd file format is not available, so the toolbox relies upon reverse engineering efforts which may not be reliable. I am unsure as to whether data retrieved from instruments with a firmware version older than 4.42 can be imported into the toolbox.
Currently, the parser only provides conductivity, temperature and pressure data. I am in contact with FSI regarding access to the file format specification, and hope to provide auxillary sensor data in the near future.
The toolbox is able to read in files retrieved from YSI 6-series data loggers (only the 6600 v2.4 has been tested) using the YSI6Series parser. YSI have not published details of the binary file format, so the toolbox relies upon reverse engineering efforts which may not be completely reliable.
The toolbox includes a draft attempt to parse an EchoView results comma separated variable (CSV) file using the echoview parser.
This function is almost a generic CSV Parser. The list of fields to define and the column names that populate those fields are defined in a text file ./Parser/echoview_config.txt or the file specified by the property 'echoview.config' if defined in toolboxProperties.txt.
Limitations:
- Text quoting is not properly supported (fields cannot contain ,)
- Dates are only supported in the format yyyymmdd
- Times are only supported in the format HH:MM:SS.ss
- Timestamps are only supported as a date field followed by a time field yyyymmdd, HH:MM:SS.ss
The toolbox now includes a first attempt to parse NIWA's processed output ASCII file format .DAT3 using the NIWA parser as follow :
s0910ver1.DAT3 filename 1
mcat 7285 instrument type and Serial # 2
35 15.843 S 174 06.102 E lat lon (dd mm.mmm) 3
Veronica Channel, Bay of Islands description of location 4
6 5.85 water depth,meter height - m 5
2009-10-06 15:50:01, 2010-04-20 13:20:01, +12 record start/finish time & zone 6
0 0 10 0 data gap interval d,h,m,s 7
severely fouled on recovery 8
. Processed using pmd.m and read_mcat 14-Dec-2012 11:37:19 9
Green nav pile in Veronica Channel 10
Quality control by BSG using qcmd_save.m 14/Dec/2012 11
12
13
14
15
16
17
18
time con tem pre sal
yyyy-mm-dd HH:MM:SS s/m degc dbar psu
2009-10-06 15:50:01 4.020 15.176 0.9 32.386
2009-10-06 16:00:01 4.025 15.251 1.0 32.368
2009-10-06 16:10:01 4.026 15.264 1.1 32.367
...
Sampling interval and comments are read out of the header. Other information are redundant with what can be found in the .meta file (metadata) which will be used to populate the deployment database.
NetCDF file format that are IMOS ANMN compliant should be read by the toolbox using the netcdf parser. However, when the file also exists in the original instrument format, is supported by the toolbox and referenced in a deployment database, then it is recommended to use the original instrument file along with the deployment database.