Double-precision numbers need at most 17 significant decimal digits to be serialised losslessly. Yet, savetxt() uses 19 by default, meaning that most files produced with savetxt() takes up about 9% more disk space than they need to, without any benefit. I have described the problem more detailed on Stackoverflow: https://stackoverflow.com/questions/77535380/minimum-number-of-digits-for-exact-double-precision-and-the-fmt-18e-of-numpy
Is there any reason behind the default choice of savetxt(..., fmt='%.18e')? If not, why not reduce it to savetxt(..., fmt='%.16e')? _______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
