Changes between Version 20 and Version 21 of WRF4GTutorial2


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

--

Legend:

Unmodified
Added
Removed
Modified
  • WRF4GTutorial2

    v20 v21  
    44
    55== How to manage WRF4G errors ? ==
    6 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.
     6In 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.
    77
    88{{{
     
    2424
    2525[user@mycomputer~]$ cat experiment.wrf4g | grep experiment_name
    26 experiment_name = "test_2"
     26experiment_name = "test_1"
    2727
    2828[user@mycomputer~]$ cat experiment.wrf4g | grep "end_date "
     
    8888[user@mycomputer~]$ cat $WRF4G_LOCATION/etc/resources.wrf4g | grep WRF4G_BASEPATH=
    8989WRF4G_BASEPATH="/home/user/WRF4G/repository/output"
     90
    9091[user@mycomputer~]$ cd $WRF4G_LOCATION/repository/output/test_1/test_1/log/
    91 }}}
    9292
    93 The chunk log name is composed of using chunk number and job identifier (GW).
    94  * log_{chunk_number}_{job_identifier}.tar.gz
    95 
    96 {{{
    97 #!sh
    9893[user@mycomputer~]$ ls
    9994log_1_4.tar.gz  log_2_5.tar.gz  log_3_6.tar.gz  log_4_7.tar.gz
    10095}}}
    10196
     97The chunk log name is composed of using chunk number and job identifier (GW).
     98 * `log_{chunk_number}_{job_identifier}.tar.gz`
    10299In our case, chunk log name will be log_4_7.tar.gz because the chunk number is 4 and the job identifier is 7.
    103100{{{
     
    111108}}}
    112109
    113 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.
     110In 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.
    114111{{{
    115112#!sh
     
    153150    /home/user/.gw_user_6
    154151**********************************************************************************
     152}}}
    155153
     154WRF4G.log shows that ungrid was the last WRF binary. Therefore, if you check out ungrib log, you will probably discover the error. 
     155
     156{{{
     157#!sh
    156158[user@mycomputer~]$ tail ungrib_GFS_2011083000.out
    157159 100.0  X        X        X        X        X                                                                                                                                                                                 
     
    165167 Begin rrpr
    166168----------------------------------------------------
     169}}}
    167170
     171'''The problem is that there is not input data to simulate the last chunk.'''
     172{{{
     173#!sh
    168174[user@mycomputer~]$ cat $WRF4G_LOCATION/etc/resources.wrf4g | grep WRF4G_INPUT=
    169175WRF4G_INPUT="/home/user/WRF4G/repository/input"