You also shouldn't try to mention INT_MAX, negative zero, rounding error, or other computer science topics which do not exist in mathematics.
negative zero isn't in any math I know of. It is only in obsolete computer science though.
> The right answer they were looking for was 3, not 3.0. Adding that .0 implies a precision which is not correct.
In contemporary mathematics, 3 is 3.0 . Both 3 and 3.0 belong to the set of integers. There is no additional precision being demonstrated by adding a 0 at the end of the 3. This is simple notation, not refering to a new concept.
We definitely spent more time discussing different kinds of infinity than we did discussing rounding error!
I can believe that the situation might be different in "applied mathematics" or definitely in "engineering mathematics" - but at least at Berkeley, the latter degree is in the College of Engineering, not under the Math Department at all.
>>> a = 3.0
>>> b = 3
>>> type(a) == type(b)
False
The right answer they were looking for was 3, not 3.0. Adding that .0 implies a precision which is not correct. They weren't looking to see if you knew the arithmetic with that question, they wanted you to show you understood what they meant by "whole number" and understand you can't just leave arbitrary precision after rounding. You didn't give the right answer and apparently kept complaining about it instead of trying to figure out why you were wrong to the point they threatened suspension. I imagine your complaints based on your assumption you couldn't be wrong were causing quite a distraction.For example, 10 / 3 = 3.333... right? We're then asked to round to the nearest whole number, and the answer should be 10 / 3 = 3. It is not correct to then say 10 / 3 = 3.0, because that is just wrong.
I'd end up siding with the teacher on this one. Just acknowledge you didn't understand what they were looking for and do better next time.
If you round 3.05 down to 3, 3.00 is not arbitrary precision, its explicit precision that's reflective of the rounding operation you did. I wasn't claiming that `type(3.0) == type(3)`. I was claiming that:
>>> round(3.0) == 3
True
And that such a representation was valid within the context of the question. This was long before I was wise enough to understand that sir, this is a public school, just do what the book says and don't make me talk with the students more than I need do.10 / 3 != 3.000000000000000000000000 no matter how many times you refute it. You should really learn to accept it and continue on and look deeper inside yourself into this. It's sad you still haven't learned this lesson from elementary education. Maybe they should have suspended you.
In no world does 10 / 3 = 3.0. This is just a falsehood as much as 2 + 2. = 5. I don't care about your large values of 2.
Teachers not having the time to muse about such ideas and instead needing to package everything into a presentation appropriate for an entire room full of children is one of the more obvious failure modes of industrialized education.
10 / 3 will never = 3.0.
It is sad you still haven't learned this lesson after many decades.
I hope I'm never on a bridge you build or plane built to the specs you write if you truly think 10 / 3 = 3.00000.
It is perfectly reasonable to define 3: ℕ = succ(succ(succ(zero))). It's also perfectly reasonable to define 3: ℝ as the image of succ(succ(succ(zero))): ℕ under the canonical embedding. Or you can define 3: ℚ with the obvious element. You can also define 3.0: ℚ or 3.0: ℝ as the obvious elements. If you were really a deviant, I suppose you could even define 3.0: ℕ, and people would roll their eyes, but everyone would understand you. Obviously, there are reasonable ways to define things so that `3 = 3.0` is a meaningful sentence (typechecks) and also literally true.
Again, different conventions are used in different contexts. The "user" of mathematics should pick the conventions and notations that make sense for what they're doing to communicate what they're trying to say. That itself is an important lesson. The sigfig convention you learned in middle school isn't the word of God.
Not being aware of these things to be capable of musing about them is I suppose another issue with our education system.
Similarly, we calculated those ± values using the chain rule/uncertainty propagation, not with the simple decimal place rules you learn as a kid. I assume no one serious uses the child rules when CAD software can just as easily use the real ones.
> we calculated those ± values using the chain rule/uncertainty propagation
Yes, that's common in detailed engineering documents. It still doesn't change the fact if I ask for 3.000 and you give me 3.001 I'm not going to consider that in-spec despite not giving a ±. It's assumed if I wrote it out to that decimal point I'm caring about that level of precision.
> Using decimal points to indicate uncertainty was not a thing I believe I did after high school
Well, I'd imagine since the topic of lesson was understanding whole numbers at a basic level this was probably a high school or lower class, probably more like elementary or middle school. You know, in that time when you did use decimal places to indicate precision. This person wasn't talking about losing points at their engineering job.
>
> 10 / 3 will never = 3.0.
You should read what they wrote again. They wrote with `≈`, which is a different operator than `=`.
What they wrote is correct.
.
> It is sad you still haven't learned this lesson after many decades.
>
> I hope I'm never on a bridge you build or plane built to the specs you write if you truly think 10 / 3 = 3.00000.
HN doesn't allow this sort of behavior.
Math terms like "whole number" are not defined in terms of the behavior of computer programming languages.
In math, not only are 3.0 and 3 the same thing, but also, so is 2.9999999...
.
> They weren't looking to see if you knew the arithmetic with that question, they wanted you to show you understood what they meant by "whole number" and understand you can't just leave arbitrary precision after rounding.
Can you show any math reference that supports this viewpoint? This goes against my college mathematics training.
.
> You didn't give the right answer
According to mathematics, 3.0 and 3 are the same thing (and so is the Roman numeral III, and so on.) So is 6/2.
It is deeply and profoundly incorrect to treat an answer as incorrect because the mantissa was written out.
The teacher is simply incorrect, as are you.
.
> Just acknowledge you didn't understand what they were looking for and do better next time.
If a teacher asks "what is the country north of Austria," in an English speaking school, and you write "Germany," and the teacher says "no, it's Allemande," they're just incorrect. It doesn't matter if the teacher is French. There are only two ways to look at this: either the correct answer is in the language of the school, or any international answer is acceptable.
A normal person would say "oh, ha ha, Germany and Allemande are the same place, let's just move forwards."
A person interested in defeating and winning, instead of teaching, might demand that the answer come in in some arbitrary incorrect format that they expected. That's a bad teacher who doesn't need to be listened to.
Yes, we know there's also some kid who is explaining to just do as teacher instructs, but no, we're there to learn information, not to learn to obey.
> The word integer comes from the Latin integer meaning "whole" or (literally) "untouched", from in ("not") plus tangere ("to touch"). "Entire" derives from the same origin via the French word entier, which means both entire and integer.[9] Historically the term was used for a number that was a multiple of 1,[10][11] or to the whole part of a mixed number.
https://en.m.wikipedia.org/wiki/Integer
The question was to understand the idea of a "whole number" aka an integer.
The takeaway from trying to really nail down a definition of "integers" (or anything, really) is going to be something along the lines of "if it quacks like a duck up to unique isomorphism, it's a duck". The encoding is not important and one frequently swaps among encodings when convenient. In any case, no one who knows any math is going to say to a child that 3 and 3.0 aren't interchangable outside of some extremely specific contexts. In fact that's not even encoding: it's notation. They can be literally equal, not just equivalent. Those particular contexts aren't ordained, and e.g. propagation of uncertainty is "better" than significant figures if you're doing engineering anyway.
The exact context was given. They wanted only whole numbers.
> Writing something like '10/3=3' is likely to trigger the mathematicians
Sure, when lacking the context of all answers should be rounded to the nearest whole number. But that was the context, and it's astounding so many people with alleged math backgrounds arguing things like intergers aren't a thing to understand.
Being equal to 3, 2.9999... is also a whole number.
Teaching to use '=' in a statement like '10/3=3' is an example of where teachers don't know math in depth and make errors about details that are actually important/later cause confusion. 10/3 is not equal to 3. '=' doesn't mean "answer". Then not accepting 3.0 which is equal to 3 just layers on that confusion. '=' is transitive. If a=b and b=c, then a=c.
Saying 3.0≠3 is a subtlety you really only get into in math when defining these things, and then you immediately redefine them so that 3.0=3 and you don't have to think about it again.
But the question wasn't testing that you knew how to divide and round. The question was testing if you understood what the teacher was trying to teach about whole numbers, integers, rational numbers, real numbers, etc.
6/2 as written is not an integer. It is not a whole number. The value it represents can be written as a whole number, I fully agree, but as written it itself is not a whole number. Whole numbers are the set of numbers Z including -3, -2, -1, 0, 1, 2, 3, 4,... I doubt any math teacher, upon teaching "what is a whole number", draws a number line and proceeds to label it -3.999, -6/2, -12/6, -5/5, 0, 5/5, 12/6, 6/2, 3.999..., and on.
The notation was the key part of the question and was a key part of the answer.
The teacher wasn't looking for a value (which is what you're so focused on looking at), they were looking for a notation, a format.
6/2 is a whole number. 6/2 = 3. 3 is a whole number. They are equal. Usually, they are the exact same mathematical object. It is not merely that they share properties. They are literally definitionally the exact same thing (the same set in ZFC). "n is a whole number" is a proposition. It is true for n=6/2.
If a teacher is teaching that 6/2 is not an integer, unless they are in the middle of constructing the rationals and need to make a distinction between integers and equivalence classes of pairs of integers, then they are wrong. The very first thing you do after you're forced to make that distinction is you make it go away. They shouldn't be teaching the student to hyperfocus on a specific notation or format. That's a bad lesson to teach, and is something a real teacher will need to fix later. Actual mathematics professors are happy to let you write "let <christmas tree>∈ℝ". An intro proofs professor will definitely put something like "-3.999..., -6/2, -12/6, -5/5, 0, 5/5, 12/6, 6/2, 3.999..." on a number line to illustrate the point that these are just different ways to write the same thing. Fluidity in switching through and following different notations without getting distracted is a centrally important mathematical skill.
Finally, you're starting to understand the context of the question at hand.
I'm also happy you're starting to show you do understand there's a notational difference between 6/2 and 3. That the values are the same the notation is quite different, thus there are some differences. Not functionally, true, but notationally.
The notational difference was the point of this lesson. You may think it'll only be a barrier in the future to point it out like that (maybe it is!), but the notational difference was the lesson.
> Fluidity in switching through and following different notations
If you don't really have an understanding of the notations, you're going to have a hard time being fluid switching between them.
> An intro proofs professor
An intro proofs professor wasn't leading the lesson, it was probably an elementary or middle school math teacher. The point of the lesson is different, the context of the lesson is different.
In any context that a child is working in, 6/2 and 3.0 are a whole numbers. If the teacher says otherwise, they are wrong. Just because the teacher wants to teach a lesson doesn't mean that lesson is actually correct. The teacher is just confused.
If they weren't confused, it would be highly inappropriate to go into that level of detail with anyone other than a curious gifted kid that's asking questions that are years ahead of a normal curriculum. So much so that it's beyond the level of knowledge expected of a schoolteacher.
You also wouldn't mark it wrong because the entire point is to define things in a way that makes the distinction go away. Even after that distinction has been presented and is front-of-mind, you still generally write down whatever representative is convenient.
It's either literally wrong, philosophically/pedagogically wrong, or both.
Pretty sure all teachers I had even in elementary school studied at least high school level algebra. In middle school and above they all had masters or better in mathematics.
> the distinction is not relevant
> I highly doubt that the teacher was making that distinction, or even aware it exists
> the teacher was making a distinction that does not exist
The distinction both exists and does not exist. Incredible.
> it would be highly inappropriate to go into that level of detail
The detail of a thing that does not exist, right?
> it's beyond the level of knowledge expected of a schoolteacher.
Right, the teacher is wrong because you wouldn't expect the schoolteacher to be smart enough to be right about it.
There's similar logical snags when trying to define real numbers because technically you'll need distances which have to be rational because you don't have real numbers yet, but really you'd like distances to be real. It's not actually an issue though, and as far as everyone is concerned, distances are real.
Or you define things only up to unique isomorphism by their properties and wash your hands of the whole ordeal. The construction is merely to show that some object with those properties exists.
The teacher is wrong because if they are being pedantic about it to a child, they're a bad teacher. And they're missing the point.
I got threatened with suspension on protest once. It was about the meaning of a word, but still.
Luckily, I'm a university brat, so I just waited a couple days until my dad was keeping me at his office, then I wandered down the hall, and I asked some professors for a detailed and referenced way to push back. I brought candy and tums, because that's what professors want from children who can't bring beer.
About a week later, I went in with a 30 page computer printed essay. As a nine year old. It had six phone numbers in the back, four to PhDs, which could be called for further detail if needed. It was addressed to both the teacher and the principal.
An opening note was "please look into how Marilyn vos Savant was treated when she explained the Monty Hall problem, when considering whether teachers are permitted to threaten students for disagreeing politely. Are you really so afraid of being incorrect?," written by an internationally renowned mathematician.
I was carrying an etymological breakdown that to this day I can barely read, stretching all the way back to the hypothetical proto-indo-european roots.
Professors don't like kids being threatened.
I did not hear about that teacher doing that again while I was in that school.
As an example i once lost a mark on a math test because when rounding to the nearest whole number, i put 3.0 as the answer. Wrong. 3 is a whole number, 3.0 is not i was told, and threatened with suspension on protest. That kind of thing sticks with you.
I agree with your sentiment however, i just dont think its a powerful retort.