Assignments

Final Project

Details about your final project can be found here

Important Dates

• Topic due in Gradescope: 10/15/25

• Written Outline: 11/12/25

• Final Video Submission: 12/3/25

Labs (Completed in the Course VMs).

1. VMs

Detailed instructions for configuring and accessing the virtual machine for the labs in this course can be found at this link.

I recommend bookmarking this URL https://rameses.cs.unc.edu so you can easily access the log-in page.

2. Course workspace

Follow this link to accept the ``assignment’’ for our course workspace. This is where all of the starter code for each lab will be found, and where you can push updates to your assignments so you don’t lose track of your progress.

After you have generated your workspace, you will need to clone it to your machine. Run the following command in a new terminal. NOTE, you will be completing the labs inside the VMs, so cloning there may be the best place to start.

git clone <repo_name>

Then:

cd <repo_name>
ls

You should see the directory for lab1!

Submit to Gradescope by 11:59 on the posted deadline!

Lab 1. Due 9/22.

Lab 2. Due 10/12.

Lab 3. Due 11/3.

Lab 4. Due 11/17.

Lab 5. Due 12/1.

For Lab 2+, you will need to pull the new starter code before proceeding!

The starter code for each subsequent lab will be added directly into the same course repository. To update your individual repo, navigate to your workspace on the GitHub website and you should see a “Sync Fork” button. Click this and then “Update Branch.” Now if you run ``git pull’’ in your terminal, you will have all the materials you need.

IF YOU SEE AN OPEN PULL REQUEST BUTTON OR DO NOT SEE THE SYNC FORK BUTTON when you attempt to sync your workspace, please follow the below steps. If you have any trouble, come see the TAs in office hours and we will walk you through it!

1. Check for an existing SSH key

• In your terminal run:

  ls ~/.ssh

• If you see a public key file (for example id_rsa.pub or id_ed25519.pub), you already have an SSH key. You can print it with:

  cat ~/.ssh/id_rsa.pub

• If you have a key, skip to step 3 (Add the key to GitHub).

2. Create an SSH key if you do not have one already

• In your terminal run:

  ssh-keygen -t rsa -b 4096

• Press Enter to accept the default file location when prompted.

• Enter a passphrase you will remember.

• Print the public key:

  cat ~/.ssh/id_rsa.pub

• Copy the output to add to GitHub (see step 2 below).

3. Add the key to GitHub

• Copy the output of cat ~/.ssh/id_rsa.pub.
• In GitHub: Settings → SSH and GPG keys → New SSH key.
• Paste the key and give it a name like “laptop”. Save.

4. Add the starter repo as a remote

• In your local course repo run:

  git remote add starter git@github.com:comp435-fa25/comp435-fa25-comp435-workspace-435-fa25-starter.git

• Verify remotes:

  git remote -v

  You should see both origin and starter.

5. Sync your fork with the starter repo

• Pull updates from the starter remote using rebase:

  git pull starter main --rebase

• Repeat step 4 every time we push a new lab directory to the starter repo.

• The first time you make changes and try to push to your workspace, you may need to run git push origin main --force.

If anything fails (SSH permission errors, etc.), see a TA in office hours for hands‑on help.

Written Assignments

Hand-write your solutions and upload to Gradescope by 11:59 on the posted deadline!

Written Assignment 1. Due 8/28.

Written Assignment 2. Due 9/25.

Written Assignment 3. Due 10/9.

Written Assignment 4. Due 10/30.

Written Assignment 5. Due 11/13.

Written Assignment 6. Due 11/24.