This worksheet corresponds to material from lectures 1-3, which contained the Python tour and a bit of object-oriented programming. Thus it contains:
n
always prepares for Homework n
)These things might be helpful while working on the problems. Remember that for worksheets, we don't strictly limit what resources you can consult, so these are only suggestions.
Suppose you have a list of integers. Even if the list is not entirely in increasing order, there are sometimes parts of the list that are in increasing order.
For example, consider L = [1,21,4,17,38,39,35,22,0,6,2,5]
*. The list is not in increasing order, but the first two elements (i.e. L[0:2]
or [1,21]
) are in increasing order. Also, if you take the slice L[2:6]
, which is [4,17,38,39]
, that is in increasing order.
Let's call a slice of a list that is in increasing order an increasing run. A given list of integers can have many increasing runs.
In the example given above, the longest increasing run you can find in L
is L[2:6]
, and it has length 4.
Write a function IRL(L)
that takes a list L
and returns the length of the longest increasing run within L
. In order for that to make sense, you should assume the elements of L
can be compared to one another using >
and <
and ==
, but it shouldn't matter exactly what their types are. If it helps in thinking about the problem, you could imagine they are integers.
Special cases (not necessarily requiring special handling, but explained here to clarify the extremes):
L
is empty, the function should return 0L
is in decreasing order, the function should return 1 because a slice with one element can be considered to be in "increasing order", and that would be the longest increasing run.* The sample list L
shown above had a typo which was corrected on Jan 16.
Here are some sample outputs:
IRL([40, 1, 63, 20, 53, 9]) # [1,63] and [20,53] are the longest, each has length 2
IRL([22, 40, 47, 46, 26, 45, 25, 30, 47, 40]) # [22,40,47] and [25, 30, 47] are the longest
IRL([78, 26, 1, 20, 72, 19, 44, 50, 59, 67]) # [19, 44, 50, 59, 67] is the longest
IRL([1,2,3,4,5,6,7,8]) # The entire list, of length 8, is increasing!
IRL([]) # no elements = no increasing runs = max increasing run length 0
IRL([275]) # [275] is the longest increasing run
IRL([10,8,6,4,2]) # [10] and [8] and [6] and [4] and [2] are the longest, each has length 1
Hint: Here is one possible strategy: Use a for loop to scan through the list, keeping track of the current element and the previous one. As you go, make note of how many successive elements have been increasing. Use another variable to hold the largest number of increasing elements seen so far, and update it as needed on each iteration.
def IRL(L):
"""
this function takes a list L and returns the length of the longest increasing run
"""
long_run = 0 #variable to keep track of the longest run
if len(L) == 0: #if list is empty, return 0
return long_run
run = 1 #keep track of the current run
for i in range(1,len(L)):
if L[i] >= L[i-1]: #compare consecutive elements
run += 1
else:
run = 1
if run > long_run: #if current run is longer than longest, update accordingly
long_run = run
return long_run
Zitterbewegung is a German word meaning "jittery motion".
This is an exercise in object-oriented programming.
Make a class ZBPoint
that stores a point (x,y)
in the plane with integer coordinates.
The constructor should take (x,y)
as arguments and store them as attributes.
Add a __str__
method Printing an instance of this class should produce a nice string like
ZBPoint(17,-2)
Also include a method .jitter()
that will move the point up, down, left or right by one unit. It should be a mutation (modifying the coordinates, not returning anything). The direction should be chosen at random (e.g. using random.choice
or random.randint
from the Python random module that you can import with import random
.)
The code below demonstrates how you would use this class to create a point at (20,22)
and then let it jitter about for 30 steps, printing the location each time.
P = ZBPoint(20,22)
for _ in range(30):
print(P)
P.jitter()
import random
class ZBPoint:
"""class representing a point on the plane with integer coordinates"""
def __init__(self,x,y):
"""Initialize new point instance"""
self.x = x # make a new attribute (self.x)
self.y = y # make a new attribute (self.y)
def __str__(self):
"""
method for printing an instance of the class as a string
"""
return "ZBPoint({},{})".format(self.x, self.y)
def jitter(self):
"""randomly move the point left/right/up/down by 1 unit"""
direction = ['u','d','l','r'] #list of possible directions to move
move = random.choice(direction) #randomly choose one direction
if move == 'u':
self.y += 1 #move the point up (y-coord +1)
elif move == 'd':
self.y -= 1 #move the point down (y-coord -1)
elif move == 'l':
self.x -= 1 #move the point left (x-coord -1)
else:
self.x += 1 #move the point right (x-coord +1)
In this problem it's important to use a big terminal window, at least 80 characters wide and 40 lines tall.
Write a program circle.py
that takes one command line argument, r
, and then prints 40 lines of text, each containing 80 characters. The output should make a picture of a circle, using characters as pixels that can be either "on" (@
character) or "off" (` character). When
r=20the circle should be slightly too big to fit in the block of text, and when
r=1` it should be nearly too small to have any empty space inside.
For example, here is possible output for r=5.
And here is possible output for r=15:
This exercise is deliberately a little vague about how to go about this, but here is a hint: Each character you print corresponds to a certain point (x,y) in the plane, with character 40 on line 20 corresponding to (20,20). The factor of 2 in the y coordinate is because haracters in a terminal are usually twice as tall as they are wide. Calculating the coordinates of the next character to be printed inside of the main loop will be useful. Then, how would you decide whether to print a " "
or a "@"
?
# Solution by Jennifer Vaccaro
import sys
"""to determine where to print the '@' symbol, create two circles (one with radius slightly
larger, the other with radius slightly smaller) that what the user inputs, loop over the
x- and y-coordinates, and print '@' whenever the point in the plane falls between the circles"""
r = int(sys.argv[1])
outer_rad1 = r*1.2
inner_rad1 = r*0.9
for y in range(-20,21): #loop over y-coordinates
for x in range(-40,41): #loop over x-coordinates
x = x/2 #ensure the x-coordinates fall in the same range as the y-coordinates
dist = (x**2 + y**2)**0.5 #distance from the point to the origin
if dist>inner_rad1 and dist<outer_rad1:
print("@",end="") #print '@' if the point falls within the inner and outer circles
else:
print(" ",end="")
print() # Make a newline
Here's a solution to the bonus problem (using soft edges):
# Solution by Jennifer Vaccaro
import sys
r = int(sys.argv[1])
outer_rad1 = r*1.2
inner_rad1 = r*0.9
outer_rad2 = r*1.4
inner_rad2 = r*0.8
outer_rad3 = r*1.6
inner_rad3 = r*0.7
for y in range(-20,21):
for x in range(-40,41):
x = x/2
dist = (x**2 + y**2)**0.5
if dist>inner_rad1 and dist<outer_rad1:
print("@",end="")
elif dist>inner_rad2 and dist<outer_rad2:
print("*",end="")
elif dist>inner_rad3 and dist<outer_rad3:
print(".",end="")
else:
print(" ",end="")
print() # Make a newline
This builds on the ZBPoint
class from problem 2.
Suppose you start a ZBPoint
at (0,0)
and then repeatedly call the method .jitter()
until the first time it returns to (0,0)
. The number of steps it takes to do this is called the recurrence time. It's possible that this may never happen, but that is very unlikely. (It can be shown that the probability it will eventually return to (0,0)
is 100%.)
Write a program that runs this process 1000 times and records the recurrence times. (It's OK to give up on a point if it's taken 200 steps and hasn't yet returned to (0,0)
.) The program should then print a table showing how many times each recurrence time was seen (a histogram). Here's an example of what it might look like:
Ran 1000 random walks starting at (0,0). Of these:
235 returned to (0,0) after 2 steps
76 returned to (0,0) after 4 steps
51 returned to (0,0) after 6 steps
31 returned to (0,0) after 8 steps
24 returned to (0,0) after 10 steps
17 returned to (0,0) after 12 steps
18 returned to (0,0) after 14 steps
7 returned to (0,0) after 16 steps
6 returned to (0,0) after 18 steps
13 returned to (0,0) after 20 steps
7 returned to (0,0) after 22 steps
8 returned to (0,0) after 24 steps
9 returned to (0,0) after 26 steps
4 returned to (0,0) after 28 steps
2 returned to (0,0) after 30 steps
5 returned to (0,0) after 32 steps
3 returned to (0,0) after 34 steps
5 returned to (0,0) after 36 steps
2 returned to (0,0) after 38 steps
2 returned to (0,0) after 40 steps
3 returned to (0,0) after 42 steps
2 returned to (0,0) after 44 steps
1 returned to (0,0) after 46 steps
4 returned to (0,0) after 48 steps
2 returned to (0,0) after 50 steps
1 returned to (0,0) after 52 steps
7 returned to (0,0) after 54 steps
1 returned to (0,0) after 58 steps
3 returned to (0,0) after 60 steps
4 returned to (0,0) after 62 steps
4 returned to (0,0) after 64 steps
2 returned to (0,0) after 66 steps
1 returned to (0,0) after 68 steps
2 returned to (0,0) after 70 steps
1 returned to (0,0) after 72 steps
3 returned to (0,0) after 76 steps
2 returned to (0,0) after 78 steps
1 returned to (0,0) after 80 steps
2 returned to (0,0) after 82 steps
1 returned to (0,0) after 84 steps
2 returned to (0,0) after 86 steps
2 returned to (0,0) after 92 steps
2 returned to (0,0) after 94 steps
1 returned to (0,0) after 96 steps
1 returned to (0,0) after 98 steps
2 returned to (0,0) after 106 steps
1 returned to (0,0) after 108 steps
2 returned to (0,0) after 110 steps
4 returned to (0,0) after 116 steps
2 returned to (0,0) after 118 steps
1 returned to (0,0) after 122 steps
1 returned to (0,0) after 124 steps
1 returned to (0,0) after 126 steps
1 returned to (0,0) after 128 steps
3 returned to (0,0) after 130 steps
1 returned to (0,0) after 134 steps
2 returned to (0,0) after 136 steps
2 returned to (0,0) after 138 steps
1 returned to (0,0) after 142 steps
1 returned to (0,0) after 144 steps
2 returned to (0,0) after 146 steps
1 returned to (0,0) after 156 steps
1 returned to (0,0) after 158 steps
1 returned to (0,0) after 160 steps
3 returned to (0,0) after 162 steps
1 returned to (0,0) after 166 steps
1 returned to (0,0) after 174 steps
2 returned to (0,0) after 178 steps
1 returned to (0,0) after 180 steps
3 returned to (0,0) after 184 steps
1 returned to (0,0) after 190 steps
2 returned to (0,0) after 198 steps
376 didn't return to (0,0) after 200 steps
# Based on solution prepared for MCS 275 Spring 2023
"""We want to create 1000 ZBPoints, jitter each point until either the point returns
to the origin (0,0) or the point has jittered more than 200 times; we'll use a dictionary
to keep track of the number of points that return to the origin after a certain number of
steps."""
#initialize a dictionary to count the number of points that returned to the origin
#after 1 step, 2 steps, 3 steps, etc.
results_dict = {i:0 for i in range(202)}
# Run 1000 trials, creating a new ZBPoint each time
for trial in range(1000):
point = ZBPoint(0,0)
point.jitter()
recurrence_time = 1
while point.x != 0 or point.y != 0:
point.jitter()
recurrence_time += 1
if recurrence_time > 200:
break # Stop trying to jitter if we've tried more than 200 times
# Record the result in the dictionary
results_dict[recurrence_time] += 1
print("Ran 1000 random walks starting at (0,0). Of these: ")
for key, value in results_dict.items():
if key <= 200: # Consider the 200 value separately because it needs a different message
if value != 0:
# Use :3d for alignment - ensures that the number takes up 3 spaces.
print("{:3d} returned to (0,0) after {} steps".format(value,key))
else:
print("{:3d} failed to return to (0,0) after 200 steps".format(value))
I recommend you don't work on these unless you finish the other problems and have extra time in lab or want an additional challenge on your own time.
This doesn't have a solution per se, but it asks you to evaluate and possibly improve your solution to problem 1.
There are lots of ways to solve problem 1, and some are more efficient than others. That is, if L
is very long, there are some approaches where IRL(L)
will return quickly, while a valid but different way of writing the function would take a very long time to return an answer.
Try your IRL
function on a list of 10,000 or 100,000 integers in some sort of random order. An efficient solution should handle this very quickly (less than a second). If yours takes much longer, can you think of ways to make it faster (but still correct)?
The code below could be used for the necessary testing, if you add it to a file that contains your IRL
function.
import random
import time
test_length = 100_000
test_input = list(range(test_length))
random.shuffle(test_input)
t0 = time.time()
k = IRL(test_input)
delta_t = time.time() - t0
print("IRL for a list of {} random integers returned {} after {:.2f} seconds".format(
test_length,
k,
delta_t
))
Make a program circle2.py
so that it makes circles with softer edges, like this:
Here's a solution that uses @
, *
, or .
depending on how close each position is to the desired radius. This gives the type of "softer" edge seen above.
# Solution by Jennifer Vaccaro
import sys
r = int(sys.argv[1])
outer_rad1 = r*1.2
inner_rad1 = r*0.9
outer_rad2 = r*1.4
inner_rad2 = r*0.8
outer_rad3 = r*1.6
inner_rad3 = r*0.7
for y in range(-20,21):
for x in range(-40,41):
x = x/2
dist = (x**2 + y**2)**0.5
if dist>inner_rad1 and dist<outer_rad1:
print("@",end="")
elif dist>inner_rad2 and dist<outer_rad2:
print("*",end="")
elif dist>inner_rad3 and dist<outer_rad3:
print(".",end="")
else:
print(" ",end="")
print() # Make a newline