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

Fix LobsterSet #3771

Merged
merged 6 commits into from
Apr 23, 2024
Merged

Fix LobsterSet #3771

merged 6 commits into from
Apr 23, 2024

Conversation

naik-aakash
Copy link
Contributor

@naik-aakash naik-aakash commented Apr 19, 2024

Issue

The POTCARs used to generate the input set are incorrect and do not match PBE_54 POTCARs. Currently, the potcar_symbols variable stores element symbols, which leads to the input set trying to find potcars matching element symbols only.

Fix

Correctly refer to potcars that should be used based on specified functional using potcar_symbols property of its base VaspInputSet class

Todo

  • Write a test to avoid such issues in future

Copy link

coderabbitai bot commented Apr 19, 2024

Walkthrough

The modification updates the source of potcar_symbols in the incar_updates method, transitioning from using self.poscar.site_symbols to self.potcar_symbols. This change centralizes the definition of potential model symbols, potentially enhancing consistency and maintainability of the code.

Changes

File Path Change Summary
pymatgen/io/vasp/sets.py Updated variable assignment for potcar_symbols in incar_updates from self.poscar.site_symbols to self.potcar_symbols.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@janosh janosh added needs testing PRs that are not ready to merge due to lacking tests fix Bug fix PRs vasp Vienna Ab initio Simulation Package labels Apr 19, 2024
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.

is there a way to test this change with the scrambled POTCARs added by @esoteric-ephemera?

@JaGeo
Copy link
Member

JaGeo commented Apr 19, 2024

is there a way to test this change with the scrambled POTCARs added by @esoteric-ephemera?

Oh, yeah, we definitely need a test 😅

@naik-aakash
Copy link
Contributor Author

Thanks @janosh ,for the suggestion, I was indeed planning to do that 😃 , will add the test in sometime

@naik-aakash
Copy link
Contributor Author

Hi @janosh , I have added two tests for checking if the potcar symbols are consistent with PBE_54. Thus, PR could be merged incase there are no further comments on it. 😄

@janosh janosh removed the needs testing PRs that are not ready to merge due to lacking tests label Apr 23, 2024
@janosh janosh merged commit 7e2f16c into materialsproject:master Apr 23, 2024
22 checks passed
@janosh
Copy link
Member

janosh commented Apr 23, 2024

thanks @naik-aakash 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix Bug fix PRs vasp Vienna Ab initio Simulation Package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants