karawoo / 2015-04-27-wsu Goto Github PK

We should add information about accessibility to the website, something along the lines of carpentries/workshop-template#160.

Unfortunately the building we will be in is highly inaccessible - no elevators, accessible restrooms, or accessible parking. I'm going to look into what other kinds of accessibility accommodations we can make available. I'm happy to give rides to/from the front door of the building, though this probably will not help people who use wheelchairs or otherwise can't climb stairs. I think it would be possible to create lactation facilities -- IIRC the room we'll be in has a sink and fridge and some smaller adjoining rooms that could be used. I'm trying to get access to the room to double check this. Large print handouts should be no problem. I'll contact the Access Center at WSU and our hosts to see what else we might be able to provide and then send a PR adding all the info to the website.

We're planning to do a capstone exercise similar to the one Naupaka used at iPlant. I propose something like this:

Capstone exercise

Using an Rmd file, create a short analysis report using R of the gapminder dataset.

1. Pick three countries you are interested in
2. Write an Rmd script to load the gapminder data file, select all the data for that country (hint, use the filter() function), and use ggplot to make a three scatter plots (one for each country) that has year on the x-axis and GDP on the y axis. Make sure you load all the libraries you might need (dplyr, ggplot2, etc). Describe any trends you see for each country using markdown text.
3. Commit the changes to your .Rmd file using git.
4. For the year 2007, calculate the mean, min, and max life expectancies for each continent. Describe what you see in the results using markdown text.
5. Commit your changes using git and push them to GitHub.
6. Make 2 histograms of global life expectancy using ggplot. One with the default bin widths and one with narrower bin widths. Explain the differences and any interesting trends in markdown text.
7. Commit your changes and push them to GitHub.
8. Compile the final .Rmd file to HTML, make sure it looks ok, and then commit this HTML file (plus figures) and push everything to GitHub.

Comments and suggestions are very welcome.

Hi @karawoo !

I'm teaching a git lesson at the Data Carpentry event here in portland, and i wanted to start by merging the we lesson you and Karl taught in Pullman. I know that this repo creates the github pages, and i'm just having a little trouble finding where the lesson is. I remember you had slides that rendered in the browser? If you could just help orient me, i can work from there.

Thanks!

Last weekend Greg helpfully fixed the issue that was causing our syllabus/index.html page to be formatted incorrectly. I have been trying to get the lesson pages formatted to match those of the standard Software Carpentry lessons (like this) by modifying the makefile from that repo, but I don't actually know how to use make and can't figure this out, even when I try moving all the lessons/tools/etc. to the root of the repository. Right now if I run knit2html() on the RMarkdown files we get HTML that looks like this:

This isn't as nice, especially with the {.objectives} showing up, but is it good enough, @kbroman? I'm inclined to say yes because I can't bear the thought of fighting with the formatting any longer. I'd like to have the HTML pages available to teach from and for any learners who might need to use assistive devices.

If this is ok then I will put together a pull request with an updated syllabus/index.md, rendered lessons, and a page for the capstone exercise.

Something has gone wrong with the formatting of the website. At least when I view it the margins are messed up and the setup instructions are no longer sorted into columns. I don't know why this is happening but will look into it...if any of you spot what's causing this please let me know.

We can grab the gapminder data from the gapminder package as follows:

if(!require(gapminder)) {
    install.packages("gapminder")
    library(gapminder)
}
write.csv(gapminder, "gapminder.csv", row.names=FALSE)

But where should I put the file?

@karawoo added a link to the dplyr cheat sheet at the end of the relevant lesson. Should do the same for

• ggplot
• unix
• git
• Rmarkdown

See Issue #16.

Perhaps end each with a section of general resources, including books.

The softlink, /syllabus/css → /css didn't work.

We could move all of the lessons to the root directory or try to get the links to css stuff to point one directory back, but it'd be easiest to just make a copy of the css stuff, so I'm going to do that. Not ideal, but let's just get this done.

It might be good to identify or create cheat sheets for each part, and maybe bring copies for all of the students.

RStudio has a bunch of good ones:

• dplyr
• ggplot2
• R Markdown

Also need

• unix
• git