Course Outline

Course Overview

Modules

Assignments

Resources

Policies

Insurmountable Coding Problems

Push It!



[‘She’ being Github]


Must be submitted for Peer Commentary by 5:00 pm Sunday, September 17th.


Peer Commentary and Final Homework DUE at 5:00 pm Wednesday, September 20th.


Create, Clone, and Access a New Repo in RStudio

Create a repository in your GitHub account called AN588-Week-2-BUlogin (where BUlogin is your BU login name; for example, mine would be AN588-Week-2-caschmit), and clone it to your computer. Once there, create a git-referenced Project in RStudio with the same name and connect it to your cloned repository.

Write Some Code

In that Project on RStudio, create a new R Markdown (Rmd) file - you can create one using the ‘new file’ button on the editor in RStudio - and use that to write and run your well-annotated/commented Original Homework Code, which will include all of the CHALLENGES from Module 04. When you save this file, name it BUlogin_OriginalHomeworkCode_01 (i.e., for me, it would be caschmit_OriginalHomeworkCode_01).

Push It!

Once you’ve finished (or even better: as you save along the way), you must PUSH that file up to GitHub directly from RStudio (i.e., once pushed, it should be accessible in your AN588-Week-2-BUlogin repo on your GitHub account’s website). Notes in Module 03 should help you accomplish this - and, of course, feel free to come see me for additional help during my office hours if you’re having problems.

Peer Commentary for Homework 01

Peer Commentary for this week should focus on the code for the Module 04 CHALLENGES, and should also be pushed directly to your AN588-Week-2-BUlogin repo by the member of your Peer Group responsible for commenting on your Original Homework Code. Share your Original Homework Code by adding your Peer Group (and your instructor) as ‘Collaborators’ by 5:00 pm on Sunday, September 17th.

Once this process is complete, you have a number of options for reading over and commenting on your peer’s code. Options for Peer Commentary include each of you making comments on one other person’s code (e.g., Person1 on Person2’s, Person2 on Person3’s, Person3 on Peron1’s), or each of you commenting together as a group on each others’ code (Peer Group 1 on Person1’s, Peer Group 1 on Person2’s, Peer Group 1 on Person3’s). The latter option should only be used if your peer group meets in person to discuss code together as a group. The former option is the only option if you do not meet in person to discuss.

For working with peer code on your personal computer in RStudio, I recommend cloning your peer’s homework repo to your computer, creating a git-referenced Project from the cloned repo, duplicating their Original Homework Code, and renaming it Peerlogin_PeerCommentary_BUlogin_01. For example, if Prof. Eva Garrett were the commenter on my Original Homework Code, the file would be named garrette_PeerCommentary_caschmit_01, and if the whole Peer Group worked together to comment, it would be called PeerGroupX_PeerCommentary_caschmit_01). Comment/edit this Rmd file of code in RStudio so that you can easily push your changes directly to your peer’s repo in the appropriately named file. Once you’re finished, comment/name your last push to their repo FINAL PUSH so that they know it’s ready for use in editing their own code.

Please make your FINAL PUSH of comments/suggestions with enough time so that your peer can incorporate them into their Final Homework Code. To create your Final Homework Code (an Rmd file named BUlogin_FinalHomeworkCode_01), I recommend you duplicate and rename your Original Homework Code in your own homework repo, and then refer to the Peer Comments when trying out and running changes. This must be pushed to GitHub by 5:00 pm on Wednesday, September 20th.

Don’t Cheat!

Some of you will no doubt realize that you will be able to see your colleagues’ Rmd documents on GitHub each time they push them up, if you check out their accounts… during the Peer Commentary stage, I encourage you to troubleshoot code together, but during the first phase of your homework, while writing your original code, please refrain from copying each others’ work - in person or from repositories - it is critically important that you make your original work your own!

Make it Pretty!

For the purposes of this assignment, please format your Final Homework Code however you like, but it must have some intentional alterations in formatting entered 1) in the YAML, and 2) in the body of the RMarkdown file itself that only appear when the document is knitted!

Your Final Assignment for Homework 01

Your final assignment, due to me by 5:00 pm on Wednesday, September 20th, is to have in your AN588-Week-2-BUlogin repo only the following six (6) files:
    1. Your Original Homework Code, including the five challenges you faced, as pushed to your repo by 5:00 pm on Sunday, an R Markdown and HTML file each named BUlogin_OriginalHomeworkCode_01.
    2. The FINAL PUSH of the Peer Commentary made on your code, an R Markdown file and HTML file each named Peerlogin_PeerCommentary_BUlogin_01 or PeerGroupX_PeerCommentary_BUlogin_01.
    3. Your Final Homework Code, which has taken into account any changes recommended from the Peer Commentary and which has your final prettification mods, an R Markdown file and HTML file each named BUlogin_FinalHomeworkCode_01.
NOTE: If you want your homework code to look nice (beyond being very well annotated and commented), and be easy to use by others, please consider consulting the following helpful guidelines on how to write effective R Markdown documents (also available at the end of Module 03).