(1) In WRFV300 on the Mac, using the Intel Fortran 10.1 compiler, the compiler flag –switch fe_use_rtl_copy_arg_inout causes problems that weren't apparent with earlier WRF versions. Specifically, lateral boundary tendencies for water vapor are zeroed, resulting in problems in this field that grow inward from the boundaries. In the wrfbdy_d01 file, fields like QVAPOR_BXE and related entries possess only zeroes. This file is, of course, created by real.exe.
I added this switch owing to this page. Removing it does no harm. I tried several minor versions of ifort 10.1, explored 32 and 64 bit, etc.; nothing helped fix this issue except removing this switch.
(2) In WRFV300, the Lin microphysics scheme (mp_physics = 2) has issues -- noise issues. After only a few tens of minutes, the pressure field starts displaying small scale noise. Decreasing the time step, implementing 6th order smoothing, and upping the small time step smoothing (epssm) do not help. For the simulations I am examining, the noise does not appear with any other microphysics scheme. With Lin, the noise appears in higher but not in lower resolution simulations.
The Lin code was altered between WRFV221 and WRV300. I have not isolated the code changes that cause this problem.
Subscribe to:
Post Comments (Atom)
3 comments:
I am trying to get WRF to compile on the latest system builds (OS X 10.5.3, ifort 10.1.014, mkl 10.0.20, gcc 4.0.1 and WRF 3.0)
The build keeps dying from an unresolved symbol based on $non_lazy_prt. This seems to be a Mac bug since it shows up in other builds.
Has anyone figured out a way to resolve this issue? Any advice would be appreciated.
Version 10.1
ld -lcrt1.o -dynamic -arch i386 -weak_reference_mismatches non-weak -o ideal.exe /opt/intel/fc/10.1.014/lib/for_main.o ideal.o ../dyn_em/module_initialize_grav2d_x.o libwrflib.a -L/Users/todd/Desktop/WRF/WRF/WRFV3_32/external/fftpack/fftpack5 -lfftpack -L/Users/todd/Desktop/WRF/WRF/WRFV3_32/external/io_grib1 -lio_grib1 -L/Users/todd/Desktop/WRF/WRF/WRFV3_32/external/io_grib_share -lio_grib_share -L/Users/todd/Desktop/WRF/WRF/WRFV3_32/external/io_int -lwrfio_int -L/Users/todd/Desktop/WRF/WRF/WRFV3_32/external/esmf_time_f90 -lesmf_time /Users/todd/Desktop/WRF/WRF/WRFV3_32/frame/module_internal_header_util.o /Users/todd/Desktop/WRF/WRF/WRFV3_32/frame/pack_utils.o /Users/todd/Desktop/WRF/WRF/WRFV3_32/external/io_netcdf/libwrfio_nf.a -L/Users/todd/Desktop/WRF/extra32/lib -lnetcdf -L/Library/Frameworks/Intel_MKL.framework/Versions/10.0.3.020/lib/32 -L/Library/Frameworks/Intel_MKL.framework/Versions/10.0.3.020/lib/32 -L/Library/Frameworks/Intel_MKL.framework/Versions/10.0.3.020/lib/32 -L/Library/Frameworks/Intel_MKL.framework/Versions/10.0.3.020/lib/32 -L/opt/intel/fc/10.1.014/lib -L/usr/lib/i686-apple-darwin9/4.0.1/ -L/usr/lib/ -L/Library/Frameworks/Intel_MKL.framework/Versions/10.0.3.020/lib/32/ -L/usr/lib/gcc/i686-apple-darwin9/4.0.1/ -L/usr/lib/gcc/i686-apple-darwin9/4.0.1/../../../i686-apple-darwin9/4.0.1/ -L/usr/lib/gcc/i686-apple-darwin9/4.0.1/../../.. /opt/intel/fc/10.1.014/lib/libifport.a /opt/intel/fc/10.1.014/lib/libifcore.a /opt/intel/fc/10.1.014/lib/libimf.a /opt/intel/fc/10.1.014/lib/libsvml.a /opt/intel/fc/10.1.014/lib/libipgo.a -lgcc /opt/intel/fc/10.1.014/lib/libirc.a -ldl /opt/intel/fc/10.1.014/lib/libirc_s.a -ldl
Undefined symbols:
"_module_domain_type_mp_program_name_", referenced from:
_module_domain_type_mp_program_name_$non_lazy_ptr in ideal.o
_module_domain_type_mp_program_name_$non_lazy_ptr in libwrflib.a(output_wrf.o)
_module_domain_type_mp_program_name_$non_lazy_ptr in libwrflib.a(input_wrf.o)
ld: symbol(s) not found
rm /var/folders/VW/VWnzgWOjEpyaG15xDzibA++++TM/-Tmp-//ifort0Mw1NKsw_vers
rm /var/folders/VW/VWnzgWOjEpyaG15xDzibA++++TM/-Tmp-//iforthpQBmMlibgcc
rm /var/folders/VW/VWnzgWOjEpyaG15xDzibA++++TM/-Tmp-//ifortgFLiV1gnudirs
rm /var/folders/VW/VWnzgWOjEpyaG15xDzibA++++TM/-Tmp-//ifortFleDE7dashv
rm /var/folders/VW/VWnzgWOjEpyaG15xDzibA++++TM/-Tmp-//ifort7DEiZCgnudirs
make[1]: [em_ideal] Error 1 (ignored)
Just a note: the blog entry from April 5th fixes the unresolved symbol problem. I had read that entry, but did not realized that this was the same error. Todd
Post a Comment