| Note |
|---|
|
Please note that operations of the Acoustic Doppler Current Profiler requires experienced scientific staff on board. The system is not operated by the ship's crew. Announce operations with the Acoustic Doppler Current Profiler to AWI-Logistics prior to the cruise and clarify the data transfer after the cruise. |
Summary
| Sensorweb integration |
|---|
| urn | vessel:polarstern:adcp |
|---|
| contenttype | Summary |
|---|
|
|
| Sensorweb integration |
|---|
| urn | vessel:polarstern:adcp |
|---|
| contenttype | Metadata |
|---|
|
|
| Sensorweb integration |
|---|
| urn | vessel:polarstern:adcp |
|---|
| contenttype | Images |
|---|
|
|
Transducer Frequency:
| Metadata (Metadata Plugin) |
|---|
|
150 kHz |
Contacts
| Sensorweb integration |
|---|
| urn | vessel:polarstern:adcp |
|---|
| contenttype | Contacts |
|---|
|
|
Components
| Metadata (Metadata Plugin) |
|---|
|
The system consits of the transducer, the electronic chassis, the computer in the echosounder room (G-707) and the subsidiary display at the winch control station (User).
The data acquisition and processing software VmDas and the synchronizing software Easy2Sync are installed on the computer.
The 150kHz transducer is mounted behind an ice protection window and reaches water depth up to 350m with resolution of 4m ("Cell Size" at 1 to 5 kn ship's speed) and accuracy of about 0.30 m/s for a Single-Ping measurement.
The angle between the ship centerline and transducer centerline is 45° direction starboard. |
Subdevices
| Sensorweb integration |
|---|
| urn | vessel:polarstern:adcp |
|---|
| contenttype | Subdevices |
|---|
|
|
Position
| Sensorweb integration |
|---|
| urn | vessel:polarstern:adcp |
|---|
| contenttype | LocalFrame |
|---|
|
|
Data logging, storage and archiving
Logged parameters
| Sensorweb integration |
|---|
| urn | vessel:polarstern:adcp |
|---|
| contenttype | Parameters |
|---|
|
|
Central geographical ship's position and time standard
...
| Metadata (Metadata Plugin) |
|---|
|
Mass data: The data acquisition and processing software VmDas creates rawdata on the local drive of the computer.
Every hour the software Easy2Sync copies the data to a local backup file structure.
Every 3 hours the software Easy2Sync synchronizes the backup data to the directory structure of the mass storage.
Attention: Deleting files in the directory structure of the mass storage will also delete these files in the backup file structure with the next synchronization run. But: As long as these files are not removed from the local rawdata drive these files will be copied again to the local backup file structure with the next backup run and to the directory structure of the mass storage with the next synchronization run.
|
| Metadata list |
|---|
|| root directory | C:\ADCPData\ \\ or \\ C:\ADCPDataBackup\ \\ or \\ \\polsrv1\data01\ADCP\... ||
|| directory name | CruiseNo \\ e.g. \\ ANT25_3 ||
|| file name | CruiseNoVVV_RRRRRR.ENR \\ CruiseNoVVV_RRRRRR.ENS \\ CruiseNoVVV_RRRRRR.ENX \\ CruiseNoVVV_RRRRRR.LTA \\ CruiseNoVVV_RRRRRR.N1R \\ CruiseNoVVV_RRRRRR.NMS \\ CruiseNoVVV_RRRRRR.STA \\ CruiseNoVVV_RRRRRR.LOG \\ CruiseNoVVV_RRRRRR.VMO \\ with: \\ VVV = version No. \\ RRRRRR = running No. \\ e.g. \\ ANT25_3012_000000.* ||
|| Data volume (MB per day) ca | 350 ||
|| Number of files per day ca | 35 || |
...
See also http://www.rdinstruments.com/
| Sensorweb integration |
|---|
| urn | vessel:polarstern:adcp |
|---|
| contenttype | Resources |
|---|
|
|