This is an interactive extension of a visualisation I developed for an invited talk at the FAI seminar series at University College London. It is built using Svelte, D3.js, and ml-matrix.
There are plenty of other Gaussian process visualisations out there; here are some I came across so far (if you know of others you like, please let me know!):
- A Visual Exploration of Gaussian Processes (distill.pub) (source, using D3.js, ml-matrix)
- Demo by Nicolas Durrande (source, using R and Shiny)
- Demo by Johan Wågberg (source, using D3.js, Numeric.js)
- Demo by Tomi Peltola (source, using React, D3.js, Numeric.js)
- Demo by Chi Feng (source, using dat.gui, jQuery)
- Demo by Alex Y. Chan (source, using D3.js, math.js)
- Demo by Artem Artemev, run locally (source, using Python, GPflow, holoviews/bokeh)
Install the dependencies...
# cd into this directory
npm install
...then start Rollup:
npm run dev
Navigate to localhost:5000. You should see your app running. Edit a component file in src
, save it, and reload the page to see your changes.
By default, the server will only respond to requests from localhost. To allow connections from other computers, edit the sirv
commands in package.json to include the option --host 0.0.0.0
.
If you're using Visual Studio Code we recommend installing the official extension Svelte for VS Code. If you are using other editors you may need to install a plugin in order to get syntax highlighting and intellisense.
This repository is set up to use TypeScript. Run the checks with
npx svelte-check
This repository is set up to use Prettier. Before committing code, run
npx prettier -w src
To create an optimised version of the app:
npm run build
You can run the newly built app with npm run start
. This uses sirv, which is included in your package.json's dependencies
so that the app will work when you deploy to platforms like Heroku.
By default, sirv will only respond to requests that match files in public
. This is to maximise compatibility with static fileservers, allowing you to deploy your app anywhere.
If you're building a single-page app (SPA) with multiple routes, sirv needs to be able to respond to requests for any path. You can make it so by editing the "start"
command in package.json:
"start": "sirv public --single"
With Vercel
Install vercel
if you haven't already:
npm install -g vercel
Then, from within your project folder:
cd public
vercel deploy --name my-project
With surge
Install surge
if you haven't already:
npm install -g surge
Then, from within your project folder:
npm run build
surge public my-project.surge.sh