Search NASA⌕ Search

SEARCH · Search NASA

Results for “Content Code”

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.

At least 145 records · Page 8

The Model 9977 Radioactive Material Packaging Primer

The Model 9977 Packaging is a single containment drum style radioactive material (RAM) shipping container designed, tested and analyzed to meet the performance requirements of Title 10 the Code of Federal Regulations Part 71. A radioactive material shipping package, in combination with its contents, must perform three functions (please note that the performance criteria specified in the Code of Federal Regulations have alternate limits for normal operations and after accident conditions): Containment, the package must “contain” the radioactive material within it; Shielding, the packaging must limit its users and the public to radiation doses within specified limits; and Subcriticality, the package must maintain its radioactive material as subcritical

42 ENGINEERING↗

Assessment of SFR fuel pin performance codes under advanced fuel for minor actinide transmutation

Americium is a strong contributor to the long term radiotoxicity of high activity nuclear waste. Transmutation by irradiation in nuclear reactors of long-lived nuclides like {sup 241}Am is, therefore, an option for the reduction of radiotoxicity and residual power packages as well as the repository area. In the SUPERFACT Experiment four different oxide fuels containing high and low concentrations of {sup 237}Np and {sup 241}Am, representing the homogeneous and heterogeneous in-pile recycling concepts, were irradiated in the PHENIX reactor. The behavior of advanced fuel materials with minor actinide needs to be fully characterized, understood and modeled in order to optimize the design of this kind of fuel elements and to evaluate its performances. This paper assesses the current predictability of fuel performance codes TRANSURANUS and GERMINAL V2 on the basis of post irradiation examinations of the SUPERFACT experiment for pins with low minor actinide content. Their predictions have been compared to measured data in terms of geometrical changes of fuel and cladding, fission gases behavior and actinide and fission product distributions. The results are in good agreement with the experimental results, although improvements are also pointed out for further studies, especially if larger content of minor actinide will be taken into account in the codes. (authors)

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Modeling aerosols and their interactions with shallow cumuli during the 2007 CHAPS field study

The Weather Research and Forecasting model coupled with chemistry (WRF-Chem) is used to simulate relationships between aerosols and clouds in the vicinity of Oklahoma City during the June 2007 Cumulus Humilis Aerosol Processing Study (CHAPS). The regional scale simulation completed using 2 km horizontal grid spacing evaluates four important relationships between aerosols and shallow cumulus clouds observed during CHAPS. First, the model reproduces the trends of higher nitrate volume fractions in cloud droplet residuals compared to interstitial non-activated aerosols, as measured using the Aerosol Mass Spectrometer. Comparing simulations with cloud chemistry turned on and off, we show that nitric acid vapor uptake by cloud droplets explains the higher nitrate content of cloud droplet residuals. Second, as documented using an offline code, both aerosol water and other inorganics (OIN), which are related to dust and crustal emissions, significantly affect predicted aerosol optical properties. Reducing the OIN content of wet aerosols by 50% significantly improves agreement of model predictions with measurements of aerosol optical properties. Third, the simulated hygroscopicity of aerosols is too high as compared to their hygroscopicity derived from cloud condensation nuclei and particle size distribution measurements, indicating uncertainties associated with simulating size-dependent chemical composition and treatment of aerosol mixing state within the model. Fourth, the model reasonably represents the observations of the first aerosol indirect effect where pollutants in the vicinity of Oklahoma City increase cloud droplet number concentrations and decrease the droplet effective radius. While previous studies have often focused on cloud-aerosol interactions in stratiform and deep convective clouds, this study highlights the ability of regional-scale models to represent some of the important aspects of cloud-aerosol interactions associated with fields of short-lived shallow cumuli.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

Nuclear Data Sheets for A=164

