Doubt in the time index of multiple years forcing files

[tara]

Hello Roms Community,

I have doubt about the time index of the forcing files of multiple years say eg.(1998 to 2008).So, consider if my 1998 year file has daily information with time index (0, 364)and next file of year 1999 also have 0 to 364 days.The model when switch to the next year forcing file then it will read the time index as (365 to 729) days or default time index as 0 to 364.

please suggest something for this doubt and share if any other information is also necessary to set or notice for any interannual (multiple year observed forcing files)run.

With Best Regards---
Tara

[kate]

You want to pick one time origin for your entire run. You set the time origin in ocean.in and then all times in all forcing, boundary, etc. files are relative to that time. Some years ago we picked the start of year 1900 as our time origin for all runs, assuming we'll never run any hindcasts starting before that. We end up with large time values, but it doesn't matter, just be consistent.

Code: Select all

    TIME_REF = 19000101.0d0               ! yyyymmdd.dd
      DSTART = 42003.0d0                  ! days

[tara]

Dear Kate,

Thank you very much for the kind and immediate useful response.

With Best Regards-
Tara