-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Pulling all changes from private repo up to commit 2939b75
- Loading branch information
1 parent
76699f3
commit e56fbf6
Showing
16 changed files
with
958 additions
and
1,150 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,10 +9,7 @@ Date: June 2023 | |
> 1. Introduction | ||
> 2. Logging in | ||
> 3. Navigating and setting up the directories | ||
> 4. Creating environments | ||
> 5. Writing the job script | ||
> 6. Submitting and monitoring and tracking | ||
> 7. Moving outputs to project space, and local space | ||
|
||
## 1. Introduction | ||
|
||
|
@@ -21,31 +18,13 @@ This document serves as a comprehensive guide to using UBC ARC's Sockeye high co | |
For a more simplified version of using Sockeye to run Gaussian Process models, see the following notebook: []. The Sockeye tutorial in this notebook assumes that you are part of the `st-aorsi-1` allocation and have access to the group's directories. | ||
|
||
**Overview of Workflow:** | ||
- Apply to obtain resources from UBC ARC's Sockeye cloud computing platform. Professor Anais Orsi did this for us. Then, obtain permission to connect to Sockeye with your CWL. Professor Anais Orsi will have to contact Sockeye and give them your cwl ... DOUBLE CHECK THIS ... | ||
- Apply to obtain resources from UBC ARC's Sockeye cloud computing platform. Professor Anais Orsi did this for us. Then, obtain permission to connect to Sockeye with your CWL. (Professor Anais Orsi will have to contact Sockeye and give them your cwl). | ||
- Then, do the first-time set-up stuff where you install Cisco AnyConnect and enhanced CWL (two-factor authentication). | ||
- Next, try ssh-ing into Sockeye. | ||
- Make a plan of the GP jobs you would like to submit. It would be helpful to create a spreadsheet. | ||
- Next, make sure all the necessary scripts and data are set up in the directories. You can use the already set-up st-aorsi-1 group or set-up your own if you have a new allocation. | ||
- Create an environment, or use the one already set-up for st-aorsi-1. | ||
|
||
**Terms and Definitions:** | ||
|
||
- job | ||
- allocation code | ||
- ssh | ||
- home | ||
- scratch | ||
- project | ||
- vi | ||
- cwl | ||
- vpn | ||
- enhanced cwl | ||
- terminal | ||
- purging scratch space | ||
|
||
**More resources on further information:** | ||
|
||
- ... | ||
|
||
> SLIPP's allocation code: `st-aorsi-1` | ||
|
@@ -70,7 +49,7 @@ $ ssh [email protected] | |
|
||
--- | ||
|
||
## 3. Navigating and setting up the directories | ||
## 3. Navigating the directories | ||
|
||
#### **General overview** | ||
|
||
|
@@ -94,71 +73,4 @@ There are three main directories: | |
> **Access:** Shared with everyone in your allocation/team (readable/writable) | ||
> **Storage:** 5 TB + limit of 1,000,000 files | ||
#### **Directory set-up \[new allocation\]** | ||
|
||
Follow the steps below to set up the allocation space with the files required to run jobs for this project: | ||
|
||
... | ||
|
||
Each team member who plans on submitting jobs on Sockeye should | ||
|
||
|
||
#### **`st-aorsi-1` directories \[st-aorsi-1 allocation\]** | ||
|
||
The `st-aorsi-1` Sockeye space is already set-up, below shows the breakdown of the directories: | ||
|
||
**Project:** `/arc/project/st-aorsi-1/` | ||
|
||
- **`/arc/project/st-aorsi-1/data/`** | ||
- Contains the full IsoGSM raw dataset | ||
- `IsoGSM/Total.IsoGSM.ERA5.monmean.nc` | ||
- Contains data required for preprocessing (land-sea mask, and orography across Antarctica) | ||
- `IsoGSM_land_sea_mask.nc` | ||
- `IsoGSM_orogrd.nc` | ||
- Contains the full three preprocessed data files | ||
- `preprocessed/preprocessed_test_ds.nc` | ||
- `preprocessed/preprocessed_train_ds.nc` | ||
- `preprocessed/preprocessed_valid_ds.nc` | ||
- **`/arc/project/st-aorsi-1/outputs/`** | ||
- Used to store finalized outputs you want to keep | ||
- ... | ||
- `/arc/project/st-aorsi-1/shared/` | ||
- Stores environment files able to be used by everyone in the allocation group | ||
- ... | ||
|
||
**Scratch:** `/scratch/st-aorsi-1/` | ||
|
||
From May - June 2023, Shirley Zhang (cwl: `wenlansz`) submitted jobs through her directory in the scratch space. As of June 2023, the directory is set up as follows (may be different if Sockeye purges the scratch space): | ||
|
||
- **`/scratch/st-aorsi-1/wenlansz/job-scripts/`** | ||
- ... | ||
|
||
- **`/scratch/st-aorsi-1/wenlansz/outputs/`** | ||
- ... | ||
|
||
- **`/scratch/st-aorsi-1/wenlansz/e-files/`** | ||
- ... | ||
|
||
- **`/scratch/st-aorsi-1/wenlansz/o-files/`** | ||
- ... | ||
|
||
|
||
|
||
## 4. Creating environments | ||
|
||
|
||
... | ||
|
||
|
||
## 5. Writing the job script | ||
|
||
... | ||
|
||
|
||
## 6. Submitting and monitoring and tracking | ||
|
||
... | ||
|
||
## 7. Moving outputs to project space, and local space | ||
|
||
... |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.