Skip to content
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

VASP result export type map and poscar mismatch #778

Open
Cc-12342234 opened this issue Jan 13, 2025 · 0 comments
Open

VASP result export type map and poscar mismatch #778

Cc-12342234 opened this issue Jan 13, 2025 · 0 comments
Labels
wontfix This will not be worked on

Comments

@Cc-12342234
Copy link

Summary

When I was checking the type map converted by dpdata, I found that the atomic order and count were inconsistent with those in the POSCAR file, and also inconsistent with the line in OUTCAR containing "POSCAR:". When exporting without the type_map command, the order of type.raw matches the atomic numbering in the POSCAR file, but the order in type_map.raw does not correspond to the POSCAR file. Using the type_map command does not resolve this issue either.

dpdata Version

0.2.21

Platform, Python Version, etc

No response

Details

type.txt

type_map.txt

OUTCAR.txt

POSCAR.txt

@Cc-12342234 Cc-12342234 added the wontfix This will not be worked on label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant