--
You received this message because you are subscribed to the Google Groups "dirac-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dirac-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dirac-users/dbd2183f-91cf-4942-b01b-cd180550a6a0n%40googlegroups.com.
Dear Tomohiro,
Dirac uses cartesian gaussians because of the kinetic energy balance, however the 3s component (x2+y2+z2) is removed so the d occupations are true d-ao occupations.
Personally I do not see any advantage of spherical d-orbital analysis, because that will treat the z direction different from the other directions. With the Cartesian form you will see how it moves smoothly between x2, y2, and z2 if you rotate the molecule in space.
Best regards, Hans Jørgen.
Fra:
<dirac...@googlegroups.com> på vegne af "ich...@gmail.com" <ich...@gmail.com>
Svar til: "dirac...@googlegroups.com" <dirac...@googlegroups.com>
Dato: mandag den 23. juni 2025 kl. 18.04
Til: dirac-users <dirac...@googlegroups.com>
Emne: Re: [dirac-users] Help with d-Orbital Occupation Analysis in DIRAC
Du får ikke ofte mails fra ich...@gmail.com. Få mere at vide om, hvorfor dette er vigtigt |
To view this discussion visit https://groups.google.com/d/msgid/dirac-users/6af2daef-bf61-4b6b-ae14-62049af73260n%40googlegroups.com.
Dear Hans Jørgen,
Thank you for your reply.
I now understand why Cartesian basis sets are preferred for both calculations and analysis.
Best regards,
Tomohiro
Dear All,
I would appreciate information on the input needed to calculate the potential at a nucleus.
It seems that this should be done with the keyword .NUCPOT but I haven’t been able to work out where to place this keyword and how to add information on the center where the potential is to be calculated.
I haven’t been able to identify the subroutine that reads the .NUCPOT input and this might have let me work out how to create the correct input stream. Can someone tell me the routines where the input is processed.
Thanks, Paul
--
You received this message because you are subscribed to the Google Groups "dirac-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dirac-users...@googlegroups.com.
Dear Miro,
Thanks for the pointers.
I had checked the on-line documentation but I was unable to extract the prescription for how to prepare the input for .NUCPOT. If you have a sample deck with .NUCPOT input that would be great.
Thanks also for the pointers to the relevant subroutines where the .NUCPOT input is processed. I will check these codes later today to see if I can work out how the input is read. In the meantime, I will continue to calculate the potentials for Pyridine with my non-relativistic code. It will be interesting to see how the rel and non-rel potentials compare. I would expect them to be very similar.
Thanks and Regards, Paul
To view this discussion visit https://groups.google.com/d/msgid/dirac-users/CA%2BGrSJzg4jmV6bHWeUkcX9ukumbNiCVFYSWscWnNafHD5d6sGg%40mail.gmail.com.
Dear Paul,
I have looked and the documentation is wrong, .NUCPOT keyword does not work in Dirac – it writes that the potential from the individual nuclei are calculated, but they are not and they are not saved on AOPROPER. (The code doing it still exists in Dalton, but it has been deleted by someone in Dirac, presumably because there is another way of doing it in Dirac.)
If you tell me more specifically what you want to do, I might be able to help you. Do you want the expectation value?
Regards, Hans Jørgen.
Dear Hans Jorgen,
Thanks for your update on NUCPOT. I do have a rather straightforward workaround for the information that I need.
I am looking at C(1s) BE shifts in the XPS of a series of azines starting from pyridine. I want to demonstrate that the BE shifts depend on the electric potential, <1/r>, at the C atom which is ionized. This is different from the effective charge of the ionized atom since it includes contributions from all the atoms in molecule. I have already demonstrated the correlation for the C(1s) BE shifts for different configuration of an isolated C atom and I want to extend the analysis to the BEs in azines.
My workaround is to calculate the <1/r> with my non-relativistic codes. Since the azines have only light atoms, this should not be a problem.
It might be useful to correct the Dirac documentation to state that NUCPOT is not supported. BTW, what would be required to bring it back? Is there code in older versions of Dirac?
You wrote that: “presumably because there is another way of doing it in Dirac”. What do you have in mind as an alternative?
Best Regards, Paul
P.S. Are there any events (supportive or critical) planned in Denmark to mark Friday, July 4, the U.S. Independence Day?
To view this discussion visit https://groups.google.com/d/msgid/dirac-users/5C5BD817-E9CC-404B-8FE0-027EDA77C963%40sdu.dk.
Dear Paul, checked a little more.
In the .mol file, the two first characters of the atom label must be unique, thus one cannot use .xyz files because the label identifies the nuclear charge. In the .mol file, the label can be anything. For example:
Instead of e.g.:
6. 2
C -0.7000 0.0000 0.0000
C 0.7000 0.0000 0.0000
LARGE BASIS cc-pVDZ
you could have:
6. 2
aa -0.7000 0.0000 0.0000
ab 0.7000 0.0000 0.0000
LARGE BASIS cc-pVDZ
And then you can ask for the operator for the nuclear potential for the C atom with label “ab” with simply:
.OPERATOR
‘POT.E ab’
because it is a diagonal operator. The full version, useful in case you want to give it another name in output, is
.OPERATOR
‘Your-operator-name’
DIAGONAL
‘POT.E ab’
This should work, I have not tested it.
All the best, Hans Jørgen.
PS. See http://rebildfesten.dk , yearly since 1912.