Experimental nuclear structure data for the known A=164 isobaric nuclides (Sm, Eu, Gd, Tb, Dy, Ho, Er, Tm, Yb, Lu, Hf, Ta, W, Re, Os, Ir) have been evaluated, and presented together with Adopted properties of level energies, and associated γ rays. The decay data for these nuclides have also been evaluated, providing Adopted values of γ and β radiations, and log ft values. No excited states are known in 164 Eu, 164 Tb, and 164 Ir. Information for 164 Gd, 164 Re and 164 Os is limited due to insufficient experimental data. For radioactive nuclides, decay schemes of 164 Sm, 164 Gd and 164 Re are not known, and those of 164 W, 164 Tb, 164 Lu, 164 Hf, 164 Ta and 164 W are incomplete. The decay schemes of 164 Ho and the two activities of 164 Tm seem fairly complete. The decay scheme of 164 Yb presents a major problem that the Q(ε) value of 887 keV 29 recommended in 2017Wa10 is in disagreement with the population of levels at 928, 952 and 1060 keV in the daughter nucleus. This decay scheme, which so far has been mainly reported in a secondary reference (1982AdZZ) needs further investigation. Also the masses of 164 Yb and 164 Tm need either new measurements or a re-evaluation to resolve discrepancy of about 220 keV in the Q value of 164 Yb decay to 164 Tm. The reactions and decays for which no new experimental information has become available since the 2001 update have undergone revisions to incorporate conversion coefficients from BrIcc code, and evaluated Q values from 2017Wa10, but the essential content of such datasets may have remained the same as in previous evaluations. Finally, in this respect the present work greatly benefited from all the previous NDS evaluations (2001Si27,1992Sh07, 1986Sh03,1974Bu30), but at the same time data presented herein supersede all the previous published evaluations.

38 RADIATION CHEMISTRY, RADIOCHEMISTRY, AND NUCLEA↗

Corrosion of 316H stainless steel in flowing FLiNaK salt

In this report type 316H stainless steel samples were exposed to flowing FLiNaK salt for 1000 h in a monometallic thermal convection loop (TCL) with a maximum temperature of 650 °C and a minimum of 540 °C. Samples in the hottest part of the TCL lost mass, with a maximum mass loss of 1.4 mg/cm 2 , while samples in the coldest parts of the TCL gained mass, with a maximum mass gain of 1.0 mg/cm 2 . Analysis of the samples that gained mass showed an Fe-rich layer on the sample surfaces, indicating that Fe, not Cr, was the primary deposition product in the TCL. Cr loss was apparent to a depth of ~5 µm in the hot leg. Post-exposure analysis of the salt showed major increases in the Cr, Fe, and Mn contents. The TCL was modeled using the TRANSFORM code. Modeled values matched the experimental temperature measurements showing that TRANSFORM is capable of accurately simulating the TCL conditions.

36 MATERIALS SCIENCE↗

Draft Genome Sequence of Enterobacter cloacae Strain JD6301

Enterobacter cloacae strain JD6301 was isolated from a mixed culture with wastewater collected from a municipal treatment facility and oleaginous microorganisms. A draft genome sequence of this organism indicates that it has a genome size of 4,772,910 bp, an average G+C content of 53%, and 4,509 protein-coding genes.

59 BASIC BIOLOGICAL SCIENCES↗

An improved high-quality draft genome sequence of Carnobacterium inhibens subsp. inhibens strain K1T

Abstract Despite their ubiquity and their involvement in food spoilage, the genus Carnobacterium remains rather sparsely characterized at the genome level. Carnobacterium inhibens K1 T is a member of the Carnobacteriaceae family within the class Bacilli . This strain is a Gram-positive, rod-shaped bacterium isolated from the intestine of an Atlantic salmon. The present study determined the genome sequence and annotation of Carnobacterium inhibens K1 T . The genome comprised 2,748,608 bp with a G + C content of 34.85 %, which included 2621 protein-coding genes and 116 RNA genes. The strain contained five contigs corresponding to presumptive plasmids of sizes: 19,036; 24,250; 26,581; 65,272; and 65,904 bp.

59 BASIC BIOLOGICAL SCIENCES↗

Streamlined Approach for Environmental Restoration (SAFER) Plan for Corrective Action Unit 130: Storage Tanks, Nevada Test Site, Nevada, Revision 0

