Skip to content
New issue

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

mincinfo -attvalue precision #11

Open
andrewjanke opened this issue Sep 21, 2012 · 0 comments
Open

mincinfo -attvalue precision #11

andrewjanke opened this issue Sep 21, 2012 · 0 comments

Comments

@andrewjanke
Copy link
Member

$ mincinfo -attvalue zspace:step test.mnc

0.0060000000000000001249

h5dump test.mnc | grep 06
(0): 0.006

mincinfo reports
0.0060000000000000001249 while hd5dump reports 0.06 exactly, I would
say the problem is with mincinfo. Of course a 1e-20 precision is
hardly sensical for most applications, but clearly when you start to
do math with these values it can still bite you.

Would it make sense to limit the precision with which mincinfo
-attvalue reports output? Either 'hard', or under user control?
Equivalent to the -m option to hd5dump perhaps (e.g., something like
"mincinfo -fp_format '%.6f' -attvalue xspace:step ...")?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant