SiVeGCS/ray_template
6
0
Fork 1
forked from SiVeGCS/dask_template
Code Issues Pull requests Activity

Fix the readme file regarding the steps for Hawk

Browse source
This commit is contained in:
Kerem Kayabay 2024-08-26 05:49:36 +00:00
parent aa3d6b6799
commit 26cb3ed722
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -9,13 +9,13 @@ This repository looks at a deployment of a Dask cluster on Vulcan, and executing
## Getting Started ## Getting Started
### 1. Build and transfer the Conda environment to Hawk: ### 1. Build and transfer the Conda environment to Vulcan:
Only the `main` and `r` channels are available using the Conda module on the clusters. To use custom packages, we need to move the local Conda environment to Hawk. Only the `main` and `r` channels are available using the Conda module on the clusters. To use custom packages, we need to move the local Conda environment to Vulcan.
Follow the instructions in [the Conda environment builder repository](https://code.hlrs.de/SiVeGCS/conda-env-builder), which includes a YAML file for building a test environment. Follow the instructions in [the Conda environment builder repository](https://code.hlrs.de/SiVeGCS/conda-env-builder), which includes a YAML file for building a test environment.
### 2. Allocate workspace on Hawk: ### 2. Allocate workspace on Vulcan:
Proceed to the next step if you have already configured your workspace. Use the following command to create a workspace on the high-performance filesystem, which will expire in 10 days. For more information, such as how to enable reminder emails, refer to the [workspace mechanism](https://kb.hlrs.de/platforms/index.php/Workspace_mechanism) guide. Proceed to the next step if you have already configured your workspace. Use the following command to create a workspace on the high-performance filesystem, which will expire in 10 days. For more information, such as how to enable reminder emails, refer to the [workspace mechanism](https://kb.hlrs.de/platforms/index.php/Workspace_mechanism) guide.
@ -24,7 +24,7 @@ ws_allocate dask_workspace 10
ws_find dask_workspace # find the path to workspace, which is the destination directory in the next step ws_find dask_workspace # find the path to workspace, which is the destination directory in the next step
``` ```
### 3. Clone the repository on Hawk to use the deployment scripts and project structure: ### 3. Clone the repository on Vulcan to use the deployment scripts and project structure:
```bash ```bash
cd <workspace_directory> cd <workspace_directory>