# Changes between Version 20 and Version 21 of WRF4GTutorial2

Ignore:
Timestamp:
Oct 2, 2012 11:16:26 AM (10 years ago)
Comment:

--

### Legend:

Unmodified
 v20 == How to manage WRF4G errors ? == In this section, we are going to see how to manage WRF4G errors. In order to do that, we are going to create a new experiment, based on single_test, but the end_date of this experiment will be "2011-08-30_12:00:00". Follow the steps below. In this section, we are going to see how to manage WRF4G errors. In order to do that, we are going to create a new experiment called test_1, based on single_test, in which the end_date will be "2011-08-30_12:00:00". Follow the steps below. {{{ [user@mycomputer~]$cat experiment.wrf4g | grep experiment_name experiment_name = "test_2" experiment_name = "test_1" [user@mycomputer~]$ cat experiment.wrf4g | grep "end_date " [user@mycomputer~]$cat$WRF4G_LOCATION/etc/resources.wrf4g | grep WRF4G_BASEPATH= WRF4G_BASEPATH="/home/user/WRF4G/repository/output" [user@mycomputer~]$cd$WRF4G_LOCATION/repository/output/test_1/test_1/log/ }}} The chunk log name is composed of using chunk number and job identifier (GW). * log_{chunk_number}_{job_identifier}.tar.gz {{{ #!sh [user@mycomputer~]$ls log_1_4.tar.gz log_2_5.tar.gz log_3_6.tar.gz log_4_7.tar.gz }}} The chunk log name is composed of using chunk number and job identifier (GW). * log_{chunk_number}_{job_identifier}.tar.gz In our case, chunk log name will be log_4_7.tar.gz because the chunk number is 4 and the job identifier is 7. {{{ }}} In each log package you are able to see all WRF binaries executed as well as WRF4G logs such as WRF4G.log, wrfgel.out and monitor.log. In our case, we are going to focus on WRF4G.log which the main log of the simulation. In each log package you are able to see all WRF log binaries as well as WRF4G logs such as WRF4G.log, wrfgel.out and monitor.log. In our case, we are going to focus on WRF4G.log which the main log of the remote simulation. {{{ #!sh /home/user/.gw_user_6 ********************************************************************************** }}} WRF4G.log shows that ungrid was the last WRF binary. Therefore, if you check out ungrib log, you will probably discover the error. {{{ #!sh [user@mycomputer~]$ tail ungrib_GFS_2011083000.out 100.0  X        X        X        X        X Begin rrpr ---------------------------------------------------- }}} '''The problem is that there is not input data to simulate the last chunk.''' {{{ #!sh [user@mycomputer~]$cat$WRF4G_LOCATION/etc/resources.wrf4g | grep WRF4G_INPUT= WRF4G_INPUT="/home/user/WRF4G/repository/input"