Push notifications in your browser are not yet configured.
You are not logged in, you may not see all content and functionalities. If you have an account, please login .
Maximum number of variables per GRIBOUT block
I am using the CCLM 4.8_clm19 version and encountered an unexpected behaviour of CCLM :
If I define only one GRIBOUT block with default variables, then everything is ok and about 70 variables are written to the netcdf output.
But if I define several blocks, than the maximum number of variables for the second block seems to be 15?
Does anyone know about this problem? The model crashes with this message:
Here the definitions of the GRIBOUT blocks (with ngribout=2).
!out02: 2d variables (often used) &GRIBOUT ysystem=‘file’, hcomb= 0.0,29.0,1.0, l_p_filter=.FALSE., l_z_filter=.FALSE., yvarml=’‘, yvarpl=’‘, yvarzl=‘ RAIN _CON’,‘ SNOW _CON’,‘ RAIN _GSP’,‘ SNOW _GSP’,‘ GRAU _GSP’,‘ TOT _PREC’,‘ CLCT ’,‘ CLCH ’,‘ CLCL ’,‘ CLCM ’,‘ HPBL ’,‘ DURSUN ’,‘ PMSL ’,‘PS’,‘QV_2M’,‘T_2M’, luvmasspoint=.FALSE., lcheck =.TRUE., lwrite_const=.TRUE., ydir=’${outpath}/out02/’, ytunit=‘d’, /END
If I remove “T_2M” from block 2, then there are 15 variables and the model runs…
Thanks for help!
You have chosen the wrong level option. It should be
yvarml
notyvarzl
. It does not make sense to interpolate 2D-Variables to z-levels, which may give some very interesting results ;-)The maximum number of variables that can be chosen are as follows (this holds at least for cclm4.8_clm19)
Burkhardt is right.
And why do you store the constant variables in each GRIBOUT -block (lwrite_const=.TRUE.)?
Storing them in your 1. Block makes sense, since seems to contain all variables which are necessary for a further downscaling.
But storing them twice is a waste of disk capacity.
Hans-Jürgen
Okay, thank you Burkhardt, that was the error :)
@Hans-Jürgen: you are right, that doesn’t make sense. That was an old relict of a former configuration, but I set lwrite_const=.FALSE. for all GRIBOUT s except out01.