[Wrf-users] out-of-bound situation of the argument idt in SUBROUTINE geth_newdate (ndate, odate, idt)

[Andy Show]

Dear WRF users,

I'm using WRF (v3.6.1) with CLM option  to do a long term simulation (from
2006-01-01_06:00:00 to 2100). And the model stopped at the time around
2074-02-05_09:00:00 in the CLM step as following.
*   print*,'The integer idt and idts is too large; Stop in
module_sf_clm.F', idt,idts*
I checked the value of idt and it was larger than the upper bound of
INTEGER, 2,147,483,647 ( 2**31-1).

In CLM, it calls the subroutine *geth_newdate (ndate, odate, idt)* , where
idt is an INTEGER.

So, it looks like that WRF DOESN'T allow the running time larger than
2,147,483,647 seconds.

Thanks,
Ciao,

Andy

The following is a part of SUBROUTINE geth_newdate

 * SUBROUTINE geth_newdate (ndate, odate, idt) *

*      IMPLICIT NONE*

*      !  From old date ('YYYY-MM-DD HH:MM:SS.ffff') and *
*      !            [or ('YYYY-DDDDD HH:MM:SS.ffff')]*
*      !  delta-time, compute the new date.*

*      !  on entry     -  odate  -  the old hdate.*
*      !                  idt    -  the change in time*

*      !  on exit      -  ndate  -  the new hdate.*

*      INTEGER , INTENT(IN)           :: idt*
*      CHARACTER (LEN=*) , INTENT(OUT) :: ndate*
*      CHARACTER (LEN=*) , INTENT(IN)  :: odate*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/wrf-users/attachments/20151125/cb6a6e59/attachment.html