home.social

#floatingpoint — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #floatingpoint, aggregated by home.social.

  1. Ah yes, another riveting tale of microcontrollers—because who doesn't love a deep dive into floating point #arithmetic on a #hobbyist chip? 🙄 Spoiler: if you enjoy endless links leading to nowhere and cryptic jargon, this post is your Disneyland. 🎢 Go ahead, embrace the thrill of being hopelessly confused! 🤓
    danielmangum.com/posts/floatin #microcontrollers #floatingpoint #techhumor #confusion #HackerNews #ngated

  2. Ah yes, another riveting tale of microcontrollers—because who doesn't love a deep dive into floating point #arithmetic on a #hobbyist chip? 🙄 Spoiler: if you enjoy endless links leading to nowhere and cryptic jargon, this post is your Disneyland. 🎢 Go ahead, embrace the thrill of being hopelessly confused! 🤓
    danielmangum.com/posts/floatin #microcontrollers #floatingpoint #techhumor #confusion #HackerNews #ngated

  3. Ah yes, another riveting tale of microcontrollers—because who doesn't love a deep dive into floating point #arithmetic on a #hobbyist chip? 🙄 Spoiler: if you enjoy endless links leading to nowhere and cryptic jargon, this post is your Disneyland. 🎢 Go ahead, embrace the thrill of being hopelessly confused! 🤓
    danielmangum.com/posts/floatin #microcontrollers #floatingpoint #techhumor #confusion #HackerNews #ngated

  4. Ah yes, another riveting tale of microcontrollers—because who doesn't love a deep dive into floating point #arithmetic on a #hobbyist chip? 🙄 Spoiler: if you enjoy endless links leading to nowhere and cryptic jargon, this post is your Disneyland. 🎢 Go ahead, embrace the thrill of being hopelessly confused! 🤓
    danielmangum.com/posts/floatin #microcontrollers #floatingpoint #techhumor #confusion #HackerNews #ngated

  5. Ah yes, another riveting tale of microcontrollers—because who doesn't love a deep dive into floating point #arithmetic on a #hobbyist chip? 🙄 Spoiler: if you enjoy endless links leading to nowhere and cryptic jargon, this post is your Disneyland. 🎢 Go ahead, embrace the thrill of being hopelessly confused! 🤓
    danielmangum.com/posts/floatin #microcontrollers #floatingpoint #techhumor #confusion #HackerNews #ngated

  6. 🚀✨ Behold, the thrilling tale of querying 3 billion vectors—a journey where Vicki Boykis heroically attempts to decode Jeff Dean's cryptic wisdom on #mapreduce. Spoiler: It's basically a nerdy treasure hunt for semantically similar items, but with more floating-point numbers than your brain can handle. 💻🧠
    vickiboykis.com/2026/02/21/que #HackerNews #VickiBoykis #treasureHunt #techJourney #floatingPoint #HackerNews #ngated

  7. 0.1 + 0.2 In SQL = 0.30000000000000004?!

    SQL floating point precision is broken! Adding 0.1 + 0.2 creates a number with precision errors. This breaks financial calculations! Watch!

    #sql #sqltricks #database #sqltutorial #floatingpoint #precision #sqlquiz #codingchallenge #sqlshorts #sqlbugs #numericprecision #sqlwtf

    youtube.com/watch?v=C53FQIhge3U

  8. Learn about numeric data types (and the number 998,001) in Python

    The value 1 / 998,001 has an interesting property, but to see it in Python you need to learn about numeric data types.

    rodstephensbooks.com/many_digi

    #Python #FloatingPoint #Decimal #Precision

  9. I am excited to read about numpy_quaddtype, a project to include quad precision in numpy. The standard precision in numpy (and most other places) is double precision: numbers are stored in 64 bits and the precision is about 16 decimal digits. This is usually enough but not always.

    Numpy does have longdouble, which may or may not increase precision, depending on your platform, but even if it does, the increase is very modest. If I need more precision, I typically use FLINT, but that is meant for super high precision and rigorous computations. It will be very good to have another tool.

    More details in this blogpost: labs.quansight.org/blog/numpy-

    #FloatingPoint #numpy #quansight #NumericalAnalysis

  10. Малые числа, большие возможности: как плавающая запятая ускоряет ИИ и технологии

    Привет, Хабр! С вами снова ServerFlow, и сегодня мы решили погрузиться в увлекательный мир чисел с плавающей запятой . Вы когда-нибудь задумывались, почему существуют разные виды этих чисел и как они влияют на производительность наших процессоров и видеокарт? Как малые числа с плавающей запятой помогают развивать нейросети и искусственный интеллект? Давайте вместе разберемся в этих вопросах, раскроем тайны стандарта IEEE 754 и узнаем, какое значение имеют большие и маленькие числа с плавающей запятой в современных вычислениях.

    habr.com/ru/companies/serverfl

    #плавающая_запятая #fp32 #fp16 #INT8 #квантизация #Тензорные_ядра #fpu #floatingpoint #floating_point #ieee_754

  11. Today I learned that in Python you can print a floating point number with thousands separator and no floating point part with the f-string formatter `:integer_digits,.0f`.

    For instance:

    ```python
    print(f"{1234567891*1.1:15,.0f}")
    ```

    prints ` 1,358,024,680`, while

    ```python
    print(f"{1234567891*1.1:15,f}")
    ```

    prints `1,358,024,680.100000`.

    It also properly rounds up or down numbers, which is great.

    #TIL #TodayILearned #Python #FStrings #FloatingPoint #ThousandsSeparator

  12. How about we make this #FloatingPointFriday? Here's a gem I posted in another thread and that I regularly use to scare my students and to demonstrate to them the dangers of #floatingPoint. Every #IEEE 754 compliant #FPU will give the same answer. It allows me to talk about the fact that radix representations of a number may be finite in one base (10) and infinite in another (2). Then I throw in the fact that floating point numbers have #finitePrecision and that #machineEpsilon is a thing.

  13. @matthew_d_green I like to scare my students with the this little gem (and then I explain to them that every computer with an #IEEE 754 compliant #FPU will give you the same answer, and for a very good reason)

    #FloatingPoint #IEEE754 #STEM

  14. TL;DR: -fno-math-errno should always be set in C/C++ land. (unless you're using VC, then: I'm sorry)

    libm is "still" burdened with language where some functions (most importantly sqrt & sqrtf) will set 'errno'. Compilers "respect" this by default. IEEE-754 won a long time ago. It's WAY past time to flip math-errno to default to off.

    #C #C++ #sqrt #FloatingPoint

  15. Comparison of basic 1/sqrt implementations. Short versions. Next is a version by Carlos F. Borges' which is correctly rounded except for 1 value per 2 power-of-two intervals (1 per 2 exponent values...like [1,4])

    Test driver (& references to Borge) are in this gist: gist.github.com/Marc-B-Reynold

    The driver also includes:
    • 1/sqrt(x) - which I had forget to include.
    • correctly rounded versions
    • SSE rsqrt approx
    • old skool quake approx (added a modernized one)

    #FloatingPoint #Approximation #Sqrt

  16. Ein Wissenschaftler einer New Yorker Universität hat festgestellt, dass es bei einigen Python-Paketen zu Problemen mit nummerischen Berechnungen kommen kann.
    Python: Compiler-Optionen können bei Gleitkommaberechnungen zu Fehlern führen