Sections
-
Are you looking for the list of section leader names and section times?
That information can be found on the Staff/SLs page instead.
Our sections are 50-minute discussions led by section leaders each week in which the SL and students work together to solve problems.
The complete list of section leaders, their contact information, and the time/place/room of each section can be found on the Staff page of this web site, though you should have already received an email containing that information for your section.
-
Week1 Thu 12:00 PM
Week2 Mon 12:00 PM
(do this before , 5pm!)
Section
(Week Wed - Week Fri):
![icon](images/progress.gif)
Loading ...
Week1 Mon 8:00 AM
Week 1 ( - ): No section
We will not hold section during the first week of the quarter.
Sections begin during Week 2.
No pre-section problems: There are no pre-section problems this week.
You will receive full section points by showing up and participating in your section.
No pre-section problems: There are no pre-section problems this week.
You will receive full section points by showing up and participating in your section.
Pre-section problems:
- Review question 18.10 (p814) - Write a representation of the given graph as a pair of sets, V and E.
- Review question 18.11 (p814) - Draw the adjacency list representation of the graph. Also draw an adjacency matrix representation of the graph.
Pre-section problem:
Solve the following review problem on paper (hand-written or printed) and bring your sheet of paper to your section:
-
Review Question 16.9 (p724).
Draw a picture of the binary search tree (BST) that would result after adding the strings listed in the problem.
Assume that the BST orders the strings based on alphabetical order, with names earlier in the alphabet being considered "less than" ones that come later in the alphabet.
Pre-section problem: Solve the following exercise problem on paper (hand-written or printed) and bring your sheet of paper to your section:
-
Exercise: diceSum
modified.
(This problem does not come from the textbook.)
Modify the diceSum
function we wrote in lecture so that it does not print duplicate combinations that are just rearrangements of each other.
The idea of this exercise is described on slide 10 of the "11-backtracking2" lecture slides.
You might need to add/modify the parameters of the helper function to implement this.
For example, the call of diceSum(3, 7)
should now print:
{1, 1, 5}
{1, 2, 4}
{1, 3, 3}
{2, 2, 3}
You can just write the answer by hand and make your best attempt to solve the problem.
If you want to actually code them up in Qt Creator, you can do so using our starter project ZIP below, but you don't have to do so.
If you type in your solution, you'll need to print it out or rewrite it by hand so that you can turn it in on paper at your section.
We do not accept them digitally such as by email.
Note that you do not need to write a complete program; just the relevant lines of code to answer the question.
(See detailed information below about pre-section problems.)
Pre-section problem: Solve the following exercise problem on paper (hand-written or printed) and bring your sheet of paper to your section:
-
Exercise 7.7: digitSum (p346).
Make the function handle negative numbers by returning the negation of the value that a positive number would return.
For example, digitSum(-123)
returns -6
.
You can just write the answer(s) by hand and make your best attempt to solve them.
If you want to actually code them up in Qt Creator, you can do so using our starter project ZIP below, but you don't have to do so.
If you type them in, you'll need to print them out or rewrite them out by hand so that you can turn them in on paper at your section.
We do not accept them digitally such as by email.
Note that you do not need to write a complete program; just the relevant lines of code to answer the question.
(See detailed information below about pre-section problems.)
Pre-section problem: Solve the following book exercise problem on paper (hand-written or printed) and bring your sheet of paper to your section:
-
Exercise 5.19: morse code (p258)
Assume that there already exists a function named readMorseCodeMap
that reads an input file of Morse code mappings and produces a Map<char, string>
from text characters to their Morse code equivalents. For example, the key 'A'
maps to ".-"
.
You should write the following function:
void toMorseCode(Map<char, string>& codeMap, string text)
Your function accepts the Map
described above, and a string to be converted, and should print out the Morse code equivalent of the given string to the console.
For example, if the string is "SOS TITANIC"
, you should print "... --- ... - .. - .- -. .. -.-."
(without the quotes).
Note that the string might contain some characters that are not uppercase A-Z letters (like spaces); just skip those characters.
For reference, our solution to this problem has 6 lines in the function body.
You can just write the answer(s) by hand and make your best attempt to solve them.
If you want to actually code them up in Qt Creator, you can do so using our starter project ZIP below, but you don't have to do so.
If you type them in, you'll need to print them out or rewrite them out by hand so that you can turn them in on paper at your section.
We do not accept them digitally such as by email.
Note that you do not need to write a complete program; just the relevant lines of code to answer the question.
(See detailed information below about pre-section problems.)
Pre-section problems: Solve at least one of the following two (2) book exercise problems on paper (hand-written or printed) and bring your sheet of paper to your section:
- Exercise 5.2: mean (Textbook page 247, PDF page 255)
- Exercise 5.11: reshape (Textbook page 253, PDF page 261)
You can just write the answer(s) by hand and make your best attempt to solve them.
If you want to actually code them up in Qt Creator, you can do so using our starter project ZIP below, but you don't have to do so.
If you type them in, you'll need to print them out or rewrite them out by hand so that you can turn them in on paper at your section.
We do not accept them digitally such as by email.
Note that you do not need to write a complete program; just the relevant lines of code to answer the question.
(See detailed information below about pre-section problems.)
Pre-section problems:
Each week you will complete short problem(s) from the book to turn in at your section.
Completing these problems each week becomes part of your "participation" score which is part of your grade.
Another part of your "participation" score is awarded for being present in your section and participating in the discussion.
You will not be graded on whether you have a perfect solution, but on whether you have demonstrated effort.
Therefore please show some work that demonstrates how you got the answer rather than just writing the answer by itself.
We will be somewhat lenient about exactly how the work is shown.
If you want credit for doing the problems, you must bring the solutions on paper, not email them digitally to your SL.
Also, you must bring them yourself, not have a friend bring them for you.
Pre-section problem solutions are not accepted late.
Our intention is that these problems would take no more than 15-20 minutes each week.
If you find yourself taking significantly more than this, you may stop your work and write that you worked for 20 minutes.
If you have made significant progress, we will still give you credit for your work even if you did not finish the problem(s).
This document and its content are copyright © Marty Stepp, 2015.
All rights reserved.
Any redistribution, reproduction, transmission, or storage of part or all of the contents in any form is prohibited without the authors' expressed written permission.