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

surface_input_source = 3, mismatch_landmask_ivgtyp error

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.


Dear Colleagues,

For the 'surface_input_source', I can only use option 1, but when I use the default option (3), it reported the error below:
Max map factor in domain 1 = 0.98. Scale the dt in the model accordingly.
Using sfcprs3 to compute psfc
d01 2019-06-11_00:00:00 flag value of flag_qnwfa is 0
d01 2019-06-11_00:00:00 No average surface temperature for use with inland lakes
Assume Noah LSM input
-------------- FATAL CALLED ---------------
application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0

Could you please kindly let me know the reason for this?
For your convenience, I attach my namelist.input file.

By the way, I would like to know:
Based on "parent_grid_ratio = 1, 3, 3", whether there is an obvious running time difference between setting "parent_time_step_ratio" as 1,1,1 and 1,3,3?

Best wishes,


  • namelist.input
    4.3 KB · Views: 40
Hi Stella,
I first would like to apologize for the long delay in response. I've been traveling for the past few weeks and am just now catching up with forum inquiries.Thank you for your patience. Can you let me know what version of WRF you are using and what type of input data?

As for your question about parent_time_step_ratio, yes this can make a difference, but whether the difference is significant will depend on your particular run and your definition of significant. When you set it to 1, 3, 3, domains 02 and 03 are processing data 3x more often, which will take a bit more time. I would suggest that you run a couple of short cases with the settings to compare the difference in timing. You can then interpolate the time to the total time you wish to run your simulation.
Dear Colleague,

Many thanks for your kind reply. I use WRF 3.8.1, and the input data maybe indicate Geographical Static Data, which were downloaded from

By the way, could you please kindly have a look at the other two questions below:

Hope you or your colleagues could help me with them.

Best regards,
In the code dyn_em/module_initialize_real.F, we can find the following piece:
                  print *,'the grid%landmask and soil/veg cats do not match'
                  print *,'i,j=',i,j
                  print *,'grid%landmask=',grid%landmask(i,j)
                  print *,'grid%ivgtyp=',grid%ivgtyp(i,j)
                  print *,'grid%isltyp=',grid%isltyp(i,j)
                  print *,'iswater=', config_flags%iswater
                  print *,'grid%tslb=',grid%tslb(i,:,j)
                  print *,'grid%sst=',grid%sst(i,j)
                  CALL wrf_error_fatal ( 'mismatch_landmask_ivgtyp' )
               END IF

What are the other information before the message of  'mismatch_landmask_ivgtyp'?
Would you please send me your namelist.wps to take a look? Thanks.
Dear Ming,

Thanks for your kind reply. The attachment is my namelist.wps.

Best regards,


  • namelist.wps
    1.7 KB · Views: 28
Hi Stella,
This is a known problem in WFV3.8.1. It is first found when using ERA-I as forcing data for WRF (also occaasionally other input data). Please see the page

This problem is not fixed until WRFV4.1. You can find details in the website:

Can you take a look at the modified codes and manage to put them in your WRFV3.8.1? Note that WRF vertical coordinate has been changed since WRFV4.0, which makes the codes not back-consistent with older version of WRF.