Opened 4 years ago

Last modified 2 years ago

#682 new defect

1+1 <> 2 for daily driver files

Reported by: luyssaert Owned by: somebody
Priority: minor Milestone: Not scheduled yet
Component: Driver files Version: trunc
Keywords: Cc:


1D+1D differs from 2D when daily driver files are used. An good test case for this problem is the FG5 configuration. Note that FG5 is NOT the problem but just the test case because FG5 uses daily forcing files. If just the forcing files are replaced by 6-hourly files, 1D+1D equals 2D. Hence, it seems that the code that enables using daily forcing is not restartable.

The problem with the restartability of daily forcing files can likely be traced back to readdim2.f90 because FG5 should use interpol_daily when forced by daily forcing files whereas FG5 forced by 6-hourly files does not.

Some first insights from the code (there is basically no documentation)

  • L1199 reads "IF ((last_read == 0) .OR. ( rw==(1./split)) ) THEN". This block of code reads the forcing data if we have never read them before (first time step in the execution) or in the middle of the day.
  • L1275. Here are either with reading forcing data at the first time step or reading mid-day. If it is the first time step in the day (itau_split).
  • The code around L1282 -> executed at the first time step of the day. Should a restart be read?

Change History (2)

comment:1 Changed 4 years ago by luyssaert

  • Milestone changed from ORCHIDEE 4.0 to ORCHIDEE 4.1
  • Version set to trunc

comment:2 Changed 2 years ago by jgipsl

  • Milestone changed from ORCHIDEE 4.1 to Not scheduled yet
Note: See TracTickets for help on using tickets.