Spin-polarized quantities return order
See original GitHub issueDescribe the issue
#500 brought about this issue. (@tfrederiksen )
The problem is the handling of the spin-densities is that the current read_data (for polarized) returns [up, down], whereas NC/SOC returns [total, x, y, z].
This issue is to discuss the option to change the polarized return order to be [total, z].
POSITIVE:
- this would be conforming to the NC/SOC calculations
- the code would always be the same if users just wanted to plot the total charge (
[0]
) SIESTA: - Return values would not be the same as the output data (say Mulliken charges)
Comments would be much appreciated!
Issue Analytics
- State:
- Created a year ago
- Comments:14 (13 by maintainers)
Top Results From Across the Web
Spin-exchange collisions and their consequences for spin ...
The effects of spin-exchange collisions on the polarization of dense spin-polarized samples of hydrogen and deuterium are analyzed.
Read more >Spin Polarization - an overview | ScienceDirect Topics
The spin-dependent scattering arises either through spin−orbit coupling or exchange interaction, and the scattering geometry (angle between incoming and ...
Read more >Spin-polarized systems - EasySpin
First, simulate the spectrum of the unpolarized triplet and ask EasySpin to return the two transitions separately. Second, combine the transitions using ...
Read more >Phys. Rev. Lett. 128, 026403 (2022) - Spin-Polarized Nematic ...
The spin-polarized insulator state is quasidegenerate with the valley polarized state if only the dominant intravalley Coulomb interaction is ...
Read more >Relativistic hydrodynamics for spin-polarized fluids - arXiv
7.1 Perfect fluid hydrodynamics with leading-order spin treatment . ... The quantities defined in PRF are denoted by an asterisk, while unlabeled.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I would prefer [total, z] for consistency.
Typically the spin and the total charge are what is most relevant, in my opinion, not what the charge in either spin channel is on its own.
Regarding the index order, I would say first spin then orbitals.
I have never done a (meaningful) SOC calculation 😃
From my experience handling NC spins in the visualization module, I agree that it is a bit of a pain to have a completely different way of processing NC and diagonal spins.
But from my experience as a user, up/down components feel very intuitive. It is not easy for me to understand what
total
andz
would store and how would you convert toup
/down
. Could you perhaps clarify it with an example of an array storing eigenvalues for a given k point?