adcp_P1_1_a.txt : revisit cruise for P1 leg1
adcp_P1_1_b.txt : revisit cruise for P1 leg1
adcp_P14_1_a.txt :revisit cruise for P14 leg1 (& a part of the P1 revisit)
adcp_P14_1_b.txt :revisit cruise for P14 leg1 (& a part of the P1 revisit)
adcp_P14_2_a.txt :revisit cruise for P14 leg2
adcp_P14_2_b.txt :revisit cruise for P14 leg2
Data structure of each profile
(1) adcp_***_*_a.txt
The file consists of 239 profiles on the CTD site. Each profile consists of header and data. The header has three lines representing analyzed site, date and time, and position. The data has 68 layers in which depth, zonal velocity, meridional velocity, and vertical velocity of each grid are stored. Unit of depth is in meter.
Unit of flow is in m/s. On the CTD station, the CTD station name (e.g. "143_1") is recorded as the analyzed site in the header.
Mean time and position were calculated and recorded using the ADCP profiles during the CTD operation was made. The "99.999" f in the data represents no available data stored.
[ data structure of the data set A ]
Line 1: header 1
Column 1: cruise code
Column 2: analyzed site
Line 2: header 2
date
Line 3: header 3
Column 1: longitude (degree E)
Column 2: latitude (degree N)
Flow data processed in every three minutes are stored in the data set B.
The data structure is the same as that of the data set B, except for the analyzed site in the header 1.
[ data structure of the data set B: every 3 minutes ]
Line 1: header 1
Column 1: cruise code
Column 2: sequatial record number
Line 2: header 2
date
Line 3: header 3
Column 1: longitude (degree E)
Column 2: latitude (degree N)