This Streamlined Approach for Environmental Restoration (SAFER) Plan addresses the actions needed to achieve closure for Corrective Action Unit (CAU) 130, Storage Tanks, identified in the Federal Facility Agreement and Consent Order (FFACO) (1996, as amended February 2008). Corrective Action Unit 130 consists of the seven following corrective action sites (CASs) located in Areas 1, 7, 10, 20, 22, and 23 of the Nevada Test Site: • 01-02-01, Underground Storage Tank • 07-02-01, Underground Storage Tanks • 10-02-01, Underground Storage Tank • 20-02-03, Underground Storage Tank • 20-99-05, Tar Residue • 22-02-02, Buried UST Piping • 23-02-07, Underground Storage Tank This plan provides the methodology for field activities needed to gather the necessary information for closing each CAS. There is sufficient information and process knowledge from historical documentation and investigations of similar sites regarding the expected nature and extent of potential contaminants to recommend closure of CAU 130 using the SAFER process. Additional information will be obtained by conducting a field investigation before selecting the appropriate corrective action for each CAS. The results of the field investigation will support a defensible recommendation that no further corrective action is necessary. This will be presented in a Closure Report that will be prepared and submitted to the Nevada Division of Environmental Protection (NDEP) for review and approval. The sites will be investigated based on the data quality objectives (DQOs) finalized on April 3, 2008, by representatives of NDEP; U.S. Department of Energy (DOE), National Nuclear Security Administration Nevada Site Office; Stoller-Navarro Joint Venture; and National Security Technologies, LLC. The DQO process was used to identify and define the type, amount, and quality of data needed to determine and implement appropriate corrective actions for each CAS in CAU 130. The DQO process developed for this CAU identified the following expected closure options: (1) investigation and confirmation that no contamination exists above the final action levels, leading to a no further action declaration; (2) characterization of the nature and extent of contamination, leading to closure in place with use restrictions; or (3) clean closure by remediation and verification. The following text summarizes the SAFER activities that will support the closure of CAU 130: • Perform site preparation activities (e.g., utilities clearances, geophysical surveys). • Move or remove and dispose of debris at various CASs, as required. • Collect environmental samples from designated target populations (e.g., stained soil) to confirm or disprove the presence of contaminants of concern (COCs) as necessary to supplement existing information. • If no COCs are present at a CAS, establish no further action as the corrective action. • If COCs exist, collect environmental samples from designated target populations (e.g., clean soil adjacent to contaminated soil) and submit for laboratory analyses to define the extent of COC contamination. • If a COC is present at a CAS, either: - Establish clean closure as the corrective action. The material to be remediated will be removed, disposed of as waste, and verification samples will be collected from remaining soil, or - Establish closure in place as the corrective action and implement the appropriate use restrictions. • Obtain consensus from NDEP that the preferred closure option is sufficient to protect human health and the environment. • Close the underground storage tank(s) and their contents, if any, in accordance with Nevada Administrative Code regulations. • Remove the lead brick(s) found at any CAS in accordance with the Resource Conservation and Recovery Act.

54 ENVIRONMENTAL SCIENCES↗

SHIPMENT OF TWO DOE-STD-3013 CONTAINERS IN A 9977 TYPE B PACKAGE

The 9977 is a certified Type B Packaging authorized to ship uranium and plutonium in metal and oxide forms. Historically, the standard container for these materials has been the DOE-STD-3013 which was specifically designed for the long term storage of plutonium bearing materials. The Department of Energy has used the 9975 Packaging containing a single 3013 container for the transportation and storage of these materials. In order to reduce container, shipping, and storage costs, the 9977 Packaging is being certified for transportation and storage of two 3013 containers. The challenges and risks of this content and the 9977s ability to meet the Code of Federal Regulations for the transport of these materials are presented.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

RELAP5-3D Developer Guidelines and Programming Practices

Our ultimate goal is to create and maintain RELAP5-3D as the best software tool available to analyze nuclear power plants. This begins with writing excellent programming and requires thorough testing. This document covers development of RELAP5-3D software, the behavior of the RELAP5-3D program that must be maintained, and code testing. RELAP5-3D must perform in a manner consistent with previous code versions with backward compatibility for the sake of the users. Thus file operations, code termination, input and output must remain consistent in form and content while adding appropriate new files, input and output as new features are developed. As computer hardware, operating systems, and other software change, RELAP5-3D must adapt and maintain performance. The code must be thoroughly tested to ensure that it continues to perform robustly on the supported platforms. The coding must be written in a consistent manner that makes the program easy to read to reduce the time and cost of development, maintenance and error resolution. The programming guidelines presented her are intended to institutionalize a consistent way of writing FORTRAN code for the RELAP5-3D computer program that will minimize errors and rework. A common format and organization of program units creates a unifying look and feel to the code. This in turn increases readability and reduces time required for maintenance, development and debugging. It also aids new programmers in reading and understanding the program. Therefore, when undertaking development of the RELAP5-3D computer program, the programmer must write computer code that follows these guidelines. This set of programming guidelines creates a framework of good programming practices, such as initialization, structured programming, and vector-friendly coding. It sets out formatting rules for lines of code, such as indentation, capitalization, spacing, etc. It creates limits on program units, such as subprograms, functions, and modules. It establishes documentation guidance on internal comments. The guidelines apply to both existing and new subprograms. They are written for both FORTRAN 77 and FORTRAN 95. The guidelines are not so rigorous as to inhibit a programmer’s unique style, but do restrict the variations in acceptable coding to create sufficient commonality that new readers will find the coding in each new subroutine familiar. It is recognized that this is a “living” document and must be updated as languages, compilers, and computer hardware and software evolve.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

