Versions Compared

Old Version 46

changes.mady.by.user polarstern account

Saved on

compared with

New Version Current

changes.mady.by.user polarstern account

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Automatically updated by Registry2Confluence-Transporter (polarstern@ingestsrv1, ask o2a-support@awi.de for questions)

...

Sensorweb integration
urnvessel:polarstern:parasound_p70
contenttypeMetadata
ManufacturerTeledyne RESON (ATLAS Hydrographic before takeover)
ModelParasound P70
Serial No.n/a
Typeecho sounder
REGISTRY-Link↪ REGISTRY (1392)


Sensorweb integration
urnvessel:polarstern:parasound_p70
contenttypeImages

...

Metadata (Metadata Plugin)
0Frequency
High frequency: 19 - 38 kHz; Parametric signal: 0.5 - 6.0 kHz
Contacts
 Sensorweb integration
urnvessel:polarstern:parasound_p70
contenttypeContacts
 Name  Institution  Role 
Catalina GebhardtAlfred - Wegener - Institute, Helmholtz Centre for Polar and Marine ResearchPrincipal InvestigatorGerhard Kuhn
Alfred - Wegener - Institute for Polar and Marine ResearchData ScientistFrank NiessenAlfred - Wegener - Institute for Polar and Marine ResearchData ScientistAlfred Wegener Institute for Polar and Marine ResearchAlfred Wegener Institute, Helmholz , Helmholtz Centre for Polar and Marine ResearchOwner
...
 Metadata (Metadata Plugin)
0Components
The system consits of the transducer, the electronic unit, two computers with installed data acquisition and processing software ParaStore and the subsidiary display on the bridge. 
The transducer consists of four segments and is mounted without ice protection window in the box keel. The transducer transmits in the frequency range of 18 - 39 kHz and reaches water depth of 10 to 11000m. Frequency interferences generate "parametric low frequencies" between 0.5 and 6.0 kHz. Penetration depth into the sediment accounts for > 200m (depending on sediment properties) and the resolution is 6.1 cm.
Position
 Sensorweb integration
urnvessel:polarstern:parasound_p70
contenttypeLocalFrame
Origin Description:Infoxyz-position calculated from Alignment Survey Report (2016), transducer array located in box keel, electronics located in E525A, computers located in E550 (HSPS room)
X:76.498 m
(X-0 is at the center of der rudder (ref. design drawing of the vessel), positive X-axis is forward and along vessel centerline) 
Y:0.004 m
(Y-0 at centerline, positive Y-axis is portside )
Z0.0 m
(Z-0 is set to the lowest point of the keel, positive Z-axis is upwards) 

Data logging, storage and archiving
...
 Sensorweb integration
urnvessel:polarstern:parasound_p70
contenttypeParameters
 Parameter  Sensor O2ARegistry Output Type  Unit 
depthdepthm
...
Time synchronising is carried out via NMEA-telegram from the ZDA data set or via ntp between DIP2 and the central ntp-server of the on-board network. DIP2 functions as ntp-server for the computers and residual DIPs of the Parasound System.
The recorded geographical ship's position is the location of the central motion sensor MINS. The lever between transducer and the central motionsensor MINS is considered.
 Metadata (Metadata Plugin)
0timestandard
 Rawdata storage on board 
Mass data: The data acquisition and processing software ParaStore creates rawdata on the local drive depending on system configuration. PHF = primary high frequency beam amplitudes, SLF = secondary low frequency beam amplitudes, SHF = secondary high frequency beam amplitudes. Synchonising of the local data directory to mass storage has to be carried out manually. A reduced set of uncorrected measurement data is stored to the DShip system.
 Metadata (Metadata Plugin)
0Rawdata

|| root directory | R:\data01\parasound\ ||
|| directory name | CruiseNo\XXX_ASD_YYYYMMDD \\ CruiseNo\XXX_PS3_YYYYMMDD \\ CruiseNo\XXX_SGY_YYYYMMDD \\ CruiseNo\screenshots \\ CruiseNo\PSAUX \\ CruiseNo\DSHIP \\ with \\ XXX = PHF, SLF or SHF \\ YYYY = year \\ MM = month \\ DD = day \\ e.g. \\ ANT25-3\PHF_ASD_20090113\ \\ ... ||
|| file name | PS3XXX\_YYYY-MM-DDThhmmssZ\_<identNo>.asd.acf \\ PS3XXX\_YYYY-MM-DDThhmmssZ\_<identNo>.asd.acf.idx \\ XXXYYMMDDhhmm.ps3 \\ XXXYYMMDDhhmm.sgy \\ YYYYMMDD-YYYYMMDD\YYYYMMDD_hhmm*.bmp \\ ??? \\ NAV_YYYYMMDD-YYYYMMDD.txt \\ with \\ XXX = PHF, SLF or SHF \\ YYYY = year \\ MM = month \\ DD = day \\ hh = hour \\ mm = minute \\ ss = second \\ <identNo> = 8-digit running number \\ e.g. \\ PS3PHF\_2009-01-13T112415Z\_00000005.asd.acf \\ ...||
|| Data volume (MB per day) ca | 10000 || 
|| Number of files per day ca | 1000 ||
 Metadata list
Dship
 Metadata (Metadata Plugin)
0DShip
Reduced set of uncorrected measurement data.

|| Device name | parasound || 
|| Parameters | depth \[m\] ||
 Metadata list
Data archiving on land 
After the cruise, the operator transfers the measurement data along with required meta data to AWI after consultaion with the data scientist and AWI Logistics. Then, the data (including meta data) can be extracted from https://www.pangaea.de/ (for authorized users only). The reduced, unevaluated DShip data set can be extracted from https://dms.awi.de.
 Metadata (Metadata Plugin)
0DataOnLand

|| File format(s) | stored in PANGAEA or DShip system || 
|| Calibration certificates | NO ||
 Metadata list
Documentation
 Sensorweb integration
urnvessel:polarstern:parasound_p70
contenttypeResources
...