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

Adding a new variable to the module_surface_driver.F

Yumeng Liu

New member
I made modifications to the physical parameterization scheme and added one variable 'ALBOLD'. I added the new variable in Registry.EM_COMMON as follows:
1734694018765.png
I have made changes to the original variable ‘SNOALB’ and the new variable ‘ALBOLD’ in the ‘wrfrst’ file after the spin-up time, but the SNOALB variable in the ‘wrfout’ file of the next time is modified, while ALBOLD is still initialised to a value of zero.

So, I would like to know what went wrong? Why the value of ALBOLD is not successfully passed to the next time, and what changes do I need to make?
 
Apologies for the long delay in response while our time has been out much over the past few weeks, due to conferences and holidays. Thank you for your patience. Are you still experiencing issues with this? If so, did you make sure to clean the code (./clean -a), reconfigure, and then recompile after the code modifications?

Are you running wrf for a standard simulation (i.e., NOT a restart) first, and obtaining the ALBOLD in the wrfout* files and in the wrfrst* files, or are you just adding in this new variable after the standard run, prior to a restart simulation?

Are you modifying other files besides Registry.EM_COMMON? If so, can you share the modified files, along with your namelist.input file? Thanks!
 
Top