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.
#2105 (Phasing FCM version in vendors with a tag release from metomi Github repository) – NEMO

Opened 6 years ago

Last modified 4 years ago

#2105 assigned Request

Phasing FCM version in vendors with a tag release from metomi Github repository

Reported by: nicolasmartin Owned by: nicolasmartin
Priority: low Milestone:
Component: env Version: trunk
Severity: minor Keywords: FCM,
Cc:

Description

Context

The FCM source code included with NEMO looks quite outdated.
The last commit by Seb goes back 5 years ago and the last overall import has 8 eight years old: browser:/vendors/FCM@9621

Few weeks ago, I ran a basic and simple test by replacing the content of the FCM directory with a import of the last release from the official repository and I did not encounter any issue at compilation.

Proposal

Actually, the upgrade seems to be straightforward by replacing the current release (labelled as 1-5 release) with the last one (2017.10.0) but the Met Office staff would certainly have more information and an informed opinion on what it is safe to do here.

Commit History (0)

(No commits)

Change History (2)

comment:1 Changed 6 years ago by nicolasmartin

  • Owner set to nicolasmartin
  • Status changed from new to assigned

comment:2 Changed 4 years ago by clevy

  • Type changed from Enhancement to Feature request
Note: See TracTickets for help on using tickets.