Skip to content

Sediment and water cloumn concentration clash #42

@lachlan194924

Description

@lachlan194924

Summary:

In the import of WAMSI / WWMSP3/ GW. (Project 3.3), there are sites and variables that contain two types of deployments, both floating and fixed. Our system can only handle one type of deployment per site and variable pair.

This has put a hault on imports, I need to import the last sheet of the document. Additionally understanding how the insitu data relates to the other sheets.

Examples and Discussion

There are aluminium concentrations for both the water column and the seabed, this is foreseen to cause issues for MARVL and so will we be tagging them
"
Deployment,Sediment
Deployment Position,m from Ground
Vertical Reference,m from Ground

Then Height in the Datafile as a negitive
" -from brendan

"yep - and depth for all is -0.5m" - Matt

this will require us to modify csv_2_matfile and add a clause to not import (Deployment == Sediment).

That way marvl wont die:)

As a final touch Go back to wwmsp3 -sedpsd and seagrass resto to make them sediment deployments as well

Some data entries are smaller than the precision of the istrument and so have entreis of less than (precision).
"Less than entries can be set as half of the detection limit " -matt

Ill just wait on:
The variables are all workeed out

And when we deceide what to do with the depth mesurment of the water samples.

Ill assume-0.5 for the pore water as suggested already and matt has said same for seawater (0.5m)

Headerfile issue: same variable and same site with different deployment types, 0.5 from surface or 0.5 from seabed

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