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

No leap year for WRF4.5.1

htan2013

Member
Dear all experts,

I am wondering how to setup for no leap year run for WRF4.5.1 now.
I tried adding -DNO_LEAP_CALENDAR in ./configure but it shows "This option is not recognized: -DNO_LEAP_CALENDAR".

Thanks,
HT
 
Also, I am wondering how to add this option during WPS compilation too. The WPS is also looking for 02/29 while some GCM data doesn't have. Thank you
 
For a no-leap-year calendar, it can be enabled by adding - DNO_LEAP_CALENDAR to CPPFLAGS in the configure.wps;

To drive WRF model with climate data that does not have leap year, there is a compile option to do that. Edit configure.wrf and
add -DNO_LEAP_CALENDAR to the macro ARCH_LOCAL.

Can you try an older version , for example, WRFV3.9, and see whether the above options work?

Please also save the log file of compiling WRFV4.5.1 for me to take a a look. Thanks.
 
For a no-leap-year calendar, it can be enabled by adding - DNO_LEAP_CALENDAR to CPPFLAGS in the configure.wps;

To drive WRF model with climate data that does not have leap year, there is a compile option to do that. Edit configure.wrf and
add -DNO_LEAP_CALENDAR to the macro ARCH_LOCAL.

Can you try an older version , for example, WRFV3.9, and see whether the above options work?

Please also save the log file of compiling WRFV4.5.1 for me to take a a look. Thanks.
Thanks! I have it compiled. Here's the log file.
 

Attachments

  • LOG.txt
    865.1 KB · Views: 1
Your LOG.txt file indicates that WRF has been successfully compiled. Please look at the line below in your LOG file:

" ---> Executables successfully built <---"
 
Top