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

Issues with vegetation/moisture in NoahMP - suggestions for parameter option?

Pechudin

Member
Hello,

I am simulating downslope windstorms in complex terrain, which means that detailed LANDUSE is desirable. I decided to use this 250m CORINE dataset:


The authors suggest that using NoahMP is needed for this option, as well as turning off the urban physics. I did so, and geo_em files now contain the CORINE-derived LANDUSE (and LU_INDEX), and the coastline is as a result much finer in resolution. All good so far.

However, when running a test simulation, I see extremely large negative values (O ~ -3 e36) in fields which seem to be related to vegetation. I confirmed this by grepping all the Registry files with the offending fields, and they all seem to be related to NoahMP and vegetation. Examples of some fields are below - large negative values are over west Alps. Additionally, I verified that these values are NOT in the geo_em* and met_em* files, thus the issue seems to be when WRF is run (i.e., physics options).

I am having some doubts about my hypothesis however, as the issue only happens in the domain 1 (nested domains which are NOT over the Alps, and are instead over Croatia, seem not to have these issues). Additionally, the SH2O field has zero moisture (exactly 0.0, so not almost zero) exactly at those points.

My question is thus - which option would you suggest to use to avoid these issues (from 1 to 9 in the namelist.input)? Or if the issue is not the vegetation (as the issue seems not to be in the smaller domains), what could be the culprit instead?

I am also attaching my namelist.wps and .input. files.
 

Attachments

  • ncview.ETRAN_d01.ps
    1.6 MB · Views: 0
  • ncview.LAI_d01.ps
    1.6 MB · Views: 0
  • ncview.SH2O_d01.ps
    1.6 MB · Views: 0
  • namelist.input
    5.2 KB · Views: 0
  • namelist.wps
    1.3 KB · Views: 0
A development - the areas with unrealistic values seem to be related to the LANDUSE type = 24, or "Snow or ice" in USGS. Possibly the vegetation module in NoahMP does not interact well with this?

EDIT: It seems like there was a similar issue before on the thread below. I'll look at it tomorrow.
 
Last edited:
Update: As suggested in the thread in the post above, playing with the parameters:

rdlai2d = .true. (take LAI from input file, i.e., geo.em* static file) or .false. (from table)
dveg = 1-9 (whether to predict LAI or to use LAI from table or input)

The -1e+36 values (which seem to be the undefined value) persist still (for the dveg = 9 and rdlai2d = .true. LAI is from the static fields).

I am at a loss what to do.
 
Top