Search NASA⌕ Search

SEARCH · Search NASA

Results for “DOCUMENTATION”

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 1,621 records · Page 90
All sourcesNASA NTRSDOE OSTI
DOE OSTI2021

MACCS (MELCOR Accident Consequence Code System) User Guide

The MELCOR Accident Consequence Code System (MACCS) is used by Nuclear Regulatory Commission (NRC) and various national and international organizations for probabilistic consequence analysis of nuclear power accidents. This User Guide is intended to assist analysts in understanding the MACCS/WinMACCS model and to provide information regarding the code. This user guide version describes MACCS Version 3.10.0. Features that have been added to MACCS in subsequent versions are described in separate documentation. This User Guide provides a brief description of the model history, explains how to set up and execute a problem, and informs the user of the definition of various input parameters and any constraints placed on those parameters. This report is part of a series of reports documenting MACCS. Other reports include the MACCS Theory Manual, MACCS Verification Report, Technical Bases for Consequence Analyses Using MACCS, as well as documentation for preprocessor codes including SecPop, MelMACCS, and COMIDA2. PAPERWORK REDUCTION ACT STATEMENT The NUREG does not contain information collection requirements and, therefore, is not subject to the requirements of the Paperwork Reduction Act of 1995 (44 USC 3501, et seq.). PUBLIC PROTECTION NOTIFICATION The NRC may not conduct or sponsor, and a person is not required to respond to, a request for information or an information collection requirement unless the requesting document displays a currently valid OMB control number. ACKNOWLEDGEMENTS Contributions to this User Guide were received from NRC and Sandia National Laboratories (SNL) project managers, technical experts, and code authors dedicated to the production of a valuable resource for the MACCS user community. Instructions and guidance included herein were developed over many years and include advancements in the code that provide users the ability to develop complex consequence modeling scenarios. WinMACCS and many of the early MACCS developments were due to vision of an earlier Project Manager, Jocelyn Mitchell. Jonathan Barr and AJ Nosek also contributed to the development of this report. The current NRC Project Manager, Salman Haq, provided the leadership to ensure this document was completed. Several other NRC and Sandia staff provided insights supporting development of the MACCS code and of this document.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
DOE OSTI2023

SAS4A/SASSYS-1 Commercial Grade Dedication Example Report for a Generic Sodium Pool-Type Fast Reactor Application

