Checkpoint 1: Getting Started and Project Selection
Goal: Set up your team repository, verify that every team member can work with it, and provide the information needed for project assignment.
Getting Started
Before completing the Checkpoint 1 requirements, review the Project Repository and Infrastructure page. It explains how to create your team repository through Classroom 50, clone it, and understand the organization of the provided course infrastructure and student implementation files.
Once your repository is set up, complete the requirements below.
Requirements
1. Shared repository access
Every team member must be able to work with the shared repository. During Checkpoint 1, each team member should clone the repository and make and push at least one commit.
2. Team and project information
Complete the root-level project.json file with:
- your team name;
- each team member’s name and GitHub username; and
- three distinct project preferences, listed from most preferred to least preferred.
Leave assigned_problem blank until project assignments are announced.
Use the following canonical project identifiers exactly as shown in project_preferences:
| Project | project.json identifier |
|---|---|
| Traveling Salesperson Problem | traveling_salesperson |
| Minimum Graph Coloring | minimum_graph_coloring |
| Minimum Vertex Cover | minimum_vertex_cover |
| Longest Path | longest_path |
| Maximum Clique | maximum_clique |
Your three preferences must use three different identifiers from this table. These long identifiers are used in project.json; shorter names such as mvc and tsp are command-line aliases used later with src/solve.py.
Submission checklist
-
project.jsonis complete and contains three ranked project preferences. - Every team member has successfully contributed to the shared repository.
- All current work has been committed and pushed to GitHub.
- The repository has been submitted to the Checkpoint 1 Gradescope assessment with all team members included in the Gradescope group.
Assessment. Gradescope will validate the required repository structure and project.json. The instructor may inspect the repository history to verify team access and participation and will use the ranked preferences to assign projects.