Problem Set 0: Turtle Graphics

Part I (#’s 0—3) due: before class Friday, September 11, 2015, 1:00 pm

Beta due: Tuesday, September 15, 2015, 10:00 pm
Code reviews due: Thursday, September 17, 2015, 10:00 pm
Final due: Tuesday, September 22, 2015, 10:00 pm

Welcome to 6.005!

This course is about three essential properties of software:

Safe from bugs	Easy to understand	Ready for change
Correct today and correct in the unknown future.	Communicating clearly with future programmers, including future you.	Designed to accommodate change without rewriting.

The purpose of this problem set is to:

introduce the tools we will use in 6.005, including Java, Eclipse, JUnit, and Git;
introduce the process for 6.005 problem sets;
and practice basic Java and start using tools from the Java standard library.

You should focus in this problem set on writing code that is safe from bugs and easy to understand using the techniques we discuss in class.

You must install the required tools and complete Part I (problems 0 through 3) before class on Friday, September 11.

Part I

Problem 0: Install and set up

Read and complete the Getting Started guide. The guide will step through:

installing the JDK, Eclipse, and Git
configuring Eclipse
configuring Git
learning and practicing the basics of Git

You need to complete all the steps in the guide before you start working on this problem set.

Problem 1: Clone and import

This process will be identical for each problem set.

Obtain a remote repository with the starting code for the problem set by visiting didit.csail.mit.edu. Find psets/ps0 under New assignments and create a repository. You will only be able to create a repo after the course signup forms are processed and the problem set is announced.
- If you can’t create a repo after the announcement, you are not registered for 6.005. Contact the staff (how?) to check your status.
- If you are listener or not taking 6.005 for credit, you can’t create a repo. See instructions below to clone from a read-only remote.
Open the terminal (Git Bash on Windows) and go to the directory (using cd) where you would like to store your code; for example, that might be a directory named Source in your home directory.

Getting Started step 3 introduces the command line.
Clone your repo. You will access the remote repository over SSH from your laptop.

Note: Getting Started step 4 has setup you must perform before using Git.

In the terminal, run (all on one line):

git clone ssh://[username]@athena.dialup.mit.edu/mit/6.005/git/fa15/psets/ps0/[username].git ps0

The result should be a directory named ps0 with the starting code for the problem set. Keep the terminal open — you will also use it to commit your code.
- If git clone says “does not appear to be a git repository” or “could not read from remote repository”, check your repository URL for typos. Make sure your repository is listed on Didit.
- If git clone reports a “protocol error” or asks for your password but then does nothing, you should review any changes you made to your Athena dotfiles, especially .bashrc.mine and .bash_environment. Ask a TA for help if you are not familiar with Athena.
- If you are a listener or not taking 6.005 for credit, you can clone a problem set repository using a modified command: replace the last instance of [username] with didit/starting. You will not be able to push to this repository, it’s a read-only remote.
After cloning your repository, add the project to Eclipse so you can work on it.

Note: Getting Started step 2 has setup you must perform before using Eclipse in 6.005.

To import a project:
- In Eclipse, go to File → Import… → Git → Projects from Git
- On the “Select Repository Source” page, select “Existing local repository”
- On “Select a Git Repository,” click Add…, and Browse… to the directory of your clone
- The “Search results” list should show your clone, with “.git” at the end; click “Finish”
- On “Select a wizard” for importing, choose “Import existing projects”
- Finally, on “Import projects,” make sure ps0 is checked, and click “Finish”
If Git support does not work in Eclipse, you can import without telling Eclipse that your project is a Git repository:
- Go to File → Import… → General → Existing Projects into Workspace
- Choose “Select root directory” and Browse… to the directory containing your project (it will be the directory containing the src directory and a hidden .project file)
- Make sure the project is checked, make sure “Copy projects into workspace” is not checked, and click “Finish”

Problem 2: Warm up with `mayUseCodeInAssignment`

Look at the source code contained in RulesOf6005.java in package rules. Your warm-up task is to implement:

mayUseCodeInAssignment(
       boolean writtenByYourself, boolean availableToOthers,
       boolean writtenAsCourseWork, boolean citingYourSource,
       boolean implementationRequired)

You can find the policy under General Information on the course home page.

Once you’ve implemented this method, run the main method in RulesOf6005.java.

public static void main(String[] args) is the entry point for Java programs. In this case, the main method calls the mayUseCodeInAssignment method with input parameters. To run main in RulesOf6005, right click on the file RulesOf6005.java in either your Package Explorer, Project View, or Navigator View, go to the Run As option, and click on Java Application.

Unit testing

Right now, we can use the main method plus some visual inspection to verify that our implementation is correct. More generally, programs will have many dozens of methods that need to be tested; visually inspecting output for each one is fragile, time-consuming, and inherently non-scalable.

Instead, we will use automated unit testing, which runs a suite of tests to automatically test whether the implementations are correct. For this problem set, we will write unit tests for methods that do not draw graphics on the screen; unit-testing GUIs is a more complex problem.

Automated unit testing with JUnit

JUnit is a widely-adopted Java unit testing library, and we will use it heavily in 6.005. A major component of the 6.005 design philosophy is to decompose problems into minimal, orthogonal units, which can be assembled into the larger modules that form the finished program. One benefit of this approach is that each unit can be tested thoroughly, independently of others, so that faults can be quickly isolated and corrected as code is rewritten and modules are configured. Unit testing is the technique of writing tests for the smallest testable pieces of functionality, to allow for the flexible and organic evolution of complex, correct systems.

By writing thoughtful unit tests, it is possible to verify the correctness of one’s code, and to be confident that the resulting programs behave as expected. In 6.005, we will use JUnit version 4.

Anatomy of JUnit

JUnit unit tests are written method by method. There is nothing special a class has to do to be used by JUnit; it only need contain methods that JUnit knows to call, which we call test methods. Test methods are specified using annotations, which may be thought of as keywords (more specifically, they are a type of metadata), that can be attached to individual methods and classes. Though they do not themselves change the meaning of a Java program, at compile- or run-time other code can detect the annotations and make decisions accordingly. Though we will not deeply explore annotations in 6.005, you will see a few important uses of them.

Look closely at RulesOf6005Test.java, and note the @Test that precedes method definitions. This is an example of an annotation. The JUnit library uses this annotation to determine which methods to call when running unit tests. The @Test annotation denotes a test method; there can be any number in a single class. Even if one test method fails, the others will be run.

Unit test methods can contain calls to assertEquals, which is an assertion that compares two objects against each other and fails if they are not equal, assertTrue, which checks if the condition is true, and assertFalse, which checks if the condition is false. Here is a list of all the assertions supported by JUnit. If an assertion in a test method fails, that test method returns immediately, and JUnit records a failure for that test.

Run the unit tests.

To run the tests in RulesOf6005Test, right click on the RulesOf6005Test.java file in either your Package Explorer, Project View, or Navigator View, and go to the Run As option. Click on JUnit Test, and you should see the JUnit view appear.

If your implementation of mayUseCodeInAssignment is correct, you should see a green bar, indicating that all the tests (there’s only 1 test, containing 2 assertions) passed.
Try breaking your implementation and running RulesOf6005Test again.

You should see a red bar in the JUnit view, and if you click on testMayUseCodeInAssignment, you will see a stack trace in the bottom box, which provides a brief explanation of what went wrong. Double-clicking on a line in the failure stack trace will bring up the code for that frame in the trace. This is most useful for lines that correspond to your code; this stack trace will also contain lines for Java libraries or JUnit itself.
Enough breaking: fix your implementation so it’s correct again. Make sure the tests pass.

Passing the JUnit tests we provide does not necessarily mean that your code is perfect. You need to review the function specifications carefully, and always write your own JUnit tests to verify your code.

Problem 3: Commit and push `RulesOf6005`

After you’ve finished implementing the function and verified that it is correct, let’s do a first commit.

First, in the terminal, change directory (cd) to your clone, and take a look around with

git status

which shows you files that have been created, deleted, and modified in the project directory. You should see RulesOf6005.java listed under “Changes not staged for commit.” This means Git sees the change, but you have not (yet) asked Git to include the change as part of your next commit.
You can run the command

git diff

to see your changes. (Note: when the diff is more than one page long, use the arrow keys. Press q to quit the diff.)
Before committing, files must be staged for commit. Staging a file is as simple as

git add <filename>

so use

git add src/rules/RulesOf6005.java

to stage the file. You should also stage the test file if you’ve added more tests.
In addition, it’s always a good idea to review your commits before committing to them. Run

git status

again to see that your changes are now listed under “Changes to be committed.” If you run

git diff

those changes are no longer shown! Use

git diff --staged

to see exactly what Git will record if you commit now.
Ready? To perform the commit,

git commit

will actually commit the changes locally, after opening your default editor to allow you to write a commit message. Your message should be formatted according to the Git standard: a short summary that fits on one line, followed by a blank line and a longer description if necessary.

If Git warns you about configuring your default identity or you can’t edit your commit message, you did not follow the instructions in the Getting Started guide. Getting Started step 4 has setup you must perform before using Git.
You can use the command

git log

to see the history of commits in your project. Right now, you should see two of them: the initial commit to create your problem set repository with the starting code, and the commit you made just now.

Important: only the local history has the new commit at this point; it is not stored in your remote repository. This is one important aspect where Git is different from centralized systems such as Subversion and CVS.
In order to share the changes with your remote repository (which is the one we will be using for grading), you need to push to the remote repository, with

git push origin master

At this point, the remote repository on Athena now has the same history as your local repository. It is important to remember that we will be grading the history in the repository on Athena; if you forget to push, we won’t see your commits.

Didit: when you push your commit, you should see the Didit system wake up and run a subset of the autograder on your code. Didit clones its own copy of your code from what you’ve pushed to Athena, compiles it, and runs some tests.

Right now, almost all tests will fail since you’ve only implemented one method. But as the deadline approaches, it is your responsibility to check Didit’s build report and ensure that we can compile and run your code.

gitweb: you can see the contents of your Athena repository with your web browser on gitweb.

Part II

Turtle graphics and the Logo language

Logo is a programming language created at MIT that originally was used to move a robot around in space. Turtle graphics, added to the Logo language, allows programmers to issue a series of commands to an on-screen “turtle” that moves, drawing a line as it goes. Turtle graphics have also been added to many different programming languages, including Python, where it is part of the standard library.

In the rest of problem set 0, we will be playing with a simple version of turtle graphics for Java that contains a restricted subset of the Logo language:

forward(units)
Moves the turtle in the current direction by units pixels, where units is an integer. Following the original Logo convention, the turtle starts out facing up.
turn(degrees)
Rotates the turtle by angle degrees to the right (clockwise), where degrees is a double precision floating point number.

You can see the definitions of these commands in Turtle.java.

Do NOT use any turtle commands other than forward and turn in your code for the following methods.

Problem 4: `drawSquare`

Look at the source code contained in TurtleSoup.java in package turtle.

Your task is to implement drawSquare(Turtle turtle, int sideLength), using the two methods introduced above: forward and turn.

Once you’ve implemented the method, run the main method in TurtleSoup.java. The main method in this case simply creates a new turtle, calls your drawSquare method, and instructs the turtle to draw. Run the method by going to Run → Run As… → Java Application. A window will pop up, and, once you click the “Run!” button, you should see a square drawn on the canvas.

Problems 5—10: Polygons and headings

For detailed requirements, read the specifications of each function to be implemented above its function signature in TurtleSoup.java. Be careful when dealing with mixed integer and floating point calculations.

You should not change any of the method signatures (what’s a signature?) below. If you do so, you risk receiving zero points on the problem set.

Drawing polygons

Implement calculateRegularPolygonAngle
There’s a simple formula for what the inside angles of a regular polygon should be; try to derive it before googling/binging/duckduckgoing.
Run the JUnit tests in TurtleSoupTest
The method that tests calculateRegularPolygonAngle should now pass and show green instead of red.

If testAssertionsEnabled fails, you did not follow the instructions in the Getting Started guide. Getting Started step 2 has setup you must perform before using Eclipse.
Implement calculatePolygonSidesFromAngle
This does the inverse of the last function; again, use the simple formula. However, make sure you correctly round to the nearest integer. Instead of implementing your own rounding, look at Java’s java.lang.Math class for the proper function to use.
Implement drawRegularPolygon
Use your implementation of calculateRegularPolygonAngle. To test this, change the main method to call drawRegularPolygon and verify that you see what you expect.

Calculating headings

Implement calculateHeadingToPoint
This function calculates the parameter to turn required to get from a current point to a target point, with the current direction as an additional parameter. For example, if the turtle is at (0,1) facing 30 degrees, and must get to (0,0), it must turn an additional 150 degrees, so calculateHeadingToPoint(30, 0, 1, 0, 0) would return 150.0.
Implement calculateHeadings
Make sure to use your calculateHeadingToPoint implementation here. For information on how to use Java’s List interface and classes implementing it, look up java.util.List in the Java library documentation. Note that for a list of n points, you will return n-1 heading adjustments; this list of adjustments could be used to guide the turtle to each point in the list. For example, if the input lists consisted of xCoords=[0,0,1,1] and yCoords=[1,0,0,1] (representing points (0,1), (0,0), (1,0), and (1,1)), the returned list would consist of [180.0, 270.0, 270.0].

Problem 11: Personal art

Implement drawPersonalArt
In this function, you have the freedom to draw any piece of art you wish. Your work will be judged both on aesthetics and on the code used to draw it. Try to utilize helper methods, loops, etc. rather than simply listing forward and turn commands.

For drawPersonalArt only, you may also use the color method of Turtle to change the pen color. You may only use the provided colors.

Here are some examples of the kinds of images you can generate procedurally with turtle graphics, though note that many of them use more commands than what we’ve provided here. Modify the main method to see the results of your function.

Submitting

Make sure you commit AND push your work to your repository on Athena. We will use the state of your repository on Athena as of 10:00pm on the deadline date. When you git push, the continuous build system attempts to compile your code and run a subset of the autograder tests. You can always review your build results at didit.csail.mit.edu.

Didit feedback is provided on a best-effort basis:

There is no guarantee that Didit tests will run within any particular timeframe, or at all. If you push code close to the deadline, the large number of submissions will slow the turnaround time before your code is examined.
If you commit and push right before the deadline, the Didit build does not have to complete in order for that commit to be graded.
Passing some or all of the public tests on Didit is no guarantee that you will pass the full battery of autograding tests — but failing them is almost sure to mean lost points on the problem set.