Skip to content

Commit eca610c

Browse files
authored
Update README.md
1 parent ea66271 commit eca610c

File tree

1 file changed

+0
-43
lines changed
  • Libraries/oneMKL/guided_cuRAND_examples_SYCL_migration

1 file changed

+0
-43
lines changed

Libraries/oneMKL/guided_cuRAND_examples_SYCL_migration/README.md

Lines changed: 0 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -87,49 +87,6 @@ Run the programs on a CPU or GPU. Each sample uses a default device, which in mo
8787
make run_mt19937_uniform
8888
```
8989

90-
### Build and Run the `cuRAND Migration` Sample in Intel® DevCloud (Optional)
91-
92-
When running a sample in the Intel® DevCloud, you must specify the compute node (CPU, GPU, FPGA) and whether to run in batch or interactive mode. For more information, see the Intel® oneAPI Base Toolkit [Get Started Guide](https://devcloud.intel.com/oneapi/get_started/).
93-
94-
#### Build and Run Samples in Batch Mode (Optional)
95-
96-
You can submit build and run jobs through a Portable Bash Script (PBS). A job is a script that submitted to PBS through the `qsub` utility. By default, the `qsub` utility does not inherit the current environment variables or your current working directory, so you might need to submit jobs to configure the environment variables. To indicate the correct working directory, you can use either absolute paths or pass the `-d \<dir\>` option to `qsub`.
97-
98-
1. Open a terminal on a Linux* system.
99-
2. Log in to Intel® DevCloud.
100-
```
101-
ssh devcloud
102-
```
103-
3. Download the samples.
104-
```
105-
git clone https://github.com/oneapi-src/oneAPI-samples.git
106-
```
107-
4. Change to the sample directory.
108-
5. Configure the sample for a GPU node and choose the backend as OpenCL.
109-
```
110-
qsub -I -l nodes=1:gpu:ppn=2 -d .
111-
export SYCL_DEVICE_FILTER=opencl:gpu
112-
```
113-
- `-I` (upper case I) requests an interactive session.
114-
- `-l nodes=1:gpu:ppn=2` (lower case L) assigns one full GPU node.
115-
- `-d .` makes the current folder as the working directory for the task.
116-
117-
|Available Nodes |Command Options
118-
|:--- |:---
119-
| GPU |`qsub -l nodes=1:gpu:ppn=2 -d .`
120-
| CPU |`qsub -l nodes=1:xeon:ppn=2 -d .`
121-
122-
6. Perform build steps as you would on Linux.
123-
7. Run the programs.
124-
8. Clean up the project files.
125-
```
126-
make clean
127-
```
128-
9. Disconnect from the Intel® DevCloud.
129-
```
130-
exit
131-
```
132-
13390
## Example Output
13491

13592
This is example output if you built the default and ran `run_mt19937_uniform`.

0 commit comments

Comments
 (0)