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.
#1069 (AMM12 restartability problem) – NEMO

Opened 11 years ago

Closed 9 years ago

Last modified 2 years ago

#1069 closed Defect (fixed)

AMM12 restartability problem

Reported by: jchanut Owned by: nemo
Priority: lowest Milestone:
Component: OCE Version: v3.4
Severity: Keywords: AMM* BDY OPA restartability v3.4
Cc:

Description

This ticket, just to prevent you from doing the same mistake I did...

I have been struggling for a while to find out why AMM12 configuration (v3.4) was not giving identical results when started from an intermediate restart file. I finally found that this test was obviously not compatible with the use of boundary data taken at initial time (nn_tra_dta=0 in namelist), and a flow relaxation scheme. In that case, boundary data is indeed not the same in each run.

This option has been changed in v3.5alpha, so that now nn_tra_dta=1 (for which reason ?). This may not be an issue anymore. If this change is related to the restartability problem mentioned here, it would have been nice to know it somehow...

Commit History (0)

(No commits)

Change History (8)

comment:1 Changed 9 years ago by clevy

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

comment:2 Changed 8 years ago by nicolasmartin

  • Keywords BDY added; bdy removed

comment:3 Changed 8 years ago by nicolasmartin

  • Keywords nemo_v3_4* added

comment:4 Changed 6 years ago by nemo

  • Keywords AMM* added; AMM12 removed

comment:5 Changed 6 years ago by nemo

  • Keywords release-3.4* added; nemo_v3_4* removed

comment:6 Changed 6 years ago by nemo

  • Keywords restartability added; restart removed

comment:7 Changed 6 years ago by nemo

  • Keywords release-3.4* removed

comment:8 Changed 2 years ago by nemo

  • Keywords OPA v3.4 added
Note: See TracTickets for help on using tickets.