-
Notifications
You must be signed in to change notification settings - Fork 5
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
[BUG] Segmentation fault when trying to convert VASP MD trajectory using ASE. #592
Comments
The trajectory file itself would definitely help us identify the problem. You are welcome to use MDANSE-help@stfc.ac.uk to send us the file, or a download link to the file. Overall, please share more details with us, such as the OS, Python version, ASE version and VASP version you were using. If your conversion run created a log file, you can send it to us too. I expect that, since it was a segmentation fault, you received no traceback from the Python interpreter. |
I have emailed the files over, they are quite large so hopefully they make it. The other information is as follows:
The Python traceback when the error is raised:
|
Thank you for the details. It appears that the ASE read function cannot handle the I will create a new issue in the ASE issue tracker, assuming that they have not seen this one before. I will inform you once we have a better solution to this problem. |
One more comment: what I wrote above was valid for the stable version of ASE 3.23.0 which would normally be installed together with MDANSE. If I manually install the development version of ASE (at the moment this is ase-3.23.1b1) after installing MDANSE, then the loading starts correctly, but I get a crash and an error like
after about 40-80% of the conversion has been completed. Which is more consistent with the error you reported. |
I get a segmentation fault when trying to convert a VASP trajectory, using the ASE convertoer.
I can share the relevant file if necessary by email; could likely be a user error.
The text was updated successfully, but these errors were encountered: