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.
#339 (monthly outputs with monthly jobs) – NEMO

Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#339 closed Enhancement (fixed)

monthly outputs with monthly jobs

Reported by: smasson Owned by: nemo
Priority: low Milestone:
Component: OCE Version: v3.0
Severity: Keywords:
Cc:

Description

Is it really possible to do monthly outputs with monthly jobs (for example get Jan mean with a first run of 31 days and Feb mean with a second run of 28 days)?
The response is... YES!!
for example with ORCA2 which has 15 time steps per day use:

Monthnit000nitendnwritenstock
Jan115*31 = 465465465 (or any larger value)
Feb15*31 + 1 = 46615*59 = 88515*28 = 420885 (or any larger value)

but you will get:

  • wrong informations in ocean.outputs
  • wrong results in outputs done by from diagap.F90, diaptr.F90, trdmld.F90 and trdmld_trc.F90

This ticket fixes these minors bugs.

Commit History (2)

ChangesetAuthorTimeChangeLog
8395jpalmier2017-07-31T14:20:01+02:00

JPALM -- GMED #339 - split trcbio_medusa only

1342ctlod2009-03-24T11:19:33+01:00

update namelist in reference to tickets: #322, #339 & #361

Change History (2)

comment:1 Changed 14 years ago by smasson

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

fixed, see changeset:1317

comment:2 Changed 14 years ago by smasson

Not really working...
Because the value of nstock was automatically limited to nitend - nit000 + 1
fixed, see changeset:1335

Note: See TracTickets for help on using tickets.