Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
IOS Apple

Apple's Weather App Won't Say It's 69 Degrees (theverge.com) 177

An anonymous reader shares a report: If you're an iPhone user, the weather is always a particularly nice 70 degrees. Or 68 degrees. Any temperature but 69 degrees, actually, because it turns out that the built-in weather app on some versions of iOS -- including the current version, iOS 14.6 -- will refuse to display the internet's favorite number, even if the actual temperature in a given location is, in fact, 69 degrees. It's not clear if this is a bug or an intentional attempt from Apple to cut down on 69-related humor. The rounding is only visible in the weather app itself: clicking through to Apple's source data from Weather.com will show the proper temperature, as does Apple's home screen widgets.
This discussion has been archived. No new comments can be posted.

Apple's Weather App Won't Say It's 69 Degrees

Comments Filter:
  • by account_deleted ( 4530225 ) on Tuesday July 13, 2021 @11:53AM (#61578495)
    Comment removed based on user account deletion
  • Nice.
  • In 3, 2, 1...

  • 20.5C (Score:5, Interesting)

    by AmiMoJo ( 196126 ) on Tuesday July 13, 2021 @11:57AM (#61578521) Homepage Journal

    It's probably because 69F is 20.5C, so if they take data in C and convert it they always get 68 or 70.

    • Re:20.5C (Score:5, Insightful)

      by SuricouRaven ( 1897204 ) on Tuesday July 13, 2021 @12:04PM (#61578557)

      An interesting theory, and should be testable: Are there other temperature numbers that never appear?

      • Great point.
      • Also Siri has no problem saying âoe69â when asked âoewhatâ(TM)s 3 times 23â
      • Re:20.5C (Score:5, Informative)

        by Theaetetus ( 590071 ) <theaetetus DOT slashdot AT gmail DOT com> on Tuesday July 13, 2021 @01:01PM (#61578771) Homepage Journal

        An interesting theory, and should be testable: Are there other temperature numbers that never appear?

        Looks like it. Flipping through my phone's weather data for a couple different cities, it tends to show even numbers in the 60s - 64, 66, 68, 70 - and not the odd numbers, but in the 70s, it's odd numbers and not evens - 73, 75, 79. In the 80s, I see 81, 82, 84, 86, and in the 50s, I see 52, 54, 55, and 57...

        And now testing it in Excel, you're exactly right - all of those numbers are single degrees in C, converted to F, and then rounded to the nearest integer. You can only get the following values in F: 50, 52, 54, 55, 57, 59, 61, 63, 64, 66, 68, 70, 72, 73, 75, 77, 79, 81, 82, 84, 86, 88, 90, 91, 93, 95, 97, 99, 100, 102...

        So, yeah, you got it.

        • My Apple Watch - which feeds off the Apple weather app - was reporting 63 degrees a bit earlier this morning.

          Right now it says 66... I'm going to try and see what numbers it hits or misses as the temp goes up!

          • Interesting... the Accuweather app just ticked up to 67F, and the Apple Weather app switched to 68F.

            • Ha! And now it jumped from 68 to 70! So either the conversion / rounding argument is correct, or the app has some other limitation (perhaps related to not wanting to poll the servers too often).

        • by jhecht ( 143058 )
          Not just iPhone; I'm seeing only those numbers on the Notifications Weather on my Mac.
        • Re:20.5C (Score:5, Funny)

          by jellomizer ( 103300 ) on Tuesday July 13, 2021 @02:31PM (#61579165)

          But we wanted a nice conspiracy theory, not just a simple fact of Math Rounding.
          Why follow the simple and well explained idea. Where we can have some complex story of intrigue, were they are board members debating over what numbers to show. And people using these missing values as secrete meanings, as it uses 69 Degrees as a code to send over the data to Apple. But you don't notice it because it will only show 68 or 70.

          This is a Science and Technology Website, straight forward and logical answers have no place here. What do you think this is 1998!

        • Never attribute to political correctness what can be explained by sloppy conversions.

        • /utter unsurprise that Apple works in metric.

          Note the lack of precision. Just sayin'.

        • I'm hard pressed to imagine that the hardware produces integers. It seems more likely that the temperature sensor would be inherently analog. This makes me wonder what the maximum error is, given two roundings; but I'm too lazy to compute it.

          • The digitally connected one-wire thermocouples we're using for our datacenters give me 2 digits fixed-point resolution.
            Verified that I have many 69F (after conversion from C) readings in our logs.

            I also have some experience with thermocouples tied directly to ADCs, and yes, they're analog, and yes- you get as much precision as you want (though how much of that precision is noise will vary depending on all the factors involved in the reading)
    • Re:20.5C (Score:5, Informative)

      by DDumitru ( 692803 ) <`moc.ocysae' `ta' `guod'> on Tuesday July 13, 2021 @12:05PM (#61578559) Homepage

      Close. My Toyota behaves this way as well. Temperate is in Celsius, turned into an int, and then converted. There are numerous values that get skipped, including 69.

      So this is not a conspiracy, just a unit conversion rounding error.

      • by cob666 ( 656740 )

        Close. My Toyota behaves this way as well. Temperate is in Celsius, turned into an int, and then converted. There are numerous values that get skipped, including 69.

        So this is not a conspiracy, just a unit conversion rounding error.

        Does your car ever display 67 degrees F?

        • Does your car ever display 67 degrees F?

          Why yes...yes it does.

          I dunno if it displays in C....but if so, there's likely a setting I have to change somewhere, but I have no need to see temp in C. No one else here does either for the most part.

      • by AmiMoJo ( 196126 )

        Would love to know if it was deliberate, i.e. they understood the limitation and accepted it. It was kind of glaring to me, but then I often spot things like this when debugging.

        It's definitely the kind of thing that people unfamiliar with how computers handle numbers accidentally end up doing.

    • by lsllll ( 830002 )
      So are you implying their measurement instruments have only an accuracy of 0.5 degrees C? Because 20.6C would translate to 69F.
      • Is this the weather app or some on board sensor? If itâ(TM)s the weather app itâ(TM)s probably downloading the data as an integer Celsius number. If itâ(TM)s an on board sensor theyâ(TM)re probably converting the raw reading to an integer Celsius number. Either way, the integer value gets converted to Fahrenheit and rounded again. Sloppy, but I expect no less from programmers these days.
    • by spitzak ( 4019 )

      It is possible it is rounding to the nearest degree in C before converting, and then rounding to the nearest degree in F. This would also skip 71, and pretty close to 1/2 the values.

      If they round to the nearest 1/2 degree in C before converting and then truncate to F then it would skip 69 but that seems less likely they would mix truncation and rounding. If they round to 20.5, convert to 68.9 and then round then you get 69.

      • This would be pretty bad practice since Celsius has less precision as a whole number
        • Many cheap sensors only do full degrees on Celsius.

          Anything above 25 is too hot for comfort anyway.

        • by ceoyoyo ( 59147 )

          It's not particularly bad practice since you're using the temperature at a particular spot as a stand in for the actual temperature in a fairly large area. There's probably a standard deviation of at least a couple degrees.

      • by lsllll ( 830002 )
        If they did that, we'd be missing a whole bunch of numbers besides 69.
        • by spitzak ( 4019 )

          I think that may actually be what is happening. Somebody noticed that 69 is skipped and failed to notice all the other numbers that are skipped.

    • I had a similar thought. 20C is 68F, and 21C is 69.8F which is rounded up to 70F

      It'd be easy to test for someone who has an iPhone. In terms of amplitude 1C=1.8F, so it should skip many!

    • This.

      Sloppy conversion / rounding errors occur in many products. Here for example, I have a Halo reader [haloscanner.com] that can read the temperature off of Destron Fearing Lifechip Bio-Thermo [cckoutfitters.com] RFID microchips: the microchip encodes and reports the temperature in tenths of degree Fahrenheit over 74F. The Halo reader gets that value, converts it to C, then (incorrectly) rounds off the first floating point digit. As a result, when displayed in Celcius, the temperature series is missing some values - like 36.0C, 36.1C, 36.2C,

    • an american company using celsius as the default source? nah. no american company is that competent.

      i don't like F, but it allows for more precision regarding temperature for weather related purposes if you can only stick to integers. plus F is still the standard in the US.

      • Is that precision meaningful to you when you're getting dressed in the morning?

        I'm impressed if you can tell the difference between 68F and 69F by feel.

      • by ceoyoyo ( 59147 )

        US units are all legally defined in terms of international units. Pretty much everything measures in international units and then converts for Americans.

    • by jovius ( 974690 )

      A proof that in the metric system 69 is not only fun but hotter too.

      Although, in length however...

    • Right now my own home made temperature probe
      https://flightmaker.hopto.org/... [hopto.org]
      is showing 25.6C 69.1F
      let's see if it changes to the desired value in a moment...

    • If that were the case there would be no 67F. In fact there would be a lot of numbers missing if it were just a C conversion problem. I'm not an Apple user, but can anyone confirm they don't get 67F?

      Or for that matter looking at temperatures from 0C to 39C if you do =round((C*9/5)+32, 0)
      You would be missing the following numbers:
      33F, 35F, 38F, 40F, 42F, 44F, 47F, 49F, 51F, 53F, 56F, 58F, 60F, 62F, 65F, 67F, 69F, 71F, 74F, 76F, 78F, 80F, 83F, 85F, 87F, 89F, 92F, 94F, 96F, 98F, 101F

    • by lpq ( 583377 )

      Screw /. and it's latin1 only input.

      Lameness filter encountered. Post aborted!

    • Comment removed based on user account deletion
    • It's probably because 69F is 20.5C, so if they take data in C and convert it they always get 68 or 70.

      This is mathematically inept on their part. It's 68.9 degrees F, so rounded would be 69. But one wouldn't drop the additional precision of the .9 to begin with.

      20.5 C means either accuracy to tenths, C, or perhaps half a degree, depends on the measurement sensor. In either case, you don't lose enough accuracy converting to F to justify dropping the tenths, F, and, if you do, round rather than just drop it.

      Fine. Let'a get into it. With no other knowledge of the sensor, 20.5 C means 20.45C to 20.54999 C.

  • by MobileTatsu-NJG ( 946591 ) on Tuesday July 13, 2021 @11:57AM (#61578523)

    You guys will believe anything. Over the weekend the app had no problem showing me 420!

  • One nerd programmer thought "Te he he!!! I'll keep all the 69s to myself!"
    • No need to take them all, that brings unwanted attention. Just siphon some of the 69 rounding errors to your own personal account. No one will ever know the difference!
  • by shadowrat ( 1069614 ) on Tuesday July 13, 2021 @12:04PM (#61578555)
    the calculator wouldn't let you spell boobies (unless you were careful to trick the accelerometer into thinking it wasn't upside down). if you had 8008 anywhere in the readout it would clear the screen when inverted. eventually they picked a font that just doesn't come across as letters.
  • It's whats for dinner!

  • Can't have it suggesting bad behavior.
  • Way back when I was programming on an Apple ][, the way to change a hard reboot to a warm reboot was to "poke" a value into a specific location.
    The value was 45 in hex, which is 69 base 10.
    So, back in the days, they had a sense of humor
    • Apple ][ or Apple ][+ ?

      On the Apple ][ pressing Ctrl-Reset always resets the PC to $FF59. There is no way to change this behavior.

      On the Apple ][+ (the Autostart ROM) you could do POKE 1012,XX to cause pressing Ctrl+Reset do a hard reset. The reason I say XX is because it depends if you are running under DOS 3.3 or ProDOS so the value changes. The reason it works is because pressing Ctrl+Reset would jump to the Reset vector address stored at $FFFC. Eventually the ROM at $FA85 would check if location (mem

      • by hawk ( 1151 )

        >On the Apple ][ pressing Ctrl-Reset always resets the PC to $FF59.

        That's a later ][.

        Initially, Reset worked without the control key.

        You could then get into BASIC either with the loaded program (and variables?), or with a clean slate.

        Esc-B and Esc-D? It's been, uhm . . .

        (OK, it was back when I was running around the neighborhood with a push lawnmower, instead of chasing folks of my own lawn . . .)

        • Ah, yes, Control wasn't originally needed when pressing Reset. Due to the accidents of people pressing Reset by itself Apple added the "Control" guard. Oh wow, you really are going back. I didn't think you were using an original Apple ][ but sure enough you were! ;-)

          No I'm really curious what poke that was!

          • by hawk ( 1151 )

            you can probably find the old "red book" on line somewhere.

            The manual that came with them, but apparently went to press before the versions of the machine that actually shipped.

            It generally assumed that you had bought the board, like the original Apple, rather than getting a keyboard, case, and power supply. It also described a rather standard version of the Star Trek game, rather than the unique Apple Trek that actually came.

            It had ROM dumps, all the technical details, memories locations, etc.

            I really don

  • Although I am not sure who is more childish: those who post 69-related humour; or Apple that tries to stop it.

    Anyway: it should be in Centigrade, the USA is one of very few countries that use Fahrenheit [worldpopul...review.com].

    • by lsllll ( 830002 )

      Firstly, it's humor that gets some of us through our days and 69 humor is particularly a good topic.

      I could argue for and against using C for reporting environment temperature. One one hand, F is more accurate than C. On the other hand, when dealing with our normal, daily stuff, the accuracy is not needed. For almost everything, anything that can happen at 68 can happen at 69, except 69 means we do each other and 68 means you do me and I'll owe you one.

  • In Victorian times, they put clothing on piano legs because they said that they were too sexy. Gazing balls were originally to look at each other without being noticed. I see no reason to do this kind of stupid wayback.
  • In Japan the symbol for 4 looks like death, so it's a bad number. And besides, everyone knows that 71 is just two fingers away from 69. So it's all a slippery slope.
  • not the favorite number !

    I asked all my nerd friends in our Moms' basements about 69 and got nothing but blank stares. So I did a poll: What's your favorite number? After disqualifying number two; 92% agreed that it is - 42 -

  • Never ascribe to malice that which can be adequately explained by stupidity.

Every nonzero finite dimensional inner product space has an orthonormal basis. It makes sense, when you don't think about it.

Working...