-
Notifications
You must be signed in to change notification settings - Fork 104
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: Potential Inconsistency in EOS Workflows #1071
Comments
@yanghan234 thank you for reporting this. @esoteric-ephemera could you take a look? Thank you! |
Hi @JaGeo and @yanghan234: the The The docstrings at the top of |
@esoteric-ephemera thank you! Yes, it would be great if this could be included in the Docs! |
Sure thing, I'll add it to the doc PR I have up now |
Thank you @esoteric-ephemera and @JaGeo! This resolved my concern. |
Describe the bug
When using the EOS workflows, I noticed the following code snippets. Based on the class names and their docstrings, I assume these classes are intended to generate input files compatible with MP GGA setups, specifically for PBE functionals. However, the
config_dict
defined within these classes references theMPScanRelaxSet
.Could you clarify whether this behavior is intentional (a feature) or an oversight (a bug)? Thank you for your help!
Here are the relevant code lines for reference:
atomate2/src/atomate2/vasp/sets/eos.py
Lines 135 to 138 in 4b84d78
atomate2/src/atomate2/vasp/sets/eos.py
Lines 170 to 173 in 4b84d78
The text was updated successfully, but these errors were encountered: