Peter Jakobs ⛵Was sagt ihr, hätte eine Petition Chance, die verlangt, dass der Energieverbrauch von Neufahrzeugen grundsätzlich in kWh/100km angegeben werden muss?
Dr. ir. Brian R. Pauw@pjakobs J/m wäre mir lieber.
@doc für SI Puristen ;-)
Martin Ueding@pjakobs @doc
Ja, das sind die Basiseinheiten. Aber ist das im Alltag nützlich? Man müsste seinen Strom dann auch im MJ abgerechnet bekommen, damit man im Kopf rechnen kann. Ein Zeitsystem mit ks anstelle h wäre auch konsequenter.
Für mich würde sich MeV/fm natürlich anfühlen, allerdings wären die Zahlen dann extrem klein. Und im Alltag auch echt nutzlos 😅
@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.
@doc @pjakobs
Over the course of my studies I had various "attitudes". I was a SI base using die-hard. Then I ventured into h-bar = c = 1 and stopped caring about conversion between domains.
And now I think that our system of hours gives us many units that can be cancelled, but they're still useful. In order to go full SI, one would have to reform time.
@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
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 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 😁)
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 😁)
@doc @pjakobs
I see, that makes sense.
I'm Lattice QCD one formulates everything dimensionless ratios, for instance "form factor divided by pion mass" or "pion mass times lattice spacing". In this way there are no units to worry about.
In other code, I always put the unit into the variable name because floats are dimensionless. So I store "time / s" or "time / ms". And then it is explicit.