[Wrf-users] WRF/WPS 3.3 geogrid.exe segfault

[Zulauf, Michael]

Hi all,

I'm having troubles getting a working WRF/WPS 3.3 using PGI compilers.
For my most recent attempt, I used:
	WRF/WPS 3.3
	PGI 10.5
	OpenMPI 1.4.1
	netcdf 3.6.3

I'm building WPS with GRIB2 support:
	jasper 1.900
	libpng 1.4.1

Everything appears to build correctly (unlike my previous attempts with
an older version of PGI), but when I try to run geogrid, I get a
segmentation fault when processing LANDUSEF for domain 1.  There are no
useful clues in the output or the geogrid.log.  This is for a model
setup that is working well with WRF/WPS 3.2.1.

I realize there are a lot of ways that things can go wrong.  Has anybody
gotten WRF/WPS 3.3 working with PGI 10.3 or 10.5?  If so, I was
wondering if somebody could maybe share their configure.wrf and
configure.wps files with me.  If it's not obvious from the configure
files, I'd also like the details of the versions of libraries you're
building against.  I'd like to try and match up my set of libraries and
compiler options (etc) in a similar way, to see if I can get this
working.

Thanks,
Mike

-- 

PLEASE NOTE - NEW E-MAIL ADDRESS:
michael.zulauf at iberdrolaren.com

Mike Zulauf
Meteorologist, Lead Senior
Wind Asset Management 
Iberdrola Renewables
1125 NW Couch, Suite 700
Portland, OR 97209
Office: 503-478-6304  Cell: 503-913-0403



Please be advised that email addresses for Iberdrola Renewables personnel have changed to first.last at iberdrolaREN.com effective Aug. 16, 2010.  Please make a note.  Thank you.

This message is intended for the exclusive attention of the recipient(s) indicated.  Any information contained herein is strictly confidential and privileged.  If you are not the intended recipient, please notify us by return e-mail and delete this message from your computer system. Any unauthorized use, reproduction, alteration, filing or sending of this message and/or any attached files may lead to legal action being taken against the party(ies) responsible for said unauthorized use. Any opinion expressed herein is solely that of the author(s) and does not necessarily represent the opinion of the Company. The sender does not guarantee the integrity, speed or safety of this message, and does not accept responsibility for any possible damage arising from the interception, incorporation of viruses, or any other damage as a result of manipulation.