New URL for NEMO forge!

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.
#601 (use integer in calendar to avoid truncation error) – NEMO

Opened 15 years ago

Closed 15 years ago

Last modified 14 years ago

#601 closed Bug (fixed)

use integer in calendar to avoid truncation error

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


In order to avoid truncation error, we use integer in calendar computation.

To be able to do this we must have:

  • the number of second of in a day must be an even number
  • the time step (in second) must be an even number
  • the forcing frequency must be an integer => impossible to force with higher frequency than hours or change the following line infldread:
             ifreq_sec = sdjf%nfreqh * 3600   ! frequency mean (in seconds)

In dom_oce, we replaced :
rsec_year -> nsec_year
rsec_month -> nsec_month
rsec_day -> nsec_day
sec1jan000 -> nsec1jan000
rmonth_half -> nmonth_half
rmonth_end -> nmonth_end

In fldread, we replaced
freqh -> nfreqh
swap_sec -> nswap_sec
rec_b -> nrec_b
rec_a -> nrec_a

In the namelists, all frequency forcing are given in integer instead of real

for fjulday and adatrj, we also check if their value corresponds to an integer (very important for the output files and their calendar...)

Commit History (0)

(No commits)

Change History (2)

comment:1 Changed 15 years ago by smasson

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

done, see changeset:1730

warning: namelist parameters related to the forcing informations (fld_n definition) must be updated in order to use integer instead of real

comment:2 Changed 14 years ago by anonymous

  • Milestone 2009 Stream 1: User Interfaces deleted

Milestone 2009 Stream 1: User Interfaces deleted

Note: See TracTickets for help on using tickets.