File(s) | Type | Description | Action |
---|---|---|---|
all_moorings_files.tar.gz (10.08 GB) | GZIP (.gz) | This package contains 6 .csv files. Those named starting with "AMLR1" are from the AMLR1 mooring, located on the western (AMLR1) side of Palmer Deep Canyon at 345 meters. AMLR1 was deployed at -64.2119, -64.8124 (longitude/latitude). Those named starting with "AMLR2" are from the AMLR2 mooring, located on the eastern (AMLR1) side of Palmer Deep Canyon at 400 meters. AMLR2 was deployed at -64.0376, -64.864 (longitude/latitude). Each mooring has three data files associated with it: 1) an "_Sv" file containing the processed acoustic return from the mooring in volume backscattering strength in decibels (dB) from the 120 kHz narrowband echosounder in a matrix where rows represent single pings and columns indicate depth bins; 2) a "_dp" file representing the depth (in meters) of the depth bins for each return with the same dimensions as the "_Sv" file; and 3) a "_tm" file containing a vector of timestamps corresponding to each ping in seconds since Jan 1 1970 (POSIX), where the length of the vector is equivalent to the number of rows in each matrix. |
Files
Type: GZIP (.gz)
Description: This package contains 6 .csv files. Those named starting with "AMLR1" are from the AMLR1 mooring, located on the western (AMLR1) side of Palmer Deep Canyon at 345 meters. AMLR1 was deployed at -64.2119, -64.8124 (longitude/latitude). Those named starting with "AMLR2" are from the AMLR2 mooring, located on the eastern (AMLR1) side of Palmer Deep Canyon at 400 meters. AMLR2 was deployed at -64.0376, -64.864 (longitude/latitude). Each mooring has three data files associated with it: 1) an "_Sv" file containing the processed acoustic return from the mooring in volume backscattering strength in decibels (dB) from the 120 kHz narrowband echosounder in a matrix where rows represent single pings and columns indicate depth bins; 2) a "_dp" file representing the depth (in meters) of the depth bins for each return with the same dimensions as the "_Sv" file; and 3) a "_tm" file containing a vector of timestamps corresponding to each ping in seconds since Jan 1 1970 (POSIX), where the length of the vector is equivalent to the number of rows in each matrix.