In the U.S., a key component of the commercialization of advanced reactors is completion of a license application, which must ultimately be approved by the Nuclear Regulatory Commission (NRC). The approval of the license application by the NRC is contingent on satisfactory demonstration of the design basis and the response of the advanced reactor design to transient and accident scenarios using accepted codes and methods. This report describes the qualification and dedication requirements that the advanced reactor safety analysis system software SAS4A/SASSYS-1 are expected to need to fulfill to be used for sodium-cooled pool-type fast reactor licensing. The qualification and dedication requirements are identified through performance critical characteristics and evaluation model acceptance criteria representative of the advanced reactor design considered for licensing. This document captures, additionally, the verification process developed to demonstrate that the software fulfills the qualification and dedication requirements for a generic sodium-cooled pool-type fast reactor as part of the commercial grade dedication process. Like most software that has primarily existed in the research and development space, the most significant challenge facing SAS4A/SASSYS-1 for use in a licensing framework is the availability of a documentation basis describing the code pedigree. SAS4A/SASSYS-1 has been used for licensing of the fast flux test facility (FFTF) and the JOYO sodium-cooled fast reactor in Japan, as well as the design of the CRBR Plant. However, the historical verification and validation (V&V) activities supporting SAS4A/SASSYS-1 development do not align with modern software quality assurance (SQA) and V&V requirements. Two approaches to use of SAS4A/SASSYS-1 in a commercial licensing framework have been identified: commercial-grade dedication (CGD) and software qualification. The methods and requirements prescribed in the ASME NQA-1-2008/2009 Standard and Regulatory Guide 1.203 on the evaluation model development and assessment process (EMDAP) have been used as guidance to define the CGD and qualification processes, respectively. A qualification and dedication requirements matrix has been developed which utilizes fundamental software verification. In this process, software verification is defined as a software quality process aimed at defining software requirement specifications, developing software design documentation, and performing and documenting acceptance testing of the code against requirements. A key element of software qualification and dedication includes determination of software acceptance with respect to critical characteristics relevant to the functional requirements of the software. To assist with identification of cross-cutting transient phenomena and functional requirements, domestic SFR vendor designs have been reviewed to identify a reference SFR design. For this report, the reference design is defined as a pool-type reactor with metal alloy fuel, a liquid-metal intermediate heat transport system, and passive decay heat rejection systems. Given this reference, a series of high-level cross-cutting phenomena was identified for a general class of single-fault undercooling or reactivity insertion transients that scopes the design basis space, with the goal of assisting with prioritization of documentation development efforts for key transient models in SAS: 1) Reactivity feedback response prior to scram; 2) System-wide thermal inertia; 3) Transition in natural circulation flow regime in heat removal systems; 4) Decay heat generation; 5) Steady-state fuel characterization; 5) Clad/fuel behavior at elevated temperatures; 6) Point kinetics and decay heat; 7) Pump coastdown behavior; 8) Core flow redistribution in loss of forced convection; 9) Pool stratification. As a demonstration of CGD of SAS4A/SASSYS-1 for a sodium pool reactor, a software qualification and dedication gap analysis as it relates to code documentation has been performed. This effort leverages the framework established as part of the SAS4A/SASSYS-1 SQA Program. This CGD demonstration provides a framework that vendors can build upon to demonstrate the applicability of the SAS4A/SASSYS-1 software for licensing a sodium-cooled pool-type fast reactor.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
DOE OSTI2024

ICSBEP Benchmark Template

The purpose of this document is to demonstrate the ability of LATEX to create an ICSBEP benchmark evaluation. Creating a large document in LATEX offers many benefits, such as automatic numbering of items such as tables and figures, and easier placement of objects in the page. Additionally, it is easier to have multiple styles of pages in the same document, and in general the handling of large documents (which evaluations very commonly are) is not problematic. The formatting of this document is meant to conform to both the standards of the document and formatting guide and established practices in order to make the creation of new evaluations a more streamlined process. This will also help reduce the benchmark-to-benchmark variation in style.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2022

Super-localisation of a point-like emitter in a resonant environment: Correction of the mirage effect

In this paper, we show that it is possible to overcome one of the fundamental limitations of super-resolution microscopy: the necessity to be in an optically homogeneous environment. Using recent modal approximation results from [ 10 , 7 ], we show, as a proof of concept, that it is possible to recover the position of a single point-like emitter in a known resonant environment from far-field measurements, with a precision two orders of magnitude below the classical Rayleigh limit. The procedure does not involve solving any partial differential equation, is computationally light (optimisation in \begin{document}$ \mathbb{R}^d $\end{document} with \begin{document}$ d $\end{document} of the order of \begin{document}$ 10 $\end{document} ) and is therefore suited for the recovery of a very large number of single emitters.

Mathematics↗
DOE OSTI2024

Pathways to IEC Standards for Heliostat Design Qualification and Site Acceptance in Central Receiver CSP Applications

