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 .
Dear all,
I have an issue concerning the INT2LM routine that has already happened to some of you. However, I'm unable to solve it with the tips that were given in other threads.
Here is my error:
izerrorgrid is 9
external data file namelist input
ie_ext 1900 1900
je_ext 900 900
lonll -32.794998168945312 -31.392499999999998
latll -9.4610004425048828 -8.0625000000000000
lonur 19.427499771118164 18.080000000000005
latur 15.261500358581543 13.910000000000000
dlon 2.7499998915251962E-002 2.7500000000000000E-002
dlat 2.7500000891086125E-002 2.7500000000000000E-002
pollat 53.862998962402344 53.862998962402344
pollon -162.59700012207031 -162.59700012207031
polgam 0.0000000000000000 0.0000000000000000
wrong grid for LM external parameters
*------------------------------------------------------------*
* PROGRAM TERMINATED BECAUSE OF ERRORS DETECTED
* IN ROUTINE: int2lm_org
*
* ERROR CODE is 2
* Error in read_nc_gdefs_ext_lm
My LMGRId is defined as follows:
LMGRID
ielm_tot = 1800, jelm_tot=800, kelm_tot=60,
pollat = 53.863, pollon = -162.597,
dlon = 0.0275, dlat = 0.0275,
startlat_tot=-8.09, startlon_tot=-31.42,
ke_soil_lm=9,
czml_soil_lm = 0.0050,0.025,0.07,0.16,0.34,0.70,1.42,2.86,5.74,11.50,
irefatm=2,
ivctype=2, !<-- Default is 1 (vertical coordinate system)
lanalyt_calc_t0p0=.TRUE., !<-- new fast wave solver
/END
I already tried different combinations of startlat_tot and startlon_tot such as:
-8.08 -31.32
-8.1175 -31.4475
-8.0625 -31.3925
and some more of those, but it always results in the same error.
Any suggestions on how I could solve this?
if I take the numbers
dx=2.7499998915251962E-002
lonll=-32.794998168945312
latll=-9.4610004425048828
lonll+dx*(0:60)
latll+dx*(0:60)
I get as possible values:
-8.113500 -8.086000 -8.058500
and
-31.4475 -31.4200 -31.3925 -31.3650 -31.3375 -31.3100
so the startlat_tot values you tried may be wrong?
Dear Rolf, thank you for your help and the explanation.
Is there a list with explanations of the Error Codes somewhere? It now finishes with ExtPar but then terminates here:
heck the external parameters from CM
File: /gpfs/data/fs72281/lar/CCLM_vsc5/forcing/cas2023082700.nc
ie_in_tot = 544 je_in_tot = 224
var ee lev min imin jmin max imax jmax mean
CLOSING ncdf FILE
*------------------------------------------------------------*
* PROGRAM TERMINATED BECAUSE OF ERRORS DETECTED
* IN ROUTINE: int2lm_org
*
* ERROR CODE is 38
* Not all necessary fields could be read or interpolated
*------------------------------------------------------------*
Thank you already in advance.
Cheers, Laurenz
Hey, I don´t know about any list…
normally some errors are quite self-explainatory, like the one you got: “Not all necessary fields could be read or interpolated” …. or I can infer the problem from when the error happens (before, after or during a file is read for example)….
if I can´t find the error (and in your case, think that the forcing file ist okay and namelist values match), I search the int2lm source code.
So doing a
grep "Not all necessary fields could be read or interpolated" *
inside the int2lm source code folder gives me the fileexternal_data.f90
and inside before the error message gets set in the code I see the list of variables that gets checked for (depenting on nameslist settings)But maybe my way is stupid 😄 and someone else can tell you about a trouble-shooting list that exists, that I don´t know of 😄
uh, and (was is increasing of decreasing?… I think increasing) changing the namelist parameter idbg_level gives you more infos in the log, which may also help (during this debugging phase)
Cheers
Rolf
Hi, there really is no list of the error codes, but the message mostly gives a good hint. In this case (not all fields could be read) you have to take a look to the file ASCII file OUTPUT: at the very end it contains a list, which fields have been read, and which one not. Then you have to see what you have to change for the input.
Thank you Ullrich for your help.
Dear all.
thank you for your help. The issue has been resolved.
Cheers :)