For a version without the collapsible details sections (so you can search the whole thing in your browser), click here.
using UnityEngine; | |
using Unity.Collections; | |
using Unity.Audio; | |
using Unity.Mathematics; | |
using Unity.Burst; | |
using System.Collections; | |
/* | |
For allocations inside AudioKernels, use Allocator.AudioKernel | |
*/ |
The optimisation algorithm used in most of DeepMind's deep RL papers is RMSProp (e.g in the Mnih et al Atari paper, in the IMPALA paper, in the RL experiments of the PBT paper, in the Zambaldi et al paper). I have seen speculation online that this is because RMSProp may be well-suited to deep learning on non-stationary distributions. In this note I try to examine the RMSProp algorithm and specifically the significance of the epsilon
hyperparameter. The references are
- Karpathy's CS231n notes
- Hinton's lecture notes
- The deep learning textbook Chapter 8
Often in the literature RMSProp is presented as a variation of AdaGrad (e.g. in the deep learning textbook and in Karpathy's class). However, I think this is misleading, and that the explanation in Hinton's lecture is (not surprisingl
A. Checkout the developer version of JUCE
git clone -b develop https://github.com/WeAreROLI/JUCE.git
(For consequent updadets, you just need to)
git checkout develop; git fetch; git pull
B. Build Projucer, where JUCE is the root of your clone
xcodebuild -project JUCE/extras/Projucer/Builds/MacOSX/Projucer.xcodeproj
b. Optionally build DemoRunner and AudioPluginHost
GTD/BASB Templates for Emacs and Org-Mode
- Daily Review Template
- Weekly Review Template
- Monthly Review Template
- Annual Review Template (I don’t usually do these in Emacs, but I’ve included them for the sake of completeness)
As I’ve said on Twitter, I don’t actually necessarily perform these on a chronological basis.
written in December 2018.
The practical development of deep learning and its associated infrastructure has initiated a broad re-examination of the practice of computer programming. In this document we briefly survey how this discussion has evolved over the past few years, and then describe our point of view on the underlying mathematics.
We begin with some appeals to authority, in the form of the following references:
from IPython.display import HTML | |
# Youtube | |
HTML('<iframe width="560" height="315" src="https://www.youtube.com/embed/S_f2qV2_U00?rel=0&controls=0&showinfo=0" frameborder="0" allowfullscreen></iframe>') | |
# Vimeo | |
HTML('<iframe src="https://player.vimeo.com/video/26763844?title=0&byline=0&portrait=0" width="700" height="394" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe><p><a href="https://vimeo.com/26763844">BAXTER DURY - CLAIRE (Dir Cut)</a> from <a href="https://vimeo.com/dannysangra">Danny Sangra</a> on <a href="https://vimeo.com">Vimeo</a>.</p>') |
While it's possible to download packages and install them manually, it's such a hassle. Fortunately for us, OS X has an unofficial package manager called http://brew.sh Let's install it. Open you Terminal and paste the following code:
ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
Great. Homebrew will automatically install packages to /usr/local. Conveniently, that directory is already in your include and link paths.
It's not immediately obvious how to pull down the code for a PR and test it locally. But it's pretty easy. (This assumes you have a remote for the main repo named upstream
.)
Getting the PR code
-
Make note of the PR number. For example, Rod's latest is PR #37: Psiphon-Labs/psiphon-tunnel-core#37
-
Fetch the PR's pseudo-branch (or bookmark or rev pointer whatever the word is), and give it a local branch name. Here we'll name it
pr37
:
$ git fetch upstream pull/37/head:pr37