Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

(RESOLVED) Real.exe, error:could not find trapping x locations

Lily_Zh

Member
Hello,

I am running WRF3.8 real.exe, got this error on 2017-07-01_03, began run from 2017-06-21. I attached the met file and namelist.input.
I used NAM met data, NCLD40,
used WPS-ghrsst-to-intermediate to process GHRSST MUR 1km data got every three-hour SST file with SST and SSTMASK variable and replace landsea using sstmaks for SKINTEMP and SST in metgrid/METGRID.TBL.ARW, (ignored WARNING: Entry in METGRID.TBL not found for field SSTMASK. Default options will be used for this field!, compared SKINTEMP, has diff value along coastline),
also used MADIS/point/metar data to get wrfsffda.

I am not sure the reason. I will be thankful for any suggestion.

d01 2017-07-01_03:00:00 Timing for input 6 s.
d01 2017-07-01_03:00:00 med_sidata_input: calling optional_input
d01 2017-07-01_03:00:00 flag_soil_layers read from met_em file is 1
d01 2017-07-01_03:00:00 flag_soil_layers at end of optional_lsm_levels is 1
d01 2017-07-01_03:00:00 flag_soil_levels at end of optional_lsm_levels is 0
d01 2017-07-01_03:00:00 st_levels_input = 5 25 70 150
d01 2017-07-01_03:00:00 sm_levels_input = 5 25 70 150
d01 2017-07-01_03:00:00 sw_levels_input = 5 25 70 150
d01 2017-07-01_03:00:00 med_sidata_input: back from init_domain
d01 2017-07-01_03:00:00 med_sidata_input: calling init_domain
d01 2017-07-01_03:00:00 checking boundary conditions for grid
d01 2017-07-01_03:00:00 boundary conditions OK for grid
Using sfcprs3 to compute psfc
d01 2017-07-01_03:00:00 calling inc/HALO_EM_VINTERP_UV_1_inline.inc
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 5346
troubles, could not find trapping x locations
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 20

Thank you.

Lily
 

Attachments

  • namelist.input
    6.6 KB · Views: 41
  • metoa_em.zip
    247.9 MB · Views: 30
Hi Lily,
Can you try to set p_top_requested to 5000 in your namelist.input file and see if that makes a difference? Thanks!
 
Thank you for your reply!
Sorry, I uploaded a wrong namelist.input.
The namelist.input I used set p_top_requested =5000. Let me attach it and one wrfsfdda file
I tried to use met_em without SST and landsea update, the error still exist.

Thank you.
 

Attachments

  • namelist.input
    6.7 KB · Views: 40
  • wrfsfdda_d01.zip
    153.2 MB · Views: 28
I found there is NaN in rsl.out file.

d01 2017-07-01_03:00:00 calling inc/HALO_EM_VINTERP_UV_1_inline.inc
i,j = 131 21
target pressure and value = 10.53415 9514.549
column of pressure and value = 11.58932 0.0000000E+00
column of pressure and value = 11.58349 50.93316
column of pressure and value = 11.55992 277.2463
column of pressure and value = 11.53578 512.0856
column of pressure and value = 11.51104 751.7999
column of pressure and value = 11.48603 996.5197
column of pressure and value = 11.46049 1246.259
column of pressure and value = 11.43428 1501.409
column of pressure and value = 11.40733 1762.495
column of pressure and value = 11.37962 2029.869
column of pressure and value = 11.35110 2304.094
column of pressure and value = 11.32171 2585.815
column of pressure and value = 11.29137 2875.484
column of pressure and value = 11.26001 3173.593
column of pressure and value = 11.22757 3480.454
column of pressure and value = 11.19401 3796.404
column of pressure and value = 11.15927 4121.673
column of pressure and value = 11.12325 4456.551
column of pressure and value = 11.08587 4801.768
column of pressure and value = 11.04702 5158.387
column of pressure and value = 11.00659 5527.677
column of pressure and value = 10.96442 5910.798
column of pressure and value = 10.92036 6309.476
column of pressure and value = 10.87426 6725.913
column of pressure and value = 10.82589 7162.677
column of pressure and value = 10.77502 7622.538
column of pressure and value = 10.72138 8107.297
column of pressure and value = 10.66469 8618.919
column of pressure and value = 10.60456 9160.081
column of pressure and value = NaN -1.5742746E+07
column of pressure and value = 8.517193 20787.68
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 5346
troubles, could not find trapping x locations
-------------------------------------------
 
Hi,
Thanks for sending the correct file. Besides a problem with the p_top_requested setting, this error can sometimes occur when the met_em* files are missing data in the upper levels (meaning the input data was missing those levels). I glanced through your metoa* files and didn't see anything immediately, but you may want to look a little closer, just to make sure.

Your e_vert setting is also pretty low for the size of your domains. I would recommend increasing that to at least 50. I'm not certain whether this could cause this error, but you can try that and see if makes a difference.
 
Thank you for your reply and suggestion!
I checked the NAM files I used, they are every 6 hours, but I used it to generate every 3 hours met_em. I am not sure if it lead to missing data.
I will used 40km Eta files for 03, 09, 15... hour and try again.

Thank you.

Lily
 
I added Eta and NAM for fg_name of metgrid part in namelist.wps.
p_top_reuqested=50 and add Eta data both did not work.
 
I found it should be a bug for WPS3.8 for NAM.
https://www2.mmm.ucar.edu/wrf/users/wps_files/wpsv3.8/known-prob-3.8.html

but the bug fix package link did not work.
https://www2.mmm.ucar.edu/wrf/users/src/fix_wps/wps_bug_fix_March2017.tar

Let me try WPS3.9
 
Hi,
I've tried searching for that bug fix file on our server and I'm unable to locate it. I assume the source code for WPSV3.9 should include the fix, so hopefully that will work for you. Please let me know. Thanks!
 
Top