Version 12 (modified by valva, 11 years ago) (diff) |
---|
Table of Contents
wrf4g_framework
Usage
wrf4g_framework {start|stop|restart|reload}
Synopsis
wrf4g_framework manages WRF4G framework components: drm4g and mysql (in case it is needed). It load the framework configuration from etc/framework4g.conf.
wrf4g_prepare
Usage
wrf4g_prepare [--dry-run] [--reconfigure] [--verbose] [--help]
Synopsis
Given a file (experiment.wrf4g) describing the experiment, prepare the experiment creating the realization and chunks needed to perform it.
Options
--dry-run Perform a trial run with no changes made. --reconfigure Reconfigure experiment. With this option we can change the start and end date of the experiments and add new physics. Values are taken from a modified experiment.wrf4g. --verbose Verbose mode. Explain what is being done --help Shows this help
wrf4g_submit
Usage
wrf4g_submit [--dry-run] [--nchunk N] [--nrea N] [--frea FILE] [--priority P] [--rerun] [--verbose] [--force] [--help]
Synopsis
Submits an experiment or realization. If the user do not specify an experiment or realization with the options, the name of the experiment will be retrieved from experiment.wrf4g in case it exists in the current folder.
Options
--version show program's version number and exit -h, --help show this help message and exit -n, --dry-run Perform a trial run with no changes made -e name, --exp=name Name of the experiment to sumbit -r name, --rea=name Name of the realization to sumbit -F FILE, --frea=FILE File containing the name of the realization to sumbit. -a, --rerun Force to run although ths realization or experiment has finished -o, --run-just-one Run just the first chunk of the first realization. Only for testing purposes. -C N, --nchunk=N Run the next N chunks not finished of each realization -R N, --nrea=N Run the next N realizations not finished of the experiment -p P, --priority=P P is the priority the experiment or realization is going to be launched with (P is a integer between 1 and 100) -v, --verbose Verbose mode. Explain what is being done -f, --force Don't ask the user if he wants to submit an experiment already submitted
wrf4g_status
Usage
wrf4g_status [--exp experiment] [--rea realization] [--long] [--help]
Synopsis
Prints the experiment or realization status.
Options
--version show program's version number and exit -h, --help show this help message and exit -e name, --exp=name Name of the experiment. -r name, --rea=name Name of the realization -l, --long Show a detailed status.
Output field description
Summarized output: Shows realizations' status of each experiment (Default).
valva@sipc18:/tmp/WRF4G/experiments/wrfuc_single_serial$ wrf4g_status Experiment P W R D F test 0 0 0 1 0 uc_phys 0 4 1 0 0 uc_single 1 0 0 0 0
- P: Prepared
- W: Waiting
- R: Running
- F: Failed
Long output: Shows a detailed realization status of every experiment
valva@sipc18:/tmp/WRF4G/experiments/single/testc$ wrf4g_status Realization GW Stat Chunks Comp.Res WN Run.Sta ext % testc 2 R 3/3 mycomputer sipc18 Down. Bound. - 66.67
- Realization: Realization name.
- Status: It can be take the following values: P(Prepared), S(Submitted), R(Running), F(Failed) and D(Done).
- Chunks [Chunk currently running/Total Chunks]: A realization is split into chunks. Each chunk is sent as a job.
- Computer resource: Computing Resource where the job is running. (It has to be one of the resources listed by wrf4g_resources)
- WN: Computing node where the job is running.
- Run.Sta: Job status in the WN (Downloading data, running ungrib, real, wrf, ...)
- ext: Exit Code. If exit code is different from 0, there has been an error. Error codes are explained in $WRF4G_LOCATION/lib/bash/wrf4g_exit_codes.sh
- % : percentage of simulation finished.
wrf4g_resources
Usage
wrf4g_resources [-h] [-c delay] [-nfx] [-m job_id] [host_id]
Synopsis
Prints information about all the resources configured in framework4g.conf (default)
Options
-h print this help -c delay refresh host information every delay seconds -n do not print the header -f full format -x xml format -m job_id print hosts matching the requirements of a given job host_id only monitor this host_id, printing also queue information
Output field description
valva@sipc18:~$ wrf4g_resources HID PRIO OS ARCH MHZ %CPU MEM(F/T) DISK(F/T) N(U/F/T) LRMS HOSTNAME 0 1 GNU/Linux2.6.32 x86_6 2000 0 484/3270 1152/8662 0/1/1 FORK mycomputer 1 1 GNU/Linux2.6.18 x86_6 2127 0 12/2048 671273/921472 88/0/88 PBS asna_t1 2 1 GNU/Linux2.6.18 x86_6 2127 0 11/2048 671273/921472 168/0/168 PBS asna_b2
FIELD INFORMATION HID host unique identification assigned by the GridWay system PRIO priority assigned to the host OS operating system ARCH architecture MHZ CPU speed in MHZ %CPU free CPU ratio MEM(F/T) system memory: F = Free, T = Total DISK(F/T) secondary storage: F = Free, T = Total N(U/F/T) number of slots: U = used by GridWay, F = free, T = total LRMS local resource management system, the jobmanager name HOSTNAME FQDN of this hostthe QUEUE FIELD INFORMATION QUEUENAME name of this queue SL(F/T) slots: F = Free, T = Total WALLT queue wall time CPUT queue cpu time COUNT queue count number MAXR max. running jobs MAXQ max. queued jobs STATUS queue status DISPATCH queue dispatch type PRIORITY queue priority