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

Problems plotting band structure with HSE06 #146

Closed
TheGreatDeadOne opened this issue May 6, 2024 · 4 comments
Closed

Problems plotting band structure with HSE06 #146

TheGreatDeadOne opened this issue May 6, 2024 · 4 comments

Comments

@TheGreatDeadOne
Copy link

Pyprocar can even plot graphs properly, but the software can't identify the symmetry points for the kpath labels. I tried using KPOINTS from an SCF, but the package only managed to list the labels but not the band structure.

Figure_1
Figure_2

@lllangWV
Copy link
Collaborator

lllangWV commented May 6, 2024

Hello,

Can I see your input files? Also, what files are in your directory, and what code are you using?

Logan Lang

@TheGreatDeadOne
Copy link
Author

Hello,

Can I see your input files? Also, what files are in your directory, and what code are you using?

Logan Lang

I'm using VASP. The calculation files are attached.
hse.zip

@lllangWV
Copy link
Collaborator

lllangWV commented May 6, 2024

Thanks for the files!

Upon reviewing your files, the issue seems to stem from the explicit k-points path specified in the KPOINTS file. We currently, do not have a method to parse this.

I can incorporate this functionality, but it will take a few days to implement.

In the meantime, I recommend using line mode to generate the k-path, as indicated in your KPATH file. However, please note a discrepancy: the KPATH file seems to suggest 180 k-points for the kpath, while the PROCAR file contains 190. Therefore, simply replacing the KPOINTS file with the path from the KPATH file won’t work. You'll need to rerun the calculation to resolve this.

Try this and let me know if you run into any issues again!

Logan Lang

@TheGreatDeadOne
Copy link
Author

Thanks for the files!

Upon reviewing your files, the issue seems to stem from the explicit k-points path specified in the KPOINTS file. We currently, do not have a method to parse this.

Okay, got it

Try this and let me know if you run into any issues again!

Thanks for the tips, I'll give it a try.

Logan Lang

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

2 participants