Update README.md

Deformation is limited to bouncing along each side without rotation, simplifying data structure design to be able to cache points of deformation where the object collides on its side and then deforms and reforms by updating the translation of individual points. This runs in O(V) time on initial calculation which is done in preprocessing, but only a fraction of that time when doing actual deformation. The amount of deformation scales with the speed of impact.

We have two separate files that we are currently working with: [GraphicsAndWindowTest](https://agile.bu.edu/gitlab/ec504/ec504_projects/group2/-/blob/master/src/main/java/org/example/newmat/GraphicsAndWindowsTest.java?ref_type=heads) and [MillionTriangles](https://agile.bu.edu/gitlab/ec504/ec504_projects/group2/-/blob/master/src/main/java/org/example/newmat/MillionTriangle.java?ref_type=heads). The reason we have the split is to demonstrate the different portions of our project working where it is easier to see individual parts. 

We have two separate files that we are currently working with: [GraphicsAndWindowTest](https://agile.bu.edu/gitlab/ec504/ec504_projects/group2/-/blob/master/src/main/java/org/example/newmat/GraphicsAndWindowsTest.java?ref_type=heads) and [MainScene](https://agile.bu.edu/gitlab/ec504/ec504_projects/group2/-/blob/master/src/main/java/org/example/newmat/MainScene.java?ref_type=heads).

[MillionTriangles.java](https://agile.bu.edu/gitlab/ec504/ec504_projects/group2/-/blob/master/src/main/java/org/example/newmat/MillionTriangle.java?ref_type=heads) is essentially an updated version of the minimum requirements where we have a physics engine with proper deformation and user input working on a single shape with at least 1 fps on the lab computers.

[MainScene](https://agile.bu.edu/gitlab/ec504/ec504_projects/group2/-/blob/master/src/main/java/org/example/newmat/MainScene.java?ref_type=heads) is the UI of our project which allows the user to configure the three runable figures from preset options, use commandline arguments, or provide an image from their file system. It also allows for the number of obstacles to be set. There are two types, one type is immovable, and the other type is the game obstacle which disappears on collision. This menu allows you to launch [GraphicsAndWindowTest.java](https://agile.bu.edu/gitlab/ec504/ec504_projects/group2/-/blob/master/src/main/java/org/example/newmat/GraphicsAndWindowsTest.java?ref_type=heads).

[GraphicsAndWindowTest.java](https://agile.bu.edu/gitlab/ec504/ec504_projects/group2/-/blob/master/src/main/java/org/example/newmat/GraphicsAndWindowsTest.java?ref_type=heads)  is the game version of our code which has multiple objects able to run with solid obstacles and also removable obstacles which are used in the game. Essentially the shapes can be bounced by clicking and dragging on the xy axis and using W/S keys on the keyboard to move the shape on the z axis. The camera can be turned using the arrow keys. When the shapes hit orange obstacles, they bounce off and if they hit green obstacles, the obstacles are consumed and the score counter in the upper corner goes up. In so doing we demonstrate all the features together in this test as the game. However, for this file, we recommend using our teapot objects which we document in the install section because we are able to run this with a higher frame count. It will be optimized by the final report in two weeks.

- Wrote commandline parser for the first object and read in of file

- Implemented lighting and environment

- Wrote auxiliary program to convert .obj files to the proper format

- Added in file path functionality to the main menu

- Co-created UI menu to allow the user to modify aspects of the application

### Louis

- Minimum requirement bouncing figure of a million triangles that bounces at 1 fps

- Created the 100 obstacles and modified them to fit our game

- Created visible normalized window

- Normalized Coordinates

- Co-created UI menu to allow the user to modify aspects of the application

### Sergio

- Java Documentation