8000 failed to read VASP: no atoms or `Number of atom types mismatches the number of counts` · Issue #60 · grimme-lab/mctc-lib · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

failed to read VASP: no atoms or Number of atom types mismatches the number of counts #60

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

Closed
e-kwsm opened this issue Apr 27, 2023 · 1 comment · Fixed by #64
Closed
Labels
bug Something isn't working

Comments

@e-kwsm
Copy link
Contributor
e-kwsm commented Apr 27, 2023

mctc-lib cc30341 compiled by GCC 10.2.1 on Debian bullseye.

Prepare the following POSCAR:

POSCAR
3.0
1.0  0.0  0.0
0.0  1.0  0.0
0.0  0.0  1.0
 S
 1
direct
0.0  0.0  0.0

mctc-convert converts the file successfully:

$ mctc-convert POSCAR -o xyz -
1
poscar
S            0.00000000000000        0.00000000000000        0.00000000000000

However, if the indentation of the ion species and numbers are removed, i.e. changed to

S
1

mctc reads nothing:

$ mctc-convert POSCAR -o xyz -
0
poscar

Also, Number of atom types mismatches the number of counts is issued if changed to:

Si
1
 S
1
S
 1

The error does not occur if the above patterns are indented.

If the number of the ions are increased to ten,

  • good: S\n10, Si\n10, Si\n10, Si\n 10
  • bad: S\n10, S\n 10
@e-kwsm
Copy link
Contributor Author
e-kwsm commented Apr 27, 2023

If the number of elements are two, mctc reads POSCAR successfully independently of the length of symbols and indentation.

poscar
3.0
1.0  0.0  0.0
0.0  1.0  0.0
0.0  0.0  1.0
B N
1 1
direct
0.0  0.0  0.0
0.5  0.5  0.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0