Date: Thu, 28 Mar 2024 18:26:26 +0000 (UTC) Message-ID: <1396971417.31.1711650386208@dcconf.dc.onc> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30_1007149023.1711650386207" ------=_Part_30_1007149023.1711650386207 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This is a description of this raw DOPPLER mode data from COVIS.
Oceans 3.0 API filt=
er: dataProductCode=3DCPDRF
The TAR.GZ files contain the raw data and the metadata needed to process= and interpret in files of CSV, JSON and BIN formats. The following table l= ists the types of files and the information each contains. All of the JSON = files are ascii text and human readable (with some effort). Similarly the C= SV files can be read directly as ascii or loaded into a spreadsheet program= like Excel. The BIN files are binary. Further details are supplied within = the examples below.
File Type |
Contents |
---|---|
sweep.json |
Main metadata including timestamp, acquisitio= n mode (=E2=80=9Cimaging=E2=80=9D), and various sonar parameters (transmit = pulse length, frequency, etc.). Some parameters can be set by direct intera= ction with the sonar and some are fixed. |
attitude.csv |
This contains data from the attitude sensor (= time, pitch, roll, heading). All measurements are in degrees. Pitch and Rol= l are gravity referenced. Heading is magnetic. There is one record per rota= tor stop. |
rotator.csv |
This file contains data from the rotator moto= rs (pitch, roll, yaw). All measurements are in degrees relative to an arbit= rary reference. There is one record per rotator stop. |
index.csv |
This file is derived from the above two files= but contains one record per sonar ping. It lists the pings (numbering from= 1 up) and gives the time (seconds, microseconds), rotator data (pitch, rol= l, yaw), and attitude data ( pitch, roll, heading) for each ping. |
rec_7000_xxxxxx.json |
These are the metadata for each ping. Some of= this information may overlap with sweep.json and some of it is set by the = experimenter. |
rec_7038_xxxxxx.bin |
These are the actual data files ping-by-ping.= They are in binary format. There should be one rec_7038_x.bin for every re= c_7000_x.json. |
Oceans 3.0 API filt= er: extension=3Dtar
Examples:
The examples are from APLUWCOVISMBSONAR001_20101001T121520.649Z-DOPPLER.= tar.gz
attitude.csv =E2=80=93 This the first three lines of a particul= ar file.
time=09kPAngle=09kRAngle=09kHeading 15:20.8=0918.73=090.07=09213.98 15:29.1=0919.69=090.07=09214.08
where
index.csv =E2=80=93 This the first three lines of a particular = file.
ping=09seconds=09microseconds=09pitch=09roll=09yaw=09kPAngle=09kRAngle= =09kHeading 1=091.29E+09=09145954=09201.3=09225.5=09132=0918.7=090.1=09214 2=091.29E+09=09351400=09201.3=09225.5=09132=0918.7=090.1=09214
where the columns are
Note that the attitude and rotator data should be consistent but may dis= agree since they are independently measured.
rotator.csv
time=09pitch=09roll=09yaw 15:20.8=09201.3=09225.5=09132 15:29.1=09200.2=09225.5=09132
where the columns are
rec_7000_xxxxxx.json =E2=80=93 Reson format for ascii metadata = file documented in rec7000.pdf
rec_7038_xxxxxx.bin =E2=80=93 Reson format for binary data docu= mented in rec7008.pdf
Note that the data format is basically the same for the Doppler and = ;Imaging imaging modes (the Diffuse mode is slightly different mostly because the pitch= of the sonar is constant).
The difference in the modes relates to the sonar setup, that is which re= ceiver and transmitter are used or what pulse length is used. The table bel= ow listed the relevant parameters for each period of ongoing operation.
Sweep count, start position, position increments, position steps, and se= ttling time control the operation of the rotators. Ping count, ping rate, a= nd delay control the overall collection of pings as well as how the pings a= re coordinated with the rotator motions. Two different source transducers a= re available (200 kHz and 400 KHz); different modes use different transmitt= ers. The sonar range controls how long the sonar listens and records for ea= ch ping (sufficient time for two way travel over the specified range). The = pulse width controls the resolution along the ping. Transmit power controls= the energy put into the water with each ping. Reciever gain controls how m= uch the received signal is amplified before digitizing. All the rest of the= relevant parameters (like sampling rate for the digitization) are the same= for all three modes. This information is collected in the sweep.json files= , whether it varies between mode or not.
To comment on this product, click Add Comment below.