[Wrf-users] WRF 3.2 Model not running after 4hrs of Integration.

Geeta Geeta geeta124 at hotmail.com
Wed Mar 9 02:35:09 MST 2011





Dear all, 
I was running the model on the IBM P570 machine with 3 nested domains, 27, 9 and 3 kms. This problem I had reported earlier as well. The time step I have used is 120sec. The model was running up to 6hrs and after which It aborted by giving Core file. 


I am attatching the namelist.input file and the rsl files. 

bash-3.2$ ls -lrt wrfout* 
-rw-r--r--    1       51017984 Mar 08 03:06 wrfout_d01_2010-08-06_00:00:00
-rw-r--r--    1      176907272 Mar 08 03:06 wrfout_d02_2010-08-06_00:00:00
-rw-r--r--    1      252611432 Mar 08 03:06 wrfout_d03_2010-08-06_00:00:00
bash-3.2$ 
bash-3.2$ ncdump -v Times wrfout_d01_2010-08-06_00:00:00
imes =
  "2010-08-06_00:00:00",
  "2010-08-06_01:00:00",
  "2010-08-06_02:00:00",
  "2010-08-06_03:00:00",
  "2010-08-06_04:00:00",
  "2010-08-06_05:00:00",
  "2010-08-06_06:00:00" ;
}
bash-3.2$ 
AS SUGGESTED, I have tried to look for NaN in the wrfout files but It does not exist.!!!!!!

bash-3.2$ ncdump  wrfout_d01_2010-08-06_00:00:00 | grep -i NaN 
                IVGTYP:description = "DOMINANT VEGETATION CATEGORY" ;
                ISLTYP:description = "DOMINANT SOIL CATEGORY" ;
bash-3.2$ ncdump  wrfout_d02_2010-08-06_00:00:00 | grep -i NaN
                IVGTYP:description = "DOMINANT VEGETATION CATEGORY" ;
                ISLTYP:description = "DOMINANT SOIL CATEGORY" ;
bash-3.2$ ncdump  wrfout_d03_2010-08-06_00:00:00 | grep -i NaN
                IVGTYP:description = "DOMINANT VEGETATION CATEGORY" ;
                ISLTYP:description = "DOMINANT SOIL CATEGORY" ;
bash-3.2$ 
bash-3.2$ date
Tue Mar  8 03:29:15 IST 2011
bash-3.2$ 

bash-3.2$ ls -lrt core*
coredir.5:
total 655848
-rw-r--r--    1      335790224 Mar 08 03:07 core

coredir.3:
total 643664
-rw-r--r--    1      329553200 Mar 08 03:07 core

coredir.2:
total 646352
-rw-r--r--    1     330929600 Mar 08 03:07 core

coredir.1:
total 611240
-rw-r--r--    1    312953392 Mar 08 03:07 core

coredir.7:
total 606376
-rw-r--r--    1     310461104 Mar 08 03:07 core

coredir.6:
total 605224
-rw-r--r--    1     309871168 Mar 07 05:15 core

coredir.4:
total 658528
-rw-r--r--    1      337166176 Mar 08 03:07 core

coredir.0:
total 758952
-rw-r--r--    1      388580736 Mar 08 03:07 core
bash-3.2$ ls -lrt core*

I have used GREP in the rsl files 




ash-3.2$ grep -i NAN
rsl.error.0000

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 22 1 -NaNQ 5000.000000

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 49 1 NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.error.0001

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 65 1 -NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.error.0002

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 1 32 -NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.error.0003

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 63 32 -NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.error.0004

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 1 63 -NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.error.0005

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 63 81 -NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.error.0006

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 2 94 NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.error.0007

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 63 94 -NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.out.0000

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 22 1 -NaNQ 5000.000000

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 49 1 NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.out.0001

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 65 1 -NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.out.0002

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 1 32 -NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.out.0003

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 63 32 -NaNQ 5000.000000

bash-3.2$ grep -i NAN
rsl.out.0004

  WOULD GO OFF TOP:
KF_ETA_PARA I,J,DPTHMX,DPMIN 1 63 -NaNQ 5000.000000


I have Decreases the TIME step to 90sec but It has not helped me. The model aborts after running successfully for about 2-3 hours. 
PLS suggest. 

