Changes between Version 26 and Version 27 of WRF4GTutorial2


Ignore:
Timestamp:
Oct 2, 2012 12:53:31 PM (10 years ago)
Author:
carlos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WRF4GTutorial2

    v26 v27  
    193193== How to use `wrf4g_kill` command ==
    194194
    195 In this example, we are going to simulate an experiment with independent realizations which has [[WRF4Gexperiment_wrf4g#Experimenttime-specification| multiple_parameters flag]] activated. The experiment is compose of five realizations with three chunk per realization. In order to use [[WRF4GCommandLineInterface#wrf4g_kill | wrf4g_kill command]], we are going to first submit the experiment.
     195In this example, we are going to simulate an experiment with independent realizations which has [wiki:WRF4Gexperiment_wrf4g#Experimenttime-specification| multiple_parameters flag] activated. The experiment is compose of five realizations with three chunk per realization. In order to use [wiki:WRF4GCommandLineInterface#wrf4g_kill | wrf4g_kill command], we are going to first submit the experiment.
    196196{{{
    197197#!sh
     
    379379== How to add new computing resources to WRF4G ==
    380380
     381[wiki:WRF4Gframework4g_conf framework4g.conf] file which is located under `$WRF4G_LOCATION/etc` directory has a section called '''Computing Resources'''
     382
     383 WRF4G uses DRM4G in order to configure computing resources. Using that tool, users are able to access different Distributed Resource Managements (DRM) such as:
     384
     385    PBS/Torque
     386    SGE
     387    FORK
     388    LoadLeveler
     389    MN SLRUM (only for Red Española de Supercomputación)
     390
     391
     392This file contains one resource per line, with format:
     393
     394{{{
     395   FQDN    attributes
     396   ...     ...
     397   FQDN    attributes
     398}}}
     399 where:
     400   
     401   * FQDN: is the name of the resource.
     402   * attributes: are the static attributes of the resource. The syntax is:
     403
     404        <scheme>://<username>@<host>?<query>
     405
     406        -scheme: the URL schemes available are "ssh" and "local".
     407            * ssh:   access to remote DRM via SSH
     408            * local: use the local DRM
     409        -username: user name
     410        -host: host name
     411        -query: contains additional information. The query string syntax is:
     412            * key1=value1;key2=value2;key3=value3
     413            Variable options:
     414               LRMS_TYPE   (mandatory)                : DRM system for execution [pbs | sge | fork | loadleveler | mnslurm ]
     415               PROJECT     (optional for SGE,         : specifies the project to which the jobs are assigned
     416                            PBS and LoadLeveler)
     417               GW_RUNDIR   (optional)                 : directory on the resource in which jobs are deployed. By default, it is user's home
     418               GW_LOCALDIR (optional)                 : defines the working directory on the Working Node (have to be an absolute path)
     419               NODECOUNT   (optional)                 : total number of slots on the DRM system 
     420               QUEUE_NAME  (optional)                 : the name of the queue to configure 
     421
     422Examples
     423
     424mycomputer                   local://localhost?LRMS_TYPE=fork;NODECOUNT=1
     425#PBS_cluster                 local://localhost?LRMS_TYPE=pbs;QUEUE_NAME=estadistica
     426#SGE_cluster                 local://localhost?LRMS_TYPE=sge;PROJECT=l.project
     427#RES_cluster                 local://localhost?LRMS_TYPE=mnslurm
     428#remote_PBS_cluster          ssh://user@hostname_submitting_machine?LRMS_TYPE=pbs;QUEUE_NAME=short
     429#remote_SGE_cluster          ssh://user@hostname_submitting_machine?LRMS_TYPE=sge;PROJECT=l.project
     430#remote_RES_cluster          ssh://user@hostname_submitting_machine?LRMS_TYPE=mnslurm
     431#remote_FORK_cluster         ssh://user@hostname_submitting_machine?LRMS_TYPE=fork
     432#remote_LoadLeveler_cluster  ssh://user@hostname_submitting_machine?LRMS_TYPE=loadleveler;NODECOUNT=100
     433
     434
     435[[NoteBox(note, After modifying this file\, in order to make changes effective\, users will have to execute: || `wrf4g_framework reload`)]]