Due: Tuesday, February 7, 2017, 11:59 pm

What is a Shape?

The purpose of this project is to give you chance to break down simple problems (such as drawing a logo) into precise steps that solve the problem (draw the logo). In computer science speak, you will be developing algorithms. In this case you will write your algorithms as sequences of Python turtle commands that make the turtle draw complicated shapes for you.

Tasks

1. If you haven't already set yourself up for working on the project, then do so now.
   1. Mount your directory on the Personal server.
   2. Open the Terminal and navigate to your Project1 directory on the Personal server.
   3. Open TextWrangler. If you want to look at any of the files you have already created, then open those files.
2. Invent a shape, such as a cross, or an L or a simple chair. The next instruction is to write Python code to make the turtle draw the shape, so keep the shape fairly simple.

3. Create a file called shapeA.py in your Project1 directory. It should follow the same basic format as simple_turtle.py, so make sure the first and last lines in shapeA.py are the same as the first and last lines in simple_turtle.py. Between those lines, put the turtle commands to draw the shape you just invented. Run the program (i.e. type python shapeA.py in the terminal) and take a picture of the shape (i.e. Shift-Cmd-4).

   Include a picture of this shape in your write-up. This is required image 1

4. Repeat your process for a second shape, putting its code in a file named shapeB.py.

   Include a picture of the new shape in your write-up. This is required image 2.

5. Make a new Python file called shapes.py. As the name implies, this file will have code that draws more than one shape. We will begin by putting the shapeA and shapeB code into it as functions. We will then create a shapeC function that is composed of shapes A and B.
   1. Create two functions shapeA and shapeB. A function is simply a collection of Python commands with a label, just like our lists above. For example, I could make a function that draws a triangle by use the following code.

      	def triangle():
      	   forward( 100 )
      	   left( 120 )
      	   forward( 100 )
      	   left( 120 )
      	   forward( 100 )
      	   left( 120 )
      

      Note how the commands that make up the function are all tabbed in the same amount relative to the function definition. That is how you tell Python those commands are part of the function triangle. In Python the visual indentation of the text has the semantic meaning that the indented text is part of the function labeled as triangle. Not all programming languages give semantic meaning to the visual organization of the code, but Python does. That means that the way Python code looks also has something to do with how it works.

      Your shapeA and shapeB functions should draw the shapeA and shapeB shapes you defined in the prior step. You can copy and paste that code into the functions, tabbing in the code appropriately.

   2. Invent a shape C that is composed of shapeA and shapeB. The code for shapeC will call the functions for shapeA and shapeB. You can call a function in Python by using the function name followed by parentheses. For example, the following code creates a function called shapeC that does three things. First it executes the code in the shapeA function, then it moves the turtle forward by 100 pixels, then it executes the code in the shapeB function.

      	def shapeC():
      	   shapeA()
      	   forward( 100 )
      	   shapeB()
      
      	shapeC()
      	raw_input('Enter to continue')
      

   3. At the end of your shapes.py file, put a call to the shapeC function, as in the example above. That will tell Python to call the function when you run the shapes.py program. Note that the call to shapeC is not tabbed in and will therefore be executed by Python when you execute your file. Recall that the role of the final line of code is to keep the turtle window open until you are ready to let it go away. It does so by preventing the program from ending without you pressing Enter/Return.
   4. Test your code (i.e. run it by typing python shapes.py in the Terminal). If it doesn't work, then carefully read any error message. It should direct you to the line of the file that failed to work. Some common errors include the following.
      • Syntax error: Forgetting the colon at the end of a function definition line
      • Syntax error: Forgetting to pair all parentheses (Python really hates it when you have more left/open parentheses than right/close parentheses)
      • Typo: Misspelling a turtle command or function name
      • Tabbing/White Space error: Having inconsistent tabbing. All code should be lined up carefully. The main code should have no spaces or tabs at the beginning of the line. The code "inside" a function definition should be tabbed in once, with all lines tabbed in the same amount.

        Note that Python considers tabs and white space to be different things, which is sometimes hard to debug because all of your code looks correct. If you think your code is correct, then select all of your code (cmd-A) and then choose Text::Entab in TextWrangler to convert all of your white space to tabs or Text::Detab to convert all of your white space to spaces. That will generally correct the problem if the error is mis-matched white space.

