Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Software Construction”

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 451 records · Page 25

X-Ray Spectroscopy of Optically Bright Planets using the Chandra Observatory

Since its launch in July 1999, Chandra's Advanced CCD Imaging Spectrometer (ACIS) has observed several planets (Venus, Mars, Jupiter and Saturn) and 6 comets. At 0.5 arc-second spatial resolution, ACIS detects individual x-ray photons with good quantum efficiency (25% at 0.6 KeV) and energy resolution (20% FWHM at 0.6 KeV). However, the ACIS CCDs are also sensitive to optical and near-infrared light, which is absorbed by optical blocking filters (OBFs) that eliminate optical contamination from all but the brightest extended sources, e.g., planets. .Jupiter at opposition subseconds approx.45 arc-seconds (90 CCD pixels.) Since Chandra is incapable of tracking a moving target, the planet takes 10 - 20 kiloseconds to move across the most sensitive ACIS CCD, after which the observatory must be re-pointed. Meanwhile, the OBF covering that CCD adds an opt,ical signal equivalent to approx.110 eV to each pixel that lies within thc outline of the Jovian disk. This has three consequences: (1) the observatory must be pointed away from Jupiter while CCD bias maps are constructed; (2) most x-rays from within the optical image will be misidentified as charged-particle background and ignored; and (3) those x-rays that are reported will bc assigned anomalously high energies. The same also applies to thc other planets, but is less serious since they are either dimmer at optical wavelengths, or they show less apparent motion across the sky, permitting reduced CCD exposure times: the optical contamination from Saturn acids approx.15 eV per pixel, and from Mars and Venus approx.31 eV. After analyzing a series of short .Jupiter observations in December 2000, ACIS parameters were optimized for the February 2003 opposition. CCD bias maps were constructed while Chandra pointed away from Jupiter, and the subsequent observations employed on-board software to ignore any pixel that contained less charge than that expected from optical leakage. In addition, ACIS was commanded to report 5 x 5 arrays of pixel values surrounding each x-ray event, and the outlying values were employed during ground processing to correct for the optical contamination.

Ford, P. G.↗

Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Source record↗

Automated Generation of Fault Management Artifacts from a Simple System Model

Our understanding of off-nominal behavior - failure modes and fault propagation - in complex systems is often based purely on engineering intuition; specific cases are assessed in an ad hoc fashion as a (fallible) fault management engineer sees fit. This work is an attempt to provide a more rigorous approach to this understanding and assessment by automating the creation of a fault management artifact, the Failure Modes and Effects Analysis (FMEA) through querying a representation of the system in a SysML model. This work builds off the previous development of an off-nominal behavior model for the upcoming Soil Moisture Active-Passive (SMAP) mission at the Jet Propulsion Laboratory. We further developed the previous system model to more fully incorporate the ideas of State Analysis, and it was restructured in an organizational hierarchy that models the system as layers of control systems while also incorporating the concept of "design authority". We present software that was developed to traverse the elements and relationships in this model to automatically construct an FMEA spreadsheet. We further discuss extending this model to automatically generate other typical fault management artifacts, such as Fault Trees, to efficiently portray system behavior, and depend less on the intuition of fault management engineers to ensure complete examination of off-nominal behavior.

Spinup and Orient↗

NASA Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule and budget development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Planning↗

NASA Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements.

Schedule↗

NASA Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for Work Breakdown Structure (WBS) and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements.

Formulation↗

NASA Work Breakdown Structure (WBS) Handbook

The purpose of this document is to provide program/project teams necessary instruction and guidance in the best practices for WBS and WBS dictionary development and use for project implementation and management control. This handbook can be used for all types of NASA projects and work activities including research, development, construction, test and evaluation, and operations. The products of these work efforts may be hardware, software, data, or service elements (alone or in combination). The aim of this document is to assist project teams in the development of effective work breakdown structures that provide a framework of common reference for all project elements. The WBS and WBS dictionary are effective management processes for planning, organizing, and administering NASA programs and projects. The guidance contained in this document is applicable to both in-house, NASA-led effort and contracted effort. It assists management teams from both entities in fulfilling necessary responsibilities for successful accomplishment of project cost, schedule, and technical goals. Benefits resulting from the use of an effective WBS include, but are not limited to: providing a basis for assigned project responsibilities, providing a basis for project schedule and budget development, simplifying a project by dividing the total work scope into manageable units, and providing a common reference for all project communication.

Christopher Lewis Sadler↗

