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

Ocean side mesh: Eddy regime / non-eddy regime requirements #149

Open
Tracked by #165
saeed-moghimi-noaa opened this issue May 9, 2024 · 2 comments
Open
Tracked by #165
Assignees

Comments

@saeed-moghimi-noaa
Copy link

No description provided.

@felicio93
Copy link
Collaborator

felicio93 commented May 17, 2024

Eddying Regime

Information from Joseph's "Mesh generation for Eddying and Transitional Regime" (MSCI602) class:

  • Eddying regime: weakly forced, mostly balanced (geostrophic)
    • For 3D model, the mesh transition should be gradual and smoother in eddying and transition regimes
    • Most challenging situation is where the transitional regime is very tight (e.g., steep slopes)

Why?:

  • Mesh generation for eddying regime therefore should strive to preserve this balance by using gradually varying resolution
    • This is also because the bathymetric variation in the deep ocean is negligible
    • Sharp transition would distort or create spurious eddying processes (Wang and Danilov 2013)
    • Simplicity in mesh design here is a virtue: do not over-constrain the mesh unnecessarily in eddying regime
    • Use auxiliary arcs to avoid excessive resolution in deep water (hydrostatic assumption)
    • Horizontal Resolution >> Vertical Depth

The mesh should be "featureless" (do not follow the bathymetry), e.g.:

Image

Non-Eddying Regime

Image

  • Note that:
    • The recommendation is to keep the mesh the mesh "featureless" even in areas close to sharp slope transitions (no smoothing in the deep)
    • In areas of high slopes (>45 degrees), i.e. non-eddying, take full advantage of polymorphism, irregular elements, lsc2m etc.

Result:

Image

@felicio93
Copy link
Collaborator

tagging @feiye-vims in case he has any other requirement

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

2 participants