Skip to end of metadata
Go to start of metadata

SIDSSE UURS Spectral Data

Processed data products for SIDSSE (Sanya Institute of Deep-Sea Science and Engineering) Underwater Ultraviolet Raman Spectrometers (UURS) are described here. Raw data is acquired directly from the instrument, stored normally as raw log files. The data products described here are simple presentations of the spectral data reported by the instrument. The MAT and CSV file products contains the spectral data as a single vector/array, while the PNG/PDF plot products are simple plots of those spectral counts versus pixel number. Conversion of counts and pixel units to physical units requires calibration. One method has been suggested by the P.I.'s:

The horizontal axis, in the current form, is in pixels, not yet in Raman shift. This requires a linear conversion.
In the attached plot, the small peak in the middle (~425th pixel) belongs to water, which has a Raman shift of 1600cm-1. 
Another small peak on the left (around the 215th pixel) belongs to the olivinite, which has a Raman shift of 550cm-1. 
Raman shift of the other points can be deduced using linear interpolation.


Oceans 2.0 API filter
dataProductCode=UURS

Revision History:

  • 2019024: initial release

Formats

CSV file UURS Spectral Data

This is very simple comma separated text file with some header lines. The first column is the pixel index, the second column is the spectral counts. Here is an example:

# Ocean Networks Canada Comma Separated Variables data file for SIDSSE Underwater Ultraviolet Raman Spectrometer
# Spectrum scan time: 07-Jan-2019 00:04:05
# Device Name: SIDSSE Underwater Ultraviolet Raman Spectrometer (UURS) SN 01
# Device Code: SIDSSEUURS01
# Pixels, Counts
1,2098
2,2097
3,2110
4,2091
5,2086
6,2104
7,2092
8,2089
9,2100
10,2093
11,2095
12,2095
13,2091

Oceans 2.0 API filterextension=csv

MAT file UURS Spectral Data

MAT files contain the spectral data:

UURSdata: a structure containing the following data fields:

  • data: vector / array of the spectral counts. Pixel index is simply 1:length(UURSdata.data).
  • scanDate: matlab datenum format date of the scan / spectral data acquisition
  • units: text field for the units of data

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 UURS Spectral Data

Spectral UURS data are provided in PNG/PDF format as a simple line plot of Count versus Pixel. As previously noted, the spectrum isn't calibrated. Standard ONC metadata is display. PDF data products are collated into in a single file. See examples below:

SIDSSEUURS01_20190107T000405.900Z_20190107T120406.213Z-UURSspect.pdf

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

Discussion

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

  • No labels