This paper surveys the existing landscape of standards relevant to heliostats, identifies their gaps, and proposes a path forward to a comprehensive set of heliostat guidelines, technical specifications, and standards under the framework of International Electrotechnical Commission (IEC) TC 117. Gaps in existing guidelines and standards are surveyed using a three-tiered taxonomy: component-level, heliostat-level, and field-level. At each level, the gap analysis is followed by a proposal for a coordinated path forward on the development of standards. At the component level, advances in the understanding of wind loading should inform a technical specification for drives and structures. Reflectors require consolidation of measurement guidelines into existing standards documents. Communications & controls require technical standards to inform their selection and secure implementation. At the heliostat level, IEC 62817 (solar trackers) adequately characterizes drive systems, structures, and electronics, but requires adaptation to heliostats' use patterns, operating modes, and expected life cycles. IEC 62817 does not address heliostat beam quality and pointing accuracy, but the process for determining both is elaborated in the SolarPACES Guideline for Heliostat Performance Testing. This SolarPACES document requires two main modifications: adaptation to IEC language and inclusion of testing after heliostats which have undergone accelerated weathering and mechanical cycling (to understand performance degradation). At the field level, IEC 62862-4-2 addresses the function and control of heliostat fields but does not cover the statistically rigorous testing of heliostat groups, or field performance factors like security and soiling. The addition of documents under IEC-62862-4 is proposed to address this gap.

beam↗
NASA NTRS1984

Guidelines for submitting data to the National Space Science Data Center

The mission of the National Space Science Data Center (NSSDC) is to disseminate space science data for further analysis beyond that provided by the principal investigators (PIs) or team leaders (TLs) and their coworkers. Consequently, the NSSDC is responsible for the acquisition, organization, storage, retrieval, announcement, and distribution of scientific data obtained mainly from satellites and spacecraft. Any scientist may acquired data from the NSSDC and use them in further studies, either alone or in conjunction with data from ground-based or spacecraft experiments. With the responsibility for archiving data is the concomitant responsibility for distributing the documentation necessary to make those data usable. Since the group most knowledgeable about a particular experiment and its data is the PI or TL and his coworkers, and since the NSSDC cannot possibly supply the qualified personnel needed to write this documentation comprehensively, it is the responsibility of the PI or TL to provide the essential documentation. The NSSDC will support this effort by defining what is needed, by reviewing what is provided, and by reproducing and distributing the resulting documentation with the data. For a high-use data set, the NSSDC may publish the documentation as a Data Users Note; for a low-use data set, the NSSDC may distribute a Xerox, microfilm, or microfiche copy of the documentation.

Source record↗
NASA NTRS1986

Ada Structure Design Language (ASDL)

An artist acquires all the necessary tools before painting a scene. In the same analogy, a software engineer needs the necessary tools to provide their design with the proper means for implementation. Ada provide these tools. Yet, as an artist's painting needs a brochure to accompany it for further explanation of the scene, an Ada design also needs a document along with it to show the design in its detailed structure and hierarchical order. Ada could be self-explanatory in small programs not exceeding fifty lines of code in length. But, in a large environment, ranging from thousands of lines and above, Ada programs need to be well documented to be preserved and maintained. The language used to specify an Ada document is called Ada Structure Design Language (ASDL). This language sets some rules to help derive a well formatted Ada detailed design document. The rules are defined to meet the needs of a project manager, a maintenance team, a programmer and a systems designer. The design document templates, the document extractor, and the rules set forth by the ASDL are explained in detail.

Chedrawi, Lutfi↗
NASA NTRS1992

Software engineering laboratory series: Annotated bibliography of software engineering laboratory literature

This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: (1) the Software Engineering Laboratory; (2) the Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. This document contains an index of these publications classified by individual author.

Morusiewicz, Linda↗
NASA NTRS1994

A hypertext system that learns from user feedback

Retrieving specific information from large amounts of documentation is not an easy task. It could be facilitated if information relevant in the current problem solving context could be automatically supplied to the user. As a first step towards this goal, we have developed an intelligent hypertext system called CID (Computer Integrated Documentation). Besides providing an hypertext interface for browsing large documents, the CID system automatically acquires and reuses the context in which previous searches were appropriate. This mechanism utilizes on-line user information requirements and relevance feedback either to reinforce current indexing in case of success or to generate new knowledge in case of failure. Thus, the user continually augments and refines the intelligence of the retrieval system. This allows the CID system to provide helpful responses, based on previous usage of the documentation, and to improve its performance over time. We successfully tested the CID system with users of the Space Station Freedom requirements documents. We are currently extending CID to other application domains (Space Shuttle operations documents, airplane maintenance manuals, and on-line training). We are also exploring the potential commercialization of this technique.

