Skip to content

Latest commit

 

History

History
82 lines (60 loc) · 2.34 KB

README.md

File metadata and controls

82 lines (60 loc) · 2.34 KB
Raw

Stat 133, Fall 2017

Repository for HW assignments of Stat 133 (Fall 2017)

  • Student name: First Last
  • Github username: usrname
  • Lab section: 101
  • GSI: Leia Organa

Get your own repository

Get your own copy (clone) of this repository. This means that you will have to git clone the repository. Do NOT confuse cloning with forking (please do NOT fork this repo).

  • In your computer, open the command line.
  • Optional: move to the directory where you will clone this repository.
  • Run the following command (this will clone the repo to your working directory):
git clone https://github.com/ucb-stat133/stat133-fall-2017.git
  • Customize the README.md file with your Name, github username, lab section, and GSI name.
  • Add the changes to your local repo:
git add README.md
  • Commit the changes:
git commit -m "readme: customize readme file"
  • Push to github:
git push origin master

Working on a HW assignment

  • You should organize most HW assignments with the following file structure:
hw04/
  data/
  code/
  report/
  README.md
  • Use the directory data/ to put the data file(s)
  • Use the directory code/ to put all your .R files (e.g. scripts, functions, tests)
  • Use the directory report/ to put your .Rmd file (or slides)
  • Make sure the README.md file contains:
    • Title of the HW assignment
    • Brief description
    • Special instructions for any user (if necessary)
    • Special instructions for graders (if necessary)
    • Links to any resources that you used to complete the HW
    • List of references that you used to complete the HW
  • Some assignments may need more directories: e.g. app/, images/

As soon as you start working on a HW:

  • Keep track of changes with Git
  • Commit changes
  • Push commits to your github repository
  • Don't wait till the last day/hours/minutes to push to Github

Submitting your work

You should submit the repository link of each HW to bCourses, providing the commit number that corresponds to the closest time-stamp before the due date.

You can keep working on a HW once its due date has passed. However, we won't grade anything after the due date. Why bother? Because it is good professional practice. And it will help you have a nice portfolio for the course that you could show to the rest of the world (don't underestimate this).