[Wrf-users] how to run WRF with no leap year calendar

[Rui Mei]

Hi, Ufuk,

Thanks for the reply. Now I understand that only /external/esmf_time_f90 is
used with WRF to calculate time. The actual ESMF code is within the folder
/external/io_esmf and to enable this part, we need to set ESMF_COUPLING  to
1 and also install ESMF libraries, right? But the coupling with ESMF is not
needed in my case, so What I need to do is to change the code in external
folder, e.g., to hardwire it to noleap calendar instead of gregorian
calendar. Is that correct ?

Another question: do I still need to add that -DNO_LEAP_CALENDAR to the
macro ARCH_LOCAL in configure.wps file ?

My machine is down for now. I will test it later today and let you know if
I can fix it. Meanwhile if someone can offer an exact solution, please let
me know.

Thanks,
-Rui

On Tue, Aug 14, 2012 at 1:28 PM, Ufuk Utku Turuncoglu (BE) <
u.utku.turuncoglu at be.itu.edu.tr> wrote:

>  Hi Rui,
>
> WRF uses ESMF Time module to calculate time inside of the model. To do
> that, WRF developers split the ESMF_Time module from original ESMF library.
> So, it is just a subset of ESMF library (but i don't know which version it
> is). For the coupling, you need to install ESMF library first (like a
> netcdf library) and then you have to point that directory to compile the
> ESMF enabled code. It is little bit confusing but the code works like this.
> So, if you want to add noleap year support, you can change the code in
> external/ folder. I hope it helps.
>
> Regards,
>
> Ufuk Turuncoglu
>
>
> On 8/14/12 6:54 PM, Rui Mei wrote:
>
> Dear all,
>
> I was trying to run WRF with climate data, which is 365-day calendar. So I
> added -DNO_LEAP_CALENDAR to the macro ARCH_LOCAL in configure.wps file,
> according to the user guide.
>
> Here is the line:
> ARCH_LOCAL = -DNONSTANDARD_SYSTEM_SUBR -DNO_LEAP_CALENDAR
>
> There is no problem compiling the model, but when I run real.exe, it
> crashes.
> Here is the error message:
> -------------- FATAL CALLED ---------------
> Error:: ESMF_Initialize not called
> -------------------------------------------
> Rank 1 [Mon Aug 13 18:11:45 2012] [c22-2c2s2n3] application called
> MPI_Abort(MPI_COMM_WORLD, 1) - process 1
>
> I tracked down the error message and it comes
> from external/esmf_time_f90/ESMF_Time.f. I browsed the ESMF_time codes
> under that directory and it says WRF is hard-wired to gregorian calendar. I
> am still trying to understand those ESMF codes to figure the problem out.
>
>  Another thing I do not understand is that currently in configure.wrf, we
> have the following in default
>
>  # switch to use separately installed ESMF library for coupling:  1==true
> ESMF_COUPLING       = 0
>
>  Does that indicate ESMF lib is used or not ? I assume if it is set to 0,
> ESMF is still used somehow, otherwise why would that error comes from there
> ?
>
>  I will appreciate if someone can offer an answer or advice. Thanks very
> much!
>
> -Rui
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>
> _______________________________________________
> Wrf-users mailing listWrf-users at ucar.eduhttp://mailman.ucar.edu/mailman/listinfo/wrf-users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/wrf-users/attachments/20120814/0ec8af14/attachment.html