79 | | In this example, the publicly available NCEP Reanalysis (run 1) data are going to be used. This data can be dowloaded from [http://nomad3.ncep.noaa.gov/pub/reanalysis-1/6hr] in GRIB format. These are monthly files that get updated each month nearly in real time. Two files are needed for each month, one with the pressure level data, labeled "pgb", and other one with 2D data, labeled "grb2d". extdata_path defined in experiment.wrf4g must pint to the folder where these files are located. Alternatively, it is possible to write a [wiki:WRF4G/WRF4GPreprocessor preprocessor] that downloads the data itself. Note that the file names must be parsed by the [wiki:WRF4G/WRF4GPreprocessor preprocessor]. In this case, if both files are located into the same folder, and provided the extension ".grb" is appended to them, the default [wiki:WRF4G/WRF4GPreprocessor preprocessor] will parse them correctly, since it looks for monthly files with year/month (YYYY/mm) into their names. For example, the files for December 2010 should be: |
| 79 | In this example, the publicly available NCEP Reanalysis (run 1) data are going to be used. This data can be dowloaded from [http://nomad3.ncep.noaa.gov/pub/reanalysis-1/6hr] in GRIB format. These are monthly files that get updated each month nearly in real time. Two files are needed for each month, one with the pressure level data, labeled "pgb", and other one with 2D data, labeled "grb2d". extdata_path defined in experiment.wrf4g must point to the folder where these files are located. Alternatively, it is possible to write a [wiki:WRF4G/WRF4GPreprocessor preprocessor] that downloads the data itself. Note that the file names must be parsed by the [wiki:WRF4G/WRF4GPreprocessor preprocessor]. In this case, if both files are located into the same folder, and provided the extension ".grb" is appended to them, the default [wiki:WRF4G/WRF4GPreprocessor preprocessor] will parse them correctly, since it looks for monthly files with year/month (YYYY/mm) into their names. For example, the files for December 2010 should be: |
88 | | == How to manage WRF4G errors == |
| 88 | === Keeping organized === |
| 89 | |
| 90 | Before starting to create an experiment, is good practice to create some directories to be tidy. For example, if our project is called "seawind", we can create the following directory hierarchy. |
| 91 | |
| 92 | {{{ |
| 93 | projects/seawind/submit/exp1 |
| 94 | projects/seawind/submit/exp2 |
| 95 | ... |
| 96 | projects/seawind/domains |
| 97 | projects/seawind/data |
| 98 | projects/seawind/scripts |
| 99 | projects/seawind/figures |
| 100 | }}} |
| 101 | |
| 102 | Of course, many other combinations are possible, depending in the organization of the resources available to the user. |
| 103 | |
| 104 | === The test experiment === |
| 105 | |
| 106 | Before creating a large experiment, with many chunks and realizations, it is convenient to run a smaller test experiment with exactly the same model configuration. This way we can see that everything is working as we want. Frequently, some attempts are needed before WRF runs, because of mistakes in the configuration files or in the set up of input files. |
| 107 | |
| 108 | Go to the "submit" folder and create another folder called "sw_test": |
| 109 | |
| 110 | {{{ |
| 111 | cd projects/seawind/submit |
| 112 | mkdir sw_test |
| 113 | cd sw_test |
| 114 | }}} |
| 115 | |
| 116 | Now we need to copy here the templates of experiment.wrf4g and resources.wrf4g. |