Update Drivers Further and Update README

Author: mrosoff

ExampleDriverFiles/Spheres/Spheres.txt

@@ -8,7 +8,7 @@ sphere 10000000020 0 0 10000000000 0.3 0.3 0.8
 sphere 0 10000000020 0 10000000000 0.9 0.9 0.9
 sphere 0 0 -10000000020 10000000000 0.3 0.8 0.3
 sphere 0 0 10000000020 10000000000 0.8 0.3 0.3
-sphere -6 -9 -4 2 0.8 0.8 0.8 glass
-sphere -4 -9 3 2 0.8 0.8 0.8 mirror
+sphere 8 -17 -7 3 0.8 0.8 0.8 glass
+sphere 12 -17 5 3 0.8 0.8 0.8 mirror
 model 1.0 0.0 0.0 90 20 5 -20 0 0 ExampleDriverFiles/Spheres/CheckerBoard.obj
 model 0 0 1 90 0.8 7 22.1 0 0 ExampleDriverFiles/Spheres/Light.obj

ExampleDriverFiles/Spheres/SpheresMaterials.mtl

@@ -7,5 +7,5 @@ newmtl darkGreyLambertian
 albedo 0.25 0.25 0.25
 
 newmtl lightSource
-albedo 5 5 5
+albedo 8 8 8
 light

ExampleDriverFiles/Spheres/images/Spheres10.ppm

@@ -2,6 +2,10 @@
 
 An engine built to render complex scenes with all the capabilities of real world private engines. Images are outputted in the PPM format and use a simple driver file system for creation.
 
+## For Ben and Wen
+
+The Two Drivers that I am submitting are Spheres and Mando. Spheres is the simpler of the scenes, I have found that running it with a sample size of 100 results in a reasonable run time of about 5 minutes. The second driver file is actually amazing, but it is incredibly complex to render. I have provided a version titled QuickMando for testing purposes. Running QuickMando with a sample size of 100 results in a run time of about 2 hours. If you run it with 10 samples the image will have significant degredation but will still produce a semi-accurate image with at a reasonable speed. QuickMando has a resolution of 240x135. The regular Mando file is identical but its resolution has been brought up to 1920x1080. I have probed this driver with what limited time I have and have found it to produce images with 100 samples in around a week. The resulting images folders contain the images that are created at various resolutions. I am running the Mando driver file at higher resolutions currently and they will be completed by the end of winter break. If Ross wants the image for his wall, I can provide it to him them. I plan on implementing the bounding box hierarchy at some point over the break, but it didn't make it for this release. It has been fun learning from you and I am sure I will see you around as I am taking 510 next semester. Have a great break!
+
 ## Features
 
 The engine uses a Monte Carlo technique to render images. This process randomly fires rays on contact with Lambertian materials. This creates much more accurate lighting than traditional Ray Tracing. The downside is of course speed. The engine can handle simple Lambertian surfaces, metal surfaces with total reflection, and refractive surfaces such as glass. The engine also produces accurate shadows and highlights and has complex material control.
@@ -16,14 +20,22 @@ Built with:
 
 ## Example Images
 
-Show below are the resulting images when running the engine with the driver "Spheres".
+Shown below are the resulting images when running the engine with the driver "Spheres".
 
 | Number of Samples | Resulting Image |
 | ----------------- | --------------- |
 | 10 Samples | ![10 Samples](./ExampleDriverFiles/Spheres/resultingImages/Spheres10.jpg) |
 | 100 Samples | ![100 Samples](./ExampleDriverFiles/Spheres/resultingImages/Spheres100.jpg) |
 | 1000 Samples | ![1000 Samples](./ExampleDriverFiles/Spheres/resultingImages/Spheres1000.jpg) |
 
+Shown below are the resulting images when running the engine with the driver "Mando".
+
+| Number of Samples | Resulting Image |
+| ----------------- | --------------- |
+| 10 Samples | ![10 Samples](./ExampleDriverFiles/Mando/resultingImages/Mando10.jpg) |
+| 100 Samples | ![100 Samples](./ExampleDriverFiles/Mando/resultingImages/Mando100.jpg) |
+| 1000 Samples | ![1000 Samples](./ExampleDriverFiles/Mando/resultingImages/Mando1000.jpg) |
+
 
 ## Installation