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

Additional workflow step to check a non-magnetic state energy #62

Open
blokhin opened this issue Aug 16, 2022 · 3 comments
Open

Additional workflow step to check a non-magnetic state energy #62

blokhin opened this issue Aug 16, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@blokhin
Copy link
Member

blokhin commented Aug 16, 2022

@ansobolev since we have assured that our workflows are smart enough to drive CRYSTAL into a reasonable magnetic state, we do not need to iterate over all the possible spin states and check them 👍 However as you have suggested a simple check of a non-magnetic state against a magnetic state would not harm.

@blokhin blokhin added the enhancement New feature or request label Aug 16, 2022
@ansobolev
Copy link
Member

Tha has to be done in mpds-aiida, check if we have a high-spin state, and if yes, then turn off guess_spinlock in th next calculation to get non-magnetic energy

@blokhin blokhin self-assigned this Dec 12, 2022
@blokhin
Copy link
Member Author

blokhin commented Dec 12, 2022

@ansobolev this is actually the SPIN keyword in the DFT input part. I think it can be skipped given there are no d-electrons to save computing resources. Sometimes however it was reported to improve convergence even for the non-magnetic systems.

@ansobolev
Copy link
Member

Well, usually for consistency people are doing spin-polarized calculations even when there is no spin involved (see, for instance, DeltaCodesDFT project)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

2 participants