|
|
(68 intermediate revisions by 3 users not shown) |
Line 1: |
Line 1: |
− | {{GPU610/DPS915 Index | 20181}}
| |
− | = Project Name Goes here =
| |
− | == Team Members ==
| |
− | # [mailto:aminassian@myseneca.ca?subject=dps915 Alek Minassian], Some responsibility
| |
− | # [mailto:achowdhury17@myseneca.ca?subject=dps915 Ariquddowla Chowdhury], Some other responsibility
| |
− | # [mailto:ayeung24@myseneca.ca?subject=dps915 Alfred Yeung], Some other responsibility
| |
− | [mailto:aminassian@myseneca.ca;achowdhury17@myseneca.ca;ayeung24@myseneca.ca Email All]
| |
| | | |
− | == Assignment 1 ==
| |
− | === Creating ray-traced images by Alek Minassian ===
| |
− | This is an open-source program available from [http://cosinekitty.com/raytrace/chapter05_cpp_code.html here]. This program can be built and run on both Windows and Linux. A copy of the source code in ZIP format is available in the section below as well as instructions for building and running. The program works by creating one or more objects and placing them on a "Scene". It then adds one or more light sources and traces them as they reflect off or refract through objects. As an example, the following chessboard is generated as follows:
| |
− | *A chessboard is created, rotated, and added to the scene.
| |
− | *Three spheres are created and added to the scene.
| |
− | *Three light sources are added.
| |
− | *Finally, the new image is saved.
| |
− |
| |
− | [[File:Chessboard.png]]
| |
− |
| |
− | ==== Downloading the source code ====
| |
− | A modified version of the project is available from [[Media:Raytrace.a1.zip | here]]. The following modifications were made:
| |
− | *The raytrace/raytrace/build file used for building on Linux is modified to enable profiling as well as using version 7.2.0 of g++ on Matrix.
| |
− | *The raytrace/raytrace/profile.sh file is added to run the program and create a flat profile and call graph.
| |
− | *The Visual Studio solution raytrace/raytrace.sln is upgraded to Visual Studio 2017.
| |
− | *Some code has been added to scene.cpp in order to report the time spent in certain parts of the code. This is so that we can get a more granular timing than what is available through profiling.
| |
− |
| |
− | ==== Building and running on Windows ====
| |
− |
| |
− | ==== Building and running on Linux (Matrix) ====
| |
− |
| |
− | == Assignment 2 ==
| |
− | == Assignment 3 ==
| |