GNU Units(gnu.org)
gnu.org
GNU Units
https://www.gnu.org/software/units/
116 comments
Trying your examples, especially considering that the elliptical orbit of the earth likewise causes the Sun's angular diameter change depending on where our orbit is, I found that Units current has a buggy definition of moondist_min and moondist_max. It's defined in the definitions file as 356.371 km and 406.720 km respectively. These should be Mm! (Or remove the period, either will work)
Just to work around the bug, you can use a local definitions file to correct it:
Just to work around the bug, you can use a local definitions file to correct it:
cat > ~/.units <<EOF
moondist_min 356.371 Mm
moondist_max 406.720 Mm
EOFinteresting, looks like an effort to improve the precision resulted in a factor of 1000 error! `help moondist_max` shows me considerably less precise values:
sundist 1.0000010178 au # mean earth-sun distance
moondist 3.844e8 m # mean earth-moon distance
sundist_near 1.471e11 m # earth-sun distance at perihelion
sundist_far 1.521e11 m # earth-sun distance at aphelion
moondist_min 3.564e8 m # approximate least distance at
# perigee 1901-2300
moondist_max 4.067e8 m # approximate greatest distance at
# apogee 1901-2300Where are you typing help to get that output?
at the units prompt
You have: help moondist_max
I could've sworn I tried and didn't get anything. Now it is working. I don't know what I did! (running version 2.22, at any rate)
sweet
search is also pretty nice
search is also pretty nice
You have: search gallon
alegallon beergallon
beergallon 282 UKinch^3
brgallon 4.54609 l
drygallon 1|2 uspeck
gallon usgallon
imperialgallon brgallon
irishgallon 217.6 UKinch^3
scotsgallon 827.232 UKinch^3
usgallon 231 in^3
winegallon 231 UKinch^3I use GNU Units a lot (and have mentioned it fairly frequently on HN -- 37 comments and one story submission: <https://news.ycombinator.com/item?id=7297219>), and have for a couple of decades now, but not like this, despite what I consider to be some reasonably advanced conversions (e.g., <https://news.ycombinator.com/item?id=8196590> & <https://news.ycombinator.com/item?id=7606949>).
This is an absolutely awesome comment. Thanks, kragen.
This is an absolutely awesome comment. Thanks, kragen.
thank you, that means a lot
Impressive list. The maintainers should copy paste this onto that page
they have my permission
everyone is free to redistribute my comment, in whole or in part, modified or unmodified, with or without credit; i waive all rights associated with it to the maximum extent possible under applicable law. where applicable, i abandon its copyright to the public domain. i wrote and published this comment in argentina in 02023
everyone is free to redistribute my comment, in whole or in part, modified or unmodified, with or without credit; i waive all rights associated with it to the maximum extent possible under applicable law. where applicable, i abandon its copyright to the public domain. i wrote and published this comment in argentina in 02023
I had a lot of fun working with the maintainers of this utility to better support Gaussian units[1]. This is usually done (incorrectly) by multiplying, say, some number of SI coulombs by a dimensionless constant (actually 2_997_924_580) to produce some number of statcoulombs that represents the same charge. It's very subtle, though, that statcoulombs and coulombs have different dimensions (which is the point of Gaussian units) despite representing the same physical quantity[2], so the conversion is much more involved. I learned a lot about the nature of units and software development working with them.
[1]: https://en.wikipedia.org/wiki/Gaussian_units
[2]: A consequence of this is that electromagnetic equations formulated in terms of Gaussian units have goofy things like sqrt(grams) as "base" units. That was the tricky part to handle.
[1]: https://en.wikipedia.org/wiki/Gaussian_units
[2]: A consequence of this is that electromagnetic equations formulated in terms of Gaussian units have goofy things like sqrt(grams) as "base" units. That was the tricky part to handle.
Yes - you haven't seen the full scope until you confront unit system conversions as alluded to in my other comment (https://news.ycombinator.com/item?id=36988497).
There should also be conversions to/from SI|CGS and "natural units" (particle physics) and "gravitational units" (general relativity - G=c=1).
The "input/output" can be a bit more subtle, too - since you may need to tell the converter the abstract physical kind/"meta type" of the thing like "energy" or "momentum" or "charge" to fully define what might happen (and in some ideal world get back an expression with powers of G's and c's in there symbolically rather than only numerically). Some of this shows up in an unresolved issue on that Nim library I mentioned[1]: https://github.com/SciNim/Unchained/issues/8
EDIT: { One reason to preserve a symbolic capability is that some constants have resisted precise measurement for centuries - G is still only known to about 5 decimals [2] - and you don't want round-trip unit conversion to add such errors to the calculation. }
[1] https://news.ycombinator.com/item?id=36988225
[2] https://en.wikipedia.org/wiki/Gravitational_constant#Modern_...
There should also be conversions to/from SI|CGS and "natural units" (particle physics) and "gravitational units" (general relativity - G=c=1).
The "input/output" can be a bit more subtle, too - since you may need to tell the converter the abstract physical kind/"meta type" of the thing like "energy" or "momentum" or "charge" to fully define what might happen (and in some ideal world get back an expression with powers of G's and c's in there symbolically rather than only numerically). Some of this shows up in an unresolved issue on that Nim library I mentioned[1]: https://github.com/SciNim/Unchained/issues/8
EDIT: { One reason to preserve a symbolic capability is that some constants have resisted precise measurement for centuries - G is still only known to about 5 decimals [2] - and you don't want round-trip unit conversion to add such errors to the calculation. }
[1] https://news.ycombinator.com/item?id=36988225
[2] https://en.wikipedia.org/wiki/Gravitational_constant#Modern_...
IIRC, GNU Units was once the center of a small controversy. Google (still, AFAIK) offers unit conversion as a part of their search box; you can type a unit conversion into Google and get a conversion done. Some people noted this, wondered about what the backend might be, and typed some stuff in which was known to trigger a then-present bug in GNU Units. And wouldn’t you know it, Google showed the same bug. This was all well and good, since GNU Units uses GPL, not the AGPL (which did not even exist at the time). But then some time later, Google fixed the bug; the unit conversion could no longer be triggered to exhibit the bug. But no fix for GNU Units was forthcoming from Google. At the time, this was surprising and cause for some hullabaloo, since Google was still ostensibly in their “Don’t be evil” stage.
(Disclaimer: I only heard about all of this via the rumor mill; some details may be wrong or omitted.)
(Disclaimer: I only heard about all of this via the rumor mill; some details may be wrong or omitted.)
This is why I AGPL my projects even if i feel like it isn't likely to be used as a network backend.
What's nice about AGPL is that, as per Google's policy, it serves as an automatic ban from your software being used at Google, including non-networked applications like Android. Some people have said this is a downside or that Google's policy represents a red flag about the license itself, I see it as a good thing that the license makes them nervous.
Maybe the ripped out GNU Units.
Never know, since they never distributed it.
Never know, since they never distributed it.
It’s also possible they fixed the bug in some other way that didn’t involve touching GNU Units, like using a different conversion program only for requests that could trigger the big.
This is a great program and I use it almost every day. A+
For my local units file, I've also defined a “floppyMB” for retro computing purposes. The old “1.2 MB”, “1.44 MB”, “2.88 MB” measures were based on the idea that “1 MB = 1000 KiB” (seriously). The “1.44 MB” floppies would be measured as either 1.47 MB or 1.41 MiB in more conventional units.
For my local units file, I've also defined a “floppyMB” for retro computing purposes. The old “1.2 MB”, “1.44 MB”, “2.88 MB” measures were based on the idea that “1 MB = 1000 KiB” (seriously). The “1.44 MB” floppies would be measured as either 1.47 MB or 1.41 MiB in more conventional units.
echo "floppyMB 1000 KiB" >> ~/.units
units "1.44 floppyMB" MiBThis is highly cursed.
Hardware manufacturers of the 90s have a lot to answer for with regards to binary prefix units.
Hardware manufacturers of the 90s have a lot to answer for with regards to binary prefix units.
This tool is underrated. Failing to deal with units conversion already crashed a Mars probe: https://www.latimes.com/archives/la-xpm-1999-oct-01-mn-17288...
I wonder if the recent problem with the voyager was due to something like this, for example, 2 arcminutes or 2*pi radians being mistaken for 2 degrees.
I wonder if the recent problem with the voyager was due to something like this, for example, 2 arcminutes or 2*pi radians being mistaken for 2 degrees.
>This tool is underrated. Failing to deal with units conversion already crashed a Mars probe
The mistake there was that they were unaware that they had to make the unit conversion, not that they did it wrong.
No tool can, by itself, overcome your ignorance of its necessity.
The mistake there was that they were unaware that they had to make the unit conversion, not that they did it wrong.
No tool can, by itself, overcome your ignorance of its necessity.
> No tool can, by itself, overcome your ignorance of its necessity.
A type system that understands units of measurement can help:
https://learn.microsoft.com/en-us/dotnet/fsharp/language-ref...
A type system that understands units of measurement can help:
https://learn.microsoft.com/en-us/dotnet/fsharp/language-ref...
That still requires you to know about its existence.
It's perfectly possible to write F# code without those and messing up units conversion.
It's perfectly possible to write F# code without those and messing up units conversion.
Someone on the team needs to know about it. That person needs to set up the API to expect properly typed inputs. Others can remain ignorant about units of measurement and the compiler will educate them.
F# has this built in but it can be achieved with libraries in some other languages. For example, in Haskell with the dimensional package[1]:
[1] https://hackage.haskell.org/package/dimensional
F# has this built in but it can be achieved with libraries in some other languages. For example, in Haskell with the dimensional package[1]:
import Numeric.Units.Dimensional.Prelude
import Numeric.Units.Dimensional.NonSI (mile)
speedLimit :: Velocity Double
speedLimit = 30 *~ (mile / hour)
main :: IO ()
main = do
let speed1 = 35 *~ (kilo meter / hour)
let speed2 = 35 *~ (mile / hour)
let speed3 = 35
print (speed1 <= speedLimit)
print (speed2 <= speedLimit)
print (speed3 <= speedLimit)
[1] https://hackage.haskell.org/package/dimensional
You're not getting it. The Mars probe didn't crash because of bad unit conversion. It crashed because there were no units in the data!!!
Go read about it yourself. NASA got some data from a contractor. The data had no units at all. The contractor assumed the data to be in some kind of US-standard units. NASA got these raw numbers and assumed they were in some kind of SI units.
Having enforced units in your language isn't going to help in this situation at all. They weren't exchanging code, they were exchanging raw data, or more specifically, a table with a bunch of numbers on it. The people at NASA simply assumed some units (instead of calling the contractor and asking), and they would have done this in your scenario too.
Go read about it yourself. NASA got some data from a contractor. The data had no units at all. The contractor assumed the data to be in some kind of US-standard units. NASA got these raw numbers and assumed they were in some kind of SI units.
Having enforced units in your language isn't going to help in this situation at all. They weren't exchanging code, they were exchanging raw data, or more specifically, a table with a bunch of numbers on it. The people at NASA simply assumed some units (instead of calling the contractor and asking), and they would have done this in your scenario too.
> The mistake there was that they were unaware that they had to make the unit conversion, not that they did it wrong.
I think the root cause here was continued use of medieval units, instead of just standardizing on the metric system as it's already done around nearly the entire world.
I think the root cause here was continued use of medieval units, instead of just standardizing on the metric system as it's already done around nearly the entire world.
Even if it was all metric, in embedded systems you often have to deal with the same measurements in different units, like angles in radians, degrees, centidegrees, length in mm, m, cm, due to various reasons (mostly historical, like integer math being faster than floating point math).
It is getting less frequent in modern code bases that target 32-bit MCUs with hardware-floating point support, but converting large codebases
It is getting less frequent in modern code bases that target 32-bit MCUs with hardware-floating point support, but converting large codebases
> Even if it was all metric, in embedded systems you often have to deal with the same measurements in different units, like angles in radians, degrees, centidegrees, length in mm, m, cm, due to various reasons (mostly historical, like integer math being faster than floating point math).
It’s also cultural - different fields use different SI units for historical or practical reasons.
My second year at MIT I was in a program (16.001 & 2) that had different classes using cgs, mks, and mills. They all met in the same classroom (different times of course!), so there was no spacial reminder. But we all survived.
It’s also cultural - different fields use different SI units for historical or practical reasons.
My second year at MIT I was in a program (16.001 & 2) that had different classes using cgs, mks, and mills. They all met in the same classroom (different times of course!), so there was no spacial reminder. But we all survived.
[deleted]
Have you ever accidentally set your calculator to gradians? We were warned about it when doing trigonometry in school, the first time we had to go between degrees and radians.
The idea of using units is underrated, yes. More programming languages should be offer support for units, and more program should be using them.
That particular tool, "GNU Units"? Nope. It is pretty good command-line calculator (especially if you give inputs on command line so that history is preserved), but it is not really scriptable, and you'd _definitely_ want to avoid all manual calculations in any sort of important process.
That particular tool, "GNU Units"? Nope. It is pretty good command-line calculator (especially if you give inputs on command line so that history is preserved), but it is not really scriptable, and you'd _definitely_ want to avoid all manual calculations in any sort of important process.
it's somewhat scriptable, and it keeps its own history; i usually use it interactively to get better tab-completion. that also makes search with ^r provide more relevant search hits
as an example of scriptability, i just added this function to ~/.units
with this i can calculate, for example, the convergence angle required for concentrated sunlight to melt iron (asymptotically, assuming no heat losses to conduction or convection)
as an example of scriptability, i just added this function to ~/.units
# note that theta is the angle from the central axis of the cone to its side
conesolidangle(theta) units=[radian;sr] range=[0,) 2 pi (1 - cos(theta)) sr ; \
acos(1 - conesolidangle/sr/2/pi)
with this i can calculate, for example, the convergence angle required for concentrated sunlight to melt iron (asymptotically, assuming no heat losses to conduction or convection)
You have: 2 ~conesolidangle(conesolidangle(asin(sunradius/sundist)) tempC(1538)**4 stefanboltzmann / (1000W/m2))
You want: dms
13 deg + 10 arcmin + 34.428619 arcsec
> More programming languages should be offer support for units, and more program should be using them.
There is some solution for most programming languages:
https://gmpreussner.com/research/dimensional-analysis-in-pro...
How well it works mostly depends on features of a programming language or it's compiler.
That said it's rare for a programming language to have a type system with extra features and unit checking support in it's standard library like F# or GNAT does:
https://learn.microsoft.com/en-us/dotnet/fsharp/language-ref...
https://gcc.gnu.org/onlinedocs/gnat_ugn/Performing-Dimension...
There is some solution for most programming languages:
https://gmpreussner.com/research/dimensional-analysis-in-pro...
How well it works mostly depends on features of a programming language or it's compiler.
That said it's rare for a programming language to have a type system with extra features and unit checking support in it's standard library like F# or GNAT does:
https://learn.microsoft.com/en-us/dotnet/fsharp/language-ref...
https://gcc.gnu.org/onlinedocs/gnat_ugn/Performing-Dimension...
Worth looking at: https://github.com/aurora-opensource/au
It's a C++ library for handling physical quantities (and subsequent unit conversions)
Only tangential to this but somebody might find it usefull. I’m doing lots of calculations in Python involving various units. I’m using a similar library called Pint. https://github.com/hgrecco/pint
My business is thermodynamics of power plants. Professionals in the industry tend to use convenient units like C, bars, kJ/kg and so on. But the formulas usualy need basic SI units. Using this library not only streamlines the conversion process but also keeps track of the unit itself. So instead of variable turbine_output_gj and turbine_output_mw I can have just turbine_output which is convenient.
It is hard to put a value on that but I believe it has already spared me many trivial mistakes that I had to explain to my clients.
My business is thermodynamics of power plants. Professionals in the industry tend to use convenient units like C, bars, kJ/kg and so on. But the formulas usualy need basic SI units. Using this library not only streamlines the conversion process but also keeps track of the unit itself. So instead of variable turbine_output_gj and turbine_output_mw I can have just turbine_output which is convenient.
It is hard to put a value on that but I believe it has already spared me many trivial mistakes that I had to explain to my clients.
I'll second that. I work in the renewable energy space where we get all manner of atmospheric and power data in a wide variety of units depending on the data source, so Pint is incredibly useful in normalizing them as well as making it clear in the code what and how unit conversion is happening. The fact that it integrates fairly nicely with Pandas and Numpy is great, too.
I will third that and add that I use pint regularly and currently work in non-renewable energy.
Unrelated question. I was recently appointed to a citizens energy commission and I'm finding my self modeling energy use and generation in Python. I'm curious if you would suggest any models of residential and commercial energy consumption and renewable energy generation. I'm currently generating a lot of my own from scratch and I'm being (rightly) criticized by my colleagues to use something off the shelf.
If you're looking for something turn-keyish, you might be able to get some help with this from one or more of the big players in the renewable energy analysis and forecasting space, including (in no particular order) DNV, Vaisala, Bloomberg, and Ventyx. Beware, their offerings can get pretty expensive and there's often no standard list pricing. Also, I strongly encourage you to always do your own validation of any model data they might give you, so the work you're doing to produce your own models is probably not wasted.
I personally use Qalculate (https://qalculate.github.io/), specifically their CLI version for this purpose. I'm not sure how well it compares to GNU Units, but it works well enough for my needs; and it's fairly simple due to the English syntax.
I was about to say the same. ;-) Except I use the Qt UI.
Units of measure are, of course, the aboriginal type system for pre-software hand calculation.. carrying units along to make sure you do not add apples to oranges { unless you know how to convert "apples" to "oranges" for some adapted metaphorical fruits.. e.g. orange section/segment/slices :-) }.
Nim [1] has sufficient compile-time strength that units can be integrated with the static type system: https://github.com/SciNim/Unchained
[1] https://nim-lang.org/
Nim [1] has sufficient compile-time strength that units can be integrated with the static type system: https://github.com/SciNim/Unchained
[1] https://nim-lang.org/
F# also has units integrated into the type system. Seems like a great feature though I've never used a language with it.
Just for curiosity, what Nim does that other languages with operator overloading wouldn't do? Aside from the "number.unit" syntax, you could do some trickery to get units comparison and conversions even on C++
> units comparison and conversions even on C++
See mp-units[1].
[1]: https://github.com/mpusz/mp-units
See mp-units[1].
[1]: https://github.com/mpusz/mp-units
I work in large C++ codebase for a suite of physics simulation software, and there are like 200 something strongly typed arithmetic units here.
Anything with a finite (200 is small even) number of units misses the algebraic structure of the problem mentioned in https://news.ycombinator.com/item?id=36988497 wherein multiplying|dividing two things gives you a (potentially) new unit which implies an open ended "space" of units.
To be concrete (hah!), in C++ a template meta-type with 12 signed integer parameters (6 numerators & 6 denominators for rational exponents of SI base units) might be one way to model it.
Unlike C++ template stuff, Nim macros (like Lisp macros) makes metaprogramming more like procedural programming - just against abstract syntax trees. I think that helps to shield some of this type complexity from users, but the documentation README https://github.com/SciNim/Unchained does better job than I can in an HN comment.
Of course, for unit system conversion, the number of dimensions (6 in SI, 3 in CGS/Gaussian) changes. So, for full generality you need compile-time (if you want static type integration/CT errors) linear algebra over a rational field (at least & conventionally) to project|inverse project. That might be theoretically possible in C++. I would think it very un-fun and unlikely to ever have been done. There's probably a Mathematica package, though.
EDIT: It seems that mp-units mentioned in a sibling comment has some rare support for varying unit systems (no GR or Planck ones, but at least "natural" & "hep" & not sure about system-conversion or just system-use). That lib also leans very heavily on many very modern C++ (C++20 & beyond) features, has constexpr everywhere in use cases. I am not sure I would say it shields users wonderfully or makes it seem like units are very ordinary types. Just looking at mp-units/example/VARIOUS.cpp makes it look syntactically very noisy, verbose, and a lot to learn.
To be concrete (hah!), in C++ a template meta-type with 12 signed integer parameters (6 numerators & 6 denominators for rational exponents of SI base units) might be one way to model it.
Unlike C++ template stuff, Nim macros (like Lisp macros) makes metaprogramming more like procedural programming - just against abstract syntax trees. I think that helps to shield some of this type complexity from users, but the documentation README https://github.com/SciNim/Unchained does better job than I can in an HN comment.
Of course, for unit system conversion, the number of dimensions (6 in SI, 3 in CGS/Gaussian) changes. So, for full generality you need compile-time (if you want static type integration/CT errors) linear algebra over a rational field (at least & conventionally) to project|inverse project. That might be theoretically possible in C++. I would think it very un-fun and unlikely to ever have been done. There's probably a Mathematica package, though.
EDIT: It seems that mp-units mentioned in a sibling comment has some rare support for varying unit systems (no GR or Planck ones, but at least "natural" & "hep" & not sure about system-conversion or just system-use). That lib also leans very heavily on many very modern C++ (C++20 & beyond) features, has constexpr everywhere in use cases. I am not sure I would say it shields users wonderfully or makes it seem like units are very ordinary types. Just looking at mp-units/example/VARIOUS.cpp makes it look syntactically very noisy, verbose, and a lot to learn.
I haven’t looked at the code for this but somehow I think the conversion problem is very similar to a graph search. If you build a graph in which the vertices are the units and the edges are compatible convert scales, you can use this graph with say, BFS to find the right traversal path. Multiplying the scales would get you the result converting from a unit to another. Or, dividing would give you the reversed conversion.
I used to think we could use a hash table for this kind of stuff. It is faster of course but you need to account for all sort of conversion, even the crazy ones like Lightyear to feet’s, for instant. With the graph, I think I could just throw everything in it. No matter how crazy the conversion is, if there is a path, you will get it!
How does GNU unit get the conversion tables to bootstrap, does anybody know?
How does GNU unit get the conversion tables to bootstrap, does anybody know?
no dude you're seriously overcomplicating the problem
it's just a finite-dimensional vector space over ℚ
https://en.wikipedia.org/wiki/Dimensional_analysis#Mathemati...
the conversion tables are in /usr/share/units/definitions.units (or previously /usr/share/misc/units.dat)
they are the result of many years of careful scholarship by adrian mariano
it's just a finite-dimensional vector space over ℚ
https://en.wikipedia.org/wiki/Dimensional_analysis#Mathemati...
the conversion tables are in /usr/share/units/definitions.units (or previously /usr/share/misc/units.dat)
they are the result of many years of careful scholarship by adrian mariano
It's more like a 2-level situation for most things with a little more structure than you might realize. There are "physical kinds" or meta types like "energy" and then different concrete units those can be which allow conversion.
The physical kind is a point in an N-dimensional rational space of exponents of base units, such as Mass * Distance ^2 * Time^-2 or (1,2,-2) for energy (maybe with some carry over ^0s for unused slots of a >3D meta-type space). Additive (like add, subtract, compare, and convert) are only meaningful at the same point in that lattice. If you are interested in learning more, this is all a part of dimensional analysis: https://en.wikipedia.org/wiki/Dimensional_analysis .
Even the dimensionality of that rational exponent space (the "unit system", if you will) is more of convenience / convention than fundamental. https://en.wikipedia.org/wiki/Planck_units clobber most things away leaving only 1 dimension (and a tendency for complex rational exponents). Meanwhile, the SI unit system is very "dimension promiscuous" (mass, length, time, electric current, temperature, amount of substance, luminous intensity) [1] to avoid non-integer exponents (but you cannot really forever since as soon as some formula has some square some solution of it has some root that probably gets you a 1/2 exponent).
There are some situations with not purely "conversion factor" scale offsets like thermal units (e.g. Celsius to Fahrenheit) that people often describe in math-ese as "affine conversions". Something like GNU Units attends these things, but they are kind of "conversion only" orphan step-children more than "real" types which "compose better". In physics formulae one will often only care about delta-Temperature, not levels, for example.
EDIT: The implicit creation of a potentially brand new type any time you multiply | divide two extant things is, incidentally, why you need either a dynamic or a very powerful static type system to express these things.
[1] https://en.wikipedia.org/wiki/International_System_of_Units
The physical kind is a point in an N-dimensional rational space of exponents of base units, such as Mass * Distance ^2 * Time^-2 or (1,2,-2) for energy (maybe with some carry over ^0s for unused slots of a >3D meta-type space). Additive (like add, subtract, compare, and convert) are only meaningful at the same point in that lattice. If you are interested in learning more, this is all a part of dimensional analysis: https://en.wikipedia.org/wiki/Dimensional_analysis .
Even the dimensionality of that rational exponent space (the "unit system", if you will) is more of convenience / convention than fundamental. https://en.wikipedia.org/wiki/Planck_units clobber most things away leaving only 1 dimension (and a tendency for complex rational exponents). Meanwhile, the SI unit system is very "dimension promiscuous" (mass, length, time, electric current, temperature, amount of substance, luminous intensity) [1] to avoid non-integer exponents (but you cannot really forever since as soon as some formula has some square some solution of it has some root that probably gets you a 1/2 exponent).
There are some situations with not purely "conversion factor" scale offsets like thermal units (e.g. Celsius to Fahrenheit) that people often describe in math-ese as "affine conversions". Something like GNU Units attends these things, but they are kind of "conversion only" orphan step-children more than "real" types which "compose better". In physics formulae one will often only care about delta-Temperature, not levels, for example.
EDIT: The implicit creation of a potentially brand new type any time you multiply | divide two extant things is, incidentally, why you need either a dynamic or a very powerful static type system to express these things.
[1] https://en.wikipedia.org/wiki/International_System_of_Units
Wouldn't the most sensible option just be too have the SI units at the center and everything else heaving a conversion edge to that? While intriguing, there is probably no need to make that graph any denser.
Yep. Especially if using a bignum library to keep sufficient precision during the intermediate conversion.
Then how do you deal with non-SI units, like money?
Notice how money isn't handled (at least per the examples) by GNU Units. Because currency (and fungible financial instruments in general) have variable exchange rates.
For currency conversion, it's a lot more tricky because there's many ways to convert. Eg; if I want to go from CHF to USD there's a lot of CHF->USD volume and there are market rates for that exact conversion. But between eg; SGD (singapore dollar) and Peruvian Soles (PEN) the market is a lot smaller so it may be actually beneficial to do SGD -> USD -> PEN.
Typically this means ingesting a feed of real time prices + any fees and then doing a limited-hop graph traversal.
For currency conversion, it's a lot more tricky because there's many ways to convert. Eg; if I want to go from CHF to USD there's a lot of CHF->USD volume and there are market rates for that exact conversion. But between eg; SGD (singapore dollar) and Peruvian Soles (PEN) the market is a lot smaller so it may be actually beneficial to do SGD -> USD -> PEN.
Typically this means ingesting a feed of real time prices + any fees and then doing a limited-hop graph traversal.
money is handled by gnu units
the base unit is the us dollar
this is arguably incorrect but inarguably useful
from the man page:
> The units program database includes currency exchange rates and prices for some precious metals. Of course, these values change over time, sometimes very rapidly, and ‘units’ cannot provide real-time values. To update the exchange rates, run ‘units_cur’, which rewrites the file containing the currency rates, typically ‘/var/lib/units/currency.units’ or ‘/usr/local/com/units/currency.units’ on a Unix-like system or ‘C:\Program Files (x86)\GNU\units\definitions.units’ on a Windows system.
the base unit is the us dollar
this is arguably incorrect but inarguably useful
from the man page:
> The units program database includes currency exchange rates and prices for some precious metals. Of course, these values change over time, sometimes very rapidly, and ‘units’ cannot provide real-time values. To update the exchange rates, run ‘units_cur’, which rewrites the file containing the currency rates, typically ‘/var/lib/units/currency.units’ or ‘/usr/local/com/units/currency.units’ on a Unix-like system or ‘C:\Program Files (x86)\GNU\units\definitions.units’ on a Windows system.
It is interesting because I see a file `currency.units` in the source distribution. It has the list of all countries' currencies normalized to USD. If Units doesn't deal with currency, why does it maintain this conversion file? And, I agree that the exchange rate varies day to day. But, this may provide an estimate conversion.
You can't really convert units of money to any other units, so I'm not convinced of the utility of money conversion in this kind of tool.
US Dollars would be connected to US Cents in the graph, and Pounds Sterling and New Pence would be connected to each other too, but those two subgraphs would be entirely disconnected from each other and from any SI unit like distance or mass.
US Dollars would be connected to US Cents in the graph, and Pounds Sterling and New Pence would be connected to each other too, but those two subgraphs would be entirely disconnected from each other and from any SI unit like distance or mass.
It's useful for some practical conversions like fuel efficiency calculations. I think in USD per mile and it's handy to be able to directly take CAD/liter and l/km for my trips to Canada.
Money (currency, really) is a whole forest of units with bespoke scales, arithmetic, and market-driven conversion logic. If you are converting money to other units with a library, you are almost certainly doing it wrong, or are operating at a level of abstraction much higher than my puny brain can fathom.
Just pick a unit as the "standard" for that type of quantity.
Convert to USD then back. Which is what Units does.
Think a spoke/hub type thing would be a lot easier. Just convert inputs to SI, then from SI to the output.
Parent was suggesting a hash table lookup though, in which case the topology of the graph would be irrelevant. The number of entries in the table would be constant regardless of whether the original graph was connected with the fewest number of edges or with the greatest number of edges (a complete graph, which is what the table would be encoding).
I get it that some suggest the graph is a complicated/over-engineer while other suggest just stick to SI. Well, my rationale is that not everything has a SI conversion, and simple SI/hub/spoke would need you to maintain a unit -> SI (or base unit like USD in currency conversion).
What I like about the graph solution is that you don’t have to use SI or base unit at all! If your graph has km -> m, now you add (updating your graph) for m -> feet, you could traverse from km -> feet. Later on, you can add nautical mile -> feet, using this graph you could basically get km -> nautical mile if you need to.
What I like about the graph solution is that you don’t have to use SI or base unit at all! If your graph has km -> m, now you add (updating your graph) for m -> feet, you could traverse from km -> feet. Later on, you can add nautical mile -> feet, using this graph you could basically get km -> nautical mile if you need to.
My current alias for units is "units -1v -d max". This makes this improves output and uses max precision.
Is there a spreadsheet that supports units in its cells and GNU Units in formulas? Seems like that would be an amazing open source tool.
to my surprise, it turns out that org-mode's spreadsheet does support units, because it uses emacs calc-eval. But calc seems to have its own dimensional analysis engine rather than using gnu units. i was hoping to get a temperature in this last column, for example:
| 3 mm | 4 kg | 0.44444444 kg / mm^2 | 44.444444 kg m^2 / (s^2 mm^2) | (44.444444 kg m^2 / (s^2 mm^2 stefanboltzmann))^0.25 |
| 2 mm | 1 kg | kg / (4 mm^2) | 25 kg m^2 / (s^2 mm^2) | (25 kg m^2 / (s^2 mm^2 stefanboltzmann))^0.25 |
#+TBLFM: $3=$2/$1/$1::$4=$3*(10m/s)**2::$5=($4/ stefanboltzmann)**(1/4)
| 3 mm | 4 kg | 0.44444444 kg / mm^2 | 300 mm m^2 / s^2 | (300 mm m^2 / (s^2 stefanboltzmann))^0.25 |
| 2 mm | 1 kg | kg / (4 mm^2) | 200 mm m^2 / s^2 | (200 mm m^2 / (s^2 stefanboltzmann))^0.25 |
#+TBLFM: $3=$2/$1/$1::$4=$1*(10m/s)**2::$5=($4/ stefanboltzmann)**(1/4)
| 22.8 Wh | 16.8 Wh | 6. Wh | 7.4W | 0.81081081 Wh / W |
#+TBLFM: $3=$1-$2::$5=$3/$4Not a full spreadsheet, but I have a passion project that can support units:
https://instacalc.com/56734
I wanted a quick, shareable "back of the envelope" tool.
https://instacalc.com/56734
I wanted a quick, shareable "back of the envelope" tool.
One of my favorite feature is guessing the physical quantity from the dimensions. For example:
You have: A / m
You want: ?
H_FIELD B_FIELD / (mu0/mu0_SI)
MAGNETIZATION MAGNETIC_DIPOLE_MOMENT / VOLUME
Oe oersted
oe Oe
oersted gauss / mu0
A ! # The ampere, symbol A, is the SI unit of electric current.
ampere A # It is defined by taking the fixed numerical value of the
amp ampere # elementary charge, e, to be 1.602 176 634 * 10^-19 when
# expressed in the unit C, which is equal to A*s.
#
# The previous definition was the current which produces a
# force of 2e-7 N/m between two infinitely long wires a meter
# apart. This definition was difficult to realize accurately.
#
# The ampere is actually realized by establishing the volt and
# the ohm, since A = V / ohm. These measurements can be done
# using the Josephson effect and the quantum Hall effect,
# which accurately measure voltage and resistance, respectively,
# with reference to two fixed constants, the Josephson
# constant, K_J=2e/h and the von Klitzing constant, R_K=h/e^2.
# Under the previous SI system, these constants had official
# fixed values, defined in 1990. This created a situation
# where the standard values for the volt and ohm were in some
# sense outside of SI because they depended primarily on
# constants different from the ones used to define SI. After
# the revision, since e and h have exact definitions, the
# Josephson and von Klitzing constants will also have exact
# definitions that derive from SI instead of the conventional
# 1990 values.
#
# In fact we know that there is a small offset between the
# conventional values of the electrical units based on the
# conventional 1990 values and the SI values. The new
# definition, which brings the practical electrical units back
# into SI, will lead to a one time change of +0.1ppm for
# voltage values and +0.02ppm for resistance values.
#
# The previous definition resulted in fixed exact values for
# the vacuum permeability (mu0), the impedance of free space
# (Z0), the vacuum permittivity (epsilon0), and the Coulomb
# constant. With the new definition, these four values are
# subject to experimental error.GNU Units is an absolute favourite of mine and a true gem. I'd first learnt of it through an HN perennial, Trey Harris's "The 500 Mile Email" (61 submissions, and counting: <https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...>).
It wasn't until a decade or so of using it that I realised it was actually a units-aware calculator, and could make interesting conversions (say: how much land area you'd need to supply all US energy needs with solar power, given various factors of incident sunlight, spacing factors, panel efficiencies, etc.). kragen's comment in this thread blows away my own usage (I learned several new things reading it, which means this is a Good Day).
Note for MacOS and *BSD users: the variant of units shipping on your systems is a parlously pale shadow of the GNU version. MacOS boffins can install GNU Units via Homebrew, where it's accessed as "gunits" by default.
It wasn't until a decade or so of using it that I realised it was actually a units-aware calculator, and could make interesting conversions (say: how much land area you'd need to supply all US energy needs with solar power, given various factors of incident sunlight, spacing factors, panel efficiencies, etc.). kragen's comment in this thread blows away my own usage (I learned several new things reading it, which means this is a Good Day).
Note for MacOS and *BSD users: the variant of units shipping on your systems is a parlously pale shadow of the GNU version. MacOS boffins can install GNU Units via Homebrew, where it's accessed as "gunits" by default.
At some point I was looking at using a units library, but came up short because I could not find one that could convert using log scale units (which I needed). The same is True for gnu units.
It can convert from linear to log units, e.g.:
You have: 10W You want: dBm 40
but not the other way around (unless I'm missing something):
You have: 40 dBm ^ Parse error
I understand that log units are tricky to get right, but in some fields they are pretty ubiquitous.
It can convert from linear to log units, e.g.:
You have: 10W You want: dBm 40
but not the other way around (unless I'm missing something):
You have: 40 dBm ^ Parse error
I understand that log units are tricky to get right, but in some fields they are pretty ubiquitous.
You have: dBm(40)
You want: W
* 10
/ 0.1
You have: ~dBm(2 W + dBm(10))
You want:
Definition: 33.031961
I actually did a WebAssembly port of the GNU Units library and you can now use it in your browser.
Demo: https://yanosh.net/units-wasm/ GitHub Repo for the demo: https://github.com/yanosh-k/units-wasm GitHub Repo for the WASM project: https://github.com/yanosh-k/gnu-wasmunits
Demo: https://yanosh.net/units-wasm/ GitHub Repo for the demo: https://github.com/yanosh-k/units-wasm GitHub Repo for the WASM project: https://github.com/yanosh-k/gnu-wasmunits
Wow I was just preparing to start this project myself. Before starting the process I did a last minute check and found this. Goes to show you that all you need to do is wait and someone will write the code for you.
Thank you!
Thank you!
You have: 20 furlongs per fortnight
You want: miles per hour
* 0.0074404762
/ 134.4
https://en.wikipedia.org/wiki/FFF_system
You want: miles per hour
* 0.0074404762
/ 134.4
https://en.wikipedia.org/wiki/FFF_system
I also highly recommend checking out https://frinklang.org/
ah, so that's how you do °C / °F ...
You have: tempF(45)
You want: tempC
7.2222222I use this daily eg.
temp 42F
temp 39C
#!/bin/sh
if echo "$1" | grep -q '[0-9][0-9]*[fF]' ; then
val=`units "tempF( $(echo $1 | sed 's/[a-zA-Z]//g') )" tempC`
echo ${val}C
else
val=`units "tempC( $(echo $1 | sed 's/[a-zA-Z]//g') )" tempF`
echo ${val}F
fi
exit 0Temperature is weird. every other measurement scale starts at 0 but nether C nor F does. you have to use kelvin or rankine for that. This throws a big wrench into the calculation engine as now it has to support offsets for this one single use case. In fact openbsd units still does not support the C to F calculation.
It's even more weird than that.
units(1) can compute "starting at T Celsius, if i add N degrees celsius, how many degrees Fahrenheit did I add? and defaults to this for naive attempts to convert between the two, AND "what is X Fahrenheit in Celsius?"
That is, it can convert between delta-C and delta-F, and also between absolute C and F.
units(1) can compute "starting at T Celsius, if i add N degrees celsius, how many degrees Fahrenheit did I add? and defaults to this for naive attempts to convert between the two, AND "what is X Fahrenheit in Celsius?"
That is, it can convert between delta-C and delta-F, and also between absolute C and F.
this one single use case
?!
$ units
Currency exchange rates from FloatRates (USD base) on 2023-08-03
3539 units, 109 prefixes, 111 nonlinear units
You have: dBm(0)
You want:
You want:
Argument of function outside domain
You have: gasmark(0.25)
You want:
You want:
You want:
You want:
You want:
You want:
You want:
You want:
You want:
You want:
You want:
You want:
You want:
brwiregauge <piecewise linear>
drillgauge <piecewise linear>
gaugepressure <nonlinear>
plategauge <piecewise linear>
screwgauge <nonlinear>
standardgauge 4 ft + 8.5 in
stdgauge <piecewise linear>
wiregauge <nonlinear>
zincgauge <piecewise linear>
You have: plategauge(0)
You want:
You want:
You want:
You want: sugar_conc_bpe # computed via this
You want:
You want:
You want:
You want: psi
?!
$ units
Currency exchange rates from FloatRates (USD base) on 2023-08-03
3539 units, 109 prefixes, 111 nonlinear units
You have: dBm(0)
You want:
Definition: 0.001 kg m^2 / s^3
You want:
Definition: 1000 mol / m^3
Argument of function outside domain
You have: gasmark(0.25)
You want:
Definition: 380.37222 K
You want:
Definition: 394.26111 K
You want:
Definition: 401.20556 K
You want:
Definition: 408.15 K
You want:
Definition: 411.62222 K
You want:
Definition: 0.20955 m
Definition: shoesize_men(n) = shoe_men0 + n shoesize_delta
n is dimensionless
You want:
Definition: 2.5110222e-27 cd / m^2
Definition: airmass(alt) = 1 / (sin(alt) + 0.50572 (alt / degree + 6.07995)^-1.6364)
defined for 0 degree <= alt <= 90 degree
You want:
Definition: 37.919608
Definition: atm_transmissionz(zenith) = exp(-extinction_coeff airmassz(zenith))
defined for 0 degree <= zenith <= 90 degree
You want:
Definition: 0.77637004
You want:
Definition: 0.81063327
You want:
Definition: 9.746164e-06 cd sr / m^2
You want:
Definition: 2.54e-06 cd sr / m^2
You want:
Definition: 1000 kg / m^3
brwiregauge <piecewise linear>
drillgauge <piecewise linear>
gaugepressure <nonlinear>
plategauge <piecewise linear>
screwgauge <nonlinear>
standardgauge 4 ft + 8.5 in
stdgauge <piecewise linear>
wiregauge <nonlinear>
zincgauge <piecewise linear>
You have: plategauge(0)
You want:
Definition: 0.0079375 m
You want:
Definition: 0.0082514628 m
You want:
Definition: 1475.0252 kg / m^3
You want: sugar_conc_bpe # computed via this
86.975291
Definition: interpolated table with points
sugar_conc_bpe(0) = 0 K
sugar_conc_bpe(5) = 0.0788 K
sugar_conc_bpe(10) = 0.169 K
sugar_conc_bpe(15) = 0.2729 K
...
sugar_conc_bpe(99.6) = 70.1448 K
sugar_conc_bpe(99.7) = 76.7867 K
You want:
Definition: 1076.0456 kg / m
You want:
Definition: 256
You want:
Definition: 64
You want: psi
* 14.695949
/ 0.068045964
Thanks, that was puzzling me at first.
Slightly related...
I have once created a c++ templated class that encapsulates all SI units. Using the values of the different SI quantities, you can let the compiler perform all kinds of quantity interference or checking.
What on Earth is an "aeginamina?"[1]
[1] https://www.gnu.org/software/units/manual/units.html
[1] https://www.gnu.org/software/units/manual/units.html
It's an ancient unit of weight or currency. See the first answer on this page: https://www.reddit.com/r/commandline/comments/oy6xk5/units_c...
(2016)
Posted a few times recently
Here's some more discussion 3 years ago: https://news.ycombinator.com/item?id=25657311
Posted a few times recently
Here's some more discussion 3 years ago: https://news.ycombinator.com/item?id=25657311
It's not (2016) in my opinion - this page was last updated then, but the most recent release of the software was in 2022.
If we’re going by age of article, (1997) is probably closer:
http://ftp.gnu.org/gnu/units/
Though, back then, most GNU utils were copies of older unix stuff, so (1980) or even (1960) wouldn’t surprise me.
http://ftp.gnu.org/gnu/units/
Though, back then, most GNU utils were copies of older unix stuff, so (1980) or even (1960) wouldn’t surprise me.
Related:
GNU Units - https://news.ycombinator.com/item?id=25657311 - Jan 2021 (203 comments)
GNU Units - https://news.ycombinator.com/item?id=25657311 - Jan 2021 (203 comments)
When I run `sudo pacman -Fy units` on Arch Linux I only get a similar tool from plan9port, it's strange they took the GNU version out of the repos.
Without looking into it at all, it probably just didn't have an active package maintainer.
The author of the AUR package, removed it from the community repo and moved it to the AUR. And now it has another maintainer in the AUR.
The original maintainer still maintains 2185 packages [2].
Can't find an explanation why though.
[0]: https://github.com/archlinux/svntogit-community/commit/2b5ec...
[1]: https://aur.archlinux.org/cgit/aur.git/commit/?h=units&id=e6...
[2]: https://archlinux.org/packages/?packager=arojas
The original maintainer still maintains 2185 packages [2].
Can't find an explanation why though.
[0]: https://github.com/archlinux/svntogit-community/commit/2b5ec...
[1]: https://aur.archlinux.org/cgit/aur.git/commit/?h=units&id=e6...
[2]: https://archlinux.org/packages/?packager=arojas
Interesting! Good sleuthing, that is odd. Guessing arojas just didn't want to deal with it any more so they moved it to the AUR and handed it over to someone else straight away. Maybe it had some quirk that made it not worth the time, though I dunno how it would, there's only a new release of units roughly once a year. http://ftp.gnu.org/gnu/units/
Yeah looks like you need to install `units` from AUR.
I've been learning emacs calc (my HP-48g calculator finally died) and it seems to have this built-in. It's super impressive.
i was excited by your comment but disappointingly emacs calc seems to have its own, less powerful unit conversion system https://news.ycombinator.com/item?id=36991392
It would be nice to get implemented as an extension in VScode.
Having used Emacs for most of my adult life, I find it pretty amazing that basic unit conversion isn't a part of every OS out there. I use it several times every week. I don't use the gnu units package though, I stay with the functionality built into Emacs calc.
> You have: 17 yards + 2 feet + 5 inches
Measuring things like this seems brain dead.
Measuring things like this seems brain dead.
Yes, it's a sample, like how sample programming code snippets use names such as Foo and Bar. Similarly braindead to do it in practice!
Though imperial-system users don't mix units like that, it's not like "20 minutes 30 seconds", they just use fractions or decimals as appropriate. "20 and a half minutes" or "20.5 minutes". You'd just say "17.8 yards".
(Metric user here, with an appreciation for base 12)
Though imperial-system users don't mix units like that, it's not like "20 minutes 30 seconds", they just use fractions or decimals as appropriate. "20 and a half minutes" or "20.5 minutes". You'd just say "17.8 yards".
(Metric user here, with an appreciation for base 12)
imperial system users totally do mix units like that: 5 feet 10 inches, two pounds and six ounces, nine stone and six pounds
nobody has a tape measure marked in decimal yards or decimal feet, so nobody is going to say 17.8 feet or 17.8 yards
sexagesimal system users also mix units like this: 2 hours, 10 minutes, and 5.2 seconds
same for larger units of time: 5 years, 2 months, and 12 days (which is an example units(1) can't hack)
nobody has a tape measure marked in decimal yards or decimal feet, so nobody is going to say 17.8 feet or 17.8 yards
sexagesimal system users also mix units like this: 2 hours, 10 minutes, and 5.2 seconds
same for larger units of time: 5 years, 2 months, and 12 days (which is an example units(1) can't hack)
I wish our number system was duodecimal. Then we probably would have ended up with base-12 metric, which would have been freaking awesome.
units supports the dozenal system by default
You have: QuedraTim
You want: hour
* 1
/ 1
You have: QuedraTim
You want: minutes
* 60
/ 0.016666667
You have: TrinaTim
You want: minutes
* 5
/ 0.2
You have: DunaTim
You want: minutes;seconds
25 seconds
You have: QuenaTim
You want: hour
* 12
/ 0.083333333
You have: Grafut
You want:
Definition: gravity Tim^2 = 0.29558045 m
You have: QuedraGrafut
You want:
Definition: 12^4 Grafut = 6129.1562 mMeasuring is a highly subjective and personal experience in general.
As a physics undergrad I had a fascinating discussion with a lecturer on metrology. I always used SI units, my friend always preferred natural units, and the lecturer used gaussian units frequently (which always threw me off).
My position was that SI is the only reasonable measuring system because it’s a widely accepted standard, has no silly conversions, and bears resemblance to things we experience in every day life. I can space my hands apart by a metre through guesswork and I’m generally quite close, but centimetres or inches I’m awful at (any excuse, eh?). I can judge how many kilograms something is but not grams or pounds.
“Ah,” said the lecturer. “But these are units you are familiar with because they match your everyday experiences. In mine, statVolts etc are the most natural thing in the world - I don’t have constants where I don’t need them, and my numerical results are at a comfortable order of magnitude”.
“The most natural thing in the world are the universal constants - planck’s constant, the speed of light, the charge on an electron”, countered my friend. “If I measured something in those, anyone or anything in the universe, under any physical conditions, can recreate my measurements. If civilisation ended and my calculations were discovered millions of years later by an entirely new intelligent species, they would understand it with enough legwork”.
I quickly became a proponent of natural units. But then 50mph signs being renamed to 7.46e-8 might not go down well with the highways agency.
Anyway, the point of this story is that measurements are measurements, as long as they’re consistent. It isn’t about intellect, it’s about what you’re working with, what you normally work with, culture, and all kinds of things. If you have a 17 yard thingamagig and need 2ft clearance on one side and 5in clearance in the other, then this is a perfectly reasonable task to ask a computer with a teraflop or so of computational power.
As a physics undergrad I had a fascinating discussion with a lecturer on metrology. I always used SI units, my friend always preferred natural units, and the lecturer used gaussian units frequently (which always threw me off).
My position was that SI is the only reasonable measuring system because it’s a widely accepted standard, has no silly conversions, and bears resemblance to things we experience in every day life. I can space my hands apart by a metre through guesswork and I’m generally quite close, but centimetres or inches I’m awful at (any excuse, eh?). I can judge how many kilograms something is but not grams or pounds.
“Ah,” said the lecturer. “But these are units you are familiar with because they match your everyday experiences. In mine, statVolts etc are the most natural thing in the world - I don’t have constants where I don’t need them, and my numerical results are at a comfortable order of magnitude”.
“The most natural thing in the world are the universal constants - planck’s constant, the speed of light, the charge on an electron”, countered my friend. “If I measured something in those, anyone or anything in the universe, under any physical conditions, can recreate my measurements. If civilisation ended and my calculations were discovered millions of years later by an entirely new intelligent species, they would understand it with enough legwork”.
I quickly became a proponent of natural units. But then 50mph signs being renamed to 7.46e-8 might not go down well with the highways agency.
Anyway, the point of this story is that measurements are measurements, as long as they’re consistent. It isn’t about intellect, it’s about what you’re working with, what you normally work with, culture, and all kinds of things. If you have a 17 yard thingamagig and need 2ft clearance on one side and 5in clearance in the other, then this is a perfectly reasonable task to ask a computer with a teraflop or so of computational power.
One of the best features of my HP-50G calculator is the units library.
how does it handle the examples i posted in https://news.ycombinator.com/item?id=36988917
Great utility. Almost the only thing I use Termux for nowadays.
(2016)
gnunits*
GNU should make it's own system of measurement, best of all :)
how long will my laptop take to charge at its current rate of charging?
how long will a 2000mAh 18650 cell take to discharge at 2.5 watts, using a nominal voltage of 3.7 volts?
what energy density is that, so i can compare it to the volume needed for other forms of energy storage?
what's the specific energy of stoichiometrically mixed oxyhydrogen fuel?
okay but how much volume? say at atmospheric pressure?
so that's how much energy density?
(i may be off by a factor of 2 here)
how much energy can this capacitor hold?
how much energy density is that?
how thick of a cable do i need to support me in a lightweight fabric-sling chair (or, from a different point of view, to pose a risk of accidental strangulation)? suppose its tensile strength is 2.7 gigapascals
note that this is the radius of the cable, not its diameter!
the datasheet says this 400×240 display uses 175 μW if all the pixels flip once per second and 60 μW for a static display. how much energy is that per pixel flip?
if i overclock it to 60 fps how much power will it use?
and how many pixels is its diagonal?
what is the visual angle subtended by the sun as seen from earth?
okay, how does that compare to the moon?
on average the moon looks a little smaller, which is why annular eclipses are so common, but we can also calculate that total eclipses are possible because sometimes the moon looks bigger
what percentage of this copper sulfate is actual copper?
how fast can i write to this slc flash chip without wearing it out in 53 years, assuming perfect wear leveling and no write amplification?
how much fuel will this truck need to get across the country?
how much is that per kilogram of lettuce or sodium lauryl sulfate or whatever?
okay, but how much energy is 52 mℓ of diesel per kg of lettuce?
how much data can i transfer overnight during unmetered hours on a 2400-baud modem?
how much power does the earth receive from the sun, assuming a solar constant of 1400 W/m²?
what would the equilibrium temperature of an object be if it were illuminated at that brightness and had a flat emission spectrum?
how about here in buenos aires at the winter solstice? first, what angle is the sun at anyway? we're at 34°36’ south, and the sun's latitude at the solstice is 23°26’
so that reduces the peak insolation to how much? here underneath the atmosphere we only get 1kW/m²
and that would be what temperature in equilibrium?
(integrating the sun's angle over the course of the day as the earth rotates is sadly beyond its capacities)
how much money could a sensible heat storage reservoir of 15 kg of water save me over 16 years? say power rates go down to only 2.5¢/kWh because of solar
what's the surface area of a 300mm × 400mm × 150mm backpack? like how much cloth?
okay but in cm²
what's the electrical impedance of a 1000 μF cap at an audio highpass frequency of 20Hz?
what's the time constant of 100 pF (roughly the smallest capacitance you can get in a macroscopic circuit with any degree of precision) and 1 MΩ?
okay. so how long will an 0.1μF cap take to discharge through a 100kΩ resistor from 5 volts down to a 1.3 volt threshold?
how many bits of precision does a linear adc need to be able to measure a difference of 1.8 millivolts if 1.5 volts is full-scale?
if this oxygen absorber contains 7 grams of iron which oxidizes to Fe₂O₃, how much air can it remove all the oxygen from? air is 21% oxygen by volume (and roughly by mass) and weighs 1.2 grams per liter
i've lost 7 kg over the last two months; how much of a caloric deficit does that represent in my diet?
if you were to spread the moon evenly over russia, how deep would it be?
how big is nigeria compared to massachusetts?
how many ounces of platinum is a ton of oil worth at 40 dollars per megawatt hour?
or in grams?