paths

The approach is just - Trace random paths from light sources until they terminate (usually decided with Russian roulette).

Bidirectional path tracing is one way of sampling paths (actually it combines many techniques for sampling paths and weights those using something called Multiple Importance Sampling).

That would mean at least four perfect paths for me, maybe more.

Thanks for giving the name; I wanted to describe why connecting two paths works.

This process is called Next Event Estimation and we can combine both 'accidental' paths and 'connected' paths by using a technique called Multiple Importance Sampling (MIS).

- Trace random paths from the camera (usually N per pixel, or you can use more paths in noisy areas) until they terminate.

If you mount your working directory exactly like on your host machine, you can even use relative paths in your Dockerfile.

My guess is it's a combo of string processing, many temp objects, etc with too many interpreted versus JIT'd code paths.

It's in all our critical real-time code paths that bring up candidates while you're typing.

It's worth noting that in Bostrom's Superintelligence, biology is included among potential paths to superintelligence.

Another issue: If we are calculating on a per pixel basis, that means bundling multiple paths together to figure out what the weighted return will look like.

My observation is that the refactor step implicitly allows new untested code paths.

Bidirectional path tracing doesn't do anything clever to "try to connect" paths from light sources and cameras.

Symlinks create the basic structure of what the "default" paths should be for a given application, and an alternate path can always be specified manually to call a different version.

If one could choose their Tor link to include enough paths not likely to be monitored by colluding parties, then one could be more certain they are not facing a "global adversary" in the sense that the Tor site means.