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

Error when reading UPF file during PW calculations #5880

Open
1 of 10 tasks
ahxbcn opened this issue Jan 24, 2025 · 0 comments
Open
1 of 10 tasks

Error when reading UPF file during PW calculations #5880

ahxbcn opened this issue Jan 24, 2025 · 0 comments
Labels
Questions Raise your quesiton! We will answer it.

Comments

@ahxbcn
Copy link

ahxbcn commented Jan 24, 2025

Details

I'm trying to do a planewave calculation using ABACUS 3.9.0 for isolated Nd atom, and I want to consider noncollinear spin-polarized magnetization and SOC effect in the calculation. The SG15_ONCV pseudopoential library does not provide pseudopotential file for Nd. I found the pseudopotential file Nd.PD04.PBE.SOC.UPF downloaded from https://www.pwmat.com/potential-download can be used. However, the calculation crashes with the following output in stdout:

Pseudopotential data do not match.
CHECK IN FILE : OUT.Nd-atom/warning.log

It seems that the problem arises when reading the UPF file. Input files and output files are attatched in the below link.

Nd-PD04-SOC.tar.gz

Have you read FAQ on the online manual http://abacus.deepmodeling.com/en/latest/community/faq.html

  • Yes, I have read the FAQ part on online manual.

Task list for Issue attackers (only for developers)

  • Understand the problem or question described by the user.
  • Check if the issue is a known problem or has been addressed in the documentation.
  • Test the issue or problem on a similar system or environment, if possible.
  • Identify the root cause or provide clarification on the user's question.
  • Provide a step-by-step guide, including any necessary resources, to resolve the issue or answer the question.
  • If the issue is related to documentation, update the documentation to prevent future confusion (optional).
  • If the issue is related to code, consider implementing a fix or improvement (optional).
  • Review and incorporate any relevant feedback from users or developers.
  • Ensure the user's issue is resolved or their question is answered and close the ticket.
@ahxbcn ahxbcn added the Questions Raise your quesiton! We will answer it. label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Questions Raise your quesiton! We will answer it.
Projects
None yet
Development

No branches or pull requests

1 participant