Changes between Version 12 and Version 13 of Docs/PostProcessingAppArcherSetup


Ignore:
Timestamp:
30/11/18 10:58:17 (12 months ago)
Author:
ros
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Docs/PostProcessingAppArcherSetup

    v12 v13  
    11= ARCHER specific setup instructions for data transfer to JASMIN = 
    22 
    3 If you wish to transfer files from the RDF to JASMIN using the transfer app then you will need to make the following changes in addition to those detailed on the Post Processing App page. 
    43 
    5 == Suite Modifications == 
     4 
     5 
     6== Adding the PP Transfer task to a suite == 
     7 
     8You only need to follow these instructions if your suite doesn't already have the "PP Transfer" option available. 
     9 
     10Search in the ''rose edit'' GUI for the variable '''PPTRANSFER'''. If it is not found you will need to proceed with the following instructions. 
    611 
    712=== `rose-suite.conf` === 
    813 1.  Add '''PPTRANSFER=true''' 
    914 
    10  2. The PPTRANSFER variable will, by default, appear under ''"suite conf -> jinja2"''.  To tell Rose to place it with all the other suite control switches under ''"suite conf -> Build and Run"'' edit `meta/rose-meta.conf` to add in the metadata for the PPTRANSFER variable. (This step is optional.) 
     15 2. The PPTRANSFER variable will, by default, appear under ''"suite conf -> jinja2"''.  To tell Rose to place it with all the other suite control switches (e.g. "Build UM" & "Run Reconfiguration") usually found in a panel in the ''suite conf'' section under ''"Build and Run"'' or ''Tasks'' edit the `meta/rose-meta.conf` file to add in the metadata for the PPTRANSFER variable.  Place it under the definition for POSTPROC. (This step is optional.) 
    1116{{{ 
    1217[jinja2:suite.rc=PPTRANSFER] 
     
    1419description=Transfer files archived with PostProc to a remote machine 
    1520help= 
    16 ns=Build and Run 
     21ns=<panel_namespace> 
    1722sort-key=runPostproc1 
    1823title=PP Transfer 
    1924type=boolean 
    2025}}} 
     26 
     27 Where `<panel_namespace>` is the same value as for the POSTPROC entry in this file; e.g. `ns=Build and Run` 
    2128 
    2229=== `suite.rc` === 
     
    6875}}} 
    6976 
     77 Take care to ensure there is no trailing whitespace at the end of each added line. 
     78 
    7079  3. In the `[[postproc]]` task check that `pre-script` is set as follows:  
    7180{{{ 
    7281    [[postproc]] 
    7382        inherit = ... 
    74         pre-script = "module load nco/4.6.8; module load anaconda; export PYTHONPATH=$PYTHONPATH:$UMDIR/lib/python2.7; module list; ulimit -s unlimited" 
     83        pre-script = "module load nco/4.5.0; module load anaconda/2.2.0-python2;  module list 2> &1; export PYTHONPATH=$PYTHONPATH:$UMDIR/lib/python2.7; ulimit -s unlimited" 
    7584        ... 
     85}}} 
     86 
     87 Note: If your are running the coupled model and using netcdf module `cray-netcdf/4.4.1.1` then the pre-script line will need to be: 
     88 
     89{{{ 
     90        pre-script = "module load nco/4.6.8; module load anaconda; module list 2>&1; export PYTHONPATH=$PYTHONPATH:$UMDIR/lib/python2.7; ulimit -s unlimited" 
    7691}}} 
    7792