mengronglu
New member
Previously, I had run multiple simulations using the same dataset, model, and parameters. Later, I modified p_top_requested = 10000 and successfully completed a full simulation, obtaining the wrfout output.
When I tried to run it again afterwards, the error started to occur:
Error info 1:
===========================================================
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 330337484 bytes allocated
med_initialdata_input: calling input_input
Input data is acceptable to use:
CURRENT DATE = 2022-09-01_00:00:00
SIMULATION START DATE = 2022-09-01_00:00:00
Max map factor in domain 1 = 1.01. Scale the dt in the model accordingly.
D01: Time step = 120.0000 (s)
D01: Grid Distance = 30.00000 (km)
D01: Grid Distance Ratio dt/dx = 4.000000 (s/km)
D01: Ratio Including Maximum Map Factor = 4.041906 (s/km)
D01: NML defined reasonable_time_step_ratio = 6.000000
---- WARNING : Older v3 input data detected
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 684
---- Error : Cannot use moist theta option with old data
-------------------------------------------
Abort(1) on node 22 (rank 22 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 22
===========================================================
Afterwards I tried many times but it still didn’t work. I checked the data and confirmed there was no missing TITLE with V4.* — I have always included it. I then prepared to rerun real.exe to regenerate the data, but a new issue occurred:
Error info 2:
===========================================================
Using sfcprs3 to compute psfc
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 6506
troubles, could not find trapping x locations
-------------------------------------------
Abort(1) on node 1 (rank 1 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 1
===========================================================
I then found on the forum that in some cases, errors occurred after modifying p_top_requested = 10000. So I readjusted p_top_requested = 5000 and regenerated the new met_em.d0* data starting from WPS. However, the same error still occurred — “troubles, could not find trapping x locations,” as shown in the attached file.
This happened even after I changed the input data (I originally used ERA5_pl together with surface reanalysis data and Vtable.ECMWF, and then tried GFS-FNL data with Vtable.GFS) and even after recompiling WPS (v4.1) and WRF (v4.5.2, same version as before). The problem still persisted. (rsl.error.0014 are attatched)
Therefore, my question is: in my sample file, which variables are incorrect? Is it the PRES variable, where the data at k=0 comes from PSFC? However, I have previously run large-domain simulations in cases where PRES at k=0 was also taken from PSFC, and I did not encounter similar issues.
Given that all these problems occurred after I once modified p_top_requested, I am not sure whether this could have any lasting or potential effects on the system environment.
Because after error info 1 occurred, I used the same set of data without rerunning WPS, modified p_top_requested, and ran the model with the original met_em.d0* data. The error message I got was:
Error info 3:
===========================================================
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 95 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 96 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 97 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 98 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 99 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 100 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 101 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 102 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 103 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 104 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 105 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 106 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 107 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 108 30 38 , setting Qv to 0
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1339
grid%p_top > previous value
-------------------------------------------
Abort(1) on node 2 (rank 2 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 2
===========================================================
When I tried to run it again afterwards, the error started to occur:
Error info 1:
===========================================================
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 330337484 bytes allocated
med_initialdata_input: calling input_input
Input data is acceptable to use:
CURRENT DATE = 2022-09-01_00:00:00
SIMULATION START DATE = 2022-09-01_00:00:00
Max map factor in domain 1 = 1.01. Scale the dt in the model accordingly.
D01: Time step = 120.0000 (s)
D01: Grid Distance = 30.00000 (km)
D01: Grid Distance Ratio dt/dx = 4.000000 (s/km)
D01: Ratio Including Maximum Map Factor = 4.041906 (s/km)
D01: NML defined reasonable_time_step_ratio = 6.000000
---- WARNING : Older v3 input data detected
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 684
---- Error : Cannot use moist theta option with old data
-------------------------------------------
Abort(1) on node 22 (rank 22 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 22
===========================================================
Afterwards I tried many times but it still didn’t work. I checked the data and confirmed there was no missing TITLE with V4.* — I have always included it. I then prepared to rerun real.exe to regenerate the data, but a new issue occurred:
Error info 2:
===========================================================
Using sfcprs3 to compute psfc
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 6506
troubles, could not find trapping x locations
-------------------------------------------
Abort(1) on node 1 (rank 1 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 1
===========================================================
I then found on the forum that in some cases, errors occurred after modifying p_top_requested = 10000. So I readjusted p_top_requested = 5000 and regenerated the new met_em.d0* data starting from WPS. However, the same error still occurred — “troubles, could not find trapping x locations,” as shown in the attached file.
This happened even after I changed the input data (I originally used ERA5_pl together with surface reanalysis data and Vtable.ECMWF, and then tried GFS-FNL data with Vtable.GFS) and even after recompiling WPS (v4.1) and WRF (v4.5.2, same version as before). The problem still persisted. (rsl.error.0014 are attatched)
Therefore, my question is: in my sample file, which variables are incorrect? Is it the PRES variable, where the data at k=0 comes from PSFC? However, I have previously run large-domain simulations in cases where PRES at k=0 was also taken from PSFC, and I did not encounter similar issues.
Given that all these problems occurred after I once modified p_top_requested, I am not sure whether this could have any lasting or potential effects on the system environment.
Because after error info 1 occurred, I used the same set of data without rerunning WPS, modified p_top_requested, and ran the model with the original met_em.d0* data. The error message I got was:
Error info 3:
===========================================================
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 95 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 96 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 97 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 98 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 99 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 100 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 101 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 102 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 103 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 104 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 105 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 106 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 107 30 38 , setting Qv to 0
d01 2022-09-01_09:00:00 t(i,j,k) was 0 at 108 30 38 , setting Qv to 0
-------------- FATAL CALLED ---------------
FATAL CALLED FROM FILE: <stdin> LINE: 1339
grid%p_top > previous value
-------------------------------------------
Abort(1) on node 2 (rank 2 in comm 0): application called MPI_Abort(MPI_COMM_WORLD, 1) - process 2
===========================================================