Opened 5 years ago

Closed 22 months ago

#1572 closed Enhancement (fixed)

diaar5 assumes inputs are on the model grid

Reported by: acc Owned by: cetlod
Priority: low Milestone:
Component: OCE Version: release-3.6
Severity: minor Keywords:
Cc: cetlod Review:
MP ready?:
Progress:

Description

dia_ar5_init uses the namtsd information to access the initial/climatological salinity field but doesn't use the fld_read mechanism. This means attempts to use interpolation on the fly for initial conditions can fail unexpectedly if key_diaar5 is enabled. In at least one case (ORCA1 with initial conditions on the WOA grid)
it simply hangs in dia_ar5_init with no indication of what the problem is.

Commit History (2)

ChangesetAuthorTimeChangeLog
6665cetlod2016-06-03T15:44:55+02:00

trunk:bugfix on diaar5 routine to read salinity input file on model grid, see ticket #1572

6664cetlod2016-06-03T15:42:46+02:00

bugfix on diaar5 routine to read salinity input file on model grid, see ticket #1572

Change History (5)

comment:1 Changed 4 years ago by cetlod

One solution - the easiest I think -  is to have both the raw initial/climatological salinity for the fld_read mechanism ( for initial state, salinity restoring and damping ) and a salinity file already interpolated onto the model grid when key_diaar5 is activated

comment:2 Changed 4 years ago by cetlod

The routine diaar5 is modified to read, during the initialization phase,  a salinity file named sali_ref_clim_monthly.nc, that has already been interpolated onto the model grid. Exactly what was done in the previous version of NEMO - v3.2, v3.4 …

comment:3 Changed 3 years ago by clevy

  • Cc cetlod added
  • Owner changed from nemo to cetlod
  • Status changed from new to assigned

comment:4 Changed 3 years ago by nicolasmartin

  • Type changed from Bug to Enhancement

comment:5 Changed 22 months ago by cetlod

  • Resolution set to fixed
  • Severity set to minor
  • Status changed from assigned to closed

Done in v4.0

Note: See TracTickets for help on using tickets.