You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
FATAL CALLED FROM FILE: <stdin> LINE: 5817 invalid parent id for domain 2
- Thread starter loly_
- Start date
I'm working with data gfs: gfs.t00z.pgrb2.0p50.f012 .....gfs.t00z.pgrb2.0p50.f036
Hi,
Okay I took a closer look at your namelist.input file, and I'm not sure why this would be causing that particular error, but the issue is this line:
That is not a namelist parameter, so you'll need to remove that. You'll then need to change num_metgrid_levels to = 34. Not related to this error, you also need to increase your e_vert settings. Try using something like = 45, 45.
Okay I took a closer look at your namelist.input file, and I'm not sure why this would be causing that particular error, but the issue is this line:
Code:
BOTTOM-TOP_GRID_DIMENSION = 34,That is not a namelist parameter, so you'll need to remove that. You'll then need to change num_metgrid_levels to = 34. Not related to this error, you also need to increase your e_vert settings. Try using something like = 45, 45.
So, I need the new problem
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 1126949440 bytes allocated
d01 2023-06-15_12:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.5
d01 2023-06-15_12:00:00 Input data is acceptable to use: met_em.d01.2023-06-15_12:00:00.nc
metgrid input_wrf.F first_date_input = 2023-06-15_12:00:00
metgrid input_wrf.F first_date_nml = 2023-06-15_12:00:00
d01 2023-06-15_12:00:00 Timing for input 0 s.
d01 2023-06-15_12:00:00 flag_soil_layers read from met_em file is 1
d01 2023-06-15_12:00:00 Turning off use of MAX WIND level data in vertical interpolation
d01 2023-06-15_12:00:00 Turning off use of TROPOPAUSE level data in vertical interpolation
Max map factor in domain 1 = 1.21. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
d01 2023-06-15_12:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2023-06-15_12:00:00 forcing artificial silty clay loam at 2 points, out of 33432
d01 2023-06-15_12:00:00 Timing for processing 1 s.
d01 2023-06-15_12:00:00 Timing for output 2 s.
d01 2023-06-15_12:00:00 Timing for loop # 1 = 3 s.
DYNAMICS OPTION: Eulerian Mass Coordinate
alloc_space_field: domain 1 , 1126949440 bytes allocated
d01 2023-06-15_12:00:00 Yes, this special data is acceptable to use: OUTPUT FROM METGRID V4.5
d01 2023-06-15_12:00:00 Input data is acceptable to use: met_em.d01.2023-06-15_12:00:00.nc
metgrid input_wrf.F first_date_input = 2023-06-15_12:00:00
metgrid input_wrf.F first_date_nml = 2023-06-15_12:00:00
d01 2023-06-15_12:00:00 Timing for input 0 s.
d01 2023-06-15_12:00:00 flag_soil_layers read from met_em file is 1
d01 2023-06-15_12:00:00 Turning off use of MAX WIND level data in vertical interpolation
d01 2023-06-15_12:00:00 Turning off use of TROPOPAUSE level data in vertical interpolation
Max map factor in domain 1 = 1.21. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
d01 2023-06-15_12:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
d01 2023-06-15_12:00:00 forcing artificial silty clay loam at 2 points, out of 33432
d01 2023-06-15_12:00:00 Timing for processing 1 s.
d01 2023-06-15_12:00:00 Timing for output 2 s.
d01 2023-06-15_12:00:00 Timing for loop # 1 = 3 s.
Attachments
Liangcheng Qiu
New member
Mr Kwerner, I am encountering the same issue when preparing to simulate the process of dust transport. Please review the attached files. Could you please help me identify and resolve the problem? Thank you.Hi,
Do you get this error when you're running wrf.exe or when you run real.exe? Can you attach the full rsl.*.0000 files? It looks like you've only included the final few lines. Please also let me know which version of WPS/WRF you are using. Thanks!
Attachments
@Liangcheng Qiu,
As with the other user, the issue was related to a namelist error (although the error message isn't helpful in determining that). I haven't looked through your entire namelist, but I do notice that you have all of your chemistry variables listed in the &domains namelist record. It looks like you have them in both places. Make sure to put the variables in the correct location in your namelist. If you have any doubts, you can search each variable within the files inside the Registry directory. For e.g.,
(make sure to use the "-i" so that your search is not case-sensitive)
and that gives
You can see that the 4th column shows that it is a namelist variable, and specifically in the &chem section of the namelist.
As with the other user, the issue was related to a namelist error (although the error message isn't helpful in determining that). I haven't looked through your entire namelist, but I do notice that you have all of your chemistry variables listed in the &domains namelist record. It looks like you have them in both places. Make sure to put the variables in the correct location in your namelist. If you have any doubts, you can search each variable within the files inside the Registry directory. For e.g.,
Code:
grep -i kemit *and that gives
Code:
registry.chem:rconfig integer kemit namelist,chem 1 9 irh "kemit" "" ""You can see that the 4th column shows that it is a namelist variable, and specifically in the &chem section of the namelist.
Liangcheng Qiu
New member
Thank you very much. now it is ok. I noticed that there were some duplicates in my namelist.wps.