Technology Solutions Case Study: Hygrothermal Performance of a Double-Stud Cellulose Wall

Moisture problems within the building shell can be caused by a number of factors including excess interior moisture that is transported into the wall through air leakage and vapor drive, bulk water intrusion from leaks and wind-driven rain, capillary action from concrete to wood connections, and through wetted building materials such as siding wetted from rain splash back. With the increasing thickness of walls, moisture issues could increase. Several builders have successfully used “double-wall” systems to more practically achieve higher R-values in thicker framed walls. A double wall typically consists of a load-bearing external frame wall constructed with 2 × 4 framing at 16 in. on center using conventional methods. After the building is enclosed, an additional frame wall is constructed several inches inside the load-bearing wall. Several researchers have used moisture modeling software to conduct extensive analysis of these assemblies; however, little field research has been conducted to validate the results. In this project, the Building America research team Consortium for Advanced Residential Buildings monitored a double-stud assembly in climate zone 5A to determine the accu¬racy of moisture modeling and make recommendations to ensure durable and efficient assemblies.

Building America↗

ISOCS-based Extended In Situ Gamma Spectrometry Services Tool SuperISOCS for Waste Measurements - 20275

Canberra's In Situ Object Counting System (ISOCS) is an established tool used for gamma spectrometry. It allows physical representation of complex geometries and mathematical calculation of the calibration function while avoiding the need for radioisotope standards. ISOCS provides a large range of templates to generate the geometry for most nuclear waste components in nuclear facilities. Nonetheless, there are some complex geometries where the accuracy attainable is limited by the conventional ISOCS templates. An ISOCS-based extended in-situ Gamma Spectrometry service tool has been developed, based on the so-called SuperISOCS (SISOCS) software. This tool was developed to generate the most complex geometries. The principle of geometry construction is based on the composition of 8 different primitive geometries. The primitive object is able to be cut and to change a part of an object. An object is able to overlap to another one to form a more complex object. These functions refine the modelled geometry compared to the real objects and decrease the measurement systematic error because they allow the mathematical model to represent the real-life geometry more faithfully through reducing the approximations and simplifications that need to be made The algorithm of SISOCS is the same as that of standard ISOCS. A set of calculations was done in comparison with MCNP efficiency calculation and SISOCS results. 80 different models were compared between SISOCS and MCNP, with added 30 cases compared between ISOCS and SISOCS. The average differences were less than 2%, for all energy's efficiency calculations. In this paper we illustrate the benefits that this new tool can provide, in terms of improved accuracy for complex realistic geometries, through simulation of some example scenarios. Furthermore, we demonstrate, through SISOCS modelling of the real object data test, the comparison between SISOCS to ISOCS calculations for the same geometry. This paper describes the added functions that are easily employed using SISOCS. Our results show the potential application and benefit of this technique for real waste assay projects and the way to integrate the tool into the waste assay systems. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Object oriented development of engineering software using CLIPS

Engineering applications involve numeric complexity and manipulations of a large amount of data. Traditionally, numeric computation has been the concern in developing an engineering software. As engineering application software became larger and more complex, management of resources such as data, rather than the numeric complexity, has become the major software design problem. Object oriented design and implementation methodologies can improve the reliability, flexibility, and maintainability of the resulting software; however, some tasks are better solved with the traditional procedural paradigm. The C Language Integrated Production System (CLIPS), with deffunction and defgeneric constructs, supports the procedural paradigm. The natural blending of object oriented and procedural paradigms has been cited as the reason for the popularity of the C++ language. The CLIPS Object Oriented Language's (COOL) object oriented features are more versatile than C++'s. A software design methodology based on object oriented and procedural approaches appropriate for engineering software, and to be implemented in CLIPS was outlined. A method for sensor placement for Space Station Freedom is being implemented in COOL as a sample problem.

Yoon, C. John↗

The g-code file

The slicing process for additive manufacturing (AM) involves many steps, including slicing the object to be printed and fitting toolpaths to each resulting layer. The toolpaths define the trajectories that the machine must follow during printing to construct the object. Once the slicing is complete and all toolpaths have been found and properly planned, this data must be transferred to the 3D printer in a way the printer can use to construct the object. This is achieved by exporting a file, usually a g-code file, from the slicing software. The g-code file is a text-based file that contains instructions for the machine, controlling the system and defining the motions for each toolpath. The file, which often contains thousands of lines of code, is mostly composed of numbers that command positions for axis motions. This chapter will outline the contents of a g-code file, discuss various commands and their implementation, then provide example codes and files for object construction.