On the Maximum Mass of Accreting Primordial Supermassive Stars

Supermassive primordial stars are suspected to be the progenitors of the most massive quasars at z ∼ 6. Previous studies of such stars were either unable to resolve hydrodynamical timescales or considered stars in isolation, not in the extreme accretion flows in which they actually form. Therefore, they could not self-consistently predict their final masses at collapse, or those of the resulting supermassive black hole seeds, but rather invoked comparison to simple polytropic models. Here, we systematically examine the birth, evolution, and collapse of accreting, non-rotating supermassive stars under accretion rates of 0.01–10 M {sub ⊙} yr{sup −1} using the stellar evolution code Kepler . Our approach includes post-Newtonian corrections to the stellar structure and an adaptive nuclear network and can transition to following the hydrodynamic evolution of supermassive stars after they encounter the general relativistic instability. We find that this instability triggers the collapse of the star at masses of 150,000–330,000 M {sub ⊙} for accretion rates of 0.1–10 M {sub ⊙} yr{sup −1}, and that the final mass of the star scales roughly logarithmically with the rate. The structure of the star, and thus its stability against collapse, is sensitive to the treatment of convection and the heat content of the outer accreted envelope. Comparison with other codes suggests differences here may lead to small deviations in the evolutionary state of the star as a function of time, that worsen with accretion rate. Since the general relativistic instability leads to the immediate death of these stars, our models place an upper limit on the masses of the first quasars at birth.

79 ASTRONOMY AND ASTROPHYSICS↗

A korarchaeal genome reveals insights into the evolution of the Archaea

The candidate division Korarchaeota comprises a group of uncultivated microorganisms that, by their small subunit rRNA phylogeny, may have diverged early from the major archaeal phyla Crenarchaeota and Euryarchaeota. Here, we report the initial characterization of a member of the Korarchaeota with the proposed name,"Candidatus Korarchaeum cryptofilum," which exhibits an ultrathin filamentous morphology. To investigate possible ancestral relationships between deep-branching Korarchaeota and other phyla, we used whole-genome shotgun sequencing to construct a complete composite korarchaeal genome from enriched cells. The genome was assembled into a single contig 1.59 Mb in length with a G + C content of 49percent. Of the 1,617 predicted protein-coding genes, 1,382 (85percent) could be assigned to a revised set of archaeal Clusters of Orthologous Groups (COGs). The predicted gene functions suggest that the organism relies on a simple mode of peptide fermentation for carbon and energy and lacks the ability to synthesize de novo purines, CoA, and several other cofactors. Phylogenetic analyses based on conserved single genes and concatenated protein sequences positioned the korarchaeote as a deep archaeal lineage with an apparent affinity to the Crenarchaeota. However, the predicted gene content revealed that several conserved cellular systems, such as cell division, DNA replication, and tRNA maturation, resemble the counterparts in the Euryarchaeota. In light of the known composition of archaeal genomes, the Korarchaeota might have retained a set of cellular features that represents the ancestral archaeal form.

59 BASIC BIOLOGICAL SCIENCES↗

A Korarchael Genome Reveals Insights into the Evolution of the Archaea

