Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'mixed.cutoff' inconsistency #107

Open
231Harriet opened this issue Sep 16, 2020 · 0 comments
Open

'mixed.cutoff' inconsistency #107

231Harriet opened this issue Sep 16, 2020 · 0 comments

Comments

@231Harriet
Copy link

Hi there,

I have a suggested change for the 'mixed.cutoff' object in the meta.depths() and thermo.depth() functions.

Currently, the 'mixed.cutoff' object is a user specified filter that removes profiles which are not sufficiently stratified to define a metalimnion top/bottom. The units of this filter are water temperature range, and are defaulted to 1°C. See code from thermo.depth();

if (diff(range(wtr, na.rm = TRUE)) < mixed.cutoff) { return(NaN) }

However, considering that the thermocline, metalimnion top and bottom are all defined using units of the density gradient between consecutive sensors, it is inconsistent to use a water temperature based filter. This is particularity problematic for the metalimnion top/bottom because it is possible for the mixed.cutoff value to be met even when the 'slope' object (i.e. the user defined threshold that is used to determine what can be considered as homogeneous) has not been met.

Therefore, I propose that the mixed.cutoff value is removed and where the 'slope' is not met at all in the water column profile, the metalimnion/depth is returned as NA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant