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

troubles, could not find trapping x locations

Yiping

New member
Hi! I am using WRF 4.2 to simulate a heavy rain case and the time range is less than 13 hours. The pressure level data and surface data are from ERA5. However, when I run the real.exe, it shows:
Using sfcprs3 to compute psfc
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 6241
troubles, could not find trapping x locations
-------------------------------------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

Could anyone assist me on how to solve this problem please?

I will show the data I downloaded and my namelist.wps and namelist.input
 

Attachments

  • namelist.input
    3.5 KB · Views: 2
  • namelist.wps
    695 bytes · Views: 2
  • WRF_domain.png
    WRF_domain.png
    1 MB · Views: 5
  • down1.txt
    1.3 KB · Views: 4
  • down2.txt
    1.4 KB · Views: 2
I ran into a similar problem when I was working with WRFv4.2 & ERA5 data.

Don't spatially subset the grid.
So instead of this,
'area': [
55, 80, 5,
160,

Try this,
'area': [
90, -180, -90,
180,


Try using my attached files/scripts (get-era5.txt is Python script which it looks like you are using).
 

Attachments

  • Vtable.txt
    3.4 KB · Views: 1
  • METGRID.TBL.txt
    34.1 KB · Views: 3
  • get-era5.txt
    2.6 KB · Views: 9
  • GEOGRID.TBL.txt
    19.1 KB · Views: 0
You may also download ERA5 from NCAR RDA, which are the ERA5 we have tested and worked fine for WRF.
Please see the attached document that describes what variables should be downloaded.
 

Attachments

  • ERA5_download_instruction.pdf
    539.2 KB · Views: 7
I ran into a similar problem when I was working with WRFv4.2 & ERA5 data.

Don't spatially subset the grid.
So instead of this,
'area': [
55, 80, 5,
160,

Try this,
'area': [
90, -180, -90,
180,


Try using my attached files/scripts (get-era5.txt is Python script which it looks like you are using).
Thank you so much! Now it works!
 
You may also download ERA5 from NCAR RDA, which are the ERA5 we have tested and worked fine for WRF.
Please see the attached document that describes what variables should be downloaded.
Thank you for your help! I downloaded the data with the area below and it works very well!
90, -180, -90,
180,
 
Hi! I am using WRF 4.0 and ERA5 data and have the same problem now. It shows:

taskid: 0 hostname: hpc-cx50_38_i2
module_io_quilt_old.F 2931 T
Ntasks in X 8 , ntasks in Y 16
REAL_EM V4.0 PREPROCESSOR
*************************************
Parent domain
ids,ide,jds,jde 1 418 1 218
ims,ime,jms,jme -4 60 -4 21
ips,ipe,jps,jpe 1 53 1 14
*************************************
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 105545888 bytes allocated
d01 2018-06-25_00:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.0
d01 2018-06-25_00:00:00 Input data is acceptable to use: met_em.d01.2018-06-25_00:00:00.nc
metgrid input_wrf.F first_date_input = 2018-06-25_00:00:00
metgrid input_wrf.F first_date_nml = 2018-06-25_00:00:00
d01 2018-06-25_00:00:00 Timing for input 4 s.
d01 2018-06-25_00:00:00 flag_soil_layers read from met_em file is 1
Max map factor in domain 1 = 1.44. Scale the dt in the model accordingly.
Using sfcprs to compute psfc
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 5875
troubles, could not find trapping x locations
-------------------------------------------
Abort(1) on node 0 (rank 0 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0
In: PMI_Abort(1, application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0)

The attached files are the namelist and scripts I used for simulation and downloading ERA5 data respectively. I have tried to use ERA5 data with the area of [90, -180, -90, 180] as well, but it doesn't work in my test.

Could anyone assist me on how to solve this problem please?

Looking forward to your suggestions! Thank you!
 

Attachments

  • sf20180625_all.txt
    1 KB · Views: 0
  • pl20180625_all.txt
    882 bytes · Views: 0
  • namelist.wps
    1.3 KB · Views: 1
  • namelist.input
    4.6 KB · Views: 0
@Yiping --- Than you for the update. I am glad it works for you.

@Jiarui Liu Can you issue the command below:
ncdump -h met_em > log
(met_em can be any met_em files you produced using ERA5 )

Then send me your log file to take a look? thanks.
 
Thanks for your replying!

The attached file is the log file of one of my met_em files.

I temporarily solved this problem by slightly adjusting the size of the computational domain (the biggest change is to expand the right boundary of the outer layer), but I am still confused about the reason for this error. Is it because my inner right boundary is too close to the outer right boundary? I have attached the picture of my computational domain before and after adjustments.

Looking forward to your answers and suggestions! Thank you!
 

Attachments

  • log.txt
    22.6 KB · Views: 3
  • domain_after_adjustment.png
    domain_after_adjustment.png
    32 KB · Views: 5
  • domain_before_adjustment.png
    domain_before_adjustment.png
    19.1 KB · Views: 4
It seems that you didn't download global ERA5 data. if you only have a subset of global ERA5 over a specific region, and your WRF domain is beyond the region cobered by your ERA5, then you will get the error like "troubles, could not find trapping x locations".
 
Top