Closed sullivannicole closed 7 years ago
Topic | Excellent | Satisfactory | Needs Work |
---|---|---|---|
Coding style | x | ||
Coding strategy | x | ||
Presentation: graphs | |||
Presentation: tables | |||
Achievement, creativity | x | ||
Ease of access | x |
Remarks:
git status
to check what files you have added before committing them. This is best practice, especially at first.Full R .gitignore file (saved as .gitignore
):
# History files
.Rhistory
.Rapp.history
# Session Data files
.RData
# Example code in package build process
*-Ex.R
# Output files from R CMD build
/*.tar.gz
# Output files from R CMD check
/*.Rcheck/
# RStudio files
.Rproj.user/
# produced vignettes
vignettes/*.html
vignettes/*.pdf
# OAuth2 token, see https://github.com/hadley/httr/releases/tag/v0.3
.httr-oauth
# knitr and R markdown default cache directories
/*_cache/
/cache/
# Temporary files created by R markdown
*.utf8.md
*.knit.md
Coding styleL: Excellent
Coding strategy: Excellent
Presentation(graphs): N/A
Presentation(tables): N/A
Achievement, creativity: Excellent
Ease of access: Excellent
Nicole did a really good job. Her file included all the basic R Markdown technics mentioned on the course website. What's more, her work is very interesting. It showed great creativity. I like her content. I encountered fatal error as well. All in all, it's a great work!
How changes were made to README.md
Difficulties encountered
While (of course) it took some experimentation to write the code correctly and preview it, the main difficulty I encountered was an error message when I attempted to commit changes. Sometimes RStudio would return the message fatal error- and fatal is a frightening word to see on my computer! However, when I would click "commit" again, the correct message was returned ("insertion, deletion" etc.), and when I pushed the changes to GitHub, they appeared nearly exactly as I had seen in the "Preview" option of RStudio (although I didn't realize that option existed for a commit or two!).