Changes between Version 4 and Version 5 of WRF4Gexperiment_wrf4g


Ignore:
Timestamp:
Sep 6, 2011 6:35:03 PM (11 years ago)
Author:
MarkelGarcia
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WRF4Gexperiment_wrf4g

    v4 v5  
    33 * '''experiment_name:''' Name of the experiment. '''It has to be unique'''. Duplicity of experiment names would give different WRF4G answers:
    44== Domain of simulation ==
    5  * '''max_dom:''' Number of domains
    6  * '''domain_name:''' Name of the folder where there is all the information of the domain of simulation ('{{{nameslit.wps}}}' & '{{{geo_em.d[nn].nc}}}'). This folder will be find in {{{${WRF4G_DOMAINPATH}}}} of the [wiki:Developers#resources.wrf4g resources.wrf4g] file
     5 * '''max_dom:''' Number of domains.
     6 * '''domain_name:''' Name of the folder with the information about the domain of the simulations, this is, the files generated by geogrid.exe ('{{{nameslit.wps}}}' & '{{{geo_em.d[nn].nc}}}'). This folder needs to be located at {{{${WRF4G_DOMAINPATH}}}} of the [wiki:Developers#resources.wrf4g resources.wrf4g] file.
    77
    88== Input data ==
    9  * '''extdata_vtable:''' Vtable of the {{{ungrib}}} module to be used to decode provided GRIB input data
    10  * '''extdata_preprocessor:''' name (just the ending {{{[NAME]}}} section '{{{preprocessor.[NAME]}}}') of the necessary pre-processor useful to make the specific input data available for WRF model. User could not be interested on the permanent WRF-necessary modification of any source of data. With the specification and design of a pre-processor, necessary WRF modifications (g.e.: ASCII to GRIB, variables re-coding, complete input data). Pre-processors are included within the {{{WRF4G-1.0beta.tar.gz}}} tar file from '{{{${WRF4G_LOCATION}/repository/apps}}}'
    11  * '''extdata_path :''' Path to the data. It must be consistent with the pre-processor design
    12  * '''extdata_interval:''' Interval of the input data (in seconds). On multiple input data sources place the smallest one
     9 * '''extdata_vtable:''' Vtable of the {{{ungrib}}} module to be used to decode provided GRIB input data.
     10 * '''extdata_preprocessor:''' Name (just the ending {{{[NAME]}}} section in '{{{preprocessor.[NAME]}}}') of the necessary pre-processor useful to make the specific input data available for WRF model. User could not be interested on the permanent WRF-necessary modification of any source of data. With the specification and design of a pre-processor, necessary WRF modifications (g.e.: ASCII to GRIB, variables re-coding, complete input data). Pre-processors are included in {{{WRF4G-1.0beta.tar.gz}}} tar file in '{{{${WRF4G_LOCATION}/repository/apps}}}'
     11 * '''extdata_path :''' Path to the input data. It must be consistent with the pre-processor design.
     12 * '''extdata_interval:''' Interval of the input data (in seconds). On multiple input data sources use the smallest one.
    1313
    1414== Output data ==
    15  * '''postprocessor:''' user migh tbe interested on the transformation of the WRF outputs. A first generic post-process of the output will be automatically done if a valid name {{{postprocessor.[NAME]}}} is provided. Post-processors are included within the {{{WRF4G-1.0beta.tar.gz}}} tar file from '{{{${WRF4G_LOCATION}/repository/apps}}}'
     15 * '''postprocessor:''' user might be interested in the transformation of the WRF output files. A first generic post-process of the output will be automatically carried out if a valid name {{{postprocessor.[NAME]}}} is provided. Post-processors are included in the {{{WRF4G-1.0beta.tar.gz}}} tar file at '{{{${WRF4G_LOCATION}/repository/apps}}}'
    1616
    1717== Experiment time-specification ==
    1818 * '''start_date:''' Beginning of the experiment
    1919 * '''end_date:''' End of the experiment.
    20  * '''chunk_size_h:''' Length (in hour) of the smallest independent temporal piece of the experiment. It will be the same for all the realizations of the experiment and at the end of each one will be written a {{{wrf-restart}}} file in order to continue the experiment with the consecutive chunk
     20 * '''chunk_size_h:''' Length (in hours) of the smallest independent temporal piece of the experiment. It will be the same for all the realizations of the experiment, and at the end of each one a {{{wrf-restart}}} file will be written , in order to continue the experiment with the consecutive chunk
    2121 * '''multiple_dates:''' Binary flag (0:No, 1:Yes) indicating whether the experiment will be based on independent realizations started at different dates with the same length. When activated it has to be accompanied with appropriated values of:
    22    * simulation_interval_h: interval (in hour) between independent realizations. It can be specified as multiple values as follows: '{{{N*chunk_size}}}'
    23    * simulation_length_h: length (in hour) of the independent realization. It can be specified as multiple values as follows: '{{{M*chunk_size}}}'
    24  * '''rerun:''' Binary flag (0;No , 1: Yes) indicating whether the experiment should be rerun although experiment has already run (over-writing output files and data-base values)
    25  * '''multiple_parameters:''' Binary flag (0;No , 1: Yes) indicating whether the experiment will be based in independent realizations with different values on the WRF-namelist.input file. When activated it has to be accompanied with appropriated values of:
    26    * multiparams_variables: set of parameters that would be different (some of them or all) between realizations. It is given as a coma-separated WRF-namelist.input files (no record specification is necessary if the parameter already appears on the provided WRF-version  [wiki:Developers#nameslit.input_template namelist.input template], If not it should be {{{[parameter]__[record]}}})
    27    * multiparams_combinations: set of values that would take each parameter on the realization (coma-separated). Realizations are separated by '{{{/}}}'
    28    * multiparams_nitems: number of values that should have the namelist parameter. {{{${max_dom}}}}, as many values as domains; {{{1}}}, a single value
    29    * multiparams_labels: organization of the output of the experiment will be done with a folder for each realization. Pattern of the folder name of a given realization will be {{{[start_date]_[multiparams_combinations]('_' separated)}}}. However, if user provide a set of names ('{{{/}}}' separated) for each realization, folder names will be '{{{[start_date]_[multiparams_labels]}}}'
     22   * simulation_interval_h: interval (in hours) between independent realizations. It can be specified as multiple values, as follows: '{{{N*chunk_size}}}'
     23   * simulation_length_h: length (in hours) of the independent realizations. It can be specified as multiple values, as follows: '{{{M*chunk_size}}}'
     24 * '''rerun:''' Binary flag (0;No , 1: Yes) indicating whether the experiment should be rerun, if the experiment has already run (over-writing output files and data-base values)
     25 * '''multiple_parameters:''' Binary flag (0;No , 1: Yes) indicating whether the experiment is based on independent realizations with different values on the WRF-namelist.input file. When activated it has to be accompanied with appropriated values of:
     26   * multiparams_variables: The set of parameters that we want to change (some of them or all) between realizations. It is given as a coma-separated WRF-namelist.input files (no record specification is necessary if the parameter already appears on the provided WRF-version  [wiki:Developers#nameslit.input_template namelist.input template], If not it should be {{{[parameter]__[record]}}})
     27   * multiparams_combinations: Values of the  changing parameters for each realization. Parameters should be separated by commas and realizations are separated by '{{{/}}}'.
     28   * multiparams_nitems: number of values that should have the namelist parameter. {{{${max_dom}}}}, as many values as domains; {{{1}}}, a single value.
     29   * multiparams_labels: the output of the experiment is organized with a folder for each realization. Pattern of the folder name for a given realization is {{{[start_date]_[multiparams_combinations]('_' separated)}}}. However, if user provides a set of names ('{{{/}}}' separated) for each realization, folder names will be '{{{[start_date]_[multiparams_labels]}}}'
    3030
    3131== Debugging ==