In this topic, your are given 4 crystals (these files will be directly downloaded to your download folder — some browsers nowadays do not allow that. In that case: right-click on the link, copy the url, go to a new tab, paste the link there, and if your browser asks to allow an unsafe or untrusted download, then do allow this) :
In all cases, the given crystal structures are the ground state crystal structures and they have been extensively experimentally investigated. In case you wonder about argon: you know this as a gas, but if you cool it down below 84 K, it crystallizes.
Imagine you have no other prior knowledge about these 4 crystals apart from their experimental structure. The question we ponder now is: how can you determine from DFT which type of chemical bond is at work in each of them? OK, there is a fair chance that for these four prototype materials you know the chemical bond already from your basic courses in physics and chemistry. But that’s not the point. We will examine how DFT can tell you about chemical bonding, not only for these four crystals yet for any other crystal you are interested about.
cohesive energy
First, we calculate the cohesive energy for all four crystals, obtained as the total energy per formula unit minus the total energy of a formula unit of free atoms — look at the results here, and verify one or more of these (quick) calculations using your favourite DFT code (yes, by now you are able to do this – some input files for Quantum Espresso are at the bottom of this page, to verify your set-up).
The cohesive energies (expressed in eV per formula unit) fall into two categories: very small values (less than 0.05 eV per formula unit, fcc-Ar) and much larger values (several eV per formula unit, everything else). This is the way to detect Van der Waals bonding: it is much weaker than the other three types of chemical bond. We can conclude that the Ar-atoms in the fcc-Ar atom are hold together by Van der Waals’ bonds.
Note that the picture depends a bit on whether you express cohesive energies per formula unit (or per mole), or per atom. If you express them per formula unit or per mole, the cohesive energy increases with the number of atoms in a formula unit. That’s well-defined, yet makes it harder to compare one crystal with another: the energy gained by making one formula unit of rocksalt is almost twice as large as the energy gained by making one formula unit of aluminum, yet rocksalt has two atoms in that formula unit and aluminum only one. Hence, for the same amount of atoms (as opposed to formula units), the energy gain is comparable. Therefore, cohesive energies are sometimes expressed per atom as well. In these units, fcc-Al, germanium and rocksalt all have cohesive energies between 3 and 4 eV per atom.
bond directionality
We have separated the Van der Waals’ bond from the other types. How to distinguish further between ionic, covalent and metallic bonds? The directionality of the bond will be a useful criterion. Covalent bonds are directional, while ionic and metallic bonds are more isotropic. Bond directionality can be detected by inspecting the charge density: when a bond is directional, somewhat more electron charge accumulates along the strong bonding directions. This is a small charge accumulation, however, and on a plot of the charge density as such, it will not be easily seen. A much more useful plot is a charge density difference: for every point in the unit cell (or in a 2D cut through the unit cell) the difference is made between the charge density of the crystal in that point, and the charge density of a hypothetical crystal that is built from a superposition of free atoms. The charge density difference shows how electrons are redistributed when the initially free atoms combine and bond to form a crystalline solid. The procedure how to make such plots with Quantum Espresso is explained here. You can inspect the results for our 4 example crystals here (it is very instructive to reproduce one or more of these cases, and to play with the 3D visulation — it says much more than these static pictures).
When inspecting these pictures, a considerable pile-up of electron charge in between neighbouring Ge atoms is obvious — that’s the signature of a directional bond, and therefore covalent bonding. This is almost absent in aluminum and rocksalt.
Distinguishing between metallic and ionic bonding is less clear-cut. Ionic bonding involves electrostatic attraction, and requires therefor atoms that can donate electrons as well as atoms that can receive electrons. That requires at least two different elements, such that by exclusion aluminum cannot be an ionic solid. That’s a weak argument, however, and it could not be applied to the many intermetallic crystals that are around (e.g. Fe-Al alloys). The nearly perfect spherical symmetry in the case of rocksalt, compared to the slight traces of charge pile-up between the atoms in aluminum is a more general argument that points to metallic bonding for aluminum and ionic bonding for rocksalt.
If you have other suggestions how to deduce the type of chemical bonding from DFT information, please post them on the chapter forum:
Started by: william
Started by: Samra Mahmood
Started by: Himanshu Sharma
Started by: vladgladkikh
Started by: laitvo
Started by: thsr
Started by: Arthur Adriaens
Started by: Arthur Adriaens
Started by: Arthur Adriaens
The numbers quoted hereabove were calculated with Quantum Espresso (PBE, with PAW pseudopotentials). Information to reproduce these calculations is listed hereafter (if you study this course with your own preferred DFT code, then start from the cif files given at the top of this page). More explicit information for doing single atom calculations with Quantum Espresso will follow in the chapter on supercells. Basis set size and pseudopotentials must be identical for the single atom and solid state cases.
single atom files:
solid state (crystal) files (use the same pseudopotential files as for the single atoms):
Verify a few of the total energy and difference density calculations given above.
expected time: 60m
report time spent (page code AW07C)