> For the complete documentation index, see [llms.txt](https://madzhou1s-organization.gitbook.io/cs186/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://madzhou1s-organization.gitbook.io/cs186/assignments/proj4/submitting-the-assignment.md).

# Submitting the Assignment

## Files

You may **not** modify the signature of any methods or classes that we provide to you, but you're free to add helper methods.

You should make sure that all code you modify belongs to files with `TODO(proj4_part1)` and `TODO(proj4_part2)` comments in them (e.g. don't add helper methods to DataBox). A full list of files that you may modify follows:

* `src/main/java/edu/berkeley/cs186/database/concurrency/LockType.java`
* `src/main/java/edu/berkeley/cs186/database/concurrency/LockManager.java`
* `src/main/java/edu/berkeley/cs186/database/concurrency/LockContext.java` (Part 2 only)
* `src/main/java/edu/berkeley/cs186/database/concurrency/LockUtil.java` (Part 2 only)
* `src/main/java/edu/berkeley/cs186/database/table/Table.java` (Part 2 only)
* `src/main/java/edu/berkeley/cs186/database/table/PageDirectory.java` (Part 2 only)
* `src/main/java/edu/berkeley/cs186/database/memory/Page.java` (Part 2 only)
* `src/main/java/edu/berkeley/cs186/database/Database.java` (Part 2 only)

Make sure that your code does *not* use any static (non-final) variables - this may cause odd behavior when running with maven vs. in your IDE (tests run through the IDE often run with a new instance of Java for each test, so the static variables get reset, but multiple tests per Java instance may be run when using maven, where static variables *do not* get reset).

## Gradescope

Once all of your files are prepared in your repo you can submit to Gradescope through GitHub the same way you did for [Project 0](/cs186/assignments/proj0/submitting.md#pushing-changes-to-github-classroom).

### Submitting via upload <a href="#submitting-via-upload" id="submitting-via-upload"></a>

If your GitHub account has access to many repos, the Gradescope UI might time out while trying to load which repos you have available. If this is the case for you, you can submit your code directly using via upload. You can zip up your source code with `zip -r submission.zip src/` and submit that directly to the autograder.

## Partners

If you haven't yet already make sure [this form](https://docs.google.com/forms/d/e/1FAIpQLSeqB2F-aXGiORqNlOFuZjtknE_ydTI9yqznaYdI3V2ZCj2WKw/viewform?usp=sf_link) has the correct partner information so we know who you're working with. **We're no longer allowing partner submissions on Gradescope**. If you worked with a partner you'll both need to submit on your own (you're still free to submit identical code if you like though). Slip days will be deducted individually. For example: You submit on time, but your partner submits a day late. Your partner will have to use a slip day or will receive a late penalty on the project (but you will not).

## Grading

* Your submission for Part 1 will be worth 20% of your Project 4 grade and will come entirely from the Part 1 public tests.
* Your submission for Part 2 will be worth 80% of your Project 4 grade.
  * 5% for Part 1 hidden tests
  * 60% for Part 2 public tests
  * 15% for Part 2 hidden tests

Your Part 2 submission will be used to run all hidden tests (and public Part 2 tests). If you do not have a submission for Part 2, you will receive a 0% on all hidden tests for Part 1 and 2. You may go back and make changes to Part 1 even after that part deadline has passed before submitting to Part 2.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://madzhou1s-organization.gitbook.io/cs186/assignments/proj4/submitting-the-assignment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.