Changes between Version 16 and Version 17 of WRF4G/ExecutionEnvironments


Ignore:
Timestamp:
Feb 21, 2013 5:07:40 PM (9 years ago)
Author:
carlos
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WRF4G/ExecutionEnvironments

    v16 v17  
    328328== Tirant ==
    329329
     330{{{
     331ssh username@tirant1.uv.es
     332}}}
     333
    330334=== Running Jobs ===
    331335
     
    338342The user’s limits are assigned automatically to each particular user (depending on the resources granted by the Access Committee) and there is no reason to explicitly set the #@class directive. Anyway you are allowed to use the special class: "debug" in order to performe some fast short tests. To use the "debug" class you need to include the #@class directive
    339343
    340 Table 1: Classes Class debug Max CPUs 64 CPU Time 10 min Wall time limit 10 min
     344|| Class || Max CPUs || CPU Time || Wall time limit ||
     345|| debug || || 64 || 10 min || 10 min ||
     346
    341347The specific limits assigned to each user depends on the priority granted
    342348by the access committee. Users granted with ”high priority hours” will have access to a maximum of 1024 CPUs and a maximum wall clock limit of 72