-
Notifications
You must be signed in to change notification settings - Fork 670
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
DCD file reader EOF error #4057
Comments
Yes, that is most likely the issue. I will stick with 2.1 for now, it is
good enough for me, but will keep an eye out for the patch.
…On Tue, Mar 7, 2023 at 9:55 AM Irfan Alibay ***@***.***> wrote:
I suspect this is probably related to #4039
<#4039>? Does version 2.3
work for you @dkonstan <https://github.com/dkonstan> ? We'll be releasing
a patch release to fix this issue soon.
—
Reply to this email directly, view it on GitHub
<#4057 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALLHQPZG2U5Y5WIMRIN4NZ3W25D7PANCNFSM6AAAAAAVSSCGUI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Close as duplicate of #4039 ? |
Perhaps it's not worth mentioning now if this is going to be closed, however, this may be helpful information. I am experiencing a similar error, except it only occurs when slicing the trajectory. It always occurs at the same frame of a somewhat large (100,000 frames, 6.7 gb) trajectory. A minimal example is: u = mda.Universe("./test_data_files/lv300.data", "./test_data_files/dump300.dcd",)
for ts in u.trajectory[:-1]:
print(ts.frame) Always on the frame 29793, this gives the error:
Removing the indexing in the example above lets the trajectory run fine. If it helps, the trajectory is of a pure water box generated from lammps. MDAnalysis version is 2.4.2 from pip in macOS arm64. The issue does not occur with 2.3.0. |
Thanks @chappertron , when have a 2.4.3 patch release, could you please try again to check if the error persists? |
@orbeckst I'll keep an eye out for the release! |
@orbeckst This issue seems to be fixed for me! Thanks! |
In version 2.4 on Linux (a cluster running CentOS), the DCDReader often crashes with an EOF error. Usually the beginning of the trajectory is read ok, but after the beginning it crashes. To reproduce the error, just do
for ts in uni.trajectory:
pass
until it crashes, which it should. This happens for any trajectory. This is for python 3.10. I reverted to version 2.1 and the issue went away.
The text was updated successfully, but these errors were encountered: