[RegCNET] help
Graziano Giuliani
ggiulian at ictp.it
Wed Aug 15 11:15:32 CEST 2012
On 08/13/2012 01:03 PM, xhbhyq11 wrote:
> Hi :
> I run regcm4.1.1 with ccsm data, but when leap year
[...]
Please note that RegCM has internal date functions supporting different calendar
types only from version 4.2. In previous versions, only gregorian calendar was
supported (i.e. with leap year). If you must stick to 4.1.1, when using
noleap/360dys calendar input GCMs, your only option is to fake the RegCM.
Just look at the code, and force the jump from 28 of February to March, 1st in
mod_tendency at line 2209 where the addhours subroutine is called. Something like:
if (lmonth == 2 .and. lday == 28 .and. lhours > 18) then
call addhours(ldatez, ibdyfrq+24)
else
call addhours(ldatez, ibdyfrq)
end if
To use instead a 360 days calendar, a more in deep modification to the addhour
function itself would be required.
Another option would be to upgrade to the model latest version.
Ciao!
--
Graziano Giuliani - Earth System Physics Section
The Abdus Salam International Centre for Theoretical Physics
Strada Costiera, 11 - I - 34151 Trieste Italy
More information about the RegCNET
mailing list