1 / 4

NEMOVAR path to version 3.4.

NEMOVAR path to version 3.4. Release of NEMO v3.4 (expected shortly). Outer loop stuff like observation operators and IAU part of reference code (since 3.3). Some ASM mods to filter increments. ORCA1 available (but not the L42 version). Will form the basis for ECMWF’s future developments.

thetis
Download Presentation

NEMOVAR path to version 3.4.

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NEMOVAR path to version 3.4. • Release of NEMO v3.4 (expected shortly). • Outer loop stuff like observation operators and IAU part of reference code (since 3.3). • Some ASM mods to filter increments. • ORCA1 available (but not the L42 version). • Will form the basis for ECMWF’s future developments. • We will need this around mid 2012 since it is going to be used by various projects. • What do the rest of you plan to do?

  2. NEMOVAR path to version 3.4 (2). • Inner loop issues: • Some modules used by the inner loop is most likely changed, so the some adaptation is going to be needed. • Adopt to new dynamic memory workspace linked list structure? • TAM version of v3.4? • New dynamic memory structure could cause some headaches. • Minimum TAM for 3D-VAR initially?

  3. NEMOVAR path to version 3.4 (3). • Suggestion: form a NEMOVAR working group to bring NEMOVAR v3.2.2 (?) up to 3.4 for initially a 3D-VAR FGAT version. • Kristian volunteer to take the lead (other volunteers welcome)… • Ideally at least one participants per institution. My suggestionis the following: • Isa for dealing with the filters. • Andrea for the parallel remapping. • Arthur for TAM. • Kristian for observation stuff and coordination.

  4. NEMOVAR path to version 3.4 (4). • Some questions for discussion: • Implement in OOPS? • Potentially attractive but is it too much work? • Use general parallel remapping for the initial version? • How to deal with developments done with version 3.0 and 3.2 while this work is ongoing? • To be migrated by the developers or by the WG? • Full TAM version and 4D-VAR test at what point in time and who does this? • PIANO scripts single cycle sufficient?

More Related