I’m doing a DOS/PDOS/Band structure calculation on a 2x2x2 bulk supercell where I replace an atom in the system with a Mn. However w/ the electrons in the d-orbital of Mn, I got my fermi energy shifting below my VBM due to the fact of how the energy states were being filled. Nevertheless, the job successfully converged and performed all requested calculations. As a solution, I sought out to control the spin of those electrons using the below addition to my .fdf file.
######################
NonCollinearSpin .true.
%block DM.InitSpin
16 + 0. 0.
%endblock DM.InitSpin
######################
When I ran the calculation I received an ‘Exceeded job memory limit’ error and the job quit after the .bands file was written (i.e. at the start of the DOS/PDOS calc.). After reading ([memory] pdos calculations and eigenvalue array (#45) · Issues · siesta-project / siesta · GitLab) I figured the number of k-points I was using was too large, so in order to test the extent that the error would go I chose extremely low k-point values (i.e. not reasonable results) in all possible facets with the following inputs:
######################
%block kgrid_Monkhorst_Pack
4 0 0 0.0
0 4 0 0.0
0 0 4 0.0
%endblock kgrid_Monkhorst_Pack
NonCollinearSpin .true.
%block DM.InitSpin
16 + 0. 0.
%endblock DM.InitSpin
BandLinesScale ReciprocalLatticeVectors
%block Bandlines
1 0.000 0.000 0.000 \Gamma
2 0.000 0.500 0.000 X
2 0.500 0.500 0.000 M
2 0.000 0.000 0.000 \Gamma
2 0.500 0.500 0.500 R
%endblock Bandlines
%block ProjectedDensityOfStates
-8.00 4.00 0.200 10 eV
%endblock ProjectedDensityOfStates
######################
Even w/ such few points, I received the same ‘Exceeded job memory limit’ error.
Is this a known ‘bug’ when using NonCollinearSpin and DM.InitSpin, or is there an obvious piece that I am missing? Any guidance is much appreciated.
Brian Leininger