Skip to content

SG_PAR variable Check and Date Issue #44

@lachlan194924

Description

@lachlan194924
  • I have had my best effort at matching datalake header variable names to varkey variable names, but needs to be double checked

  • The date is stored twice in this dataset. and they conflict.

          -           One is stored in UTC and matches our format.
          -           One is stored as a combination of date and then also as a time. 
    
       For sites 6 and 7 these two dates differ but 573 hours (and 37 mins) to 640 hours (and 36 mins). This is too big to actually be a timezone difference. ( the other 3 sites have a difference of 8 hours, which agrees with perths timezone). Currently the code uses the UTC, but this has been coded in a way that makes it easy to swap
    
  • The headerfile is missing deployment information. Im not sure if this type of sensor is deployed at the surface or the bottom, this is probably quite obvious with context of what the sensor is measuring. At the moment the header file says "NOT SURE" and the depth in the datafile is 0 with a header of "Depth". Ie i have assumed floating on surface in the datafile.
    I have now made it fixed, to the bottom at a deployment depth of 0.2m above seabed.

The last issue is also a super quick fix:

  • the variable names read in from the datalake have pre appended with whitespace to match the varkey however at them moment the varkey is being editted by someone else and is not version tracked so am waiting. All that needs to be done is remove whitespace from the variables related to SG_PAR in the WWMSP2 sheet and reupload to davy and run the import_vark_key matlab script.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions