@ObsidianUrbex that’s freaking awesome 🤩

@AssalRad not a snappy enough soundbite perhaps, combined with well-founded fear of retaliation or (legal) “trouble” to report anything negative concerning Israel’s treatment of those affected by their siege/genocide. I’ll have to get me a copy of your book on that topic soon…

@martin_ueding @pjakobs 2/2 unit and magnitude conversion errors have been the cause of many incidents too and loss of life, so we should take a leaf out of the Japanese playbook and demand SI everywhere 😉. We will get used to the numbers eventually.
As for time, it’s Julian date for me! ( I kid, I kid. But at least I insist on stating UTC for international online meetings 😁)

@martin_ueding @pjakobs I’ve become a bit of an absolutist because in my field, people are commonly using two different units for scattering vector magnitude and for absolute scattering intensity, and it continues to lead to unnecessary errors when students try to fit data.
Magically, when sticking to SI base units everywhere in code, all the scaling problems disappear (just make sure to use float32 at least to avoid entering the realm of monsters). 1/2

@martin_ueding @pjakobs and that’s the attitude that gets you units like “kWh/day” as opposed to… you know… “W”. In any case 450 J/m doesn’t sound so incomprehensible.

@pjakobs J/m wäre mir lieber.

@sonsti I think we found out when we were about 1/3rd of the way. I remember my dad was extremely annoyed at the guide at that point. It was certainly an experience to remember, though!