150 Problem Set 2
150 Problem Set 2
Problem Set 2
This second problem set explores mathematical logic. We've chosen the questions here to help you
get a more nuanced understanding for what frsttorder logic statements mean (and, importantly,
what they don't mean) and to give you a chance to practice your proofwriting. By the time you've
completed this problem set, we hope that you have a much better grasp of mathematical logic and
how it can help improve your proofwriting structure.
Because of the Dr. Martin Luther King, Jr. holiday, there are a few problems on this problem set
that reference concepts we will cover in Monday’s lecture. Those questions are clearly marked as
such, and anything that doesn’t explicitly warn about this can be completed purely using the material
up to and including the lecture when this problem set is released. If you’d like to get an early jump
on the remaining problems, visit the course website and check out the Guide to Negations and
Guide to FirsttOrder Translations, which will provide an overview of the relevant skills.
Before attempting this problem set, we recommend that you do the following:
• Familiarize yourself with the online Truth Table Tool and play around with it a bit to get a
feel for the propositional connectives.
• Read the online “Guide to Negations” and “Guide to FirsttOrder Translations” (either on
Monday, or when this problem set goes out if you want to get a jump on things).
• Read Handout #14, “FirsttOrder Translation Checklist,” to get a better sense for common
errors in frsttorder logic translations and how to avoid them. We will be running these
checklists on your translations, so please be sure to double-check your work before sub-
mitting!
This week’s checkpoint problem comes in the shape of a Google Form, which you can fnd online using
this link. Unlike the other assignments for this quarter, you will not submit this assignment on Gradet
Scope, and you’ll get feedback about incorrect answers as you go.
After you’ve written up a draft of your proofs, take a minute to read over them and apply the criteria from
the Proofwriting Checklist. Here are a few specifc things to watch out for:
• If you want to prove in part (ii) that a set T is a hereditary set, you need to prove the statement “ev -
ery element of T is a hereditary set.” That’s a universally-quantifed statement. If you’re proving it
via a direct proof, you’ll probably need to pick some arbitrary element x ∈ T, then prove that x is a
hereditary set by making specifc claims about the variable x. Read over your proof and make sure
that (1) you’ve introduced a new variable to refer to some arbitrarily-chosen element of T and that
(2) you’re making specifc claims about the variable x, rather than talking in general about how ele -
ments of T behave. You may need to introduce multiple variables in the course of your proofs.
• A common mistake we see people make when they’re just getting started is to restate defnitions in
the abstract in the middle of a proof. For example, we commonly see people say something like
“since A ⊆ B, we know that every element of A is an element of B.” When you’re writing a proof,
you can assume that whoever is reading your proof is familiar with the defnitions of relevant
terms, so statements like the one here that just restate a defnition aren’t necessary. Instead of restat -
ing defnitions, try to apply those defnitions. A better sentence would be something to the efect of
“Since x ∈ A and A ⊆ B, we see that x ∈ B,” which uses the defnition to conclude something about a
specifc variable rather than just restating the defnition.
• Although we’ve just introduced frst-order logic as a tool for formalizing defnitions and reasoning
about mathematical structures, the convention is to not use frst-order logic notation (connectives,
quantifers, etc.) in written proofs. In a sense, you can think of frst-order logic as the stage crew in
the theater piece that is a proof – it works behind the scenes to make everything come together, but
it’s not supposed to be in front of the audience. Make sure that you’re still writing in complete sen -
tences, that you’re not using symbols like ∀ or → in place of words like “for any” or “therefore,” etc.
10 / 11
A symmetric Latin square is a Latin square that is symmetric across the main diagonal (the one from the
uppertleft corner to the lowertright corner). That is, the elements at positions (i, j) and (j, i) are always the
same. For example:
1 2 3 4 5
4 2 3 1
1 2 3 2 4 5 3 1
2 3 1 4
2 3 1 3 5 2 1 4
3 1 4 2
3 1 2 4 3 1 5 2
1 4 2 3
5 1 4 2 3
Prove that in any n × n symmetric Latin square where n is odd, every number 1, 2, 3, …, n must appear at
least once on the main diagonal.
As a hint: split the Latin square into three regions – the main diagonal and the two regions above and below
the main diagonal. Then think about how often each element appears in each group.
Once you’ve written up a draft of your proof for this problem, try out the following exercise as a way of
checking your work. If you look at the sample Latin squares shown above, you can see that the result given
above is not true in the case where the Latin square isn’t symmetric, and it’s also not true in the case where
the square has even size. As a result, if your proof does not specifcally use the fact that the Latin square is
symmetric and does not specifcally use the fact that the Latin square has odd size, it has to contain an error
somewhere. Otherwise, you could change the setup to the problem and end up with a proof of an incorrect
result. (Do you see why this is?) So go back over your proof and ask yourself – where, specifcally, am I
making reference to the fact that the Latin square is symmetric? Where, specifcally, am I making reference
to the fact that the Latin square has odd size? And why would my proof break down if I eliminated either
of those references?
Going forward, this approach to checking your proofs – perturbing the starting assumptions and seeing
where your logic breaks down – is an excellent way to smoke out any underlying logic errors.
11 / 11