Deadlines

Warning: There are 3 deadlines for this project, and some deadlines require you to submit multiple deliverables. Please double-check that you submitted everything!
Assignment Tasks Deliverable Points Due Date
Project 5A - Partnerships
- Setup
- Design Document
Partnership formation 50 Tues, Nov 10
11:59pm PT
Lab 12 Fri, Nov 13
11:59pm PT
Re-pairing requests (if needed) — Mon, Nov 16
11:59pm PT
Dissolution requests (if needed) — Wed, Nov 18
11:59pm PT
Design Document 50 Wed, Nov 18
11:59pm PT
Project 5B - World Generation
- Light Sources (groups of 3 only)
Code and World Screenshots on Gradescope
(optional regrade/clobber at your checkoff)
200 Tues, Nov 24
11:59pm PT
Project 5C
No Extensions
- Task 1: Main Menu
- Task 2: Interactivity
- Task 3: HUD
- Task 4: Saving and Loading
- Task 5: Toggleable Light Sources (groups of 3 only)
- Task 6: Pathfinding
- Task 7: Ambition Features
Code on Gradescope and Live Checkoff with TA
(Checkoffs will happen Mon Nov 30 – Fri Dec 4; Nov 30 and Dec 1 are optional early slots)
500 Tues, Dec 1
11:59pm PT
To request extensions on Project 5, all group members need to submit separate extension requests on Beacon.

Policies

Project 5 checkoffs will be held Monday, November 30 – Friday, December 4.

  • Wednesday – Friday (Dec 2 – Dec 4) are the main checkoff days.
  • Monday – Tuesday (Nov 30 – Dec 1) are for groups who want to get checked off early, or who can’t make Wednesday – Friday.

Upon 5C release sign up for a check off slot and complete it at your assigned time.

  • See the Ed announcement for more details.
  • Make sure to prepare accordingly to avoid any last-minute emergencies!

The code that you present during your demo should be the code that you submitted to the Project 5C assignment on Gradescope. In other words, the Project 5C due date (plus any extensions you requested) is the deadline for making any changes to your code. Even if your checkoff doesn’t happen until later, you can’t make any changes after your Project 5C due date. If you check off early (Nov 30 or Dec 1), the code you demo is your final 5C submission: you can’t change it after your checkoff.

The following is exactly what the TA will do when checking you off: we recommend you do a dry-run of this to ensure you didn’t miss anything. You can clone your repository in some random destination on your computer (like your home directory) if you want to follow along and simulate your checkoff.

Attendance

All group members should be present in person for the checkoff.

  • Be on time. Your checkoff starts at the exact time of your slot. There is no Berkeley time for checkoffs: a 2:00 PM slot starts at 2:00 PM, not 2:10 PM.
  • Late: each group member who is late loses 10% of the checkoff points (33 points).
  • No-show: each group member who misses the checkoff loses 50% of the checkoff points (165 points), unless they filled out the extenuating circumstances form below.

The checkoff points are the 330 points of Project 5C graded at the checkoff (Light Sources, Pathfinding, and Ambition Features).

Please fill out the Checkoffs Extenuating Circumstances Form if you are experiencing extenuating circumstances and need accommodations for the following:

  • Need to be checked off outside of the checkoff window (11/30 – 12/4), AND/OR
  • Need to be checked off online

The deadline for this form is Tuesday, December 1st at 11:59PM (Project 5C deadline). We cannot guarantee any accommodations if you do not submit this form by then.

Setup

Designate one group member to be the presenter; this should be the group member who signed up for the demo slot. They should make sure to already have the following set up:

  • IntelliJ open with your Project 5 code (doesn’t matter what class)
  • The program running with the BYOW main menu displayed
  • The state of your repo should be the commit containing the version of your project you want to demo. The code you demo should be the same as the code you submitted to Gradescope. If this is your most recent commit, just make sure your Git status is clean. If it is a past commit, you can get to this state by running git switch --detach <commit id>. (To get your repo back to normal, run git switch main.)
  • If you choose to demo a version of your project that is past the deadline (for a percentage penalty, per the syllabus), make sure to let the TA know.
  • Your Git status should be clean (no changes to commit)

Checkoff Script

Everything below is checked live by a TA.

  1. The grader will ask for your SID to find your group and then confirm names, SIDs, and group number.
  2. One group member should designate their laptop as the “check-in laptop”, and already have a terminal window in their fa26-proj5-g***/proj5. Their Git should be in a clean state (git status should be clean), IntelliJ should be open, and the Project 5 main menu should be running.
    • If any of these requirements are not fulfilled, you may not receive a grade for Proj5 checkoff.
  3. The grader will check that your project is ready to be checked off:
    • Run git log and make sure that the HEAD commit is a commit from before the deadline (or tell the grader you’re demoing a late version).
    • Run git status and make sure your workspace is clean.
    • Run pwd and make sure the path matches that of the open IntelliJ window.
  4. The grader will ask whether you want your world generation (5B) regraded. If you didn’t get full credit on 5B and say yes, they will check your worlds (see 5B: World Generation below).
  5. The grader will ask which group size and ambition feature option you chose (e.g. 2 primaries, or 1 primary + 1 secondary).
  6. If you are a group of 3, the grader will ask you to toggle all of your Light Sources on and off with your keypress, then save and load to check that the on/off state is preserved.
  7. The grader will then ask you to demonstrate the Pathfinding task: they will click a tile (a shortest path should be drawn), then click the same tile again (the avatar should animate along the path, not just teleport).
  8. The grader will then ask you to demonstrate your ambition features, along with saving and loading (must save state of ambition feature). If you implemented more features than your option needs, tell the grader which ones to grade.
  9. The grader will tell you which items you received/did not receive credit for. They will ask if you agree with your score: if you do not, you will have the opportunity to request a regrade within 24 hours of your checkoff. This can be done under the Checkoff tab in Beacon.
Section Groups of 2 Groups of 3
5B: World Generation (optional regrade) up to 200 up to 200 (includes 30 for Light Sources)
5C: Toggleable Light Sources — 40
5C: Pathfinding 110 70
5C: Ambition Features 220 220

5B: World Generation (optional regrade)

Your 5B worlds are first graded from the screenshots you submitted by the 5B deadline. At your checkoff, the TA will ask whether you want your world generation graded again:

  • If you already got full credit on 5B, there’s nothing to regrade, so just say no.
  • If you didn’t, say yes. The TA will start a new world from a few different seeds and check it against the Project 5B World Requirements (including Light Sources for groups of 3). Your checkoff score replaces your 5B score if it’s higher.

See the 5B grading breakdown for exactly what is checked and what each part is worth.

5C: Toggleable Light Sources (groups of 3 only, 40 points)

  • The TA will toggle all of your light sources on and off with your keypress.
  • The TA will save and load, and check that the lights’ on/off state is preserved.

See the Light Sources rubric for exactly what each item is worth.

5C: Pathfinding

Worth 110 points for groups of 2 and 70 points for groups of 3.

  • The TA will click a square, and a path will be drawn to that square. This must be a shortest path.
  • The TA will click the same square, and the avatar will be animated and moved to that square following the path

See the Pathfinding rubric for exactly what each item is worth.

5C: Ambition Features (220 points)

  • State and demonstrate your ambition features. You should be very explicit about how to “activate” or use each feature.
  • Groups of 2 need 2 primary features, OR 1 primary and 1 secondary feature. Groups of 3 need 3 primary features, OR 2 primary and 1 secondary feature.
  • The TA will grade each feature using the checklist under it on the Ambition Features page, which also lists what each feature is worth.