Skip to content

Don't do a hard bandgap==0 check in the r2SCAN workflow #3036

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

Merged
merged 2 commits into from
Jun 2, 2023
Merged

Don't do a hard bandgap==0 check in the r2SCAN workflow #3036

merged 2 commits into from
Jun 2, 2023

Conversation

Andrew-S-Rosen
Copy link
Member

Closes #3023. CC'ing @janosh and @munrojm.

Copy link
Member

@janosh janosh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @arosen93! 👍

@janosh janosh enabled auto-merge (squash) June 2, 2023 14:46
@Andrew-S-Rosen
Copy link
Member Author

Thanks for adding those unit tests! Greatly appreciated!!

@janosh janosh added enhancement A new feature or improvement to an existing one io Input/output functionality vasp Vienna Ab initio Simulation Package labels Jun 2, 2023
@janosh janosh merged commit be5ca04 into materialsproject:master Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A new feature or improvement to an existing one io Input/output functionality vasp Vienna Ab initio Simulation Package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

if self.bandgap == 0 is probably not the best in MPScanRelaxSet
2 participants