Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Performance Tools”

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 361 records · Page 20

Summary of BISON Development and Validation Activities - NEAMS FY15 Report

The objective of the NEAMS ToolKit is to develop a “pellet-to-plant” simulation capability useful for predicting performance and safety for a broad range of nuclear reactor power systems. The NEAMS ToolKit has been organized into a Fuels Product Line (FPL) and a Reactor Product Line (RPL) and is modular in design. Within the FPL, a multiscale approach has been adopted in which simulations of fuel performance at the engineering scale are informed by material property and irradiation performance models developed from mesoscale simulations of microstructural evolution. The focus in this report is on development and validation of the engineering-scale fuel performance analysis tool within the FPL, which is BISON. This summary report contains an overview of work performed under the work package enti- tled “FY2015 NEAMS INL-Engineering Scale Fuel Performance & Interface with RPL Tools.” A first chapter identifies the specific FY-15 milestones, providing a basic description of the asso- ciated work and references to related detailed documentation. Where applicable, a representative technical result is provided. A second chapter summarizes major additional accomplishments including 1) a BISON validation paper, 2) a multiphysics coupling paper, 3) application of BI- SON to Reactivity Insertion Accident analysis and 4) use of BISON for uncertainity analysis in fuel modeling. A final chapter outlines FY-16 future work.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Are Event Traces Really That Necessary?

Many performance monitoring tools are currently available to the super-computing community. The performance data gathered and analyzed by these tools fall under two categories: statistics and event traces. Statistical data is much more compact but lack the probative power event traces offer. Event traces, on the other hand, can easily fill up the entire file system during execution such that the instrumented execution have to be terminated. In this paper, we propose an innovative methodology for monitoring and trace representation that offers a middle ground. The user can trace-off trace data size vs. quality incrementally. Specifically, the user will be able to limit the amount of trace collected and, at the same time, carry out some of the analysis event traces offer for the entire execution. With the help of a few CFD examples, we illustrate the use of our technique in performance tuning. We also compare quantitatively, the quality of the traces we collected vs. event traces.

Schmidt, Melisa↗

METAREP: JCVI metagenomics reports—an open source tool for high-performance comparative metagenomics

JCVI Metagenomics Reports (METAREP) is a Web 2.0 application designed to help scientists analyze and compare annotated metagenomics datasets. It utilizes Solr/Lucene, a high performance scalable search engine, to quickly query large data collections. Furthermore, users can use its SQL-like query syntax to filter and refine datasets. METAREP provides graphical summaries for top taxonomic and functional classifications as well as a GO, NCBI Taxonomy and KEGG Pathway Browser. Users can compare absolute and relative counts of multiple datasets at various functional and taxonomic levels. Advanced comparative features comprise statistical tests as well as multidimensional scaling, heatmap and hierarchical clustering plots. Summaries can be exported as tab-delimited files, publication quality plots in PDF format. A data management layer allows collaborative data analysis and result sharing.

59 BASIC BIOLOGICAL SCIENCES↗

Diagnosing Anomalous Network Performance with Confidence

Variability in network performance is a major obstacle in effectively analyzing the throughput of modern high performance computer systems. High performance interconnec- tion networks offer excellent best-case network latencies; how- ever, highly parallel applications running on parallel machines typically require consistently high levels of performance to adequately leverage the massive amounts of available computing power. Performance analysts have usually quantified network performance using traditional summary statistics that assume the observational data is sampled from a normal distribution. In our examinations of network performance, we have found this method of analysis often provides too little data to under- stand anomalous network performance. Our tool, Confidence, instead uses an empirically derived probability distribution to characterize network performance. In this paper we describe several instances where the Confidence toolkit allowed us to understand and diagnose network performance anomalies that we could not adequately explore with the simple summary statis- tics provided by traditional measurement tools. In particular, we examine a multi-modal performance scenario encountered with an Infiniband interconnection network and we explore the performance repeatability on the custom Cray SeaStar2 interconnection network after a set of software and driver updates.

Settlemyer, Bradley W↗

Technology Performance Level (TPL) Scoring Tool

Three different ways of combining scores are used in the revised formulation. These are arithmetic mean, geometric mean and multiplication with normalisation. Arithmetic mean is used when combining scores that measure similar attributes, e.g. used for combining costs. The arithmetic mean has the property that it is similar to a logical OR, e.g. when combining costs it does not matter what the individual costs are only what the combined cost is. Geometric mean and Multiplication are used when combining scores that measure disparate attributes. Multiplication is similar to a logical AND, it is used to combine ‘must haves.’ As a result, this method is more punitive than the geometric mean; to get a good score in the combined result it is necessary to have a good score in ALL of the inputs. e.g. the different types of survivability are ‘must haves.’ On balance, the revised TPL is probably less punitive than the previous spreadsheet, multiplication is used sparingly as a method of combining scores. This is in line with the feedback of the Wave Energy Prize judges.

97 MATHEMATICS AND COMPUTING↗

HelioScope Energy Performance Modeling Validation: Cooperative Research and Development Final Report, CRADA Number CRD-17-00685

HelioScope is a unique solar design and energy performance modeling tool that bridges the worlds of research and industry, bringing the most rigorous methods from the performance modeling community to thousands of solar developers of all backgrounds. However, many financial institutions and municipalities are hesitant to accept the energy production modeling results of HelioScope (including shading losses) in place of costly, time-intensive, and/or redundant methods due to lack of vetting from a respected institution like NREL. We expect that the proposed validation exercises will give municipalities and financial institutions the comfort needed to incorporate HelioScope into their operations, thereby significantly reducing the needs of existing and potential HelioScope users' to otherwise obtain information that HelioScope produces automatically. Folsom Labs was selected for a Small Business Voucher from the U.S. Department of Energy for the National Renewable Energy Laboratory to validate the performance of HelioScope’s simulation engine against measured PV system performance.