6. The final task is to make your shape-drawing functions more flexible by enabling the caller to specify how many pixels forward to travel. For example, consider the triangle-drawing function above. Each triangle edge is always 100 pixels.

   It would be better to have a triangle that could be drawn many different sizes. In other words, instead of using a raw, or hard-coded number to indicate the forward distance, it would be better to have the distance be adjustable. In programming terminology, this means we would like to use a variable for the distance instead of a hard-coded number. You can create parameters for functions that allow you to pass information into a function. In the function definition, you put a list of variable names inside the parentheses. You can then use the parameter variables within the function.

   When you call a function with parameters, you put the value of the parameters in the parentheses. For example, the following code defines a triangle and then calls it with two different values.

   	def triangle( distance ):
   	   forward( distance )
   	   left( 120 )
   	   forward( distance )
   	   left( 120 )
   	   forward( distance )
   	   left( 120 )
   
   	triangle( 50 )
   	triangle( 100 )
   

   1. Create a shapeD function that draws a shape (like shapeA or shapeB) and uses one or more variables in the forward commands, just like the triangle function above.
   2. Then write a shapeE function that calls the shapeD function multiple times with different parameters. At the end of your file, make sure to put a call to shapeE.
   3. Test your code. This means run it and make sure it works. If it doesn't work, then carefully read any error message. It should direct you to the line of the file that failed to work. Some common errors include
      • Syntax error: Forgetting the colon at the end of a function definition line
      • Syntax error: Forgetting to pair all parentheses (Python really hates it when you have more left/open parentheses than right/close parentheses)
      • Typo: Misspelling a turtle command or function name
      • White Space error: Having inconsistent tabbing. All code should be lined up carefully. The main code should have no spaces or tabs at the beginning of the line. The code "inside" the function definition should be tabbed in once, with all lines tabbed in the same amount.
      • Argument/Parameter Mismatch error: Having a mismatch between the number of values passed in to a function when it is called and the number of parameters that function has defined (e.g. the triangle function needs 1 parameter, so both lines below will cause errors because the actual function wants one parameter).

        	triangle()
        	triangle( 4, 3 )
        

   Include a picture of the new shape in your write-up. This is required image 3.

Extensions

Each assignment will have a set of suggested extensions. The required tasks constitute about 73% of the assignment, and if you do only the required tasks, do them well, and have a well-written write-up you will earn a B. To earn a higher grade, you need to undertake one or more extensions. The difficulty and quality of the extension or extensions will determine your final grade for the assignment. One complex extension, done well, or 2-3 simple extensions are typical.

The following are a few suggestions on things you can do as extensions to this assignment. You are free to choose other extensions.

• Create some additional functions that draw different shapes. Create a function that calls all of them to make an interesting graphic.
• Write a function that will draw an N-gon. It should take in the distance of a side and the number of sides.
• Figure out how to have a set of instructions repeat a certain number of times.
• Build a hierarchy of functions. For example, suppose you already have a function shapeG that draws one shape. Make a new function shapeH that calls function shapeG multiple times, but in different places, so that you get multiple shapes. Then make another function shapeJ that calls shapeH multiple times. Go up one more level of complexity.

Turn in your code

You will turn in your code by putting it in a directory in the Courses server. On the Courses server, you should have access to a directory called CS151, and within that, a directory with your user name. Within this directory is a directory named private. Files that you put into that private directory you can edit, read, and write, and the professor can edit, read, and write, but no one else. To hand in your code and other materials, you will create a new directory, such as Project1, and then copy your code into the project directory for that week. Note: This directory will not be available during lab, but will become available during the week before the projects are due.

As with the Personal server, there are two ways to mount the appropriate directory.

• Option 1: Load the root server directory and navigate to your directory.

  You can mount the Colby fileserver root directory by going to the Finder and typing cmd-K, or selecting 'Connect To Server...' from the Go menu. It will bring up a dialog box, into which you want to enter the following.

  Mac:	smb://filer.colby.edu/Courses
  Windows:	\\filer.colby.edu\Courses

  Then click on the CS151 directory, and then your hand-in directory (it will have your username as its name).

• Option 2: Mount your directory directly.

  You can mount your personal directory explicitly using the the following path in the 'Connect To Server...' dialog.

  smb://filer.colby.edu/Courses/CS151/<username>

Turn in your code by copying your entire Project1 directory from your Personal server to the Courses server. The easiest way to do this is to drag and drop the folder from one Finder (one open to Personal) to another (one open to Courses).

Write about the project on the wiki

In lab, you made a new wiki page for your assignment. Put the label cs151s17project1 in the label field on the bottom of the page. But give the page a meaningful title (e.g. Ying's Project 1).

In general, your intended audience for your write-up is your peers not in the class. Your goal should be to be able to use it to explain to friends what you accomplished in this project and to give them a sense of how you did it. Follow the outline below.

• A brief summary of the project, in your own words. This should be no more than a few sentences. Give the reader context and identify the key purpose of the assignment.
• A description of your solution to the tasks, including any images you created. This should be a description of the form and functionality of your final code. You may want to incorporate code snippets in your description to point out relevant features. Note any unique computational solutions you developed. Code snippets should be small segments of code--usually less than a whole function--that demonstrate a particular concept. If you find yourself including more than 5-10 lines of code, it's probably not a snippet. You should not include all your code in the writeup.
• A description of any extensions you undertook, including images demonstrating those extensions. If you added any modules, functions, or other design components, note their structure and the algorithms you used.
• A brief description (1-3 sentences) of what you learned.
• A list of people you worked with, including TAs, and professors. Include in that list anyone whose code you may have seen, such as those of friends who have taken the course in a previous semester.
• Don't forget to label your writeup so that it is easy for others to find. For this lab, use cs151s17project1

© 2017 Ying Li. Page last modified: .