geeta



Date: Fri, 4 Mar 2011 12:46:29 -0700
From: wrfhelp at ucar.edu
To: geeta124 at hotmail.com
Subject: Re: WRF 3.2 Model not running after 4hrs of Integration.



  


    
    Message body
  
  
    Can you use ncview to look at your wrfout files? You may need to do
    to those outputs that are right before model stopped. Please check
    whether there is any weird data in those output files? 

    

    Did you see any NaN when typing ncdump wrfout | grep -i Nan? 

    

    

    On 3/3/2011 9:32 PM, Geeta Geeta wrote:
    
      
      Dear Sir, 

      Thanks for the reply. I am running WRf 3.2 for the 3 domains 27, 9
      and 3 km for the 48hrs Forecast on the IBM P570 Machine. The
      Operating system is AIX5.3 and the code is compiled using xlf with
      POE in place. 

      I had given the command bash$ time poe ../wrf.exe -procs 8. 

      

      1. The model gave segmentation fault after 4hrs of Integration. I
      also plotted the Model forecast for 2nd and 3rd hour at 27km
      resolution (Domain 1) So it showed me some data being plotted 

       But when I tried to plot the output for the 2nd and 3rd
          domain, IT says ENTIRE GRID UNDEFINED. Kindly suggest.  
       

      

      2. >>>What data I have used ??

      I am using the .grib2 files as Initial and BC taken from
          ftp://ftpprd.ncep.noaa.gov.in at 1x1 degree resolution.  

       

      3. >>>What is the error message in your output file? Did
      you find any CFL violation?  Your namelist.input looks fine.
      Please send us error messages in your run.

      I am attatching the rsl.error* and the rsl.out* files,
          namelist.input and namelist.wps files. It seems to me
        that there is no CFL violation.  

      

      Thanks. 

      geeta

      

      

      

      Date: Thu, 3 Mar 2011 17:20:41 -0700

      From: wrfhelp at ucar.edu

      To: geeta124 at hotmail.com

      Subject: Re: WRF 3.2 Model not running after 4hrs of Integration.

      

      Geeta,

      

      What is the error message in your output file? Did you find any
      CFL violation? 

      

      Your namelist.input looks fine. Please send us error messages in
      your run. 

      

      

      On 3/3/2011 3:57 AM, Geeta Geeta wrote:
      
        Dear All, 

        I am running WRF3.2 for 3 domains, at 27, 9 and 3kms.  After
        integrating for 4hours, the model  gives segmentation fault. and
        these directories are created and does not integrate beyond. 

        

        bash-3.2$ ncdump -v Times wrfout_d01_2010-08-04_00:00:00

        Times =

          "2010-08-04_00:00:00",

          "2010-08-04_01:00:00",

          "2010-08-04_02:00:00",

          "2010-08-04_03:00:00",

          "2010-08-04_04:00:00" ;

        }

        

        bash-3.2$ ncdump -v Times wrfout_d02_2010-08-04_00:00:00

        Times =

          "2010-08-04_00:00:00",

          "2010-08-04_01:00:00",

          "2010-08-04_02:00:00",

          "2010-08-04_03:00:00",

          "2010-08-04_04:00:00" ;

        

        bash-3.2$ ncdump -v Times wrfout_d03_2010-08-04_00:00:00

        Times =

          "2010-08-04_00:00:00",

          "2010-08-04_01:00:00",

          "2010-08-04_02:00:00",

          "2010-08-04_03:00:00",

          "2010-08-04_04:00:00" ;

        

        After integrating for 4hours, the model  gives segmentation
        fault. and these directories are created and does not integrate
        beyond. 

        drwxr-xr-x    2            256 Mar 03 04:20 coredir.5

        drwxr-xr-x    2            256 Mar 03 04:20 coredir.3

        drwxr-xr-x    2            256 Mar 03 04:20 coredir.2

        drwxr-xr-x    2            256 Mar 03 04:20 coredir.1

        

        Kindly help. The namelist.input file is also attached for
        reference. 

        

        Geeta 

        

      
      

    
    
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/wrf-users/attachments/20110309/6593bffd/attachment.html 


More information about the Wrf-users mailing list