Bug in mod_stepping.f90?

[wangzc]

160 allocate (Lfout(Ngrids))
161 Lbout(1:Ngrids)=1

[kate]

Nice one - there's also an Lbout variable so it would compile, no problem.

[wangzc]

hi kate,
After deleting '#define ADJUST_BOUNDARY' AND '#define ADJUST_STFLUX' in WC13/I4DVAR/wc13.h, this bug is prompted when compiling. By the way, thinking of computation cost and memory space limits, i want to do I4DVAR test by using ROMS_2D first. So every cpp option about solve3D is deleted. As follows,
**-----------------------------------------------------------------------------
** Nonlinear basic state settings.
**-----------------------------------------------------------------------------
*/
#define UV_ADV
#define DJ_GRADPS
#define UV_COR
#define UV_QDRAG
#define UV_VIS2
#define CURVGRID
#define PROFILE
#define SPLINES
#define MASKING

/*
** Common options to all 4DVAR algorithms.
*/

#if defined IS4DVAR

# define ADJUST_WSTRESS
# define FORWARD_WRITE
# define FORWARD_READ
# define OUT_DOUBLE
#endif

Error 1 occured
fortcom: Error: cgradient.f90, line 1179: This name does not have a type, and must have an explicit type. [NF_FREAD3D]
status=nf_fread3d(ng, model, ncname, ncid, &
-------------^
compilation aborted for cgradient.f90 (code 1)
make: *** [/export/home/wangzc/swgfs/projects/WC13/I4DVAR_2D/Build/cgradient.o] Error 1

Then i check the place, it happened in the part !Read surface momentum stress, line 2668 in cgradient.F. while nf_fread3d is just used when define SOVLE3d. 'USE nf_fread_mod, ONLY: nf_fread3d' unconditionally, line 2385 in cgradient.F? Similar question occured in Utility/wrt_hessian.F, line 39, 392 and 421. Also, in Adjoint/ad_wrt_his.F, line 43. Samely, it happened in Tangent/tl_wrt_his.F, line 49.
--zongchen