Homework Policy

Collaboration Policy

While working on homework, students are encouraged to work together in a group of at most 3 students. Students who opt to work together must list the full names and netids of the students that they have collaborated with at the top of the document. Each student must also turn in their own homework answers. This means that students should not share or copy homework answers, which may involve written explanations and code. In general, students should strive to independently write answers to the homework problems. Failure to do so will likely result in an academic integrity investigation being opened.

In addition, there is a lot of R code on the internet. Many students will be tempt to copy and paste code online or request help from programming communities. This behavior is okay as long as you cite where the code originated from and are not having someone answer the question in verbatim. Any code that is not cited but is able to be matched with available works online will be treated as plagiarism and fall under the class’ academic integrity policy.

Distribution Policy

Each homework will be distributed over a GitHub Classroom assignment link. Please accept the assignment to create your repository.

Within your assignment, you should have:

  • hw01-assign.Rmd, the file used to create the homework document.
    • You may wish to use this as a template for your assignment.
  • hw01-assign.html, the homework rendered as an html file.
  • hw01-assign.pdf, the homework rendered as a pdf file.
  • Additional files such as external data or infrastructure files that should not be modified unless specifically told.

NB 01 should be replaced by the current two-digit homework number.

Assignment Submission

Homework must be submitted online through the GitHub Repository generated for each student.

The online submission must contain:

  • hw01-NetID.Rmd
  • hw01-NetID.html or hw01-NetID.pdf

The NetID component represents your NetID, e.g. the NetID is infront of @illinois.edu, and 01 represent the two-digit homework assignment number.

Inside the .Rmd file, please make sure to update the author value away from "Full Name (NetID)" to your name and NetID.

As an example, on the fifth homework assignment, your instructor, whose netid is balamut2, would submit:

  • hw05-balamut2.Rmd
  • hw05-balamut2.html or hw05-balamut2.pdf
  • Any files needed to create the output document, e.g. hw05-balamut2.html, from hw05-balamut2.Rmd.

The hw05-balamut2.Rmd file would have

title: 'hw05: Radio Statistics'
author: 'James Balamuta (balamut2)'
date: 'Due: Friday, Month Day, YYYY at HH:MM PM'
output: html_document

Depending on the assignment, you may need to place in the GitHub repository additional assets. For example, screenshots, scripts, or a package.

In general, the file structure for hw01 would look like:

|- /
   |- hw01-NetID.Rmd
   |- hw01-NetID.html
   |- image-exercise1.png
   |- image-exercise2.png
   |- image-exercise3.png
   |- README.md 
   |- test/
       |- render_rmds.R
   |- .travis.yml 
   |- project.Rproj 

All digital submissions must be made using either the RStudio git client or by using git terminal. Avoid adding, creating, renaming, or removing a file via the GitHub web interface. Any student found to be using the GitHub web interface to submit their homework will lose all points associated with committing.

This is presently the only class that emphasizes git skills within the Statistics department curriculum. Please do not try to circumvent learning this skill.


Each homework assignment will be a variable number of points; however, each homework assignment will have equal weight towards your final grade. Grades will be based on both accuracy and presentation of information. In general, you should make your document as easy to read for the CAs as possible.

Documents that are difficult to read will receive overall point reductions depending on the level of difficulty.

Late Homework

Homework is always due at 6:00 PM on the assigned due date. You are allowed to drop one homework assignment over the course of the semester.

As a result, late homework will not be accepted. There will be no exceptions to this policy. Please start early and make sure your environment is working correctly and you are able to produce a working document.

Academic Integrity

If a student is caught sharing, copying, or providing any part of a homework solution or code to another student, this will be treated as an infraction of the University’s rules on Academic Integrity. Rest assured, any violation of Academic Integrity will be punished as severely as possible.

The range of penalities that will be enforced are:

  • First offense: receiving an undroppable zero on the assignment and being written up for an academic integrity violation.
  • Second offense: receiving an F in the course, an academic integrity violation, and recommendation for expulsion from the University.

Note that cheating includes both obtaining others’ work, as well as distributing your own work.

  • You may discuss the assignment with your classmates, but your final answers must be your own. Your final document should be created independently.
  • To avoid any issues, do note copy and paste code. (With an exception for code provided for the course.)
  • Do not share RMarkdown files.

If we detect academic integrity violations, we will contact you through the FAIR system.

In short, please do not cheat.


  • Please read every exercise carefully. If the wording of an exercise is problematic, immediately let the course staff know.
  • Include your name and NetID in the final document, not only in your filenames.
  • Your .Rmd file must be written such that, when stored in a folder with any data you are asked to import, it will knit properly without modification. If your git repository is organized properly, this should not be an issue. That is, you should use relative references to external files.
  • Your resulting .html or .pdf file will be considered a “report” which is the material that will determine the majority of your grade. Be sure to visibly include all R code and output that is relevant to answering the exercises. (You do not need to include irrelevant code you tried that resulted in error or did not answer the question correctly.)
  • Be aware of directions for code randomization for each exercise.