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.
#1642 (Generalised vertical coordinate observation operator) – NEMO

Opened 8 years ago

Closed 5 years ago

#1642 closed Task (fixed)

Generalised vertical coordinate observation operator

Reported by: kingr Owned by: mathiot
Priority: low Milestone: Unscheduled
Component: OCE Version: trunk
Severity: minor Keywords:
Cc:

Description

GO6 has introduced a variable volume layer (VVL). To properly calculate the observation equivalent values, the obsoper must use the appropriate vertical scale factors.

This has been implemented in a 2015 branch, but has not been used in a configuration where profile observations are assimilated.

This branch is to fix the bugs in the generalised vertical coordinate obsoper and make use of when VVL is used.

Commit History (1)

ChangesetAuthorTimeChangeLog
6016kingr2015-12-07T17:42:57+01:00

#1642 bug fixes for general vertical coord obsoper

Change History (6)

comment:1 Changed 8 years ago by timgraham

  • Owner changed from NEMO team to kingr
  • Type changed from Bug to Development branch
  • Version changed from v3.6 to trunk

comment:2 Changed 7 years ago by nemo

  • Type changed from Development to Task

Remove 'Development' type

comment:3 Changed 6 years ago by nicolasmartin

  • Severity set to minor
  • Status changed from new to assigned

comment:4 Changed 6 years ago by nemo

  • Milestone set to Unscheduled

Batch modification of milestone field set to 'Unscheduled'

comment:5 Changed 6 years ago by nicolasmartin

  • Owner changed from kingr to mathiot

I'm not sure if this ticket is in the scope of NEMO ST.

Need a clear statement on this work, is it still relevant now and if so who is the new PI.

comment:6 Changed 5 years ago by mathiot

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

Included in 2016 merge or before (kingr).

Note: See TracTickets for help on using tickets.