DiffSharp - Development Guide

You can clone this repository to your machine as follows:

git clone --branch dev https://github.com/DiffSharp/DiffSharp.git
cd DiffSharp

Run tests

Required:

Install .NET Core SDK for your system

Use the following command in the root directory of this repository:

dotnet test

Build DiffSharp in Docker

Required:

Install Docker for your system

Build a Docker image called diffsharp. This will work without any local .NET Core installation and build DiffSharp inside the image.

docker build -t diffsharp .

Use the following to instantiate a Docker container from the diffsharp image and run the tests inside:

docker run --rm diffsharp dotnet test

Building against locally built TorchSharp packages

To add features you may have extend TorchSharp to make extra features of LibTorch available.

The build is set up to look for a parallel build of TorchSharp, e.g.

C:\GitHub\dsyme\DiffSharp
C:\GitHub\dsyme\TorchSharp

To build, test and pack TorchSharp in that repo do this:

.\build build
.\build test
.\build pack

You will see something like this

Successfully created package 'C:\GitHub\dsyme\TorchSharp\bin/packages/Debug/TorchSharp.0.3.0-local-Debug-20200520.nupkg'.
Successfully created package 'C:\GitHub\dsyme\TorchSharp\bin/packages/Debug/LibTorch.Redist.0.3.0-local-Debug-20200520.nupkg'.

with warning:

warning : Packages will be incomplete and unusable on other platforms...

To consume the packages into DiffSharp adjust TorchSharpVersion in Directory.Build.props.

When rebuilding the TorchSharp you will need to clear your package cache to pick up the new nuget package with the same version id, e.g.

rmdir /q /s %USERPROFILE%\.nuget\packages\torchsharp
rmdir /q /s %USERPROFILE%\.nuget\packages\LibTorch.Redist
dotnet restore

The LibTorch packages are quite large and you may need to watch disk space.

The Reference Backend

The "Reference" backend defines the semantics we expect of the Torch backend.

Sometimes configurations of Torch expose small differences in semantics (e.g. when using CUDA, or functionality not suppored for integer tensors). We generally seek to paper over those cracks by working around the problems in the Torch backend.

Developing and Testing on GPU

By default in-branch testing is only done on CPU. To enable on GPU/CUDA you must:

Make sure you have a device eligible for CUDA 11.1 and all device drivers installed (e.g. install the appropriate NVIDIA CUDA SDK)
Manually enable Torch CUDA binaries in DiffSharp.Tests.fsproj or set the DIFFSHARP_TESTGPU environment variable to true (e.g. dotnet test /p:DIFFSHARP_TESTGPU=true)
Verify that dsharp.isCudaEnabled() is returning true and GPU testing is enabled in TestUtil.fs.

Micro Performance Benchmarking

Python numbers must be collected in a separate run, they are currently injected back into source code (ugh) to get figures in one report. There are better ways to do this.

To update Python benchmarks on your machine (note, writes back results into source code)

dotnet run --project tests\DiffSharp.Benchmarks.Python\DiffSharp.Benchmarks.Python.fsproj -c Release --filter "*"

This takes a while to run.

To run benchmarks:

dotnet run --project tests\DiffSharp.Benchmarks\DiffSharp.Benchmarks.fsproj -c Release --filter "*"

To filter etc., see --help

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!