Mathe, Nathalie↗
NASA NTRS1993

Annotated bibliography of Software Engineering Laboratory literature

This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. Nearly 200 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: the Software Engineering Laboratory; the Software Engineering Laboratory: software development documents; software tools; software models; software measurement; technology evaluations; Ada technology; and data collection. This document contains an index of these publications classified by individual author.

Morusiewicz, Linda↗
NASA NTRS1994

Investigations into mirror fabrication metrology analysis

This final report describes the work performed under this delivery order from June 1993 through August 1994. The scope of work included three distinct tasks in support of the AXAF-I program. The objective of the first task was to perform investigations of the grinding and polishing characteristics of the zerodur material by fabricating several samples. The second task was to continue the development of the integrated optical performance modeling software for AXAF-I. The purpose of third and final task was to develop and update the database of AXAF technical documents for an easy and rapid access. The MSFC optical and metrology shops were relocated from the B-wing of Building 4487 to Room BC 144 of Building 4466 in the beginning of this contract. This included dismantling, packing, and moving the equipment from its old location, and then reassembling it at the new location. A total of 65 zerodur samples, measuring 1 inch x 2 inches x 6 inches were ground and polished to a surface figure of lambda/10 p-v, and a surface finish of 5A rms were fabricated for coating tests. A number of special purpose tools and metal mirrors were also fabricated to support various AXAF-I development activities. In the metrology area, the ZYGO Mark 4 interferometer was relocated and also upgraded with a faster and more powerful processor. Surface metrology work was also performed on the coating samples and other optics using ZYGO interferometer and WYKO profilometer. A number of new features have been added to the GRAZTRACE program to enhance its analysis and modeling capabilities. A number of new commands have been added to the command mode GRAZTRACE program to provide a better control to the user on the program execution and data manipulation. Some commands and parameter entries have been reorganized for a uniform format. The command mode version of the convolution program CONVOLVE has been developed. An on-line help system and a user's manual have also been developed for the benefit of the users. The database of AXAF technical documents continues to progress. The titles, company name, date, and location of over 390 documents have been entered in this database. This database provides both a data search and retrieval function, and a data adding function. These functions allow a user to quickly search the data files for documents or add new information. A detailed user's guide has also been prepared. This user guide includes a document classification guide, a list of abbreviations, and a list of acronyms, which have been used in compiling this database of AXAF-I technical documents.

Dimmock, John O.↗
NASA NTRS1994

Abbreviations and acronyms

This booklet provides a partial list of acronyms, abbreviations, and other short word forms, including their definitions, used in documents at the Goddard Space Flight Center (GSFC). This list does not preclude the use of other short forms of less general usage, as long as these short forms are identified the first time they appear in a document and are defined in a glossary in the document in which they are used. This document supplements information in the GSFC Scientific and Technical Information Handbook (GHB 2200.2/April 1989). It is not intended to contain all short word forms used in GSFC documents; however, it was compiled of actual short forms used in recent GSFC documents. The entries are listed first, alphabetically by the short form, and then again alphabetically by definition.

Source record↗
NASA NTRS1994

Annotated bibliography of software engineering laboratory literature

This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. Nearly 200 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: (1) The Software Engineering Laboratory; (2) The Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. This document contains an index of these publications classified by individual author.

Kistler, David↗
NASA NTRS1995

The Empirical Investigation of Perspective-Based Reading

We consider reading techniques a fundamental means of achieving high quality software. Due to lack of research in this area, we are experimenting with the application and comparison of various reading techniques. This paper deals with our experiences with Perspective Based Reading (PBR) a particular reading technique for requirement documents. The goal of PBR is to provide operation scenarios where members of a review team read a document from a particular perspective (eg., tester, developer, user). Our assumption is that the combination of different perspective provides better coverage of the document than the same number of readers using their usual technique. To test the efficacy of PBR, we conducted two runs of a controlled experiment in the environment of NASA GSFC Software Engineering Laboratory (SEL), using developers from the environment. The subjects read two types of documents, one generic in nature and the other from the NASA Domain, using two reading techniques, PBR and their usual technique. The results from these experiment as well as the experimental design, are presented and analyzed. When there is a statistically significant distinction, PBR performs better than the subjects' usual technique. However, PBR appears to be more effective on the generic documents than on the NASA documents.

