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 181 records · Page 10

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↗

Mathematical modeling of ice accretion on airfoils

The progress toward development of a computer model suitable for predicting icing behavior on airfoils over a wide range of environmental conditions and airfoils shapes is reported. The LEWICE program was formulated to solve a set of equations which describe the physical processes which occur during accretion of ice on an airfoil, including heat transfer in a time dependent mode, with the restriction that the flow must be describable by a two-dimensional flow code. Input data comprises the cloud liquid water content, mean droplet diameter, ambient air temperature, air velocity, and relative humidity. A potential flowfield around the airfoil is calculated, along with the droplet trajectories within the flowfield, followed by local values of water droplet collection efficiency at the impact points. Both glaze and rime ice conditions are reproduced, and comparisons with test results on icing of circular cylinders showed good agreement with the physical situation.

Macarthur, C. D.↗

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↗

NSSDC Data listing

A convenient reference to space science and supportive data available from the National Space Science Data Center (NSSDC) is provided. Satellite data are organized by NSSDC spacecraft common name. The launch date and NSSDC ID are given. Experiments are listed alphabetically by the principal investigator or team leader. The experiment name and NSSDC ID, data set ID, data set name, data form code, quantity of data, and the time span of the data as verified by NSSDC are shown. Ground-based data, models, computer routines, and composite spacecraft data that are available from NSSDC are listed alphabetically by discipline, source, data type, data content, and data set. The data set name, data form code, quantity of data, and the time span covered where appropriate are included.

Source record↗

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↗

Nuclear Data Sheets for A=73☆

Experimental nuclear structure data for the known A=73 isobaric nuclides (Mn, Fe, Co, Ni, Cu, Zn, Ga, Ge, As, Se, Br, Kr, Rb and Sr) 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. For {sup 73}Mn, only the isotopic identification has been established, with no knowledge of its g.s. half-life. For {sup 73}Fe, {sup 73}Co and {sup 73}Sr, only the ground states and their half-lives are known with no information about the excited states. For {sup 73}Ni, {sup 73}Cu, {sup 73}Zn and {sup 73}Rb, little data are available for excited states. The half-life and decay modes of possibly proton-unbound {sup 73}Rb need firmly established. {sup 73}Ga structure presents a special challenge in that the 1/2{sup −} ground state and the first 3/2{sup −} state have recently been proposed, in a Coulomb excitation experiment by 2010Di14, to form an almost degenerate doublet with an estimated spacing of 229 Th with its first excited state at 7.8 eV, and {sup 235}U with its first excited state at 76 eV. Ultra-high resolution gamma-ray spectroscopic studies are warranted to search for the low-lying (73 Ga, and to determine its half-life. Level structures of {sup 73}Ga, {sup 73}Ge, {sup 73}As, {sup 73}Se, {sup 73}Br and {sup 73}Kr are quite well known, although decay schemes of radioactive ground states of {sup 73}Co, {sup 73}Cu and {sup 73}Br are considered incomplete. The reactions and decays for which no new experimental information has become available since the 2003 update have undergone revisions to incorporate conversion coefficients from BrIcc code, and evaluated Q values from 2017Wa10, but essential content of such datasets may have remained the same as in previous evaluations. In this respect the present work greatly benefited from all the previous NDS evaluations (2004Si08,1993Ki25,1987Ki13, 1980Ek01,1974Al33), but at the same time data presented herein supersede all the previous published evaluations.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Draft genome of Paraburkholderia caballeronis TNe-841 T , a free-living, nitrogen-fixing, tomato plant-associated bacterium

Paraburkholderia caballeronis is a plant-associated bacterium. Strain TNe-841 T was isolated from the rhizosphere of tomato ( Solanum lycopersicum L. var. lycopersicum) growing in Nepantla Mexico State. Initially this bacterium was found to effectively nodulate Phaseolus vulgaris L. However, from an analysis of the genome of strain TNe-841 T and from repeat inoculation experiments, we found that this strain did not nodulate bean and also lacked nodulation genes, suggesting that the genes were lost. The genome consists of 7,115,141 bp with a G + C content of 67.01%. The sequence includes 6251 protein-coding genes and 87 RNA genes.

59 BASIC BIOLOGICAL SCIENCES↗

Griffin/Pronghorn PBMR-400 Benchmark Results [Slides]

Content Overview: 1) Pronghorn & Griffin, MOOSE based applications overview: Codes capabilities description & MOOSE ecosystem overiew; Current research activities and synergies with other projects; Different multiphysics coupling scheme description. 2) PBMR-400 Benchmark: OECD NEA Benchmark and Pronghorn/Griffin models description; Standalone NK Ex1 and TH Ex2 Results description; Coupled Steady state Ex3; Results analysis for Transiet Ex4a (100-40-100 Load Following) & Ex3 (Protected PLOFC). 3) Conclusions $ Future steps.

97 MATHEMATICS AND COMPUTING↗