Opening of a branch for 2012 development of the TOP interface with complex BGC models like the BFM.

http://forge.ipsl.jussieu.fr/nemo/svn/branches/2012/dev_r3379_CMCC6_topbfm

Hi all

we are wondering why the check of consistency between dates in the namelist and in the restart file is done also for nn_rstctl=2. This means that there is no way to let the restart file drive the date and it's always needed to keep track of dates in the namelist.

Is there a specific reason for not moving the following lines in daymod.F90

            IF( nit000 - NINT( zkt ) /= 1 .AND. nrstdt /= 0 )                                         &
                 &   CALL ctl_stop( ' ===>>>> : problem with nit000 for the restart',                 &
                 &                  ' verify the restart file or rerun with nrstdt = 0 (namelist)' )

in the else part of the following if statement:

            ! define ndastp and adatrj
            IF ( nrstdt == 2 ) THEN
               ! read the parameters correspondting to nit000 - 1 (last time step of previous run)
               CALL iom_get( numror, 'ndastp', zndastp )
               ndastp = NINT( zndastp )
               CALL iom_get( numror, 'adatrj', adatrj  )
            ELSE
               ! parameters correspondting to nit000 - 1 (as we start the step loop with a call to day)
               ndastp = ndate0 - 1     ! ndate0 read in the namelist in dom_nam, we assume that we start run at 00:00
               adatrj = ( REAL( nit000-1, wp ) * rdttra(1) ) / rday
               ! note this is wrong if time step has changed during run 
            ENDIF

and assigning zkt read from the restart file into nit000?

nit000 = NINT(zkt)

Create a branch for the merge of CMCC developments in 2012 :

dev_r3365_CMCC1_BDYOBCopt dev_r3379_CMCC6_topbfm