Is there an upper limit on # of state variables output?

Any problems/questions that might not fall into the other topics in this category.

Is there an upper limit on # of state variables output?

Postby panb » Thu Apr 18, 2019 5:28 pm

Hello,

I want to add some additional state variables output. The variables are added in 1) Registry.EM_COMMON, 2) solve_em.F, 3) corresponding physics package and drivers

It seems that there is a limit on the number of variables in the wrfout. The compiler reported errors, as follow, as I continue to add new variables to Registry.EM_COMMON:
Code: Select all
WARNING: only type 'real', 'doubleprecision', or 'integer' can be part of halo exchange. lake2d in SHIFT_HALO is logical
WARNING 1b : lakemlandmask in halo spec shift_halo () is not defined in registry.
rm -f collect_on_comm.o
mpicc -cc=icc -DMPI2_SUPPORT -DFSEEKO64_OK  -o collect_on_comm.o -c -w -O3 -ip  -DDM_PARALLEL -DMAX_HISTORY=25 -DNMM_CORE=0 collect_on_comm.c
WARNING 1b : lakemlandmask in halo spec shift_halo () is not defined in registry.
WARNING 1b : lakemlandmask in halo spec shift_halo () is not defined in registry.
WARNING 1b : lakemlandmask in halo spec shift_halo () is not defined in registry.
mpicc -cc=icc -DMPI2_SUPPORT -DFSEEKO64_OK  -c -w -O3 -ip  -DDM_PARALLEL -DMAX_HISTORY=25 -DNMM_CORE=0 -DIWORDSIZE=4 pack_utils.c
WARNING 1a : lakemgrid%landmask in halo spec shift_halo () is not defined in registry.
WARNING 1a : lakemgrid%landmask in halo spec shift_halo () is not defined in registry.
rm -f module_wrf_error.o

the variable name in the WARNING is completely random. The following quote is the first error I encountered in the compile.
Code: Select all
module_comm_dm.f90(125): error #6404: This name does not have a type, and must have an explicit type.   [ASK]
CALL rsl_comm_iter_init(ask,jps,jpe)
------------------------^
module_comm_dm.f90(148): error #6404: This name does not have a type, and must have an explicit type.   [NUM_CHEM]
   + num_chem   &
-----^
module_comm_dm.f90(149): error #6404: This name does not have a type, and must have an explicit type.   [NUM_TRACER]
   + num_tracer   &
-----^
compilation aborted for module_comm_dm.f90 (code 1)
make[2]: [module_comm_dm.o] Error 1 (ignored)


It seems like a truncation error on the variable definition. It only happens on the vortex following WRF compilation.
Any suggestions?

Thank you very much!
Bowen
panb
 
Posts: 9
Joined: Fri Oct 30, 2015 1:26 pm

Return to Miscellaneous

Who is online

Users browsing this forum: No registered users and 5 guests