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

BUG: Potential Inconsistency in EOS Workflows #1071

Closed
yanghan234 opened this issue Nov 26, 2024 · 5 comments
Closed

BUG: Potential Inconsistency in EOS Workflows #1071

yanghan234 opened this issue Nov 26, 2024 · 5 comments

Comments

@yanghan234
Copy link
Contributor

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 the MPScanRelaxSet.

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:

class MPGGAEosRelaxSetGenerator(VaspInputGenerator):
"""Class to generate MP-compatible VASP GGA EOS relax input sets."""
config_dict: dict = field(default_factory=lambda: MPScanRelaxSet.CONFIG)

class MPGGAEosStaticSetGenerator(EosSetGenerator):
"""Class to generate MP-compatible VASP GGA EOS relax input sets."""
config_dict: dict = field(default_factory=lambda: MPScanRelaxSet.CONFIG)

@JaGeo
Copy link
Member

JaGeo commented Nov 26, 2024

@yanghan234 thank you for reporting this.

@esoteric-ephemera could you take a look? Thank you!

@esoteric-ephemera
Copy link
Contributor

Hi @JaGeo and @yanghan234: the MPGGA-prefixed sets use slightly updated parameters for EOS workflows but are still PBE-based. Looking in the incar_updates property of each EOS, METAGGA is unset. The rationale was having parity between workflow parameters for PBE-GGA and r2SCAN-meta-GGA flows

The MPLegacy-prefixed flows use MPRelaxSet and a few settings specific to the atomate 1 EOS flows (for consistency/reproducibility)

The docstrings at the top of vasp.jobs.eos and vasp.flows.eos explain this, but I should probably move that to the docs for visibility

@JaGeo
Copy link
Member

JaGeo commented Nov 26, 2024

@esoteric-ephemera thank you! Yes, it would be great if this could be included in the Docs!

@esoteric-ephemera
Copy link
Contributor

Sure thing, I'll add it to the doc PR I have up now

@yanghan234
Copy link
Contributor Author

Thank you @esoteric-ephemera and @JaGeo! This resolved my concern.

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

3 participants