Basili, Victor R.↗
NASA NTRS1999

History of Suction-Type Laminar-Flow Control with Emphasis on Flight Resrearch: Monographs in Aerospace History Number 13

The paper contains the following sections: Foreword; Preface; Laminar-Flow Control Concepts and Scope of Monograph; Early Research on Suction-Type Laminar-Flow Control (Research from the 1930s through the War Years; Research from after World War II to the Mid-1960s); Post X-21 Research on Suction-Type Laminar-Flow Control; Status of Laminar-Flow Control Technology in the Mid-1990s; Glossary; Document 1-Aeronautics Panel, AACB, R&D Review, Report of the Subpanel on Aeronautic Energy Conservation/Fuels; Document 2-Report of Review Group on X-21A Laminar Flow Control Program; Document 3-Langley Research Center Announcement, Establishment of Laminar Flow Control Working Group; Document 4-Intercenter Agreement for Laminar Flow Control Leading Edge Glove Flights, LaRC and DFRC; Document 5-Flight Report NLF-144, of AFTIF-111 Aircraft with the TACT Wing Modified by a Natural Laminar Flow Glove; Document 6-Flight Record, F-16XL Supersonic Laminar Flow Control Aircraft; Index; and About the Author.

Braslow, A. L.↗
NASA NTRS1999

Basic Hitchhiker Payload Requirements

This document lists the requirements for the NMSU Hitchhiker experiment payload that were developed as part of the EE 498/499 Capstone Design class during the 1999-2000 academic year. This document is used to describe the system needs as described in the mission document. The requirements listed here are those primarily used to generate the basic electronic and data processing requirements developed in the class design document. The needs of the experiment components are more fully described in the draft NASA hitchhiker customer requirements document. Many of the details for the overall payload are given in full detail in the NASA hitchhiker documentation.

Horan, Stephen↗
NASA NTRS1994

A Compositional Relevance Model for Adaptive Information Retrieval

There is a growing need for rapid and effective access to information in large electronic documentation systems. Access can be facilitated if information relevant in the current problem solving context can be automatically supplied to the user. This includes information relevant to particular user profiles, tasks being performed, and problems being solved. However most of this knowledge on contextual relevance is not found within the contents of documents, and current hypermedia tools do not provide any easy mechanism to let users add this knowledge to their documents. We propose a compositional relevance network to automatically acquire the context in which previous information was found relevant. The model records information on the relevance of references based on user feedback for specific queries and contexts. It also generalizes such information to derive relevant references for similar queries and contexts. This model lets users filter information by context of relevance, build personalized views of documents over time, and share their views with other users. It also applies to any type of multimedia information. Compared to other approaches, it is less costly and doesn't require any a priori statistical computation, nor an extended training period. It is currently being implemented into the Computer Integrated Documentation system which enables integration of various technical documents in a hypertext framework.

Mathe, Nathalie↗
NASA NTRS2005

Software to Manage the Unmanageable

In 1995, NASA s Jet Propulsion Laboratory (JPL) contracted Redmond, Washington-based Lucidoc Corporation, to design a technology infrastructure to automate the intersection between policy management and operations management with advanced software that automates document workflow, document status, and uniformity of document layout. JPL had very specific parameters for the software. It expected to store and catalog over 8,000 technical and procedural documents integrated with hundreds of processes. The project ended in 2000, but NASA still uses the resulting highly secure document management system, and Lucidoc has managed to help other organizations, large and small, with integrating document flow and operations management to ensure a compliance-ready culture.

Source record↗