Greetings:<br><br>If you are running on a Mac, use those flags at linking stage only to increase the stack (As setting the stacksize to unlimited in your bashrc etc does not suffice):<br><br>-stack_addr,0xF10000000 -Wl,-stack_size,0x64000000<br>
<br>However, from what I see below your run stopped due to a Seg Fault error: either there is a bug in your code or your time step size is too large (CFL criterion exceeded).<br><br>Cheers and hope this helps,<br><br>Alex-<br>
<br><div class="gmail_quote">On Tue, May 8, 2012 at 5:32 AM, Ahmad Wan <span dir="ltr"><<a href="mailto:ardie_coal@yahoo.com" target="_blank">ardie_coal@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><div style="font-size:12pt;font-family:garamond,new york,times,serif"><div>Thank you everyone, <br></div><div>I was pleasantly surprised that a lot of people replied to my last question (Re: [Wrf-users] Better strategy to compress wrf output files). I will definitely post some of you, if I have found another technique. Back to the issue, I have another problem with my control run, that after running for 2 years, it stopped abruptly with segmentation fault message:</div>
<div><br></div><div><div><b>Timing for main: time 1983-03-17_22:32:30 on domain 1: 0.30150 elapsed seconds.</b></div><div><b>Timing for main: time 1983-03-17_22:33:45 on domain 1: 0.30260 elapsed seconds.</b></div>
<div><b>forrtl: severe (174): SIGSEGV, segmentation fault occurred</b></div><div><b>Image PC Routine
Line Source</b></div><div><b>wrf.exe 08D7C2A0 Unknown Unknown Unknown</b></div><div><b>wrf.exe 0864F0DC Unknown Unknown Unknown</b></div><div><b>wrf.exe 0867B3B8 Unknown Unknown Unknown</b></div>
<div><b><br></b></div><div><b>Stack trace terminated abnormally.</b></div><div><br></div></div><div>For you information, I have already unlimited the stack size, and there is no apparent evidence of stability problems (such as warning messages or increasing elapsed seconds). Is it possible that my RAM is not enough? Or is it that some stability problems simply don't produce messages? I have tried the
restart run twice, but they each stop at different times (3 months/5 months/1 month into the 2nd year)</div><div><br></div><div>Regards,</div><div>Wan Ardie</div><div><br></div><div><br></div> </div></div><br>_______________________________________________<br>
Wrf-users mailing list<br>
<a href="mailto:Wrf-users@ucar.edu">Wrf-users@ucar.edu</a><br>
<a href="http://mailman.ucar.edu/mailman/listinfo/wrf-users" target="_blank">http://mailman.ucar.edu/mailman/listinfo/wrf-users</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>-------------------------------------------------------------<br>Alexandre Fierro, PhD<br>Research Scientist-<br>National Severe Storms Laboratory (NSSL/NOAA)<br><b style="font-weight:normal">The Cooperative Institute for Mesoscale Meteorological
Studies</b> (OU/NOAA)<br>Los Alamos National Laboratory, Los Alamos, NM (LANL)<br><br>"Yesterday is History, Tomorrow is a Mystery and Today is a Gift; That is why it is called the Present" <br><br>"There are only 10 types of people in the world:<br>
Those who understand binary, and those who don't" <br><br>"My opinions are my own and not representative of OU, NSSL,<br>AOML, HRD, LANL or any affiliates."<br> ^.^<br> (o o)<br> /( V )\<br>
---m---m----<br><br>