I wrote these instructions as part of "installing PyTorch with CUDA 12.1.1".
Anyway, if you still need to compile from source… here's how:
This is a dependency of PyTorch, which is sensitive to CUDA version.
Clone Magma:
""" | |
Extract the contents of a `run-{id}.wandb` database file. | |
These database files are stored in a custom binary format. Namely, the database | |
is a sequence of wandb 'records' (each representing a logging event of some | |
type, including compute stats, program outputs, experimental metrics, wandb | |
telemetry, and various other things). Within these records, some data values | |
are encoded with json. Each record is encoded with protobuf and stored over one | |
or more blocks in a LevelDB log. The result is the binary .wandb database file. |
#!/bin/bash | |
# Downloads and applies a patch from Drupal.org. | |
if [ -z "$1" ] | |
then | |
echo "You need to supply a URL to a patch file." | |
exit | |
fi | |
URL=$1; |
; /usr/share/pulseaudio/alsa-mixer/profile-sets/astro-a50-gen4.conf | |
[General] | |
auto-profiles = yes | |
[Mapping analog-voice] | |
description = Voice | |
device-strings = hw:%f,0,0 | |
channel-map = left,right | |
paths-output = steelseries-arctis-output-chat-common |
git clone https://git.videolan.org/git/ffmpeg/nv-codec-headers.git | |
cd nv-codec-headers | |
vi Makefile # change the first line to PREFIX = ${CONDA_PREFIX} | |
make install | |
cd .. | |
git clone https://git.ffmpeg.org/ffmpeg.git | |
cd ffmpeg | |
git checkout n4.2.2 | |
conda install nasm |
I wrote these instructions as part of "installing PyTorch with CUDA 12.1.1".
Anyway, if you still need to compile from source… here's how:
This is a dependency of PyTorch, which is sensitive to CUDA version.
Clone Magma:
""" | |
Creates an HDF5 file with a single dataset of shape (channels, n), | |
filled with random numbers. | |
Writing to the different channels (rows) is parallelized using MPI. | |
Usage: | |
mpirun -np 8 python demo.py | |
Small shell script to run timings with different numbers of MPI processes: |
#One workaround is to create clone environment, and then remove original one: | |
#(remember about deactivating current environment with deactivate on Windows and source deactivate on macOS/Linux) | |
conda create --name new_name --clone old_name --offline #use --offline flag to disable the redownload of all your packages | |
conda remove --name old_name --all # or its alias: `conda env remove --name old_name` | |
#There are several drawbacks of this method: | |
# time consumed on copying environment's files, | |
# temporary double disk usage. |
'use strict'; | |
////////////////////////////////// | |
// How to use? | |
// 1. Create `sequelize-schema-file-generator.js` in your app root | |
// 2. Make sure you've ran the `sequelize init` before (It should create `config`,`seeders`,`migrations` folders). | |
// 3. Update `DATABASE_DSN` below to match your connection string (works with any database adapter that Sequelize supports) | |
// 4. Run it with `node sequelize-schema-file-generator.js` | |
// 5. Review the generated migrations inside of the `migrations` folder. | |
////////////////////////////////// |
Updated 4/11/2018
Here's my experience of installing the NVIDIA CUDA kit 9.0 on a fresh install of Ubuntu Desktop 16.04.4 LTS.