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.
#2379 (VALID-11_clevy_OASIS_TESTCASE) – NEMO

Opened 3 years ago

Last modified 18 months ago

#2379 new Task

VALID-11_clevy_OASIS_TESTCASE

Reported by: clevy Owned by: clevy
Priority: normal Milestone: Unscheduled
Component: SBC Version: trunk
Severity: minor Keywords:
Cc: emalod, coquart

Description

Workplan action

Wikipage: wiki:2020WP/VALID-11_clevy_OASIS_TESTCASE

Commit History (3)

ChangesetAuthorTimeChangeLog
13242clevy2020-07-03T17:33:16+02:00

Update vlaidation script and READN for CPL_OASIS test case, see #2379

12669clevy2020-04-03T17:21:52+02:00

Update TOYATM for future NEMO release, see #2379

12663clevy2020-04-03T15:01:04+02:00

Add CPL_OASIS test case, see #2379

Attachments (1)

README_TOYATM_NEMO_12022020.txt (3.6 KB) - added by emalod 3 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 3 years ago by timgraham

  • Cc timgraham added

Changed 3 years ago by emalod

comment:2 Changed 3 years ago by emalod

Preview from L. Coquart and E. Maisonnave (CERFACS)

We validate Claire's workplan as described in the wikipage with the following remarks:
1- The described configuration was successfully assembled, compiled and executed on the CERFACS Intel Skylake computer. The different steps are described in the attached document README_TOYATM_NEMO_12022020.txt​
2- STEP 1: we propose to rename CPL_TOYATM configuration removing TOYATM from the name, to avoid confusion between the coupled configuration of NEMO and the TOYATM executable. We agree in saving the NEMO configuration in tests/ and the toy in tools/. We suggest to provide a reference ATSSTSST_toyatm_01.nc file (which includes the SST coupling fields) that would be compared with the newly produced coupling field for validation. The similarity of a simple spatial average should validate the coupled implementation. Concerning validation, we propose to share the work between CERFACS and the NEMO consortium: the same validation procedure can be done by CERFACS at any OASIS release and by the NEMO consortium at any NEMO release. CERFACS' validation would be done using the last NEMO release, and not the trunk.
3- STEP 2: we propose to keep the validation as it is for the moment. The NEMO configuration includes SI3 and TOP-PISCES, even though these modules are not explicitly coupled. We propose to validate the ocean-atmosphere interface only, as a starting point.
4- STEP 3: we propose to start from CERFACS' testcase to build NEMO testcase (see attached files and previous comments)

comment:3 Changed 3 years ago by emalod

  • wp_comment changed from Preview to Preview: OK

comment:4 Changed 3 years ago by clevy

  • Cc coquart added; timgraham removed

comment:5 Changed 3 years ago by clevy

In 12663:

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

comment:6 Changed 3 years ago by clevy

In 12669:

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

comment:7 Changed 2 years ago by clevy

In 12710:

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

comment:8 Changed 2 years ago by smasson

In 13201:

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

comment:9 Changed 2 years ago by clevy

In 13242:

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

comment:10 Changed 18 months ago by nemo

  • Milestone changed from 2020 WP to Unscheduled
Note: See TracTickets for help on using tickets.