Please help me in rectifying this error.

[kpk13]

----- ERROR: The reference pressure is not monotonically decreasing
This tends to be caused by very high topography
(i,j) = 234 172 , topography = 4005.48657 m
k = 11 , reference pressure = 60157.9219 Pa
k = 12 , reference pressure = 60158.7578 Pa
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1249
In the dynamics namelist record, reduce etac from 9.99999978E-03
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

I am attaching the namelist.input file as well as the rsl.error.0000 files here.

 

[Ming Chen]

This is a data issue. Note that REAL program requires the pressure levels in input data (i/e/. met_em files) to be monotonically increase or decrease. Your data is not organized in this way. Please correct met_em files before running REAL.

 

[Khin Myat]

Dear @Ming Chen ,

I am also having similar issue as kpk13. Could you please explain a little more about "correct met_em files before running REAL" and how I can correct the met_em file?
I also attached the name list and rsl—error file.
Thank you in advance for your time.

 

[Ming Chen]

If the vertical levels in met_em files are not monotonically increase or decrease, you need to read the data, rewrite them in levels from bottom up or from top down.
It is quite unusual that the large scale forcing data are randomly distributed in the vertical. I wonder what data did you ungrib?

 

[Khin Myat]

Dear Ming Chen,
Thank you very much for your reply. I am sorry that I attached the wrong error file.
I ungribed the NCEP GDAS/FNL 0.25 Degree data.
May I know if this error could relate to the usage of high-resolution terrain data? I think the error started in domain 3 where I assigned the higher resolution data.

Best,
Khin

 

[Ming Chen]

Khin,
Please add etac = 0.1 to your namellist.input (&dynamics), then try again. Let me know whether this can fix your problem.

 

[Khin Myat]

Dear @Ming Chen,
Thank you very much.
I have tried with etac =0.1 and 0.05 but it did not fix my problem.

Best,
Khin

 

[Khin Myat]

Dear @Ming Chen,
I have found my problem. It was the terrain data. When I checked the terrain data, I found some files were missing. When I reupload the terrain data, real.exe could be run successfully without modifying etac value.
Thank you for your time and advice.

Best,
Khin

 

[Ming Chen]

Khin,
Thank you for the update. I am glad it works for you. I am just curious about the terrain data , ---- if the data is missing somewhere in your domain, then I suppose metgrid should crash. How did you manage to pass the metgrid and reach the real program?

 

[Khin Myat]

Dear @Ming Chen,
I did not do any modifications when I ran the metgrid. When I looked up the binary file of terrain data, some binary file sizes were 0MB although there were all the binary files. When I changed the terrain data file, it worked for me.

Best,
Khin

 

[Ming Chen]

Thank you for the update. I guess the issue is related to unreasonable terrain data, but the value of the terrain height is not missing value. This makes sense because WPS cannot handle missing value, yet it works if the variable has a 'value', even if the value is unreasonable.

 

[AlbinSabu]

Dear @Ming Chen,
I did not do any modifications when I ran the metgrid. When I looked up the binary file of terrain data, some binary file sizes were 0MB although there were all the binary files. When I changed the terrain data file, it worked for me.

Best,
Khin

Dear @Khin Myat

I am facing the same problem. I would like to know which terrain data are you talking about.

Best regards,
Albin

 

[Khin Myat]

Dear @AlbinSabu ,
The terrain data that I used is ASTER Global Digital Elevation Model V003.

Best,
Khin