fogleman

27 ms·

271.
by fogleman 12y ago
Looks pretty good.
272.
The Current State of Open Source Hardware(ryansturmer.com)
2 points by fogleman 12y ago|0 comments
273.
by fogleman 12y ago
Path tracing is extremely parallelizable.
274.
by fogleman 12y ago
I actually tried changing all of my Rays to *Rays, passing pointers instead of values, and it made no significant difference in rendering times.
275.
by fogleman 12y ago
It is.
276.
by fogleman 12y ago
Here he is from another angle: http://i.imgur.com/oOnadne.png
277.
by fogleman 12y ago
Using a k-d tree. The gopher has 50,000 triangles. I'm not currently computing rays/sec.
278.
by fogleman 12y ago
Most of them rendered on the order of ~30 minutes. The gopher I ran overnight, although it really only needed about 2 hours to get really good quality. Keep in mind these durations are for large resolutions.
279.
by fogleman 12y ago
I don't have anything to compare to, but Go seems quite fast. I would guess no worse than 2x C in this case, but I'm pulling that number out of my butt. Actually I was originally going to write this in C but it started to be a PIT
280.
by fogleman 12y ago
It was SO easy! The only tricks were GOMAXPROCS and not using the shared rand functions because they are synchronized.
281.
by fogleman 12y ago
The gopher is loaded from an OBJ file. The floor and back wall are cubes added programmatically.
282.
by fogleman 12y ago
Thank you!
283.
by fogleman 12y ago
It doesn't take 1000, that's just a giant number I put in. You can stop whenever you want (acceptable noise levels) You can also reduce the resolution.
284.
Show HN: I rendered the Go gopher using Go(github.com)
287 points by fogleman 12y ago|48 comments
285.
by fogleman 12y ago
No full resolution examples that I can look at?
286.
Path tracing in Go(github.com)
9 points by fogleman 12y ago|0 comments
287.
by fogleman 12y ago
An open hydraulic system is more lightweight.
288.
by fogleman 12y ago
Can't work out those problems if you don't build a prototype.
289.
by fogleman 12y ago
So, here is my answer to the question, "What do we owe the people who we do not hire?" - Information on where they stand. - An explanation of what they are doing wrong. - Help improving. Things you will neve
290.
My Top 10 Side Projects from 2014(medium.com)
11 points by fogleman 12y ago|1 comments
291.
by fogleman 12y ago
Neil and Buzz spent 2.5 hours walking around on the moon, in a very small region. In comparison, Apollo 17's surface EVA time was 22 hours - driving a lunar rover many miles. Seems like we should be talking to the astronauts in the lat
292.
by fogleman 12y ago
I also used simulated annealing for this problem. But I only added one triangle at a time. http://stackoverflow.com/questions/3848108/reproducing-image... I'll see if I can dig up the code. It's a fun pr
293.
by fogleman 12y ago
This guy did the same thing in 2008: http://rogeralsing.com/2008/12/07/genetic-programming-evolut...
294.
by fogleman 12y ago
I agree that Watson is nothing like a true artificial intelligence. But I do not believe that this means we are unable to create such a thing. I think true AI will be a highly-parallel learning machine, possibly modeled off of something lik
295.
by fogleman 12y ago
Yeah, my solver is pretty basic. Was that puzzle from the website? BTW, love your solver... how did you learn about clingo?
296.
by fogleman 12y ago
Love the game. Just wrote a solver in Python: https://github.com/fogleman/OhHi/blob/master/main.py
297.
by fogleman 12y ago
The video was top-notch, nearly gave me goosebumps.
298.
by fogleman 12y ago
I love databases for the data they contain. And for the ability to make sense of that data more easily when it's in a nice, structured format. I don't care as much for the dev-ops side of it.
299.
by fogleman 12y ago
I've been working on a chess engine. It can already whoop me. https://github.com/fogleman/Chess It's written in C and implements the Universal Chess Interface (UCI) so it works with most chess GUIs. I've
300.
by fogleman 12y ago
Step 1: disable your own Twitter account.

More ›