Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |
| projects:fart [2019/02/26 18:59] – Update build instructions josh | projects:fart [2019/02/27 16:26] (current) – add name clarification josh |
|---|
| ====== Description ====== | ====== Description ====== |
| |
| FART was my semester project for the Computer Science 658 class at Grand Valley State University. My goal is for FART to be a distributed, object-oriented raytracer. The name is a [[wp>Recursive_acronym|recursive acronym]] similar to GNU or LAME. | FART was my semester project for the Computer Science 658 class at Grand Valley State University. My goal is for FART to be a distributed, object-oriented raytracer. The name is a [[wp>Recursive_acronym|recursive acronym]] taking inspiration from [[http://lame.sourceforge.net/about.php|LAME]]. It stands for Fart Ain't a RayTracer. |
| |
| FART takes as input a scene-description file in an ASCII-based, hierarchical input file format. After the scene file is parsed, it will be raytraced (rendered) according to the render options. Some of these options can be specified on the command line and others can be specified in the scene description file. When a given option can be specified both places, the command-line options will override what is in the scene file. | FART takes as input a scene-description file in an ASCII-based, hierarchical input file format. After the scene file is parsed, it will be raytraced (rendered) according to the render options. Some of these options can be specified on the command line and others can be specified in the scene description file. When a given option can be specified both places, the command-line options will override what is in the scene file. |
