Skip to end of metadata
Go to start of metadata

Kistler Accelerometer Data

Processed data products for Kistler Accelerometers are described here. For Kistler Accelerometer raw binary files acquired directly from the instrument, see here. Kistler processed data products are produced from each raw file, which normally contain 5 minutes of data. Processed products are available in three formats. The MAT file contains the raw, uncalibrated data parsed into MATLAB-readable format, while the PNG/PDF plot products are spectrograms of the acceleration along the X, Y, Z instrument axes. The calibration documentation (Kistler_CalSheet_2013.pdf) will be bundled with all data product requests; this data is used to calibrate the spectrograms only. Contact us for more information. Also, see the manufacturer's website: http://www.kistler.com/ca/en/products/components/acceleration-sensors/.

Oceans 2.0 API filterdataProductCode=KAD

Revision History:

  • 20150805: Data product migrated from VENUS data download

Formats

MAT file Raw Data

MAT files contain the raw uncalibrated data. The data is contained in the KisterData structure, accompanied by the usual metadata structure. The structures and fields are described below.

KistlerData: a structure containing the following raw data fields:

  • matlabtime: vector of time stamps for each measurement in matlab datenum format: days since January 1, 0000. 
  • numChannels: number of sensors, should always be 4 (X,Y,Z uncalibrated acceleration and temperature).
  • sampleRateHz: sample rate in Hz, usually 2560 Hz. 
  • waterproperty: cell array with names of the measured quantities
  • Temperature / xAxisVolts / yAxisVolts / zAxisVolts: sensor data arrays, all are not calibrated (same length as matlabtime). 
  • Temperature_QCflag / xAxisVolts_QCflag / yAxisVolts_QCflag / zAxisVolts_QCflag: sensor data QAQC flag arrays, currently, these are all 0s (same length as matlabtime). See the QAQC pages for more information. 
  • Temperature_units / xAxisVolts_units / yAxisVolts_units / zAxisVolts_units: string containing the measurement unit, since the data is not calibrated, this is always 'V' for Volts. 

Meta: a structure array containing the following metadata fields:
  • deviceID: A unique identifier to represent the instrument within the Ocean Networks Canada data management and archiving system.
  • creationDate:Date and time (using ISO8601 format) that the data product was produced. This is a valuable indicator for comparing to other revisions of the same data product.
  • deviceName: A name given to the instrument.
  • deviceCode: A unique string for the instrument which is used to generate data product filenames.
  • deviceCategory: Device category to list under data search ('Echosounder').
  • deviceCategoryCode: Code representing the device category. Used for accessing webservices, as described here: API / webservice documentation (log in to see this link).
  • lat: Fixed value obtained at time of deployment. Will be NaN if mobile or if both site latitude and device offset are null. If mobile, sensor information will be available in mobilePositionSensor structure..
  • lon: Fixed value obtained at time of deployment. Will be NaN if mobile or if both site longitude and device offset are null. If mobile, sensor information will be available in mobilePositionSensor structure.
  • depth: Fixed value obtained at time of deployment. Will be NaN if mobile or if both site depth and device offset are null. If mobile, sensor information will be available in mobilePositionSensor structure.
  • deviceHeading: Fixed value obtained at time of deployment. Will be NaN if mobile or if both site heading and device offset are null. If mobile, sensor information will be available in mobilePositionSensor structure.
  • devicePitch: Fixed value obtained at time of deployment. Will be NaN if mobile or if both site pitch and device offset are null. If mobile, sensor information will be available in mobilePositionSensor structure.
  • deviceRoll: Fixed value obtained at time of deployment. Will be NaN if mobile or if both site roll and device offset are null. If mobile, sensor information will be available in mobilePositionSensor structure.
  • siteName: Name corresponding to its latitude, longitude, depth position.
  • stationCode: Code representing the station or site. Used for accessing webservices, as described here: API / webservice documentation (log in to see this link).
  • locationName: The node of the Ocean Networks Canada observatory. Each location contains many sites.
  • dataQualityComments: In some cases, there are particular quality-related issues that are mentioned here. This is distinct from QAQC information contained in the data structure.
  • MobilePositionSensor.name: A cell array of sensor names for mobile position sensors. If not a mobile device, this will be an empty cell string.
  • MobilePositionSensor.sensorID: An array of unique identifiers of sensors that provide position data for mobile devices - this data may be used in this data product.
  • MobilePositionSensor.deviceID: An array of unique identifiers of sensors that provide position data for mobile devices - this data may be used in this data product.
  • MobilePositionSensor.dateFrom: An array of datenums denoting the range of applicability of each mobile position sensor - this data may be used in this data product.
  • MobilePositionSensor.dateTo: An array of datenums denoting the range of applicability of each mobile position sensor - this data may be used in this data product.
  • MobilePositionSensor.typeName: A cell array of sensor names for mobile position sensors. If not a mobile device, this will be an empty cell string. One of: Latitude, Longitude, Depth, COMPASS_SENSOR, Pitch, Roll.
  • MobilePositionSensor.offset: An array of offsets between the mobile position sensors' values and the position of the device (for instance, if cabled profiler has a depth sensor that is 1.2 m above the device, the offset will be -1.2m).
  • MobilePositionSensor.sensorTypeID: An array of unique identifiers for the sensor type.
  • MobilePositionSensor.correctedSensorID: An array of unique identifiers of sensors that provide corrected mobile positioning data. This is generally used for profiling deployments where the latency is corrected for: CTD casts primarily.
  • deploymentDateFrom: The date of the deployment on which the data was acquired.
  • deploymentDateTo: The date of the end of the deployment on which the data was acquired (may be omitted if still deployed).
  • samplingPeriod: Sampling rate of the instrument in seconds (maybe omitted on some devices that have no scalar sensors).
  • samplingPeriodDateFrom: matlab datenum of the start of the corresponding sample period (maybe omitted on some devices that have no scalar sensors).
  • samplingPeriodDateTo: matlab datenum of the end of the corresponding sample period (maybe omitted on some devices that have no scalar sensors).
  • searchID: unique number tracking this search request (not normally included).
  • Attribution: A structure array with Attribution information, ordered by importance and date. For internal users, go to the Network Console to configure the attributions. If an organization has more than one role it will be collated. If there are gaps in the date ranges, they are filled in with the default Ocean Networks Canada citation. If the "Attribution Required?" field is set to "No" on the Network Console then the citation will not appear. For data products with a attribution (except MAT files) and for users making products from a MAT file, if the special attribution is blank/null, then the company default attribution will be used and if it is also blank/null, then the final attribution will consist of the organization name and role: "Ocean Networks Canada (Owner, Collaborator)". Here are the fields:
    • acknowledgement: the acknowledgement text, note that if the special acknowledgement blank/null, the default acknowledgement is used.
    • startDate: datenum format
    • endDate: datenum format
    • organizationName
    • organizationRole

Oceans 2.0 API filter: extension=mat

PNG/PDF Spectrogram

Spectrograms of relative acceleration along the X,Y,Z instrument axes are provided in PNG/PDF format. As previously noted, the spectrogram is calibrated as per the calibration sheet. The calibration applies the bias voltage offset and the frequency dependent sensitivity, which converts millivolts to 1 g. The PDF format contains multiple spectrograms on multiple pages, while the PNG products will be separate files for each 5 minute spectrogram. Here is an example spectrogram:

 

Oceans 2.0 API filter: extension={png,pdf}

Discussion

To comment on this product, log in and click Write a comment... below.

  • No labels