The candidate division Korarchaeota comprises a group of uncultivated microorganisms that, by their small subunit rRNA phylogeny, may have diverged early from the major archaeal phyla Crenarchaeota and Euryarchaeota. Here, we report the initial characterization of a member of the Korarchaeota with the proposed name, ?Candidatus Korarchaeum cryptofilum,? which exhibits an ultrathin filamentous morphology. To investigate possible ancestral relationships between deep-branching Korarchaeota and other phyla, we used whole-genome shotgun sequencing to construct a complete composite korarchaeal genome from enriched cells. The genome was assembled into a single contig 1.59 Mb in length with a G + C content of 49percent. Of the 1,617 predicted protein-coding genes, 1,382 (85percent) could be assigned to a revised set of archaeal Clusters of Orthologous Groups (COGs). The predicted gene functions suggest that the organism relies on a simple mode of peptide fermentation for carbon and energy and lacks the ability to synthesize de novo purines, CoA, and several other cofactors. Phylogenetic analyses based on conserved single genes and concatenated protein sequences positioned the korarchaeote as a deep archaeal lineage with an apparent affinity to the Crenarchaeota. However, the predicted gene content revealed that several conserved cellular systems, such as cell division, DNA replication, and tRNA maturation, resemble the counterparts in the Euryarchaeota. In light of the known composition of archaeal genomes, the Korarchaeota might have retained a set of cellular features that represents the ancestral archaeal form.

59 BASIC BIOLOGICAL SCIENCES↗

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↗

Presto 4.14 user s guide.

Presto is a three-dimensional transient dynamics code with a versatile element library, nonlinear material models, large deformation capabilities, and contact. 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. Contact capabilities are parallel and scalable. The Presto 4.14 User's Guide provides information about the functionality in Presto 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 Presto is similar to that of the code Adagio [3]. Adagio is a three-dimensional quasi-static code with a versatile element library, nonlinear material models, large deformation capabilities, and contact. Adagio, like Presto, is built on the SIERRA Framework [1]. Contact capabilities for Adagio are also parallel and scalable. A significant feature of Adagio is that it offers a multilevel, nonlinear iterative solver. Because of the similarities in input and usage between Presto and Adagio, 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 Adagio may be found in the Presto 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↗

Presto 4.16 user s guide.

Presto is a three-dimensional transient dynamics code with a versatile element library, nonlinear material models, large deformation capabilities, and contact. 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. Contact capabilities are parallel and scalable. The Presto 4.16 User's Guide provides information about the functionality in Presto 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 Presto is similar to that of the code Adagio [3]. Adagio is a three-dimensional quasi-static code with a versatile element library, nonlinear material models, large deformation capabilities, and contact. Adagio, like Presto, is built on the SIERRA Framework [1]. Contact capabilities for Adagio are also parallel and scalable. A significant feature of Adagio is that it offers a multilevel, nonlinear iterative solver. Because of the similarities in input and usage between Presto and Adagio, 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 Adagio may be found in the Presto 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.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↗

Does size matter? An evaluation of length and proportion of information in environmental impact statements

Highlights: • Empirical analysis of length and proportion of information in EISs is presented. • Current EISs, in Brazil, are significantly longer than the early ones. • Baseline information is the most common element in EISs. • EIS length is affected by many variables, including project sector and size. • While relevant to decision-making, EIS length should be carefully regulated. - Abstract: For decades, authors and institutions have argued that the quality of Environmental Impact Statements (EISs) is somehow affected by the volume of information they contain. Both too little and too much information can be a problem. However, very few academic studies have addressed the issue of EIS length in detail. The objective of this article was to systematically analyze the volume of information presented in EISs, using Brazil as the empirical context. More specifically, this study evaluated the volume and proportion of information disclosed in 49 Brazilian EISs. This study also tried to identify sectorial variations and whether variables such as project size and number of pages in Terms of References are likely determinants of information volume. >146 thousand pages of EIS information were scrutinized in two rounds of content analysis. Data were organized in spreadsheets and then coded and analyzed through various descriptive and inferential statistical techniques. Overall, findings corroborate the fact that EISs are now significantly longer than the early ones, and still heavily loaded with baseline information. The average number of pages in EISs and in Non-technical Summaries was found to be 2993 and 94, respectively. Kruskal-Wallis and linear regression tests indicated that EIS length is likely affected by a combination of variables, including project size, territorial and sectorial characteristics. Such findings suggest that the historical approach of setting page limits to EISs through regulations and Terms of References is no longer appropriate for EIA practice in connection with large enterprises in Brazil, and arguably elsewhere. The article discusses its practical and academic implications, and highlights the need to further investigate the actual impacts of EIS length on decision-making.

54 ENVIRONMENTAL SCIENCES↗