6 ms·
Easy divisibility is the reason why when we switched to metric, the one thing that didn't switch is time. Which means that, for example, converting from m/s to
by btilly 11y ago
Easy divisibility is the reason why when we switched to metric, the one thing that didn't switch is time. Which means that, for example, converting from m/s to km/h is a mess. (You have to multiply by 3.6, can you easily do that in your head?)
With a base 12 version of everything you would have 1/12 of a day being 2 hours, 1/144 of a day is 10 minutes, and 1/1728 of a day is 50 seconds. These units would give us both easy divisibility and are close enough to existing time units to make sense.
This change would mean we have to memorize a 12 times table rather than a 10 times table. But in base 10 a 10 times table has easy patterns for 1, 2, 5, 9 and 10. A 12 times table has repeating patterns for 1, 2, 3, 4, 6, 8, 9, 11 and 12. The result is that a 12 times table in base 12 is actually less work to memorize than a 10 times table in base 10.
In the long run this transition would be a clear win. But it isn't enough of one compared to the transition to ever make sense to initiate.
- dnautics 11y agodecimals cause huge problems for computers. How do you represent 0.6 as a floating point? In the long run, the correct solution is for everything to be binary.
- btilly 11y agoThis one I'm entirely unconvinced of. It is easier for the computer to adapt to us, rather than vice versa. And over time things get easier and easier for the computer, while staying the same for us. Which is why over time we wind up interacting with computers in ways that are more and more adapted to us rather than them. We already have acceptably good algorithms to convert to/from different representations, and roundoff errors are generally acceptable. (If they weren't, we wouldn't default to using floating point for most things.) Where precision matters, we have reasonably efficient implementations of exact integer arithmetic and exact fraction arithmetic. The performance hit from using these is less than the hit from using a high level language like Python versus a low-level language like C. The main challenge is getting programmers to use the right representation for the purpose that they are using it for. Which is mostly challenging exactly because floating point works so well in practice that it is easy not to learn what its limitations are.
- dnautics 11y agoyou can't use exact fraction arithmetic to take a square root, which comes up, you know, just a little bit, in physics. Of course this is a problem for binary representations, too, but you might as well not start out with an input that is already imprecise.
- lmm 11y agoOn the contrary, you might as well accept imprecision and work with the level of precision you need throughout - or, if you don't know or need to adjust it, work with a symbolic representation.
- btilly 11y agoEvery representation has its limits. :-) In physics it is uncommon to have exact measurements for much of anything except integers. In physics, measurement error is usually a bigger issue than roundoff errors from floating point, so the non-existence of an exact floating point representation of the stated measurement is a non-issue. In the real world, most cases that I'm aware of where we need exact base 10 calculations have to do with dealing with money in a single currency. You would be amazed how often square roots don't come up in this context! Fractions show up as soon as you start doing currency conversions. (In fact the Euclidean algorithm for finding the GCD is believed to have been first developed by merchants for exactly this problem.) They are easy to add to a programming language, but you'd only use them in contexts (like finance) where square roots make no sense. If you want to go beyond fractions to add square roots and so on, you can do algebraic numbers. This is a fairly specialized mathematical need, but Mathematica has done it perfectly well for decades. For arbitrary real numbers, we're sort of stuck. We can come up with representations that can cover any real number that we can talk about. But we can't take 2 arbitrary representations of a real number and in finite time decide whether or not they are actually the same number. That said, Mathematica again solves this problem "well enough" for most practical purposes. See http://mathworld.wolfram.com/Ferguson-ForcadeAlgorithm.html http://mathworld.wolfram.com/Ferguson-ForcadeAlgorithm.html for more.
- dnautics 11y ago
- Terr_ 11y agoWhy? No matter what radix you pick, there's always going to be some rational-value you cannot accurately encode. Moving to binary just gives you a different distribution of "un-encodeable values". (I'd say a larger/worse set, but I'm not yet sure how to prove it.) In the long run, trinary gives you the best radix-economy, being closest to e: https://en.wikipedia.org/wiki/Radix_economy https://en.wikipedia.org/wiki/Radix_economy
- Terr_ 11y agoMaking a self-reply here, I think I know how to show binary is "worse" when it comes to un-representable rational numbers. I'm not a math major, so this is probably some incredibly obvious textbook stuff to somebody else, but... In base-N, you can accurately write any fraction of (1/y) provided that y can be expressed using the same prime-factors found in N. For example, 10 has the prime factors of 2 and 5, leading to the requirement that y=(2^a × 5^b) . This means base-10 can accurately represent (1/80), because 80 = (2^4 × 5^1). In base-2, you're limited to stuff in the form (2^a). Finally, the, uh, infinity-of-integers that matches (2^a) is always going to be "smaller" than the infinity which can be matched by (2^a × 5^b), since the latter "contains" the former when b=0.
- dnautics 11y agono. You can accurately represent anything which is k*2^n, where (k,n) are integers. Simple example: 3 is not 2^n but obviously expressing 3 as a floating point is not a problem. Similarly 1.5, etc. In this fashion, primes p seem "better" as they increase, because for a given size limits on k and n, you get more 'numbers' per unit space on the real line. Composite numbers are 'even better', but there are a lot of pains in the ass with composite numbers, stemming from Z/nZ not being a field if n not prime. Ultimately, though, your internal representation is binary, using anything not two produces other inefficiency. That's why IEEE 754 BCD is not base-10 but base-1000 (since 2^10 = 1024 which is the closest a power of two gets to a power of 10, for bit-wise representation efficiency). We don't have bi-quinary computers.
- deleted 11y ago
- vidarh 11y agoOr bcd or fixed point. But it all depends what you want to represent. For financial data bcd or fixed point encoded in integers is generally preferred over floating point because it's easy to make it behave the way people expect it to.
- Avshalom 11y agoWe've had BCD since pretty much the beginning. IEEE floating point is defined for decimals in several precisions https://en.wikipedia.org/wiki/Decimal64_floating-point_format https://en.wikipedia.org/wiki/Decimal64_floating-point_forma... It's just that top to bottom very few people are willing to trade the loss of speed for the increase in accuracy (not that decimal is great either, you still run into plenty of repeating fractions)
- threatofrain 11y agoPerhaps I'm wrong, but I believe that nothing can stop the problem that some quantities cannot be finitely represented, but I don't see why rationals are a problem because computers can finitely represent them with no information loss if they treat these numbers symbolically. We only have 0.1 + 0.2 != 0.3 issues due to using an imprecise but fast number representation system.
- such_a_casual 11y agoDecimals do not cause any problems for computers. Computers are just a bunch of switches of states. The meaning of these states is completely up to us. For example, 4 switches creates 2^4 states (16 states). That means we could have those states represent the numbers 1-16. As far as I'm aware, the only reason we use base 2 numbers in computing (floats) is because there are mathematical shortcuts you can take when doing so. There is nothing forcing a computer to interpret those 16 states as x * 2^y instead of x * 10^y. That is a software choice.
- hasenj 11y agoI'd assume if we used base 12 for everything we'd also use it for writing numbers too. 1 2 3 4 5 6 7 8 9 a b so 10 would be 12
- btilly 11y agoYou have to be clear on the difference between the number and its representation. In English we represent numbers in base 10 unless otherwise specified. Hence you say things like, The base 12 number 10 is 12. I did not otherwise specify, so I represented my numbers in base 10 everywhere even though I was talking about base 12.
- kuschku 11y agoIn math, we prefer to use either (101010)_2 or (101010)2 or 101010_2 – which represents (42)_10 (With TeX formatting implied)
- btilly 11y agoWe do? In my experience mathematicians almost always assume base 10 and don't bother indicating it. In fact we mostly indicate the base when there is a good possibility that it isn't 10, and any stray numbers fail to have a base represented, they should be assumed to be base 10. (Mathematical notation mostly uses sensible defaults except for differential geometry.)
- kuschku 11y agoYes – but if we do want to talk about other bases, we use this format. Implicit default for a number x is obviously (x)_10, as mathematicians are lazy.
- alricb 11y agoIf we weren't afraid to confuse our Greek readers, we could just use greek letters: ω (=0) α β γ δ ε ζ η θ ι κ λ, with ' to indicate a number: 15 would be written 'αγ. But see: https://en.wikipedia.org/wiki/Greek_numerals https://en.wikipedia.org/wiki/Greek_numerals
- yes_or_gnome 11y agoI am in the process of reading 'The Story of French' by Nadeau and Barlow. There's a chapter on how France was able to push their influence, during the renaissance, to get the world to switch to the metric system. Prior to developing the metric system, France had no standard for the pound; unlike England. This was the height of enlightenment in France, so the reformers wanted to replace the Gregorian Calendar with a metric time. I believe they wanted to call it the Republic Calendar; rather, the equivalent in french. So, they commissioned a poet to rename the months of the year, keeping twelve months of 30 days, with 5 or 6 ambiguous days at the end of the year. However, the major downfall was moving to a 10-day week which reduced the 'weekend' (not that it was called that) from 1 day out of a 7 day week to a 1-in-10. The plan was to have poetic names for the days of the week, but they felt that they were push their luck so instead they went with ordinal numbers. The only country to actually use the calendar was, of course, France for 16(!?) years until Napoleon repealed it during his imperial reign. https://en.wikipedia.org/wiki/Metric_time https://en.wikipedia.org/wiki/Metric_time Anyone, feel free to correct me. I, literally, just read about this (fascinating) subject a couple nights ago. I haven't had time to independently follow up on the topic, but I plan to do so soon. Amendum: A better link, https://en.wikipedia.org/wiki/Decimal_time#France https://en.wikipedia.org/wiki/Decimal_time#France
- vidarh 11y agoThe renaissance is usually seen as being the 15th and 16th centuries. France didn't switch to metric until the end of the 18th century, after the French revolution. If anything, the way the French "pushed their influence" was by conquest: The first countries that adopted metric were forced to when they were conquered by Napoleon. Many of them reverted after Napoleon was beaten, but then gradually they started converting to it again, Since you're mentioning Napoleon I assume you just got your periods mixed up. There were indeed many crazy suggestions for calendars after the French revolution...
- yes_or_gnome 11y agoThanks for the clarifications; You're right that I am mixing up eras and nomenclature. 'The Age of Enlightenment' would be the correct name, yes? This was all during the first french republic and ended by the end of Napoleon's reign.
- mark-r 11y agoIn high school I calculated a system of decimal time periods and equated them to hours/minutes/seconds, just for fun. I realized it would never work when 1/100 of a day came out to 14.4 minutes; the TV stations would need to remove 72 seconds of advertising from every half hour show, something they would never do.
- nashashmi 11y agoTo add, multiplying 5'5" and 4'4" would become a whole lot easier. It would literally be 55 x 44 instead of 5.42 x 4.33. Of course that would mean I would have to memorize the entire multiplication table again: because 55 in duodec would be 65 in dec. And 5x18 would be 84.
- akira2501 11y ago> You have to multiply by 3.6, can you easily do that in your head? Multiply by 36 (12*3) then divide by 10?
- btilly 11y agoI'd multiply by 6 twice then divide by 10. But it isn't the "move the decimal point" of other metric unit conversions.
- kw71 11y ago> (You have to multiply by 3.6, can you easily do that in your head?) I think so, by multiplying by 12 and then 3.