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
Showing many significant digits for floating point numeric attributes is not useful and takes up a lot of visual space.
This is how ETA renders numeric attributes, which I request we adopt in Player51:
https://github.com/voxel51/eta/blob/ba108043fa9afb324915a7c2419c12e6a1768bed/eta/core/annotations.py#L1188
The text was updated successfully, but these errors were encountered:
Suggest also moving this one to player51 since this affects Scoop as well.
Side note: that will render anything between 0 and 0.05 as 0.00 - if some numeric attribute is always this small, truncating it may not be useful.
0.00
Sorry, something went wrong.
Got it. Let's do "%.2g" instead of "%.2f" for floating point numbers then
"%.2g"
"%.2f"
(I'll update ETA to match this)
That does have the following side effect, though:
>>> '%.2g' % 234 '2.3e+02'
compared to:
>>> '%.2f' % 234 '234.00'
Is scientific notation desirable for these? Or do we want the %f behavior for numbers >= 1?
%f
Another option:
>>> '%g' % 234 '234' >>> '%.2g' % .0001234 '0.00012'
No branches or pull requests
Showing many significant digits for floating point numeric attributes is not useful and takes up a lot of visual space.
This is how ETA renders numeric attributes, which I request we adopt in Player51:
https://github.com/voxel51/eta/blob/ba108043fa9afb324915a7c2419c12e6a1768bed/eta/core/annotations.py#L1188
The text was updated successfully, but these errors were encountered: