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
IOError in MDAnalysis/coordinates/TRZ.py", line 242, in _read_trz_header on big-endian arches #1424
Comments
Apparently, the TRZ file format is little-endian. Patch incoming. |
4 tasks
you mean the files we have are all little-endian? Or did you find some actual reference or standard description of the format online? |
the files don't exactly have a standard, they're just written by a Fortran |
orbeckst
pushed a commit
that referenced
this issue
Jun 22, 2017
Numpy dtype int (iN) and float (fN) specifiers assume native-endian by default, so force them to be little-endian. Closes #1424.
orbeckst
pushed a commit
that referenced
this issue
Jun 22, 2017
- Numpy dtype int (iN) and float (fN) specifiers assume native-endian by default, so force them to be little-endian. - Closes #1424. - added CHANGELOG entry and docs
kain88-de
pushed a commit
that referenced
this issue
Jun 24, 2017
- Numpy dtype int (iN) and float (fN) specifiers assume native-endian by default, so force them to be little-endian. - Closes #1424. - added CHANGELOG entry and docs
kain88-de
pushed a commit
that referenced
this issue
Jun 24, 2017
- Numpy dtype int (iN) and float (fN) specifiers assume native-endian by default, so force them to be little-endian. - Closes #1424. - added CHANGELOG entry and docs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour
Testsuite passes.
Actual behaviour
67 tests fail with:
Code to reproduce the behaviour
Run the testsuite on a big-endian arch like ppc64 or s390x. Example failure on ppc64: https://koji.fedoraproject.org/koji/taskinfo?taskID=20061305 (see build.log).
Current version of MDAnalysis:
0.16.1
The text was updated successfully, but these errors were encountered: