Assignments

All starter code and instructions will be available in our release repository, hosted at https://github.com/illinois-cs-coursework/sp26_ece411_.release.

You use the Verdi waveform viewer a lot in this class to debug. We have compiled some tips and tricks using the tool here.

Setup Instructions

  1. Create a repository via https://edu.cs.illinois.edu/create-gh-repo/sp26_ece411.

  2. Next, on EWS, create a directory to contain your ECE 411 files (this will include subdirectories for each MP, so chose a name such as ece411) and execute the following commands (replacing NETID with your NetID):

    $ mkdir ece411
$ cd ece411
$ git init
$ git remote add origin git@github.com:illinois-cs-coursework/sp26_ece411_NETID.git
$ git remote add release git@github.com:illinois-cs-coursework/sp26_ece411_.release.git
$ git pull origin main
$ git branch -m main
$ git fetch release
$ git merge --allow-unrelated-histories --no-ff release/main
$ git push --set-upstream origin main

If you have not set up SSH access to your github account, you may encounter errors during cloning. More detail is provided in mp_setup.

MP Information

All MP submissions must be made in your illinois-cs-coursework repository unless otherwise specified. If you have not made one yet, please follow the setup instructions above.

mp_setup

  • Release: 01/20

  • Due: N/A

mp_verif

  • Release: 01/20

  • Due: 02/02

mp_pipeline

  • Release: 02/03

  • CP1 Due: 02/09

  • CP2 Due: 02/16

  • CP3 Due: 02/23

mp_cache

  • Release: 02/24

  • Due: 03/09

mp_ooo

This MP will use a different submission repository than the previous solo MPs. You will receive an invite closer to the release.

  • Release: 03/10

  • CP1 Due: 03/23

  • CP2 Due: 04/06

  • CP3 Due: 04/20

  • Advance Features Due: 05/04

  • Report & Presentations: TBA

Submission & Autograder

All MPs will be graded by an autograder. The autograder runs on the most recent commit in the main branch of your repository uploaded on or before 11:59PM CT for that day. To submit your MP, push your code to the main branch before 11:59PM CT on the deadline date.

The autograder runs provided before the deadline are intended to ensure the MP code interfaces with the autograder correctly. There will be tests in the grading run not present in the previous runs.

Autograder runs for each MP will begin 3 days before the deadline, and run daily through 3 days past the final submission date (to account for late submissions).

Do not use the autograder as your only verification resource. Since the runs prior to the deadline are only for autograder compatibility, the final autograder run may include additional testcases not present in the previous runs. This will also be stated as part of the MP instructions.

Late Policy

MP submissions should be submitted by 11:59PM CT of the due date in order to be acknowledged by the autograder. Late submissions are allowed, albeit subject to the following penalties:

  • 1 Day Late: 10% penalty

  • 2 Days Late: 30% penalty

  • 3 Days Late: 60% penalty

  • 4+ Days Late: No Credit

If you submit 4+ days late, the autograder will not grade your submission.

In addition, you have one “late voucher” to submit mp_verif/mp_cache or a single checkpoint of mp_pipeline late by 3 days without any penalty. This does not stack with the previous late policy, this only removes the penalty. You can still only submit at most 3 days late.

The intent of this voucher is to account for any unforeseen circumstances (illness, conflicts, etc.). Exceptions to the late policy will not be made, so use this voucher wisely. Once you choose to use your voucher for an MP/Checkpoint, you cannot retroactively choose to move it to another MP/Checkpoint.

You can redeem your late voucher by filling out the form in the pinned post of our class Campuswire. This form must be submitted before the intended deadline of the relevant MP or checkpoint.