Verify

Check the log file(s) to make sure the run has completed correctly.

If it was successful, you should see:
       SUCCESS COMPLETE

MPI runs Check the log files rsl.out* and rsl.error* (there will be one rsl.out and one rsl.error for each processor you run on). Typically the rsl.out.0000 and rsl.error.0000 files will contain the most information, but if the run failed, an error message could potentially be in any one of these files. If there is not significant information in the *.0000 files, try checking the size of all of the rsl* files. If any file is larger than the others, check the end of that file to see if an error is printed.

wrf.exe jobs Other important information is also contained in the log file(s). Specifically: - When history and restart files are written, e.g., Timing for Writing wrfout_d01_2007-10-05_06:00:00 for domain 1: 0.92500 elapsed seconds. Timing for Writing wrfout_d02_2007-10-05_06:00:00 for domain 2: 2.64900 elapsed seconds. - Time it takes to complete a single timestep, e.g., Timing for main: time 2007-10-05_00:01:00 on domain 2: 13.67200 elapsed seconds. Timing for main: time 2007-10-05_00:02:00 on domain 2: 4.11200 elapsed seconds. Timing for main: time 2007-10-05_00:03:00 on domain 2: 4.12200 elapsed seconds. Timing for main: time 2007-10-05_00:03:00 on domain 1: 37.26700 elapsed seconds. - Look out for CFL errors. They typically indicate that the model is becoming unstable. The first thing to do in such a case is to rerun the model with a reduced time step.

Check the contents of the files. For netCDF files, two good tools are:

a. Use the ncdump utility.
b. Use the ncview utility.