final review comments and suggestions

[aaronsadholz]

This is not an issue exactly, but wanted to post a few things after taking a pass through the project this morning.

• Interactive component:

  • @valmikkpatel The readme is from an old project, it should be updated or removed
  • I think we should add a link to where it is posted in our repo, and in our report.
  • I don't know how to view the most up to date version, but maybe it should include citations and a link to our project repo.

• There are still typos. Probably should take another look through our own sections, making sure to paste into something like word which checks for grammar and spelling.

• We need to remember to make our repo public when we submit, and should include a link to it in the report.

• I wasn't able to use the use the make commands that @edublancas added in the updated readme. I tried a few different things and got different errors. Maybe we can go over this in our meeting today.

• Executive summary:

  • @edublancas Do you think it makes sense to add a visualization to supplement your text?
  • @jose-alvarado-guzman the executive summary is intended to be function independently and be friendly for non technical people. Do you think its possible to rephrase without using terminology like "AFFIN, bing and nrc?"

[edublancas]

I can make it public now so we don't forget.

The instructions say that the executive summary needs to be 2 pages, my graphs are pretty big, that's why i decided not to include any, but maybe i should

[edublancas]

• Just made the repo public
• Added link to repo at the beggining of the report
• Fixed all the typos i could find
• Updated makefile