Questions about the replacement of static LAI, VEGFRA and ALBEDO with time-variant data

noah_lover

New member
Hi,
I am going to conduct a 10-year simulation with WRF-Noahmp(V4.7.0), and I want to use time-variant LAI, VEGFRA and ALBEDO (e.g. 8-days updated GLASS dataset) to replace the static monthly mean fields in WPS_GEOG.

I should set the following content in namelist.input,the following setting allow me to use the static 3D fields in WPS_GEOG instead of using the parameters from table (MPTABLE.TBL for Noahmp and VEGPARM.TBL for noah, if wrong, please tell me).
sst_update = 1,
rdlai2d = .true.,
usemonalb = .true.


I have checked several threads.
1、How to replace ALBEDO and LAI ,VEGFRA fields using Noah LSM ?
1790238026032.png
2、(RESOLVED) How to replace ALBEDO and LAI fields in my geo_em files?
1790238331448.png
1790238348517.png

Q1: According the replies of Dr. Chen, I know there are two ways of replacing LAI, ABLEDO and VEGFRAC. 1、rewrite time-variant LAI in the static data format, then process them by geogrid.exe. Note that you will also need to modify REAL (dyn_em/module_initialize_real.F). If I modify the source code, if I need to recompile WRF? 2、replace the fields in wrflowinput.nc.

Q2: I use noahmp lsm. As mentioned above, I set rdlai2d = .true., which means use leaf area index (LAI) from input data, instead of from table; However, in the following table, if I use updated LAI, FVEG, I should set dveg = 7. Both of them indicate to use input LAI, are there any conflicts between them? I should set dveg = 7 and rdlai2d = .true. simultaneously?

Q3: Regarding the soil parameters, opt_soil =3 and opt_pedo =1. If I want to replace the sand and clay data, I should replace the data in soilgrids/soilcomp, right?
 
I should set the following content in namelist.input,the following setting allow me to use the static 3D fields in WPS_GEOG instead of using the parameters from table (MPTABLE.TBL for Noahmp and VEGPARM.TBL for noah, if wrong, please tell me).
Setting up 10-year dynamic satellite vegetation forcing in WRF is guaranteed to age you faster than the model runs.
 
I have another question.
1. What is the function of auxinput4_interval?

Does auxinput4_interval specify the time interval at which real.exe writes data to wrflowinp, or does it specify the frequency at which WRF reads the time-varying LAI, VEGFRA, and ALBEDO data from wrflowinp?

In my namelist.input, I set:

auxinput4_interval = 1440
However, the LAI, VEGFRA, and ALBEDO fields in wrflowinp still have a 6-hourly time resolution, which is the same as the frequency of my WRF forcing data.

2. Replacing LAI, VEGFRA, and ALBEDO in wrflowinp with 8-day data

If I want to replace the LAI, VEGFRA, and ALBEDO fields in wrflowinp with data available every 8 days, is it sufficient to replace the records corresponding to days 1, 9, 17, ..., and 361 in the existing wrflowinp file?

How should LAI be handled between two consecutive updates? Should the previous value be held constant, or should the values be temporally interpolated?

What approach would you recommend?
 
Back
Top