We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For some calculators output number can be very small or very large. Therefore fixing manually constant precision is not the best solution.
There are some libraries which provide best-unit calculations, i.e.: https://www.npmjs.com/package/convert-units
The idea is to have a function which for 2e-9 (meters) returns "2 nm" and for 3200 (meters) returns "3.2 km".
More advanced implementation (but C++) can be found here: http://www.apc.univ-paris7.fr/~franco/g4doxy/html/G4UnitsTable_8cc-source.html
The text was updated successfully, but these errors were encountered:
See i.e. #283
Sorry, something went wrong.
No branches or pull requests
For some calculators output number can be very small or very large. Therefore fixing manually constant precision is not the best solution.
There are some libraries which provide best-unit calculations, i.e.:
https://www.npmjs.com/package/convert-units
The idea is to have a function which for 2e-9 (meters) returns "2 nm" and for 3200 (meters) returns "3.2 km".
More advanced implementation (but C++) can be found here: http://www.apc.univ-paris7.fr/~franco/g4doxy/html/G4UnitsTable_8cc-source.html
The text was updated successfully, but these errors were encountered: