Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/fogleman/pt
A path tracer written in Go.
https://github.com/fogleman/pt
Last synced: 20 days ago
JSON representation
A path tracer written in Go.
- Host: GitHub
- URL: https://github.com/fogleman/pt
- Owner: fogleman
- License: mit
- Created: 2015-01-23T19:39:29.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2019-03-21T10:07:26.000Z (over 5 years ago)
- Last Synced: 2024-10-01T17:43:21.893Z (about 1 month ago)
- Language: Go
- Size: 1.37 MB
- Stars: 2,077
- Watchers: 61
- Forks: 110
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
- awesome-go - pt - Path tracing engine written in Go. (Images / Search and Analytic Databases)
- awesome-go - pt - Path tracing engine written in Go. Stars:`2.1K`. (Images / Search and Analytic Databases)
- awesome-go - pt - A path tracer written in Go. - ★ 1662 (Images)
- awesome-go-extra - pt - 01-23T19:39:29Z|2019-03-21T10:07:26Z| (Images / Advanced Console UIs)
- awesome-go-zh - pt
- awesome-starred - fogleman/pt - A path tracer written in Go. (others)
README
# pt: a golang path tracer
[](https://travis-ci.org/fogleman/pt) [](https://godoc.org/github.com/fogleman/pt/pt)
This is a CPU-only, unidirectional [path tracing](http://en.wikipedia.org/wiki/Path_tracing) engine written in Go. It has lots of features and a simple API.
---
### Features
* Supports OBJ and STL
* Supports textures, bump maps and normal maps
* Supports raymarching of signed distance fields
* Supports volume rendering from image slices
* Supports various material properties
* Supports configurable depth of field
* Supports iterative rendering
* Supports adaptive sampling and firefly reduction
* Uses k-d trees to accelerate ray intersection tests
* Uses all CPU cores in parallel
* 100% pure Go with no dependencies besides the standard library
### Installation
go get -u github.com/fogleman/pt/pt
### Examples
The are [lots of examples](https://github.com/fogleman/pt/tree/master/examples) to learn from! To try them, just run, e.g.
cd go/src/github.com/fogleman/pt
go run examples/gopher.go
### Optional Embree Acceleration
You can optionally utilize Intel's Embree ray tracing kernels to accelerate triangle mesh intersections. First, install embree on your system: http://embree.github.io/ Then get the `go-embree` wrapper and checkout the `embree` branch of `pt`.
git checkout embree
go get -u github.com/fogleman/go-embree
### Hello World
The following code demonstrates the basics of the API.
```go
package main
import . "github.com/fogleman/pt/pt"
func main() {
// create a scene
scene := Scene{}
// create a material
material := DiffuseMaterial(White)
// add the floor (a plane)
plane := NewPlane(V(0, 0, 0), V(0, 0, 1), material)
scene.Add(plane)
// add the ball (a sphere)
sphere := NewSphere(V(0, 0, 1), 1, material)
scene.Add(sphere)
// add a spherical light source
light := NewSphere(V(0, 0, 5), 1, LightMaterial(White, 8))
scene.Add(light)
// position the camera
camera := LookAt(V(3, 3, 3), V(0, 0, 0.5), V(0, 0, 1), 50)
// render the scene with progressive refinement
sampler := NewSampler(4, 4)
renderer := NewRenderer(&scene, &camera, sampler, 960, 540)
renderer.AdaptiveSamples = 128
renderer.IterativeRender("out%03d.png", 1000)
}
```
### Adaptive Sampling
There are several sampling options that can reduce the amount of time needed to converge to an acceptable noise level. Both images below were rendered in 60 seconds. On the left, no advanced features were enabled. On the right, the features listed below were used.
Here are some of the options that are utilized to achieve this improvement:
- **stratified sampling** - on first intersection, spawn NxN rays in a stratified pattern to ensure well-distributed coverage
- **sample all lights** - at each intersection, sample all lights for direct lighting instead of one random light
- **forced specular reflections** - at each intersection, force both a diffuse and specular bounce and weigh them appropriately
- **adaptive sampling** - spend more time sampling pixels with high variance
- **firefly reduction** - very heavily sample pixels with very high variance
Combining these features results in cleaner, faster renders. The specific parameters that should be used depend greatly on the scene being rendered.
### Links
Here are some resources that I have found useful.
* [WebGL Path Tracing - Evan Wallace](http://madebyevan.com/webgl-path-tracing/)
* [Global Illumination in a Nutshell](http://www.thepolygoners.com/tutorials/GIIntro/GIIntro.htm)
* [Simple Path Tracing - Iñigo Quilez](http://www.iquilezles.org/www/articles/simplepathtracing/simplepathtracing.htm)
* [Realistic Raytracing - Zack Waters](http://web.cs.wpi.edu/~emmanuel/courses/cs563/write_ups/zackw/realistic_raytracing.html)
* [Reflections and Refractions in Ray Tracing - Bram de Greve](http://graphics.stanford.edu/courses/cs148-10-summer/docs/2006--degreve--reflection_refraction.pdf)
* [Better Sampling - Rory Driscoll](http://www.rorydriscoll.com/2009/01/07/better-sampling/)
* [Ray Tracing for Global Illumination - Nelson Max at UC Davis](https://www.youtube.com/playlist?list=PLslgisHe5tBPckSYyKoU3jEA4bqiFmNBJ)
* [Physically Based Rendering - Matt Pharr, Greg Humphreys](http://www.amazon.com/Physically-Based-Rendering-Second-Edition/dp/0123750792)
### Samples
