Skip to content

Commit 635d3a0

Browse files
authored
Update sharc.md
1 parent 1cd07b7 commit 635d3a0

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

education/sheffield_onedaycuda/sharc.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,11 @@ If you are connecting from a machine which is your own (i.e. not a CICS managed
2323

2424
[http://docs.hpc.shef.ac.uk/en/latest/hpc/getting-started.html](http://docs.hpc.shef.ac.uk/en/latest/hpc/getting-started.html).
2525

26-
Once you are logged into a ShARC head node then request an interactive session by typing `qrshx`. This creates an interactive session on a CPU worker node which supports running graphical applications as well as command line programs. The worker node **will not** be a GPU accelerated node and **cannot** be used to execute CUDA applications. The worker node can however be used for CUDA compilation, interactive editing of our GPU code and submission of jobs to a GPU accelerated worker. This is a much better solution than running an interactive session on a GPU node as interactive jobs will request GPU resource which will be unused if you are performing tasks like modifying or building your code.
26+
Once you are logged into a ShARC head node then request an interactive session by typing
27+
28+
qrshx
29+
30+
This creates an interactive session on a CPU worker node which supports running graphical applications as well as command line programs. The worker node **will not** be a GPU accelerated node and **cannot** be used to execute CUDA applications. The worker node can however be used for CUDA compilation, interactive editing of our GPU code and submission of jobs to a GPU accelerated worker. This is a much better solution than running an interactive session on a GPU node as interactive jobs will request GPU resource which will be unused if you are performing tasks like modifying or building your code.
2731

2832
## Configuring the CPU worker node ##
2933

@@ -55,7 +59,11 @@ From your interactive session on the CPU worker node get the *"hello world for G
5559

5660
git clone https://github.com/RSE-Sheffield/CUDAHelloWorld.git
5761

58-
This will check out the hello world example into the folder `CUDAHelloWorld`. Take a look at the contents of this file in the console using `nano` e.g.
62+
This will check out the hello world example into the folder `CUDAHelloWorld`. Change directory to this folder. e.g.
63+
64+
cd CUDAHellowWorld
65+
66+
Take a look at the contents of this file in the console using `nano` e.g.
5967

6068
nano helloworld.cu
6169

@@ -124,7 +132,7 @@ Before moving onto the [first lab classes](../lab01) for day 1, try modifying th
124132

125133
You can now launch your kernel using these dim variables.
126134

127-
helloworld<<<grid, block>>>();
135+
hello_kernel<<<grid, block>>>();
128136

129137
To view the y and z index of the thread or the block use the y and z member variables of the `threadIdx` or `blockIdx` dims.
130138

0 commit comments

Comments
 (0)