-
Notifications
You must be signed in to change notification settings - Fork 7
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
Towards converging DMQC methods #101
Comments
https://www.oceanbestpractices.org writes "A best practice is a methodology that has repeatedly produced superior results relative to other methodologies with the same objective; to be fully elevated to a best practice, a promising method will have been adopted and employed by multiple organizations." I would like to discuss how we could get here in the long term. i.e. with test datasets and run the code through all different approaches to quantitively show under which environmental condition / platform etc which method gives better results? Until we have not done these method inter-comparisons we will not be able to say. |
It is likely that different methods are suitable in different conditions. But one first way forward would be to create a test dataset that is representative of different regions and run it through all the available methods. I think currently, the methods people use are often linked to which platforms they are using, and the code available. |
I agree that a test dataset's representing different conditions will be key. This could be done in collaboration with the OceanGliders Datamanagrement Task Team to ensure we use the OG1.0 format etc. Maybe as a first step we can try to think which method "might" be better suited for what kind of condition and state this. Maybe for some this is clear? i.e. very strong gradient, beta ocean etc? |
At the moment we list many different implementations of the DMQC corrections.
How could we make progress in converging? This might be an issue when publishing the SOP.
This issue will remain open throughout the whole community review.
For sure we will need some more recommendations under which conditions what approach should be the default choice.
The text was updated successfully, but these errors were encountered: