Opened 5 years ago

Closed 3 years ago

#1667 closed Bug (fixed)

coherence between time steps , forcing frequency and output frequency

Reported by: cbricaud Owned by: rbourdal
Priority: low Milestone:
Component: OCE Version: release-3.6
Severity: Keywords:
Cc:

Description

we have to take care about the coherence between time steps , forcing frequency and oupt frequency

-ocean time step rdt should be a submultiple of one day and of forcing frequencies
-surface module time step == rdt*nn_fbsc hould be a submuliple of one day and of forcing frequencies
in particular , if rdt=1200s for ORCA025 and forcing frequency is 3h, then:

nn_fsbc=1 : ok because 3*3600/(2*1200)=9
nn_fsbc=2 : nok because 3*3600/(2*1200)=4.5

in those cases, perhaps we should make a test and put a ctl_stp

we have to take care about the coherence bewteen the ocean time step and the frequency output
for example, rdt=1350s and 1 hours frequency output is not ok

Commit History (3)

ChangesetAuthorTimeChangeLog
8530cbricaud2017-09-15T17:40:46+02:00

fix ticket #1667 in trunk

8529cbricaud2017-09-15T17:37:45+02:00

fix ticket #1667 in nemo_v3_6_STABLE

6619cetlod2016-05-25T14:52:53+02:00

Minor bug correction, see ticket #1667

Change History (2)

comment:1 Changed 3 years ago by clevy

  • Owner changed from nemo to rbourdal

comment:2 Changed 3 years ago by cbricaud

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

fix at http://forge.ipsl.jussieu.fr/nemo/changeset/8529 for nemo 3.63 and http://forge.ipsl.jussieu.fr/nemo/changeset/8530 for trunk
a test has been added and a warning message appears in the ocean.output when the coherency is not good between frequency of forcing and SBC timestep.

Note: See TracTickets for help on using tickets.