Roschli, Alex↗

NASA Orbital Debris Engineering Model ORDEM 3.1 - Software User Guide

This National Aeronautics and Space Administration (NASA) Orbital Debris Engineering Model (ORDEM) 3.1 Software User Guide accompanies delivery of the latest upgraded version of the model, ORDEM 3.1. The user guide also provides a top-level program description and a list of capabilities. It includes descriptions of runtime error and information codes, input/output file formats, runtimes for different orbit configurations, and how to use uncertainty files. ORDEM 3.1 supersedes the previous NASA Orbital Debris Program Office (ODPO) models – ORDEM 3.0 (Stansbery, et al. 2014) and ORDEM2000 (Liou, et al. 2002). The availability of new sensor and in situ data, re-analysis of older data, and development of new analytical techniques has enabled the construction of this more comprehensive and sophisticated model. An upgraded graphical user interface (GUI) is integrated with the software. This upgraded GUI uses project-oriented organization and provides the user with graphical representations of numerous output data products. For example, these range from the conventional flux vs. average debris size (or altitude bin) for chosen analysis orbits (or views) to the more complex color-contoured, two-dimensional (2-D) directional flux diagrams in local spacecraft elevation and azimuth. The current model, ORDEM 3.1, supports spacecraft as well as telescope/radar project assessments. ORDEM 3.1 contains updated debris populations covering low Earth orbit (LEO, up to 2000 km altitude) to geosynchronous orbit (GEO, up to 40,000 km altitude) and can assess debris calculations up to year 2050, extending coverage past the previous limit of 2035 in ORDEM 3.0. Although populations differ from its predecessor, ORDEM 3.1 is functionally the same as ORDEM 3.0 and can support ORDEM 3.0 projects through backward compatibility.

Vavrin, Andrew B.↗

NASA Orbital Debris Engineering Model ORDEM 3.2 – Software User Guide

This National Aeronautics and Space Administration (NASA) Orbital Debris Engineering Model (ORDEM) 3.2 Software User Guide accompanies delivery of the latest upgraded version of the model, ORDEM 3.2. The user guide also provides a top-level program description and a list of capabilities. It includes descriptions of runtime error and information codes, input/output file formats, runtimes for different orbit configurations, and how to use uncertainty files. ORDEM 3.2 supersedes the previous NASA Orbital Debris Program Office (ODPO) models – ORDEM 3.0 (Stansbery, et al. 2014) and ORDEM2000 (Liou, et al. 2002). The availability of new sensor and in situ data, re-analysis of older data, and development of new analytical techniques has enabled the construction of this more comprehensive and sophisticated model. An upgraded graphical user interface (GUI) is integrated with the software. This upgraded GUI uses project-oriented organization and provides the user with graphical representations of numerous output data products. For example, these range from the conventional flux vs. average debris size (or altitude bin) for chosen analysis orbits (or views) to the more complex color-contoured, two-dimensional (2-D) directional flux diagrams in local spacecraft elevation and azimuth. The current model, ORDEM 3.2, supports spacecraft as well as telescope/radar project assessments. ORDEM 3.2 contains updated debris populations covering low Earth orbit (LEO, up to 2000 km altitude) to geosynchronous orbit (GEO, up to 40,000 km altitude) and can assess debris calculations up to year 2050, extending coverage past the previous limit of 2035 in ORDEM 3.0. Although populations differ from its predecessor, ORDEM 3.2 is functionally the same as ORDEM 3.0 and can support ORDEM 3.0 projects through backward compatibility.

Andrew Vavrin↗

MDSplus Yesterday, Today and Tomorrow

MDSplus is a data acquisition and analysis system used worldwide predominantly in the fusion research community. Development began 31 years ago by a collaboration of software developers who were charged with providing a data acquisition system for three new fusion experiments under construction: CMOD at MIT, ZTH at LANL and RFX at Padova, Italy. The design of MDSplus combined the functionality of MDS (MIT/Model Data System developed at MIT for the Alcator and Tara fusion experiments) with new features suggested by the developers from the other laboratories. The development of MDSplus used a RAD (rapid application development) approach before RAD became a mainstream methodology. MDSplus was implemented and ready for the initial operation of CMOD in 1991. Since that time, many other fusion facilities started using MDSplus for data acquisition and/or for exporting their data to other sites. Today MDSplus is still used around the world for fusion energy research, space exploration and other fields of science and technology. Work on MDSplus continues to enhance its capabilities, support more platforms, and improve its reliability. It is anticipated that MDSplus will continue to provide valuable tools for the fusion energy research community. This paper describes some of the history of the MDSplus software, the work that is currently underway, and the plans to enable MDSplus to continue to be available and supported long into the future.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗

MDSplus yesterday, today and tomorrow

MDSplus is a data acquisition and analysis system used worldwide predominantly in the fusion research community. Development began 31 years ago by a collaboration of software developers who were charged with providing a data acquisition system for three new fusion experiments under construction: CMOD at MIT, ZTH at LANL and RFX at Padova, Italy. The design of MDSplus combined the functionality of MDS (MIT/Model Data System developed at MIT for the Alcator and Tara fusion experiments) with new features suggested by the developers from the other laboratories. The development of MDSplus used a RAD (rapid application development) approach before RAD became a mainstream methodology. MDSplus was implemented and ready for the initial operation of CMOD in 1991. Since that time, many other fusion facilities started using MDSplus for data acquisition and/or for exporting their data to other sites. Today MDSplus is still used around the world for fusion energy research, space exploration and other fields of science and technology. Work on MDSplus continues to enhance its capabilities, support more platforms, and improve its reliability. It is anticipated that MDSplus will continue to provide valuable tools for the fusion energy research community. In conclusion, this paper describes some of the history of the MDSplus software, the work that is currently underway, and the plans to enable MDSplus to continue to be available and supported long into the future.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗

Enter TCM and Associated Equipment into Stage One Mockup

The scope of the FY17 milestone involved entering the TCM into stage one mockup at the Materials and Fuels Complex (MFC) and completing initial testing. While the TCM head was designed and partially fabricated in FY16, the ancillary equipment and software for standalone operation at the IMCL still required development. The tasks required to prepare the TCM for stage one mockup included: 1 – develop cell feedthroughs for both optical and electrical signals, 2 – design and construction of a film thickness monitor, 3 – drafting an equipment qualification plan, 4 – develop an integrated equipment rack to house lasers and instrumentation, and 5 – develop coding instrumentation software for controlling the TCM.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Status Report on IES Plug-and-Play Framework

This report discusses the status of the flexible plug-and-play framework development currently ongoing that aims to integrate Modelica/Dymola with the Risk Analysis and Virtual ENviroment (RAVEN) software in terms of both Functional Mock-Up Interface (FMI)/Functional Mock-Up Unit (FMU) construction and repository structures that aim to ease the sharing and simulation of complex dynamic models. This report provides discusses the FMI/FMU adaptors that have been created within the HYBRID repository to allow users to quickly export models as FMUs. Several examples are shown that highlight the step-by-step process of converting an existing Modelica model into an FMU for use within the Dymola platform. Simulation results demonstrate that, while minor differences may occur, the overall control, trends, and solution integrity is maintained between standard Modelica simulation and FMU simulation results. However, it is worth noting that, for small systems, the FMU results have a slower simulation time than the Modelica only simulation. Using this process, a company can provide models that contain proprietary information to entities without disclosing any of the information about the model that could be considered business sensitive. Such an ability would allow institutions to bypass the necessity of “whitewashing” data. In addition to the investigative work being conducted on FMUs and FMIs, a series of updates to the hybrid repository has been completed. These updates include the addition of Modelica system-level regression tests and software quality assurance documentation that ensure that modifications to the Modelica models do not alter system-level model results. Overall, extensive work has been completed on developing FMUs and FMIs from existing models, understanding the requirements and limitations of FMUs, and opensourcing the HYBRID repository with an integrated regression system.

99 GENERAL AND MISCELLANEOUS↗

Repurposing a microfluidic formulation device for automated DNA construction

Microfluidic applications have expanded greatly over the past decade. For the most part, however, each microfluidics platform is developed with a specific task in mind, rather than as a general-purpose device with a wide-range of functionality. Here, we show how a microfluidic system, originally developed to investigate protein phase behavior, can be modified and repurposed for another application, namely DNA construction. We added new programable controllers to direct the flow of reagents across the chip. We designed the assembly of a combinatorial Golden Gate DNA library using TeselaGen DESIGN software and used the repurposed microfluidics platform to assemble the designed library from off-chip prepared DNA assembly pieces. Further experiments verified the sequences and function of the on-chip assembled DNA constructs.

59 BASIC BIOLOGICAL SCIENCES↗