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.
#2287 (Bug in bdy with flather) – NEMO

Opened 4 years ago

Closed 4 years ago

Last modified 14 months ago

#2287 closed Bug (fixed)

Bug in bdy with flather

Reported by: girrmann Owned by: systeam
Priority: high Milestone:
Component: BDY Version: v4.0
Severity: major Keywords: v4.0
Cc:

Description

Context

For eastern and northern boundaries (flagu = -1 and flagv = -1) use rim velocity instead of the velocity of the internal domain.

Analysis

If flagu = -1 then iim1 defined as ii + MAX( 0, INT( flagu ) is equal to ii, same thing for flagv = -1, ijm1 defined as ij + MAX( 0, INT( flagv ). pua2d(iim1,ij) used in computing the rim velocity ( pua2d(ii,ij) ) is set to the rim velocity itself.

Fix

Do not use iim1 and ijm1 indices in pua2d and pva2d. Note that those are the right indices for pssh.

Commit History (3)

ChangesetAuthorTimeChangeLog
11074girrmann2019-06-04T17:46:46+02:00

dev_r10984_HPC-13 : bug fix and cleaning of flather, see #2287 and #2285

11073girrmann2019-06-04T15:16:58+02:00

v4 : fix bug in flather for bdy, see #2287

11072girrmann2019-06-04T15:14:57+02:00

trunk : fix bug in flather for bdy, see #2287

Change History (5)

comment:1 Changed 4 years ago by girrmann

In 11072:

Error: Failed to load processor CommitTicketReference
No macro or processor named 'CommitTicketReference' found

comment:2 Changed 4 years ago by girrmann

In 11073:

Error: Failed to load processor CommitTicketReference
No macro or processor named 'CommitTicketReference' found

comment:3 Changed 4 years ago by girrmann

In 11074:

Error: Failed to load processor CommitTicketReference
No macro or processor named 'CommitTicketReference' found

comment:4 Changed 4 years ago by girrmann

  • Resolution set to fixed
  • Status changed from new to closed

comment:5 Changed 14 months ago by nemo

  • Keywords v4.0 added
Note: See TracTickets for help on using tickets.