Presentation feedback

[Gchism94]

Dear Crimson: Below is the score breakdown for your presentation. Details of things that should be updated/revised are provided in separate issues. As you address them, you should close the individual issues.

You can do this in one of two ways:

• On GitHub, by clicking on Close issue
• Via a commit that directly addresses the issue.

Please use the second method wherever a fix can be tied to a commit. If you preface your commit messages with "Fixes", "Fixed", "Fix", "Closed", or "Close", the issue will be closed when you push the changes to your repo. For example, suppose you want to close issue #2 which, hypothetically, suggested that you add a new line to the README, your commit message can say something like Add a new line to the README, closes #2.

Once you've closed all of the other issues, close this one as well, so that going into the presentation you have no open issues remaining.

	Available	Earned
Time management	2	0
Professionalism	2	2
Teamwork	3	3
Slides	3	3
Creativity Critical Thought	3	3
Content - Q1	6	6
Content - Q2	6	5
Total	25	23

Feedback: Time management: Your talk was 2 minutes over the 5 minute limit. Content - Q2: The animation was too fast (slow down the frame rate), and you could have also used fewer colors to highlight specific companies. The axes were rotated in the ridge plot, which is harder to read.

[ArunKoundinya]

Dear Prof,

1. Since it is a bar plot, we would like to retain the different colors as we have annotated the labels using geom_text in bar plots.
2. We will fix the issue by slowing down the frame rate for the animated bar plot in the next git commit.
3. If axes are not rotated, the image looks a little cluttered, so we will be retaining the same structure for last plot.

Thnx, Team