HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Dalamar42
rayt
Rust2020–2020
Dalamar42 / rayt

rayt

Monte Carlo ray tracer developed using Rust

2Distinct people
2Mentions
1Explicit recommenders
184GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Monte Carlo ray tracer developed using Rust

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

The author is actually preferentially sending samples towards "attractors" [0] for lights and dielectrics. Doing so massively reduces variance. My favorite example is Figure 5…

boulos used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2020-04-19 11:48:58 UTC to 2020-04-20 05:43:01 UTC.

012020-04-19 11:00:00 UTC to 2020-04-19 12:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 19, 11:002020-04-19 12:00:00 UTC to 2020-04-19 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 13:00:00 UTC to 2020-04-19 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 14:00:00 UTC to 2020-04-19 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 15:00:00 UTC to 2020-04-19 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 16:00:00 UTC to 2020-04-19 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 17:00:00 UTC to 2020-04-19 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 18:00:00 UTC to 2020-04-19 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 19:00:00 UTC to 2020-04-19 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 20:00:00 UTC to 2020-04-19 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 19, 20:002020-04-19 21:00:00 UTC to 2020-04-19 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 22:00:00 UTC to 2020-04-19 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-19 23:00:00 UTC to 2020-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-20 00:00:00 UTC to 2020-04-20 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-20 01:00:00 UTC to 2020-04-20 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-20 02:00:00 UTC to 2020-04-20 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-20 03:00:00 UTC to 2020-04-20 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-20 04:00:00 UTC to 2020-04-20 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-20 05:00:00 UTC to 2020-04-20 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 20, 05:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 19, 11:002020-04-19 11:00:00 UTC2020-04-19 12:00:00 UTC110
Apr 19, 12:002020-04-19 12:00:00 UTC2020-04-19 13:00:00 UTC000
Apr 19, 13:002020-04-19 13:00:00 UTC2020-04-19 14:00:00 UTC000
Apr 19, 14:002020-04-19 14:00:00 UTC2020-04-19 15:00:00 UTC000
Apr 19, 15:002020-04-19 15:00:00 UTC2020-04-19 16:00:00 UTC000
Apr 19, 16:002020-04-19 16:00:00 UTC2020-04-19 17:00:00 UTC000
Apr 19, 17:002020-04-19 17:00:00 UTC2020-04-19 18:00:00 UTC000
Apr 19, 18:002020-04-19 18:00:00 UTC2020-04-19 19:00:00 UTC000
Apr 19, 19:002020-04-19 19:00:00 UTC2020-04-19 20:00:00 UTC000
Apr 19, 20:002020-04-19 20:00:00 UTC2020-04-19 21:00:00 UTC000
Apr 19, 21:002020-04-19 21:00:00 UTC2020-04-19 22:00:00 UTC000
Apr 19, 22:002020-04-19 22:00:00 UTC2020-04-19 23:00:00 UTC000
Apr 19, 23:002020-04-19 23:00:00 UTC2020-04-20 00:00:00 UTC000
Apr 20, 00:002020-04-20 00:00:00 UTC2020-04-20 01:00:00 UTC000
Apr 20, 01:002020-04-20 01:00:00 UTC2020-04-20 02:00:00 UTC000
Apr 20, 02:002020-04-20 02:00:00 UTC2020-04-20 03:00:00 UTC000
Apr 20, 03:002020-04-20 03:00:00 UTC2020-04-20 04:00:00 UTC000
Apr 20, 04:002020-04-20 04:00:00 UTC2020-04-20 05:00:00 UTC000
Apr 20, 05:002020-04-20 05:00:00 UTC2020-04-20 06:00:00 UTC101

What Hacker News says

2 sources
boulos·Apr 20, 2020Recommendation phrase
The author is actually preferentially sending samples towards "attractors" [0] for lights and dielectrics. Doing so massively reduces variance. My favorite example is Figure 5 in this old paper [1] (I've never actually read Pete's ray tracing in a weekend, so I don't know if this is in there). The most common variance reduction technique though would be to do direct lighting (aka "next event estimation" if you want to be overly pedantic). Your lighting in that image looks like it's just a "Hi, I happen to be emitting tons of energy" sphere in space, which will cause a lot of noise. Alternatively, if you are sampling it, you are likely not sampling the sphere as well as you could. You'll want to sample the sphere following the setup in Figure 2 in Pete's "Direct Lighting" paper [2] (which as a reminder, is currently accessible at the ACM d
Read the rest
In Show HN: Monte Carlo ray tracer in Rust

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.