glenn-mcguinness
commented
6 years ago The assignment said to do at least three tasks, not all six. The relevant quote is below. You can find it in the assignment, under the heading "The Assignment" and the sub-heading "Your mission, high-level".
Pick at least three of the tasks below (in the “Task menu” section) and attack each with a table and figure. For each table, make sure to include a relevant figure! Note that:
I picked tasks 4, 5, and 6 for my three tasks.
Was I incorrect and should have done all of the tasks instead of just three?
README
task-1. Get the maximum and minimum of GDP per capita for all continents.
task-2. Look at the spread of GDP per capita within the continents.
task-3. Compute a trimmed mean of life expectancy for different years. Or a weighted mean, weighting by population. Just try something other than the plain vanilla mean.
task-4. How is life expectancy changing over time on different continents?
task-5. Report the absolute and/or relative abundance of countries with low life expectancy over time by continent: Compute some measure of worldwide life expectancy – you decide – a mean or median or some other quantile or perhaps your current age. Then determine how many countries on each continent have a life expectancy less than this benchmark, for each year.
lessThanMedianwas a great idea.task-6. Find countries with interesting stories. Open-ended and, therefore, hard. Promising but unsuccessful attempts are encouraged. This will generate interesting questions to follow up on in class.
But I want to do more!: In this section, I can't find the use of "figure side-by-side" (there are other methods other than faceting) and "there are some really nice fancy table helper packages".
General comments:
I do not find where you addressed task 1,2,3. Can you point me if you have done?
I think you wrote more discussion than coding. Instead you could write concise summary of results and could spend some time to address other tasks like task 1,2,3.
Your coding and plotting strategies were great. You could put great effort to interpret the results and commenting codes.
In chuck/Inline comments people generally avoid to explain "what" the code does because. Instead they use "why" comments. Comments may not explained what the code does, which is information that the code already contains.
I found using some of options of Code Chunks is very handy for example, cache, include, fig.cap, message etc. You can have a look.