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

ncar_boundary_scaling algorithm results in inconsistent background viscosities for tripolar grids #282

Open
russfiedler opened this issue Apr 16, 2019 · 2 comments

Comments

@russfiedler
Copy link
Collaborator

russfiedler commented Apr 16, 2019

There's already a note in the code partly adressing this issue but it skirts the main problem.

The background viscosities aiso_back and aaniso_back are on the velocity points. When using the NCAR algorithm ocean_bihgen_frictionandocean_lapgen_friction_mod` in this results in an inconsistency in the background values for (i,nj,:) and (ni-i,nj,:) which are actually the same point when using a tripolar grid

For i<ni/2 distances along the fold are measured from Russia and i>n/2 distances are measured from Canada. In short, we have 2 different viscosities for the same point!

I suggest a warning be issued is a user tries to use this algorithm and suggest that they calculate the background scaling correctly offline.

@russfiedler russfiedler changed the title ncar_boundary_scaling algorithm results in inconsistent background viscosities ncar_boundary_scaling algorithm results in inconsistent background viscosities for tripolar grids Apr 16, 2019
@aekiss
Copy link
Collaborator

aekiss commented Aug 12, 2019

Also the ncar_boundary_scaling boundary scaling is supposed to ensure western boundary currents are wide enough to resolve, so it should be on the eastern side of land cells. But is actually on the i-maximum side, which is not the same thing in the tripolar cap region. Perhaps it should simply be disabled in the tripolar cap region?

@StephenGriffies
Copy link
Contributor

Good catch.. Unless someone wishes to work through the algorithm for the bipolar region, then it might just be best to remove it north of 65N. However, that should be tested to ensure no major negative changes appear.

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

3 participants