<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-AU link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Hi all,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks for all the replies.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>It turns out that there was something
“funny” with our openmpi library. Our system admins have partly fixed the issue,
so, now WRF only hangs on certain numbers of CPUs per node. (Don’t know why
yet!). They are still working on it.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Cheers,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Jatin <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> Feng Liu [mailto:FLiu@azmag.gov] <br>
<b>Sent:</b> Tuesday, 29 March 2011 6:01 AM<br>
<b>To:</b> Jatin Kala; wrf-users@ucar.edu<br>
<b>Cc:</b> Jatin Kala<br>
<b>Subject:</b> RE: WRF is "hanging"<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Jatin and Don, <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>If the problem can
not resolved by reducing time_step, I suspect and would say that it is highly
resulted from your system. I experienced the similar issue before and took a
lot of time to research what happened to system. We also asked wrfhelp for the
solution but in vain, please see replies from wrfhelp immediate after my reply.
We have a cluster to run different models such as WRF, WRF/Chem, CMAQ, CAMx,
etc. our cluster equipped with 8 nodes each of which is dual quad-core,
originally had a 100M switch and all models including WRF3.2.1 ran perfectly.
In order to improve computing efficiency we upgraded the switch to 1 Gb and the
CMAQ, CAMx models still run fine, however, WRF 3.2.1 model hang up more often
with increasing the number of processor involved in the computing. But it
seemed fairly random. When it hang up, no error message, no stop. We checked
MPI libraries, MPICH, compiler flags…, many things. So we now leave it back to
and on the 100 M switch. Everything works well and no hang up happens to WRF
model any more though cluster slows down. Why did CMAQ (parallel version)
ran successfully with the 1 Gb switch and full nodes, but WRF 3.2.1 did not?
Before we re-order another 1 Gb or more advanced switch and test it the
question is still opened. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>For effective test,
you may use a pilot program test.f attached. If your WRF hangs up, it
should hang up too, but it lets you get quick check. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I hope it is helpful.
I will keep a close eye on this issue. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Thanks.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Feng<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>--------------------------------------------<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Wrfhelp repliy:<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Since we have not had report from other
users, I am guessing the problem has to do with your system than with the code.
If you can get help from your system support or the vendor, that might be
helpful.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>wrfhelp<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>On Jan 21, 2011, at 9:41 AM, Feng Liu
wrote:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> Hi,<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> I re-compiled WRF3.2.1. The
"hung up" problem sometimes still happens, <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> sometimes does not, it seems fairly
random. It hangs more often with <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> increasing processor number. I also
consulted with our IT staff but no <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> solution so far. Your support is
highly appreciated.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> Feng<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> -----Original Message-----<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> From: wrfhelp <a
href="mailto:[mailto:wrfhelp@ucar.edu]">[mailto:wrfhelp@ucar.edu]</a><o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> Sent: Thursday, January 06, 2011
4:38 PM<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> To: Feng Liu<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> Subject: Re: job hang up without
error message when I used<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> Could you work with your system
support people and see if they can <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> help?<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> wrfhelp<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>> On Jan 5, 2011, at 8:15 PM, Feng
Liu wrote:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> Hi,<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> I had the hang up problem with
version 3.2 no matter multiple <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> processors or single one used
but when I modified namelist.input, it <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> did work. For version 3.2.1 I
think the course of this problem is <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> different because it does work
with master nodes.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> On stability of computer you
mentioned, you may be right. We updated <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> network work card from 100M
switch to 1 G. We had stable WRF running <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> with old network card even
though its performance was poor. However, <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> I can run CMAQ4.7.1 with 64
processors ( we have 8 nodes each of <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> which has 8 processors) successfully,
and speedup factor is almost<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> 2.8 comparing against the
system with old network card.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> Thanks.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> Feng<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> -----Original Message-----<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> From: wrfhelp <a
href="mailto:[mailto:wrfhelp@ucar.edu]">[mailto:wrfhelp@ucar.edu]</a><o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> Sent: Wednesday, January 05,
2011 7:24 PM<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> To: Feng Liu<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> Subject: Re: job hang up
without error message when I used<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> Have you seen this problem with
other versions of the model code <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> before? Is your system stable?<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> Can you run other MPI jobs
steadily on this system? What I am saying <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> is that it is possible that it
is problem with the computer, not the <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> model code.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> wrfhelp<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>> On Jan 5, 2011, at 5:11 PM,
Feng Liu wrote:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> Hi,<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> Thanks for your response.
But I am using WRF3.2.1 which has the same <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> problem. I have no idea so
far.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> Thanks.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> Feng<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> -----Original Message-----<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> From: wrfhelp <a
href="mailto:[mailto:wrfhelp@ucar.edu]">[mailto:wrfhelp@ucar.edu]</a><o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> Sent: Wednesday, January
05, 2011 4:20 PM<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> To: Feng Liu<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> Subject: Re: job hang up
without error message when I used<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> Mike was using 3.2 at the
time, and the fix has been included in <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> 3.2.1.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> wrfhelp<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> On Jan 5, 2011, at 1:30 PM,
Feng Liu wrote:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> Hi,<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> I can run WRF3.2.1
successfully if I only use master node with 8 <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> processors. However, my
jobs (with MPI) hand up when I was using <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> more 16 processors or
more than two nodes, no error message, no <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> crashes. This problem
was described by Michael Zulauf as below:<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> (see <a
href="http://mailman.ucar.edu/pipermail/wrf-users/2010/001745.html">http://mailman.ucar.edu/pipermail/wrf-users/2010/001745.html</a><o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> "My jobs
sporadically (but usually eventually) hang up, most often <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> after a new wrfout file
is opened. No error messages, no crashes<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> - the processes
continue, but _all_ output stops. I eventually <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> just have to kill the
job. The wrfouts are small, and all output <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> looks good up until the
failed wrfout."<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> Mike mentioned he got a
modified code from wrfhelp and seemed to <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> fix this issue. I also
need to know which code need to be modified <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> and what is the problem
related to? Thanks for support on fixing <o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> this problem.<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>> Feng<o:p></o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>><o:p> </o:p></span></p>
<p class=MsoPlainText><span lang=EN-US>>>> wrfhelp<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> wrf-users-bounces@ucar.edu
[mailto:wrf-users-bounces@ucar.edu] <b>On Behalf Of </b>Jatin Kala<br>
<b>Sent:</b> Saturday, March 26, 2011 12:19 AM<br>
<b>To:</b> wrf-users@ucar.edu<br>
<b>Subject:</b> Re: [Wrf-users] WRF is "hanging"<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks for the suggestion Feng,
but this is not related to namelist inputs. The namelist I am running worked
fine on a different machine.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>The issue here is that WRF
simply hangs and does nothing at initialisation of Grid 2. Ie, the rsl.out and
rsl.error files print out:<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal>d01 2009-10-01_00:00:00 alloc_space_field:
domain
2, 84045408 b<o:p></o:p></p>
<p class=MsoNormal> ytes allocated<o:p></o:p></p>
<p class=MsoNormal> d01 2009-10-01_00:00:00 alloc_space_field:
domain
2, 3084672 b<o:p></o:p></p>
<p class=MsoNormal> ytes allocated<o:p></o:p></p>
<p class=MsoNormal> d01 2009-10-01_00:00:00 *** Initializing nest domain #
2 from an input file. **<o:p></o:p></p>
<p class=MsoNormal> *<o:p></o:p></p>
<p class=MsoNormal> d01 2009-10-01_00:00:00 med_initialdata_input: calling
input_input<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>and that’s it. The rsl.error and
rsl.out files do not keep growing in size, there are no more prints, they just
stop printing stuff. The job however is still in the queue and does NOT error
out, until the walltime is elapsed. No wrfout_d0* files are created. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Other people seem to have had
this issue before:<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><a
href="http://mailman.ucar.edu/pipermail/wrf-users/2010/001749.html">http://mailman.ucar.edu/pipermail/wrf-users/2010/001749.html</a>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><a
href="http://mailman.ucar.edu/pipermail/wrf-users/2010/001747.html">http://mailman.ucar.edu/pipermail/wrf-users/2010/001747.html</a>
<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Any help more than welcome.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Jatin<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> Feng Liu [mailto:FLiu@azmag.gov] <br>
<b>Sent:</b> Saturday, 26 March 2011 9:04 AM<br>
<b>To:</b> Jatin Kala; wrf-users@ucar.edu<br>
<b>Subject:</b> RE: WRF is "hanging"<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Hi Jatin,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I do not know exactly
what is wrong for your case, but one thing you can try is to reduce time_step
in namelist.input by 3 times. Good luck.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Feng<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> wrf-users-bounces@ucar.edu
[mailto:wrf-users-bounces@ucar.edu] <b>On Behalf Of </b>Jatin Kala<br>
<b>Sent:</b> Thursday, March 24, 2011 7:29 PM<br>
<b>To:</b> wrf-users@ucar.edu<br>
<b>Subject:</b> [Wrf-users] WRF is "hanging"<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal>Dear WRF-users,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have compiled WRF3.2 on our new supercomputing facility,
and having some trouble. Namely, WRF is just “hanging” at:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>d01 2009-10-01_00:00:00 alloc_space_field:
domain
2, 84045408 b<o:p></o:p></p>
<p class=MsoNormal> ytes allocated<o:p></o:p></p>
<p class=MsoNormal> d01 2009-10-01_00:00:00 alloc_space_field:
domain
2, 3084672 b<o:p></o:p></p>
<p class=MsoNormal> ytes allocated<o:p></o:p></p>
<p class=MsoNormal> d01 2009-10-01_00:00:00 *** Initializing nest domain #
2 from an input file. **<o:p></o:p></p>
<p class=MsoNormal> *<o:p></o:p></p>
<p class=MsoNormal> d01 2009-10-01_00:00:00 med_initialdata_input: calling
input_input<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The job remains in the queue, i.e, does not error out until
walltime is elapsed.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have compiled with –O0 but that did not help. I have also
compiled with the updated “gen_allocs.c” form the WRF website, but that has not
helped either. I did do a “clean –a” before.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have compiled WRF with the follows libs:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>intel-compilers/2011.1.107<o:p></o:p></p>
<p class=MsoNormal>jasper/1.900.1<o:p></o:p></p>
<p class=MsoNormal>ncarg/5.2.1<o:p></o:p></p>
<p class=MsoNormal>mpi/intel/openmpi/1.4.2-qlc<o:p></o:p></p>
<p class=MsoNormal>netcdf/4.0.1/intel-2011.1.107<o:p></o:p></p>
<p class=MsoNormal>export WRFIO_NCD_LARGE_FILE_SUPPORT=1<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Any help would be greatly appreciated!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Kind regards,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Jatin <o:p></o:p></p>
</div>
</body>
</html>