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.
#2623 (fldread not accepting the absence of next run input files at the end of a simulation) – NEMO

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#2623 closed Bug (fixed)

fldread not accepting the absence of next run input files at the end of a simulation

Reported by: smasson Owned by: systeam
Priority: low Milestone:
Component: SBC Version: trunk
Severity: minor Keywords:
Cc:

Description

Context

Because of the temporal interpolation, fldread must often access the input files corresponding to the previous/next run.
This feature is needed to insure restartability but is quite annoying when you need to provide the input files before or after the full simulation.
For example if you do a 10-year simulation with 1-year long runs, you usually do not want to prepare the input files for the year before the simulation and after the 10 years.
It was therefore decided that the code accept the absence of previous/next input files if we are at the beginning/the end of the simulation.

Analysis

This feature is broken for the end of the simulation since fldread calendar was rewritten.

Fix

simply replace a > by a >=

Commit History (2)

ChangesetAuthorTimeChangeLog
14437smasson2021-02-11T16:38:56+01:00

trunk: true bugfix in fldread, following [14436], #2623

14436smasson2021-02-11T12:48:59+01:00

trunk: minor bugfix in fldread, #2623

Change History (3)

comment:1 Changed 3 years ago by smasson

In 14436:

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

comment:2 Changed 3 years ago by smasson

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

comment:3 Changed 3 years ago by smasson

In 14437:

Error: Failed to load processor CommitTicketReference
No macro or processor named 'CommitTicketReference' found
Note: See TracTickets for help on using tickets.