| 11 | === Scenario 1 - PP Transfer not already in the suite and you have never used the Transfer app before. === |
| 12 | |
| 13 | * [#addpptransfertask Add PP Transfer task to the suite] |
| 14 | * [#sshjasmin Setup ssh-key to connect from NEXCS to JASMIN] |
| 15 | |
| 16 | === Scenario 2: PP Transfer already in suite and you have never used the Transfer app before. === |
| 17 | |
| 18 | * [#sshjasmin Setup ssh-key to connect from NEXCS to JASMIN] |
| 19 | |
| 20 | == Add PP Transfer task to a suite == #addpptransfertask |
| 21 | |
| 22 | Only follow these instructions if your suite doesn't already have the "PP Transfer" option available. |
| 23 | |
| 24 | === `rose-suite.conf` === |
| 25 | |
| 26 | 1. Add '''PPTRANSFER=true''' |
| 27 | |
| 28 | 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.) |
28 | | Add the ''pptransfer'' task into the graph for all subsequent cycles such that it runs after the ''postproc'' task and also waits for the previous ''pptransfer'' task to complete. As an example for a coupled suite (All added lines indicated with ''"<="''): |
| 46 | 1. Add the build & run of ''pptransfer'' task into the cylc graph initial cycle. Add the line: |
| 47 | {{{ |
| 48 | {{ 'fcm_make_pptransfer => fcm_make2_pptransfer' + (' => pptransfer' if RUN else '') if PPTRANSFER else '' }} |
| 49 | }}} |
| 50 | to the cylc graph for the initial cycle, indicated by ![[[ R1 ]]]. For example: (insertion indicated by ''"<= Add line here"'') |
| 51 | {{{ |
| 52 | [[dependencies]] |
| 53 | [[[ R1 ]]] |
| 54 | graph = """ |
| 55 | {{ 'fcm_make_pp => fcm_make2_pp' + (' => postproc' if RUN else '') if POSTPROC else '' }} |
| 56 | {{ 'fcm_make_pptransfer => fcm_make2_pptransfer' + (' => pptransfer' if RUN else '') if PPTRANSFER else '' }} <== Add line here |
| 57 | {{ 'fcm_make_ocean => fcm_make2_ocean' + (' => recon' if RECON else ' => coupled' if RUN else '') if BUILD_OCEAN else '' }} |
| 58 | {{ 'fcm_make_um => fcm_make2_um' + (' => recon' if RECON else ' => coupled' if RUN else '') if BUILD_UM else '' }} |
| 59 | {{ 'install_ancil => recon ' if RECON else ('install_ancil => coupled' if RUN else '')}} |
| 60 | {{ 'recon' + (' => coupled' if RUN else '') if RECON else '' }} |
| 61 | {{ 'clearout' + (' => coupled' if RUN else '') if CLEAROUT else '' }} |
| 62 | """ |
| 63 | }}} |
| 64 | |
| 65 | 2. Add the ''pptransfer'' task into the graph for all subsequent cycles such that it runs after the ''postproc'' task and also waits for the previous ''pptransfer'' task to complete. As an example for a coupled suite (All added lines indicated with ''"<="''): |