CS 70

Homework 3: Check Your Submission

After all of the work you've done, it's important to make sure that your submission is in good shape and that you won't lose points for silly things.

Final Checklist

Before submitting, make sure you've completed all of these tasks:

Code Quality

  • Style Check: Run cpplint on all of your .hpp and .cpp files and correct any errors or warnings that appear.

    cpplint *.cpp *.hpp

  • Compilation Check: Confirm that your code compiles on cs70.cs.hmc.edu with no errors or warnings.

    make clean
make

Version Control

  • Check Status: Run git status in your working directory and review the output. Make sure that:

    • There aren't any modified files in your local working copy that haven't been committed/pushed
    • No extra files (compiled files, .DS_STORE files, etc.) are in your repository

  • Clean Repository: Your repository should contain:

    • Your source files (.cpp and .hpp files)
    • Your Makefile
    • Your sprite files in spriteImages/
    • Your written answers in WrittenAnswers/Design.md
    • NO compiled files (.o files or executables)

Testing

  • Run Your Program: Make sure your animation runs correctly on cs70.cs.hmc.edu:
    1. Connect to the CS 70 server (ssh into it in a terminal)
    2. Ensure your terminal is large enough (80×40 characters minimum)
    3. Run ./our-movie
    4. Verify that your sprite scrolls across the screen
    5. Confirm that q quits the program

Submission

  • Submit with submit-this: On the CS 70 server, from inside your repository, run submit-this. It will record the current state of your work as your submission and print a submission code; enter that code in the box at the bottom of this page.

    Either partner can run submit-this.

  • Check the confirmation: submit-this tells you what it recorded and when. If you don't see that confirmation, you have not submitted successfully—read through what submit-this printed instead, and check with us if the message doesn't make sense.

Common Issues to Avoid

  • LHS Cow speaking

    Double-check these common problems before submitting!

  • Missing Files: Ensure all required files are in your repository
  • Compilation Errors: Test compilation one more time on the server
  • Wrong Server: Make sure you're testing on cs70.cs.hmc.edu, not locally
  • Terminal Size: If the animation looks wrong, check your terminal size
  • Git Issues: If git status shows uncommitted changes, commit and push them

To Complete This Part of the Assignment

You'll know you're done with this part of the assignment when you've done all of the following:

Record Your Submission Code

When submit-this succeeds, it prints a submission code that looks like

Your submission code: 8A1F-BB41-P

Copy yours in here, exactly as shown—dashes and all. Either partner can enter the code it; because this is a group answer, it counts for both of you, and only one of you needs to run submit-this because your repository belongs to both of you. It is your receipt that you submitted, and it is how we match what you entered to the snapshot that actually arrived on GitHub.

(When logged in, completion status appears here.)