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

procar.py suggestion #11

Open
mwistey opened this issue Dec 31, 2019 · 1 comment
Open

procar.py suggestion #11

mwistey opened this issue Dec 31, 2019 · 1 comment

Comments

@mwistey
Copy link

mwistey commented Dec 31, 2019

Thanks for the python interface!

In procar.py, I would suggest replacing this:
regex = re.compile( 'k-point\s+(\d+)\s*:\s+([- ][01].\d{8})([- ][01].\d{8})([- ][01].\d{8})\s+weight = ([01].\d+)' )
...with this...
regex = re.compile( 'k-point\s+(\d+)\s*:\s+([- ][01].\d+)([- ][01].\d+)([- ][01].\d+)\s+weight = (-[01].\d+)' )

I've run into one modified version of VASP that has an extra space after the "weight =". This way it's a little less fragile.

  • Mark
@bjmorgan
Copy link
Owner

Thanks for the suggestion. Can you provide an example of the modified PROCAR format you would like to parse?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants