Skip to content

Remove soc pwbase workaround - #89

Open
Minotakm wants to merge 2 commits into
aiidateam:mainfrom
Minotakm:remove-soc-pwbase-workaround
Open

Remove soc pwbase workaround#89
Minotakm wants to merge 2 commits into
aiidateam:mainfrom
Minotakm:remove-soc-pwbase-workaround

Conversation

@Minotakm

@Minotakm Minotakm commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Remove SOC workaround in Wannier90WorkChain.get_builder_from_protocol

PwBaseWorkChain.get_builder_from_protocol now supports non-collinear and spin-orbit calculations natively (added in aiida-quantumespresso v4.12.0, commit aiidateam/aiida-quantumespresso@0c81dad). It sets noncolin/nspin/lspinorb and seeds starting_magnetization from initial_magnetic_moments, the structure's magmoms, or the per-element defaults.

This PR removes the workaround in Wannier90WorkChain.get_builder_from_protocol. We now pass spin_type
straight through to the scf/nscf builders and let PwBaseWorkChain handle it.

SOC calculations are now magnetically initialized by default. Previously the workaround produced a non-magnetic SOC calculation (only lspinorb/noncolin, no starting_magnetization). Regenerated the fixtures to comply with these changes in the spin orbit case. Please let me know what you think 😃

Minotakm added 2 commits June 9, 2026 13:53
PwBaseWorkChain.get_builder_from_protocol supports SOC/non-collinear natively since aiida-quantumespresso 4.12, so pass spin_type straight through instead of forcing pw_spin_type to NONE and injecting the SYSTEM flags via the spin_orbit/spin_noncollinear overrides. SOC is now magnetically initialized by default. Bump the aiida-quantumespresso pin to >=4.12.
The previous commit changes the SOC builder output, so the spin_orbit data_regression snapshots no longer match. Regenerated against aiida-quantumespresso 4.17.0; only the spin_orbit fixtures change.
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

Successfully merging this pull request may close these issues.

1 participant