From 803f86f892fd5d1752bd4246034bcaf064153828 Mon Sep 17 00:00:00 2001
From: Fahad Khalid <f.khalid@fz-juelich.de>
Date: Tue, 5 Mar 2019 13:11:37 +0100
Subject: [PATCH] Text updated after feedback from @kirchner2.
---
README.md | 30 +++++++++++++++++++++++++-----
caffe/README.md | 5 +++++
horovod/README.md | 3 ++-
3 files changed, 32 insertions(+), 6 deletions(-)
diff --git a/README.md b/README.md
index e5d688d..d41d36d 100644
--- a/README.md
+++ b/README.md
@@ -61,15 +61,16 @@ Otherwise please join the `PADC` and `CPADC` projects.
## 2. Logging on to the supercomputers
-Assuming JURECA is the target supercomputer, following are the steps required to login
-(more information [here](http://www.fz-juelich.de/ias/jsc/EN/Expertise/Supercomputers/JURECA/UserInfo/QuickIntroduction.html?nn=1803700)).
+### 2.1 JURECA
+
+Following are the steps required to login (more information
+[here](http://www.fz-juelich.de/ias/jsc/EN/Expertise/Supercomputers/JURECA/UserInfo/QuickIntroduction.html?nn=1803700)).
1. Use SSH to login:
`ssh <username>@jureca.fz-juelich.de`
2. Upon successful login, activate your project environment (more information [here](http://www.fz-juelich.de/ias/jsc/EN/Expertise/Supercomputers/NewUsageModel/NewUsageModel_node.html)):
-
`jutil env activate -p <project name> -A <accounting project name>`
3. Change to the project directory:
@@ -78,8 +79,27 @@ Assuming JURECA is the target supercomputer, following are the steps required to
You should be in your project directory at this point. If you'd like to clone this repository
elsewhere, please change to that directory.
-**Note:** The same steps are valid for logging on to JURON, except that the server address in
-step 1 should be: `juron.fz-juelich.de`
+### 2.2 JURON
+
+Following are the steps required to login.
+
+1. Use SSH to login:
+
+ `ssh <username>@juron.fz-juelich.de`
+2. Upon successful login, activate your project environment (more information
+[here](http://www.fz-juelich.de/ias/jsc/EN/Expertise/Supercomputers/NewUsageModel/NewUsageModel_node.html)).
+ Note that the accounting project name is not included. This is because the `CPCP0` and `CPADC` projects
+ do not support accounting.
+
+ `jutil env activate -p <project name>`
+3. Change to the project directory:
+
+ `cd $PROJECT`
+
+You should be in your project directory at this point. As the `CPCP0` and `CPADC` project directories
+are shared amongst many users, it is a good idea to create a personal directory (named after your
+username) withing the project directory. You can then use your personal directory for all your work,
+including cloning this tutorial.
## 3. Cloning the repository
diff --git a/caffe/README.md b/caffe/README.md
index db7976c..dffc7af 100644
--- a/caffe/README.md
+++ b/caffe/README.md
@@ -1,3 +1,8 @@
+**Caution:** Caffe is no longer being actively developed, which is why we prefer not to support
+it as a system-wide module on the supercomputers for long. This is why Caffe is available with
+Python 2 support only on JURECA, while it is not at all supported on JUWELS. The users are advised
+to switch to other frameworks such as Tensorflow/Keras and PyTorch.
+
# Notes
There are three ways in which Caffe can be used,
diff --git a/horovod/README.md b/horovod/README.md
index 3549965..220d40b 100644
--- a/horovod/README.md
+++ b/horovod/README.md
@@ -15,7 +15,8 @@ statements that demonstrate the use of Horovod follow a comment beginning with
**Caution:** Where job submission scripts are available for both Python 2 and Python 3, please
do not submit both Python 2 and Python 3 jobs simultaneously, as one of the jobs might fail. If
-you would like to try both, please run these in tandem.
+you would like to try both, please run these in tandem such that the second job is started only
+after the first is finished.
## Keras samples
--
GitLab