Search NASA⌕ Search

SEARCH · Search NASA

Results for “explicit and implicit methods”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

381 records · Page 22

Electron correlation within the relativistic no-pair approximation

This paper addresses the definition of correlation energy within 4-component relativistic atomic and molecular calculations. In the nonrelativistic domain the correlation energy is defined as the difference between the exact eigenvalue of the electronic Hamiltonian and the Hartree-Fock energy. In practice, what is reported is the basis set correlation energy, where the “exact” value is provided by a full Configuration Interaction (CI) calculation with some specified one-particle basis. The extension of this definition to the relativistic domain is not straightforward since the corresponding electronic Hamiltonian, the Dirac-Coulomb Hamiltonian, has no bound solutions. Present-day relativistic calculations are carried out within the no-pair approximation, where the Dirac-Coulomb Hamiltonian is embedded by projectors eliminating the troublesome negative-energy solutions. Hartree-Fock calculations are carried out with the implicit use of such projectors and only positive-energy orbitals are retained at the correlated level, meaning that the Hartree-Fock projectors are frozen at the correlated level. We argue that the projection operators should be optimized also at the correlated level and that this is possible by full Multiconfigurational Self-Consistent Field (MCSCF) calculations, that is, MCSCF calculations using a no-pair full CI expansion, but including orbital relaxation from the negative-energy orbitals. We show by variational perturbation theory that the MCSCF correlation energy is a pure MP2-like correlation expression, whereas the corresponding CI correlation energy contains an additional relaxation term. We explore numerically our theoretical analysis by carrying out variational and perturbative calculations on the two-electron rare gas atoms with specially tailored basis sets. In particular, we show that the correlation energy obtained by the suggested MCSCF procedure is smaller than the no-pair full CI correlation energy, in accordance with the underlying minmax principle and our theoretical analysis. We also show that the relativistic correlation energy, obtained from no-pair full MCSCF calculations, scales at worst as X{sup −2} with respect to the cardinal number X of our correlation-consistent basis sets optimized for the two-electron atoms. This is better than the X{sup −1} scaling suggested by previous studies, but worse than the X{sup −3} scaling observed in the nonrelativistic domain. The well-known 1/Z- expansion in nonrelativistic atomic theory follows from coordinate scaling. We point out that coordinate scaling for consistency should be accompanied by velocity scaling. In the nonrelativistic domain this comes about automatically, whereas in the relativistic domain an explicit scaling of the speed of light is required. This in turn explains why the relativistic correlation energy to the lowest order is not independent of nuclear charge, in contrast to nonrelativistic theory.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

Adagio 4.16 user s guide.

Adagio is a three-dimensional, implicit solid mechanics code with a versatile element library, nonlinear material models, and capabilities for modeling large deformation and contact. Adagio is a parallel code, and its nonlinear solver and contact capabilities enable scalable solutions of large problems. It is built on the SIERRA Framework [1, 2]. SIERRA provides a data management framework in a parallel computing environment that allows the addition of capabilities in a modular fashion. The Adagio 4.16 User's Guide provides information about the functionality in Adagio and the command structure required to access this functionality in a user input file. This document is divided into chapters based primarily on functionality. For example, the command structure related to the use of various element types is grouped in one chapter; descriptions of material models are grouped in another chapter. The input and usage of Adagio is similar to that of the code Presto [3]. Presto, like Adagio, is a solid mechanics code built on the SIERRA Framework. The primary difference between the two codes is that Presto uses explicit time integration for transient dynamics analysis, whereas Adagio is an implicit code. Because of the similarities in input and usage between Adagio and Presto, the user's guides for the two codes are structured in the same manner and share common material. (Once you have mastered the input structure for one code, it will be easy to master the syntax structure for the other code.) To maintain the commonality between the two user's guides, we have used a variety of techniques. For example, references to Presto may be found in the Adagio user's guide and vice versa, and the chapter order across the two guides is the same. On the other hand, each of the two user's guides is expressly tailored to the features of the specific code and documents the particular functionality for that code. For example, though both Presto and Adagio have contact functionality, the content of the chapter on contact in the two guides differs. Important references for both Adagio and Presto are given in the references section at the end of this chapter. Adagio was preceded by the codes JAC and JAS3D; JAC is described in Reference 4; JAS3D is described in Reference 5. Presto was preceded by the code Pronto3D. Pronto3D is described in References 6 and 7. Some of the fundamental nonlinear technology used by both Presto and Adagio are described in References 8, 9, and 10. Currently, both Presto and Adagio use the Exodus II database and the XDMF database; Exodus II is more commonly used than XDMF. (Other options may be added in the future.) The Exodus II database format is described in Reference 11, and the XDMF database format is described in Reference 12. Important information about contact is provided in the reference document for ACME [13]. ACME is a third-party library for contact. One of the key concepts for the command structure in the input file is a concept referred to as scope. A detailed explanation of scope is provided in Section 1.2. Most of the command lines in Chapter 2 are related to a certain scope rather than to some particular functionality.

97 MATHEMATICS AND COMPUTING↗

Adagio 4.14 user s guide.

This document is a user's guide for the code Adagio. Adagio is a three-dimensional, implicit solid mechanics code with a versatile element library, nonlinear material models, and capabilities for modeling large deformation and contact. Adagio is a parallel code, and its nonlinear solver and contact capabilities enable scalable solutions of large problems. It is built on the SIERRA Framework [1, 2]. SIERRA provides a data management framework in a parallel computing environment that allows the addition of capabilities in a modular fashion. The Adagio 4.14 User's Guide provides information about the functionality in Adagio and the command structure required to access this functionality in a user input file. This document is divided into chapters based primarily on functionality. For example, the command structure related to the use of various element types is grouped in one chapter; descriptions of material models are grouped in another chapter. The input and usage of Adagio is similar to that of the code Presto [3]. Presto, like Adagio, is a solid mechanics code built on the SIERRA Framework. The primary difference between the two codes is that Presto uses explicit time integration for transient dynamics analysis, whereas Adagio is an implicit code. Because of the similarities in input and usage between Adagio and Presto, the user's guides for the two codes are structured in the same manner and share common material. (Once you have mastered the input structure for one code, it will be easy to master the syntax structure for the other code.) To maintain the commonality between the two user's guides, we have used a variety of techniques. For example, references to Presto may be found in the Adagio user's guide and vice versa, and the chapter order across the two guides is the same. On the other hand, each of the two user's guides is expressly tailored to the features of the specific code and documents the particular functionality for that code. For example, though both Presto and Adagio have contact functionality, the content of the chapter on contact in the two guides differs. Important references for both Adagio and Presto are given in the references section at the end of this chapter. Adagio was preceded by the codes JAC and JAS3D; JAC is described in Reference 4; JAS3D is described in Reference 5. Presto was preceded by the code Pronto3D. Pronto3D is described in References 6 and 7. Some of the fundamental nonlinear technology used by both Presto and Adagio are described in References 8, 9, and 10. Currently, both Presto and Adagio use the Exodus II database and the XDMF database; Exodus II is more commonly used than XDMF. (Other options may be added in the future.) The Exodus II database format is described in Reference 11, and the XDMF database format is described in Reference 12. Important information about contact is provided in the reference document for ACME [13]. ACME is a third-party library for contact. One of the key concepts for the command structure in the input file is a concept referred to as scope. A detailed explanation of scope is provided in Section 1.2. Most of the command lines in Chapter 2 are related to a certain scope rather than to some particular functionality.

97 MATHEMATICS AND COMPUTING↗