New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Changeset 8885 for branches/2017/dev_CNRS_2017/NEMOGCM/NEMO/SAS_SRC/step.F90 – NEMO

Ignore:
Timestamp:
2017-12-04T10:41:40+01:00 (6 years ago)
Author:
clem
Message:

remove useless references to clem's comments

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/2017/dev_CNRS_2017/NEMOGCM/NEMO/SAS_SRC/step.F90

    r8882 r8885  
    2424   USE diawri           ! Standard run outputs             (dia_wri routine) 
    2525   USE bdy_oce   , ONLY: ln_bdy 
    26    USE bdydta           ! clem: mandatory for ESIM 
     26   USE bdydta           ! mandatory for sea-ice 
    2727   USE stpctl           ! time stepping control            (stp_ctl routine) 
    2828   ! 
     
    3737 
    3838#if defined key_agrif 
    39    USE agrif_oce, ONLY: lk_agrif_debug  !clem 
     39   USE agrif_oce, ONLY: lk_agrif_debug 
    4040#endif 
    4141    
     
    8989                             CALL iom_setkt( kstp - nit000 + 1, cxios_context )   ! tell iom we are at time step kstp 
    9090 
    91       ! ==> clem: open boundaries is mandatory for ESIM because ice BDY is not decoupled from   
     91      ! ==> clem: open boundaries is mandatory for sea-ice because ice BDY is not decoupled from   
    9292      !           the environment of ocean BDY. Therefore bdy is called in both OPA and SAS modules. 
    9393      !           From SAS: ocean bdy data are wrong  (but we do not care) and ice bdy data are OK.   
     
    114114                             CALL dia_wri_state( 'output.abort', kstp ) 
    115115      ENDIF 
    116       IF( kstp == nit000   ) CALL iom_close( numror )     ! close input  ocean restart file (clem: not sure...) 
     116      IF( kstp == nit000   ) CALL iom_close( numror )     ! close input  ocean restart file 
    117117       
    118118      !>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
Note: See TracChangeset for help on using the changeset viewer.