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

Hysteresis estimate #193

Open
2 of 3 tasks
MOchiara opened this issue Feb 20, 2025 · 1 comment
Open
2 of 3 tasks

Hysteresis estimate #193

MOchiara opened this issue Feb 20, 2025 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@MOchiara
Copy link
Member

MOchiara commented Feb 20, 2025

I am getting into troubles when trying to estimate hysteresis and I would love some opinion from better brains than mine =)
Currently, to assess the potential presence of hysteresis, we calculate the percentage error as the difference between the dive and climb relative to the mean values.
However, I’m considering that it might make more sense to estimate this relative to the data range instead. I’m unsure if this approach is valid.
As illustrated in the two plots, when we compute the error using mean values, it suggests the error is negligible, even though it’s clearly significant and evident in the first plot. On the other hand, comparing the difference to the range values brings out the obvious up-down bias much more clearly.

Image

Image

Update:

Chatted to Eleanor and we decided we will keep both the range and the mean and add a row on the summary sheet to check for both

@MOchiara MOchiara added the help wanted Extra attention is needed label Feb 21, 2025
@eleanorfrajka
Copy link
Collaborator

eleanorfrajka commented Feb 24, 2025

Tricky one! For something like vertical velocity, the mean should be small (near zero), so any bias between dive-average and climb-average will likely look large relative to the mean. The range for the mean w profile for dives and climbs could be relatively quite a bit larger, due to bad behaviour near the surface (attached plot, 2 cm/s for range, maybe -0.1 cm/s for mean). So it's the opposite problem as for salinity.

I think there could be (at least) 3 options:

  • percentage of the dive-climb difference (the delta) to the mean: $\frac{\Delta C}{\left<\overline{C}\right>}>0.02$. Problematic for things like salinity or density where the differences are small compared to the absolute value.
  • percentage of the dive-climb difference to the range: $\frac{\Delta C}{\mathrm{max}(\overline{C})-\mathrm{min}(\overline{C})}>0.02$. Problematic for--@MOchiara did you say this is a problem for optics?
  • or threshold $\left|\Delta C\right|>c_0$, where the threshold $c_0$ is set somehow by the expected accuracy (salinity better than.. 0.005? temperature better than 0.005? vertical velocity better than 0.05). Problematic for backscatter where it's not clear what the absolute numbers should be.

where $\left<\cdot\right>$ is the depth-mean, and $\overline{\cdot}$ is the time mean, so that $\overline{C}$ is the mean profile (still depends on z).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants