Mini-project Goals

Your team is here to practice, and we are here as coaches. In the time scheduled for “data2doc”, your team should aim to achieve the following goals:

  • Collaborate on a GitHub repository.
  • Introduce your team via a README (Tuesday AM).
  • Script a reproducible “data-to-document” pipeline.
  • Present mini-results (Friday PM).

Practice #1: Tuesday AM

  1. Choose a git captain, and
    1. (Captain) create a GitHub repo,
    2. (Captain) invite collaborators, and
    3. (Teammates) accept invitation.
  2. (Captain) Create a ‘Rproj’ and a skeleton
  3. Clone the repo as a new RStudio project.
  4. Complete one section of and push to GitHub.

Practice #2: Tuesday PM

  1. Discuss your data:
    1. Are your data in tidy tables?
    2. Can you define relationships between tables?
    3. How will you share it within the team?
  2. Read data into R and prepare it for a simple analyis or visualization.
  3. Update the on GitHub.

Practice #3: Wednesday AM

  1. Identify the source and projection of geospatial data you have, or that could be relevant for your project.
  2. Determine which R packages can perform the necessary geospatial data processing.
  3. Continue work on a reproducible pipeline, reading and preparing data for analysis or vizualization.
  4. Share in-progress code through your GitHub repo.

Practice #4: Wednesday PM

  1. Discuss modeling approaches for your analysis.
  2. Start work on a simple regression model, if appropriate.
  3. Practice your collaborative workflow: stage, commit, pull, and push!

Practice #5: Thursday AM

  1. Continue discussion on suitable models—consider classification.
  2. Try to get a simple regression or classification model working.
  3. Ensure your local repo is up-to-date with the origin on GitHub.

Practice #5: Thursday PM

  1. Discuss the beginning steps of your reproducible pipeline. Can you aquire data programatically?
  2. Discuss and experiment with suitable vizualization of your data or model output.
  3. Use git to merge work on separate sections as necessary.

Practice #6: Friday PM

  1. Prepare to present about your project
    1. as an RMarkdown document,
    2. as a GitHub Pages site produced by RMarkdown, or
    3. show code and vizualizations in progress.