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
{{ message }}
This repository was archived by the owner on Sep 25, 2023. It is now read-only.
While only CUDA versions >= 11.2 are officially supported, cuSignal has been confirmed to work with CUDA version 10.2 and above. If you run into any issues with the conda install, please follow the source installation instructions, below.
@@ -179,7 +179,7 @@ Since the Jetson platform is based on the arm chipset, we need to use an aarch64
where `XX` is your GPU's [compute capability](https://developer.nvidia.com/cuda-gpus#compute). If you'd like to compile to multiple architectures (e.g Nano and Xavier), concatenate the `arch=...` string with semicolins.
184
184
185
185
3. Activate created conda environment
@@ -268,9 +268,9 @@ Since the Jetson platform is based on the arm chipset, we need to use an aarch64
268
268
269
269
### Source, Windows OS
270
270
271
-
We have confirmed that cuSignal successfully builds and runs on Windows by using [CUDA on WSL](https://docs.nvidia.com/cuda/wsl-user-guide/index.html). Please follow the instructions in the link to install WSL 2 and the associated CUDA drivers. You can then proceed to follow the cuSignal source build instructions, below.
271
+
We have confirmed that cuSignal successfully builds and runs on Windows by using [CUDA on WSL](https://docs.nvidia.com/cuda/wsl-user-guide/index.html). Please follow the instructions in the link to install WSL 2 and the associated CUDA drivers. You can then proceed to follow the cuSignal source build instructions, below.
272
272
273
-
1. Download and install [Andaconda](https://www.anaconda.com/distribution/) for Windows. In an Anaconda Prompt, navigate to your checkout of cuSignal.
273
+
1. Download and install [Anaconda](https://www.anaconda.com/distribution/) for Windows. In an Anaconda Prompt, navigate to your checkout of cuSignal.
274
274
275
275
2. Create cuSignal conda environment
276
276
@@ -287,7 +287,7 @@ We have confirmed that cuSignal successfully builds and runs on Windows by using
287
287
pip install cupy-cudaXXX
288
288
```
289
289
290
-
Where XXX is the version of the CUDA toolkit you have installed. 11.5, for example is `cupy-cuda115`. See the [CuPy Documentation](https://docs-cupy.chainer.org/en/stable/install.html#install-cupy) for information on getting Windows wheels for other versions of CUDA.
290
+
Where XXX is the version of the CUDA toolkit you have installed. 11.5, for example is `cupy-cuda115`. See the [CuPy Documentation](https://docs-cupy.chainer.org/en/stable/install.html#install-cupy) for information on getting wheels for other versions of CUDA.
291
291
292
292
5. Install cuSignal module
293
293
@@ -301,7 +301,7 @@ We have confirmed that cuSignal successfully builds and runs on Windows by using
301
301
pip install pytest pytest-benchmark
302
302
pytest
303
303
```
304
-
304
+
305
305
306
306
### Docker - All RAPIDS Libraries, including cuSignal
307
307
@@ -360,7 +360,7 @@ As with the standard pytest tool, the user can use the `-v` and `-k` flags for v
360
360
To reduce columns in benchmark result's table, add `--benchmark-columns=LABELS`, like `--benchmark-columns=min,max,mean`.
361
361
For more information on `pytest-benchmark` please visit the [Usage Guide](https://pytest-benchmark.readthedocs.io/en/latest/usage.html).
362
362
363
-
Parameter `--benchmark-gpu-disable` is to disable memory checks from [Rapids GPU benchmark tool](https://github.com/rapidsai/benchmark).
363
+
Parameter `--benchmark-gpu-disable` is to disable memory checks from [Rapids GPU benchmark tool](https://github.com/rapidsai/benchmark).
364
364
Doing so speeds up benchmarking.
365
365
366
366
If you wish to skip benchmarks of SciPy functions add `-m "not cpu"`
0 commit comments