14 SOLAR ENERGY↗

Supervisory telerobotics testbed for unstructured environments

A telerobotics testbed for performing tasks such as assembly and repair of spacecraft in unstructured environments is described. This fully operational multiarm system can operate in teleoperated or supervisory control modes, as well as mixed shared-control modes, thus enabling operations in totally to partially unstructured environments. Various sources of uncertainty are identified and approaches to minimize their effects are presented. In the teleoperated mode, the system uses two force-reflecting hand controllers to operate two manipulator arms. A third arm is utilized to position four cameras to view the scene. In the supervisory mode, the system can be operated from three different levels: task, process, and servo levels, providing different levels of autonomy and performance. Various tools are provided so that an operator can perform tasks even when objects are partially occluded or their positions are not known a priori.

Hayati, S.↗

Code Sharing and Collaboration: Experiences from the Scientist's Expert Assistant Project and their Relevance to the Virtual Observatory

In the Virtual Observatory (VO), software tools will perform the functions that have traditionally been performed by physical observatories and their instruments. These tools will not be adjuncts to VO functionality but will make up the very core of the VO. Consequently, the tradition of observatory and system independent tools serving a small user base is not valid for the VO. For the VO to succeed, we must improve software collaboration and code sharing between projects and groups. A significant goal of the Scientist's Expert Assistant (SEA) project has been promoting effective collaboration and code sharing between groups. During the past three years, the SEA project has been developing prototypes for new observation planning software tools and strategies. Initially funded by the Next Generation Space Telescope, parts of the SEA code have since been adopted by the Space Telescope Science Institute. SEA has also supplied code for SOFIA, the SIRTF planning tools, and the JSky Open Source Java library. The potential benefits of sharing code are clear. The recipient gains functionality for considerably less cost. The provider gains additional developers working with their code. If enough users groups adopt a set of common code and tools, defacto standards can emerge (as demonstrated by the success of the FITS standard). Code sharing also raises a number of challenges related to the management of the code. In this talk, we will review our experiences with SEA - both successes and failures - and offer some lessons learned that may promote further successes in collaboration and re-use.

Jones, Jeremy↗

Code Sharing and Collaboration: Experiences From the Scientist's Expert Assistant Project and Their Relevance to the Virtual Observatory

In the Virtual Observatory (VO), software tools will perform the functions that have traditionally been performed by physical observatories and their instruments. These tools will not be adjuncts to VO functionality but will make up the very core of the VO. Consequently, the tradition of observatory and system independent tools serving a small user base is not valid for the VO. For the VO to succeed, we must improve software collaboration and code sharing between projects and groups. A significant goal of the Scientist's Expert Assistant (SEA) project has been promoting effective collaboration and code sharing among groups. During the past three years, the SEA project has been developing prototypes for new observation planning software tools and strategies. Initially funded by the Next Generation Space Telescope, parts of the SEA code have since been adopted by the Space Telescope Science Institute. SEA has also supplied code for the SIRTF (Space Infrared Telescope Facility) planning tools, and the JSky Open Source Java library. The potential benefits of sharing code are clear. The recipient gains functionality for considerably less cost. The provider gains additional developers working with their code. If enough users groups adopt a set of common code and tools, de facto standards can emerge (as demonstrated by the success of the FITS standard). Code sharing also raises a number of challenges related to the management of the code. In this talk, we will review our experiences with SEA--both successes and failures, and offer some lessons learned that might promote further successes in collaboration and re-use.

Korathkar, Anuradha↗

GOES-16 and GOES-17 ABI INR Assessment

The first two satellites of the US Geostationary Operational Environmental Satellite R-Series (GOES-R) were launched on November 19, 2016 and March 1, 2018 respectively. GOES-16 officially became GOES East on December 18, 2017, and the designation of GOES-17 as GOES West occurred on February 12 2019. The Advanced Baseline Imager (ABI) is the primary instrument on GOES-16 and GOES-17 for imaging Earth’s surface and atmosphere to significantly improve the detection and observation of severe environmental phenomena. The Image Navigation and Registration (INR) Performance Assessment Tool Set (IPATS) was developed to assess INR performance of GOES-R series ABI images. In this paper, we first describe the assessment of IPATS algorithm accuracy. Next, we present the relationship between view zenith angle (VZA) and the quality of the IPATS measurements. Lastly, we present GOES-16 and GOES-17 navigation (NAV) assessments results from flight data spanning from the start of INR assessment to June 2019. The results show a) IPATS “stair step” measurement error is less or equal to 0.06 ABI pixel with IPATS baseline configuration; b) VZA is an effective filter to exclude outliers of the measurements; and c) ABI INR for both satellites has improved over time as post-launch tests (PLT) were performed and corrections applied. This paper also shows that the post-launch INR tuning of GOES-17 was much shorter than GOES-16.

GOES-17↗

Agni: Coupling Model Analysis Tools and High-Performance Subsurface Flow and Transport Simulators for Risk and Performance Assessments

Agni is open source /community /multi platform framework for model-based analyses (SA, UQ, PE, RA, DS). Agni can be applied independently from other Advanced Simulation Capability for Environmental Management (ASCEM) modules. Agni will be available as Mercurial repository (hg clone https://akuna.labworks.org/hg/Platform) including source code, manual, test and verification examples.

COMPUTER CODES↗