Fix for missing numpy data types on some platforms #514
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had some trouble with round-off errors today and noticed that my numpy doesn't actually have quadruple precision. So
np.float128will raise an error on my machine.np.longdouble, on the other hand, is just regular double on my machine. This is extremely weird behaviour that I neither like nor understand. I switched out the quadruple precision things for the word version so I can run the IO stuff with double precision at least.Notice that the numpy documentation says that
np.longdoubleis an alias fornp.float128on Linux x86_64 machines. So this fix applies to Mac and Windows users.