Changes between Version 60 and Version 61 of Archer2


Ignore:
Timestamp:
17/12/20 13:38:29 (4 months ago)
Author:
simon
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Archer2

    v60 v61  
    176176=== GUI === 
    177177 
    178 Now start the GUI. There will be a warning triangle next to '''suite.conf'''. 
    179 In '''suite conf->Host Machine''' select Archer2, then set the Queue standard queue and set the account group by clicking on the plus, then changing the values. Remember to put the account group in single quotes. 
    180 In '''suite conf->Domain Decomposition-> Atmosphere''' set the Max number of processors\node to be 128. If not using IO servers, it is also a good idea to change the decomposition so that the NSxEWx(OpenMP threads) is some multiple of 128 for most efficient running. Keep the total number of cores roughly the same as for ARCHER. 
     178Now start the GUI with `rose edit`. There will be a warning triangle next to '''suite conf''' section. 
     179In '''suite conf->Host Machine''' select Archer2, then set the Queue standard queue and the account group by clicking on the plus to add then to the configuration, and then changing the values. This may be in a subsection, selected by clicking the arrow. Remember to put the account group in single quotes. The aid is to remove all of the warning triangles. 
     180 
     181In '''suite conf->Domain Decomposition''' set the Max number of processors/node to be 128. If you plan to depopulate the node, set this to some multiple of 8. If not using IO servers, it is also a good idea to change the Atmosphere decomposition so that the NSxEWx(OpenMP threads) is some multiple of 128 for most efficient running. Keep the total number of cores roughly the same as for ARCHER. 
    181182 
    182183In '''fcm_um_make->env->Configuration file''' set `config_root_path` to be  
     
    185186}}} 
    186187where `x` is the UM version of the suite. 
    187  
    188 Remove the revision number from `config_revision` so that the feild is clear. 
     188Remove the revision number from `config_revision` so that the field is clear. 
     189 
     190For vn11.1 and vn11.2 jobs, in '''fcm_um_make->env->Sources''' add 
     191{{{ 
     192fcm:um.x_br/dev/jeffcole/vn11.x_archer2_fixes 
     193}}} 
     194where `x` is the UM version of the suite. 
    189195 
    190196Save the new config. 
     197 
     198Note: If you have any bespoke ARCHER app `conf` files, these may have to be renamed and updated for ARCHER2 
    191199 
    192200You should now able to submit the job to ARCHER2.