We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. Can you provide an example of the modified PROCAR format you would like to parse?
Sorry, something went wrong.
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: