Changes between Version 103 and Version 104 of WRF4G2.0/Experiment


Ignore:
Timestamp:
Sep 1, 2015 6:09:01 PM (7 years ago)
Author:
carlos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WRF4G2.0/Experiment

    v103 v104  
    4848* '''save_wps:''' Either yes or no (default value is no), indicating whether boundary and initial conditions (`real.exe` output) should be preserved or not. They will be used if the experiment is relaunched again.
    4949
    50 * '''parallel_environment:''' Tag to configure the parallel execution environment, which can be `POE` for IBM's Parallel Environment, `SRUN` for SLURM
     50* '''parallel_environment:''' Tag to configure the parallel execution environment (default value is MPIRUN), which can be `POE` for IBM's parallel environment, `SRUN` for SLURM batch system, or `MPIRUN` for Open MPI and MPICH.
    5151
    5252* '''parallel_real:''' Either yes or no (default value is yes), indicating whether the `real.exe` binary is compiled in serial or parallel mode.
     
    112112== Resource section ==
    113113
    114 Each resource section has to begin with the line [resource_name] followed by `key = value` entries. Thus, experiment variables such as `clean_after_run`, `save_wps`, `real_parallel`, `wrf_parallel`, `domain_path`, `preprocessor`, `extdata_path`, `postprocessor`, `app` and `output_path` can be defined depending on each computing resource. Therefore you can simulate your realizations concurrently on different resources.
     114Each resource section has to begin with the line [resource_name] followed by `key = value` entries. Thus, experiment variables such as `clean_after_run`, `save_wps`, `parallel_environment`, `parallel_real`, `parallel_wrf`, `domain_path`, `preprocessor`, `extdata_path`, `postprocessor`, `app` and `output_path` can be defined depending on each computing resource. Therefore you can simulate your realizations concurrently on different resources.
    115115
    116116== How to create one ==