-
Notifications
You must be signed in to change notification settings - Fork 9
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 layer depth #79
Comments
Food for thought to spark some creativity... You could consider defining a new operand const MixedLayerDepthField = Field{<:Any, <:Any, Nothing, <:MixedLayerDepthOperand}
function compute!(mld::MixedLayerDepthField)
# code that computes this 2D field
end the next component is to design the struct MixedLayerDepthOperand{B, U, K, P}
buoyancy_field :: B
velocities :: U
mixed_layer_depth_kernel :: K
parameters :: P
end Then the kernel could have a prescribed function signature (eg |
Great start with Bioceananigans! I can definitely see a function like that being a part of this repo. At the moment I think the best place for such an addition is in FlowDiagnostics. However, pretty much everything there is geared towards point-wise diagnostics (mostly because that's what I had in mind when I created the repo). So if there are plans to include more stuff of this nature it can also be productive to create something like a Thoughts? Also, feel free to create a PR and we can try things out over there |
I created a new package for biogeochemical models on Oceananigans and, with @glwagner help, I could create a function to estimate the mixed layer depth from a given buoyancy decrease criterium. Although this is working well for the purpose I had in mind, I believe that the mixed layer depth estimator could be better located in a more general repository. While discussing with @glwagner, he suggested me this repository.
We also had some ideas for improving the algorithm, like leaving for the user to define any general criterium for the mixed layer... even those which does not depend on the buoyancy? (but then it would be better called boundary layer? idk...).
What do you think about it and if you think this is a good match to this repo, where should I add it? I could first adapt the language and create a PR, adding it as it is and later create another issue for the enhancements.
The text was updated successfully, but these errors were encountered: