New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
#1846 (diaptr land suppression eORCA12) – NEMO

Opened 7 years ago

Last modified 7 years ago

#1846 closed Bug

diaptr land suppression eORCA12 — at Version 1

Reported by: mathiot Owned by: nemo
Priority: low Milestone:
Component: OCE Version: v3.6
Severity: Keywords:
Cc: rbourdal

Description (last modified by nemo)

Context

Diaptr with land suppression is not working well. Whatever the variables and the bassins, data are missing in some place because there is no processor at these locations (Antarctica and at the latitude of Bering strait) (see attachment).


Analysis

The line use to plot diaptr is defined in iom_init.F90:

CALL dom_ngb( 180., 90., ix, iy, 'T' ) !  i-line that passes near the North Pole : Reference latitude (used in plots)

In my eORCA12 decomposition, some processors are missing along this line (land processor).

It could affect any configuration using land suppression (more likely at high resolution) in NEMO_3.6_STABLE and in the trunk.

Fix

I suggest to move the test on point (180E,90N) to (-168.7E,65.6N). The suggested point, is a point in Bering Strait. The only land points cross along this line are the points over Antarctica. The issue with this is that the latitude vector range will be [-86.5:~80N (not 90N)] instead of [-86.6N:90N]. However, the latitude vector is not correct anyway in the Arctic (because or the grid distortion). So I think the latitude coordinate issue is minor.

Commit History (3)

ChangesetAuthorTimeChangeLog
8573cbricaud2017-09-28T10:31:26+02:00

Fix Ticket #1846 in trunk

8572cbricaud2017-09-28T10:27:06+02:00

Fix Ticket #1846 in NEMO_3.6_STABLE

8571cbricaud2017-09-28T10:14:57+02:00

Fix Ticket #1846 in NEMO_3.6_STABLE

Change History (2)

Changed 7 years ago by mathiot

comment:1 Changed 7 years ago by nemo

  • Description modified (diff)
Note: See TracTickets for help on using tickets.