You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Libraries/oneMKL/guided_cuRAND_examples_SYCL_migration/README.md
-43Lines changed: 0 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,49 +87,6 @@ Run the programs on a CPU or GPU. Each sample uses a default device, which in mo
87
87
make run_mt19937_uniform
88
88
```
89
89
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`.
0 commit comments