From 26cb3ed722b173b757834541158dc1d79d9ed588 Mon Sep 17 00:00:00 2001 From: Kerem Kayabay Date: Mon, 26 Aug 2024 05:49:36 +0000 Subject: [PATCH] Fix the readme file regarding the steps for Hawk --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 4efecac..5782a88 100644 --- a/README.md +++ b/README.md @@ -9,13 +9,13 @@ This repository looks at a deployment of a Dask cluster on Vulcan, and executing ## 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. -### 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. @@ -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 ``` -### 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 cd