Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “document repository”

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 91 records · Page 5

A Community Convention for Ecological Forecasting: Output Files and Metadata Version 1.0

This paper summarizes the open community conventions developed by the Ecological Forecasting Initiative (EFI) for the common formatting and archiving of ecological forecasts and the metadata associated with these forecasts. Such open standards are intended to promote interoperability and facilitate forecast communication, distribution, validation, and synthesis. For output files, we first describe the convention conceptually in terms of global attributes, forecast dimensions, forecasted variables, and ancillary indicator variables. We then illustrate the application of this convention to the two file formats that are currently preferred by the EFI, netCDF (network common data form), and comma-separated values (CSV), but note that the convention is extensible to future formats. For metadata, EFI's convention identifies a subset of conventional metadata variables that are required (e.g., temporal resolution and output variables) but focuses on developing a framework for storing information about forecast uncertainty propagation, data assimilation, and model complexity, which aims to facilitate cross-forecast synthesis. The initial application of this convention expands upon the Ecological Metadata Language (EML), a commonly used metadata standard in ecology. To facilitate community adoption, we also provide a Github repository containing a metadata validator tool and several vignettes in R and Python on how to both write and read in the EFI standard. Lastly, we provide guidance on forecast archiving, making an important distinction between short-term dissemination and long-term forecast archiving, while also touching on the archiving of code and workflows. Overall, the EFI convention is a living document that can continue to evolve over time through an open community process.

Michael C. Dietze↗

Mapping in the Northern Martian Plains: A Renewed Survey of the Acidalia Mensae and Colles Regions

Acidalia Mensae is an oblong field of tilted mesas roughly trending east-west, with Acidalia Colles encompassing a regime of knobby terrain trending northeast from the center of the mesa region. Each province extends for approximately 300km in their respective directions in the heart of the vast plains of Acidalia Planitia. As part of efforts in the 1980s targeting evidences for a putative northern Martian paleo-ocean – manifesting itself most notably in geologic maps of quadrangles in East Acidalia – the Acidalia Mensae region was selected and divided into three quadrangles ranging across 26.8 deg W to 36 deg W and 47.5 deg N to 52.5 deg N. The region was then mapped at a 1:1,000,000 scale using Canvas on a Viking base map. We present an updated draft of this document converted into ArcMap, including a completed fourth quadrangle that covers the bulk of the Acidalia Colles region. Previously mapped units have been updated according to the availability of new higher-resolution data – particularly, Thermal Emission Imaging System (THEMIS) Day Infrared (IR) data as a base map, paired with supporting Context Camera (CTX) and High Resolution Stereo Camera (HRSC) HRSC stamps extracted from the Mars Orbital Data Explorer repository. Geologic units and contacts for the mesa and knob regimes, interstitial alluvial units and the surrounding plains are comprehensively presented alongside lower-level features such as levels (hypothesized to be shorelines) and pitted cones (putative pingos). The project was mapped in a transverse Mercator projection. Upon minor revision, the map is to be submitted to the USGS for publication.

Siwabessy, Andrew G.↗

Modeling and Simulation Resource Repository (MSRR)(System Engineering/Integrated M&S Management Approach

NASA s Exploration Systems Mission Directorate (ESMD) is implementing a management approach for modeling and simulation (M&S) that will provide decision-makers information on the model s fidelity, credibility, and quality, including the verification, validation and accreditation information. The NASA MSRR will be implemented leveraging M&S industry best practices. This presentation will discuss the requirements that will enable NASA to capture and make available the "meta data" or "simulation biography" data associated with a model. The presentation will also describe the requirements that drive how NASA will collect and document relevant information for models or suites of models in order to facilitate use and reuse of relevant models and provide visibility across NASA organizations and the larger M&S community.

Milroy, Audrey↗

In-Depth Analysis of Subject Functional Performance and Subjective Feedback Data for Evaluating Argos Simulation Quality

Mechanical offloading systems such as the Active Response Gravity Offload System (ARGOS) at NASA Johnson Space Center (JSC) are used to simulate various partial gravity environments. ARGOS offloads pressurized suited subjects through a gimbaling pivot point system attached to a volumetric Portable Life Support System (PLSS). The pivot point can be configured to multiple locations with respect to the human-suit system center of gravity (CG). Previous work has tested and documented the interaction between different pivot point locations and measured CG. Observations indicated that small changes in pivot point location substantially affect the stability and functional performance (simulation quality) of a subject. This led to the development of a standardized gimbal assessment protocol to assess the functional performance of a pressurized suited subject as a function of the pivot point location, using the data obtained from a variety of planetary suit mobility tasks. As a result, an expansive repository of CG-related task metrics was generated from numerous ARGOS spacesuit test events, for different gimbal configurations and different test subjects. Based on the evaluation metrics and observed trends, several pivot point locations were iteratively identified to determine an “appropriate/optimal” configuration. This study thus describes the in-depth analysis of the CG evaluation metrics to better quantify trends and determine if specific factors are strongly associated with appropriate/optimal configurations. Quantitative and qualitative variables relating to subject task performance, subjective feedback, and anthropometry will be evaluated via probabilistic methods. The results from this study are expected to improve our understanding of optimal ARGOS gimbal settings, which will better inform the gimbal configuration identification process and improve simulation quality for extravehicular activity (EVA) training.

Joseph Yao↗

Semantic Analysis of Email Using Domain Ontologies and WordNet

The problem of capturing and accessing knowledge in paper form has been supplanted by a problem of providing structure to vast amounts of electronic information. Systems that can construct semantic links for natural language documents like email messages automatically will be a crucial element of semantic email tools. We have designed an information extraction process that can leverage the knowledge already contained in an existing semantic web, recognizing references in email to existing nodes in a network of ontology instances by using linguistic knowledge and knowledge of the structure of the semantic web. We developed a heuristic score that uses several forms of evidence to detect references in email to existing nodes in the Semanticorganizer repository's network. While these scores cannot directly support automated probabilistic inference, they can be used to rank nodes by relevance and link those deemed most relevant to email messages.

Berrios, Daniel C.↗

Principles for Integrating Mars Analog Science, Operations, and Technology Research

During the Apollo program, the scientific community and NASA used terrestrial analog sites for understanding planetary features and for training astronauts to be scientists. Human factors studies (Harrison, Clearwater, & McKay 1991; Stuster 1996) have focused on the effects of isolation in extreme environments. More recently, with the advent of wireless computing, we have prototyped advanced EVA technologies for navigation, scheduling, and science data logging (Clancey 2002b; Clancey et al., in press). Combining these interests in a single expedition enables tremendous synergy and authenticity, as pioneered by Pascal Lee's Haughton-Mars Project (Lee 2001; Clancey 2000a) and the Mars Society s research stations on a crater rim on Devon Island in the High Canadian Arctic (Clancey 2000b; 2001b) and the Morrison Formation of southeast Utah (Clancey 2002a). Based on this experience, the following principles are proposed for conducting an integrated science, operations, and technology research program at analog sites: 1) Authentic work; 2) PI-based projects; 3) Unencumbered baseline studies; 4) Closed simulations; and 5) Observation and documentation. Following these principles, we have been integrating field science, operations research, and technology development at analog sites on Devon Island and in Utah over the past five years. Analytic methods include work practice simulation (Clancey 2002c; Sierhuis et a]., 2000a;b), by which the interaction of human behavior, facilities, geography, tools, and procedures are formalized in computer models. These models are then converted into the runtime EVA system we call mobile agents (Clancey 2002b; Clancey et al., in press). Furthermore, we have found that the Apollo Lunar Surface Journal (Jones, 1999) provides a vast repository or understanding astronaut and CapCom interactions, serving as a baseline for Mars operations and quickly highlighting opportunities for computer automation (Clancey, in press).

Clancey, William J.↗

Fifth NASA Goddard Conference on Mass Storage Systems and Technologies.

This document contains copies of those technical papers received in time for publication prior to the Fifth Goddard Conference on Mass Storage Systems and Technologies. As one of an ongoing series, this conference continues to serve as a unique medium for the exchange of information on topics relating to the ingestion and management of substantial amounts of data and the attendant problems involved. This year's discussion topics include storage architecture, database management, data distribution, file system performance and modeling, and optical recording technology. There will also be a paper on Application Programming Interfaces (API) for a Physical Volume Repository (PVR) defined in Version 5 of the Institute of Electrical and Electronics Engineers (IEEE) Reference Model (RM). In addition, there are papers on specific archives and storage products.

Kobler, Benjamin↗

Fifth NASA Goddard Conference on Mass Storage Systems and Technologies

This document contains copies of those technical papers received in time for publication prior to the Fifth Goddard Conference on Mass Storage Systems and Technologies held September 17 - 19, 1996, at the University of Maryland, University Conference Center in College Park, Maryland. As one of an ongoing series, this conference continues to serve as a unique medium for the exchange of information on topics relating to the ingestion and management of substantial amounts of data and the attendant problems involved. This year's discussion topics include storage architecture, database management, data distribution, file system performance and modeling, and optical recording technology. There will also be a paper on Application Programming Interfaces (API) for a Physical Volume Repository (PVR) defined in Version 5 of the Institute of Electrical and Electronics Engineers (IEEE) Reference Model (RM). In addition, there are papers on specific archives and storage products.

Kobler, Benjamin↗

Prototype software reuse environment at Goddard Space Flight Center

The Goddard Space Flight Center (GSFC) work is organized into four phases and includes participation by a contractor, CTA, Inc. The first phase was an automation study, which began with a comprehensive survey of software development automation technologies. Eight technical areas were analyzed for goals, current capabilities, and obstacles. The study documented current software development practice in GSFC Mission Operations and Data Systems Directorate, and presented short- and long-term recommendations that included focus on reuse and object-oriented development. The second phase, which has been completed, developed a prototype reuse environment with tools supporting object-oriented requirements analysis and design. This phase addressed the operational concept of software reuse, i.e., it attempted to understand how software can be reused. This environment has two semantic networks: object and keywords, and includes automated search, interactive browsing and a graphical display of database contents. Phase 3 was a domain analysis of Payload Operations Control Center (POCC) software. The goal in this phase was to create an initial repository of reusable components and techniques. Seven existing Operations Control Centers at GSFC were studied, but the domain analysis proved to be very slow. A lesson learned from this was that senior people who understand the environment and the functionality of the area are needed to perform successful domain analyses.

Truszkowski, Walt↗

ARMS: A Developing Metadata Standard for Describing Astrobiology Research Products

These presentation slides introduce the Astrobiology Resource Metadata Standard (ARMS), a new metadata standard under development at NASA Ames Research Center, in conjunction with the Astrobiology Habitable Environments Database (AHED) project. The intent of this standard is to enable uniform, internet-based search and discovery of astrobiology 'resources', i.e. virtually any product of astrobiology research, including datasets, physical samples, software, publications, websites, images, video, presentations, etc. The current draft of ARMS defines 16 different metadata properties used to describe a given resource, including routine information such as name, resource type, description, personnel, funding, and related publications. But the true power in ARMS lies in four astrobiology-specific pieces of metadata: field site location enables geospatially-restricted search for resources using placenames or geospatial coordinates; research theme associates resources with one of six broad areas of astrobiological research (as identified in the 2015 NASA Astrobiology Strategy document); astrobiology disciplines captures the set of science disciplines most relevant to creation or use of resources; and finally, astrobiology keywords characterize resources in much in the same summarizing way that journal article keywords describe publications. An initial draft of the ARMS standard is being prepared for circulation to the astrobiology community for feedback and revision.

Science Metadata↗

Ocean Color Data at the Goddard Earth Sciences (GES) DAAC: CZCS, SeaWiFS, OCTS, MODIS-Terra, MODIS-Aqua

The Goddard Earth Sciences Distributed Active Archive Center (DAAC) is the designated archive for all of the ocean color data produced by NASA satellite missions. The DAAC is a long-term, high volume, secure repository for many different kinds of environmental data. With respect to ocean color, the Goddard DAAC holds all the data obtained during the eight-year mission of the Coastal Zone Color Scanner (CZCS). The DAAC is currently receiving data from the Sea-viewing Wide Field-of-view Sensor (SeaWiFS), and the MODIS-Terra instrument. The DAAC recently received reformatted data from the Ocean Color and Temperature Scanner (OCTS) and will also archive MODIS-Aqua Ocean products. In addition to its archive and distribution services, the Goddard DAAC strives to improve data access, ease-of-use, and data applicability for a broad spectrum of customers. The DAAC's data support teams practice dual roles, both insuring the integrity of the DAAC data archive and serving the user community with answers to user inquiries, online and print documentation, and customized data services.

Source record↗

Lessons Learned for Improving Spacecraft Ground Operations

NASA policy requires each Program or Project to develop a plan for how they will address Lessons Learned. Projects have the flexibility to determine how best to promote and implement lessons learned. A large project might budget for a lessons learned position to coordinate elicitation, documentation and archival of the project lessons. The lessons learned process crosses all NASA Centers and includes the contactor community. o The Office of The Chief Engineer at NASA Headquarters in Washington D.C., is the overall process owner, and field locations manage the local implementation. One tool used to transfer knowledge between program and projects is the Lessons Learned Information System (LLIS). Most lessons come from NASA in partnership with support contractors. A search for lessons that might impact a new design is often performed by a contractor team member. Knowledge is not found with only one person, one project team, or one organization. Sometimes, another project team, or person, knows something that can help your project or your task. Knowledge sharing is an everyday activity at the Kennedy Space Center through storytelling, Kennedy Engineering Academy presentations and through searching the Lessons Learned Information system. o Project teams search the lessons repository to ensure the best possible results are delivered. o The ideas from the past are not always directly applicable but usually spark new ideas and innovations. Teams have a great responsibility to collect and disseminate these lessons so that they are shared with future generations of space systems designers. o Leaders should set a goal for themselves to host a set numbers of lesson learned events each year and do more to promote multiple methods of lessons learned activities. o High performing employees are expected to share their lessons, however formal knowledge sharing presentation are not the norm for many employees.

Bell, Michael↗

Tiros IV Radiation Data Catalog and Users' Manual

The TIROS IV Meteorological Satellite contains a medium resolution scanning radiometer. Two of the channels of this instrument are sensitive to reflected solar radiation and the remaining two respond to emitted thermal radiation from the earth and its atmosphere. The two thermal channels are calibrated in terms of equivalent blackbody temperatures, and the reflected solar radiation channels in terms of effective radiant emittances. The calibration data, along with orbital and attitude data and the radiation data from the satellite, were incorporated in a computer program for an IBM 7090 which was used to produce, in binary form, the "Final Meteorological Radiation Tape" which is the basic repository of all radiation data. After launch, the radiometer displaye d the same degradation of response characteristics as did its predecessors in TIROS II and TIROS III. The onset of degradation results in a departure of the data from the prelaunch laboratory calibration. The cause of degradation has not been determined, and the matter is still being studied at the Goddard Space Flight Center. Before work with the TIROS IV radiation data is attempted, an understanding of the radiometer, its calibration, and the problems encountered in the experiment, especially from response degradation, is essential. The instrumentation design, development work, and the calibrations herein described were performed by the Goddard Space Flight Center Staff, whereas the computer and programming efforts were carried out jointly by the staffs of the National Weather Satellite Center, U. S. Weather Bureau, and the Goddard Space Flight Center. In this Catalog-Manual, the radiometer an d its calibration, data processing, the "Final Meteorological Radiation Tape", the observed degradation patterns, and possible corrections for degradation are discussed. The Catalog-Manual also includes, in two forms, documentation of each orbit of successfully reduced radiation data acquired by TIROS IV. One method of presentation is the Index of Final Meteorological Radiation Tapes and the other is a Subpoint Track, Summary of Available Radiation Data in diagrammatic form.

TIROS IV SATELLITE↗

A Guide to Axial-Flow Turbine Off-Design Computer Program AXOD2

A Users Guide for the axial flow turbine off-design computer program AXOD2 is composed in this paper. This Users Guide is supplementary to the original Users Manual of AXOD. Three notable contributions of AXOD2 to its predecessor AXOD, both in the context of the Guide or in the functionality of the code, are described and discussed in length. These are: 1) a rational representation of the mathematical principles applied, with concise descriptions of the formulas implemented in the actual coding. Their physical implications are addressed; 2) the creation and documentation of an Addendum Listing of input namelist-parameters unique to AXOD2, that differ from or are in addition to the original input-namelists given in the Manual of AXOD. Their usages are discussed; and 3) the institution of proper stoppages of the code execution, encoding termination messaging and error messages of the execution to AXOD2. These measures are to safe-guard the integrity of the code execution, such that a failure mode encountered during a case-study would not plunge the code execution into indefinite loop, or cause a blow-out of the program execution. Details on these are discussed and illustrated in this paper. Moreover, this computer program has since been reconstructed substantially. Standard FORTRAN Langue was instituted, and the code was formatted in Double Precision (REAL*8). As the result, the code is now suited for use in a local Desktop Computer Environment, is perfectly portable to any Operating System, and can be executed by any FORTRAN compiler equivalent to a FORTRAN 9095 compiler. AXOD2 will be available through NASA Glenn Research Center (GRC) Software Repository.

Gas Turbine Engines↗

Repository-Based Software Engineering Program: Working Program Management Plan

Repository-Based Software Engineering Program (RBSE) is a National Aeronautics and Space Administration (NASA) sponsored program dedicated to introducing and supporting common, effective approaches to software engineering practices. The process of conceiving, designing, building, and maintaining software systems by using existing software assets that are stored in a specialized operational reuse library or repository, accessible to system designers, is the foundation of the program. In addition to operating a software repository, RBSE promotes (1) software engineering technology transfer, (2) academic and instructional support of reuse programs, (3) the use of common software engineering standards and practices, (4) software reuse technology research, and (5) interoperability between reuse libraries. This Program Management Plan (PMP) is intended to communicate program goals and objectives, describe major work areas, and define a management report and control process. This process will assist the Program Manager, University of Houston at Clear Lake (UHCL) in tracking work progress and describing major program activities to NASA management. The goal of this PMP is to make managing the RBSE program a relatively easy process that improves the work of all team members. The PMP describes work areas addressed and work efforts being accomplished by the program; however, it is not intended as a complete description of the program. Its focus is on providing management tools and management processes for monitoring, evaluating, and administering the program; and it includes schedules for charting milestones and deliveries of program products. The PMP was developed by soliciting and obtaining guidance from appropriate program participants, analyzing program management guidance, and reviewing related program management documents.

Source record↗

Evolution of International Space Station Program Safety Review Processes and Tools

The International Space Station Program at NASA is constantly seeking to improve the processes and systems that support safe space operations. To that end, the ISS Program decided to upgrade their Safety and Hazard data systems with 3 goals: make safety and hazard data more accessible; better support the interconnection of different types of safety data; and increase the efficiency (and compliance) of safety-related processes. These goals are accomplished by moving data into a web-based structured data system that includes strong process support and supports integration with other information systems. Along with the data systems, ISS is evolving its submission requirements and safety process requirements to support the improved model. In contrast to existing operations (where paper processes and electronic file repositories are used for safety data management) the web-based solution provides the program with dramatically faster access to records, the ability to search for and reference specific data within records, reduced workload for hazard updates and approval, and process support including digital signatures and controlled record workflow. In addition, integration with other key data systems provides assistance with assessments of flight readiness, more efficient review and approval of operational controls and better tracking of international safety certifications. This approach will also provide new opportunities to streamline the sharing of data with ISS international partners while maintaining compliance with applicable laws and respecting restrictions on proprietary data. One goal of this paper is to outline the approach taken by the ISS Progrm to determine requirements for the new system and to devise a practical and efficient implementation strategy. From conception through implementation, ISS and NASA partners utilized a user-centered software development approach focused on user research and iterative design methods. The user-centered approach used on the new ISS hazard system utilized focused user research and iterative design methods employed by the Human Computer Interaction Group at NASA Ames Research Center. Particularly, the approach emphasized the reduction of workload associated with document and data management activities so more resources can be allocated to the operational use of data in problem solving, safety analysis, and recurrence control. The methods and techniques used to understand existing processes and systems, to recognize opportunities for improvement, and to design and review improvements are described with the intent that similar techniques can be employed elsewhere in safety operations. A second goal of this paper is to provide and overview of the web-based data system implemented by ISS. The software selected for the ISS hazard systemMission Assurance System (MAS)is a NASA-customized vairant of the open source software project Bugzilla. The origin and history of MAS as a NASA software project and the rationale for (and advantages of) using open-source software are documented elsewhere (Green, et al., 2009).

Ratterman, Christian D.↗

Governing Data Findability, Accessibility, Interoperability and Reusability (FAIR) Compliance

The most recent data strategy documents at both the federal and NASA levels stipulate that systems should strive for the data they manage to be Findable, Accessible, Interoperable, and Reusable (FAIR). The NASA Life Sciences Portal (NLSP) has already begun leading efforts in this area for HRP, initiating efforts to comply with the FAIR principles. The broad interpretation of the FAIR principles has led to a plethora of tools that use a splay of metrics specifically but variably developed to judge how compliant data and systems are with the principles. A recent review [3] identified and studied 1,180 metrics across 20 publicly available tools for checking FAIR compliance of data and systems. Because of their very recent development, many organizations and data systems managers and developers have not yet had adequate time or resources to understand these FAIR compliance tools and metrics, their variations in design, accuracy or ease of application to their specific data sets and systems. Thus, it would be best for larger organizations like NASA to approach formulating a strategy for governance of FAIR compliance that can be flexibly applied and is adaptable to an evolving awareness knowledge of FAIR compliance methods and tools. In September 2024, the NASA Science Mission Directorate(SMD) organized a workshop on NASA science data repositories, including the topics of implementing FAIR and governing FAIR compliance across SMD. The initial part of these FAIR discussions focused on developing consensus around required science metadata fields. This is challenging given the diverse nature of NASA’s scientific data portfolio, the variety of metadata models and vocabularies used, and variable level of resources available to curate these data. Later discussion focused on three possible approaches to governing FAIR compliance: distributed, in which various programs, projects or systems define their own methods for assessing FAIR compliance, reporting results up appropriate management lines; centralized, in which higher-level organization(s) specify compliance tools or methods for the various data systems; and multi-level, in which a group comprised of individuals with expertise from multiple levels with organizations is formed to provide guidance and/or specifications for governing FAIR compliance. We report on the recommendations this session yielded, and how these might be shaped specifically to help implement and govern the compliance with FAIR of Human Research Program data and systems.

governance↗

[Determine and Implement Updates to Be Made to MODEAR (Mission Operations Data Enterprise Architecture Repository)]

My main project was to determine and implement updates to be made to MODEAR (Mission Operations Data Enterprise Architecture Repository) process definitions to be used for CST-100 (Crew Space Transportation-100) related missions. Emphasis was placed on the scheduling aspect of the processes. In addition, I was to complete other tasks as given. Some of the additional tasks were: to create pass-through command look-up tables for the flight controllers, finish one of the MDT (Mission Operations Directorate Display Tool) displays, gather data on what is included in the CST-100 public data, develop a VBA (Visual Basic for Applications) script to create a csv (Comma-Separated Values) file with specific information from spreadsheets containing command data, create a command script for the November MCC-ASIL (Mission Control Center-Avionics System Integration Laboratory) testing, and take notes for one of the TCVB (Terminal Configured Vehicle B-737) meetings. In order to make progress in my main project I scheduled meetings with the appropriate subject matter experts, prepared material for the meetings, and assisted in the discussions in order to understand the process or processes at hand. After such discussions I made updates to various MODEAR processes and process graphics. These meetings have resulted in significant updates to the processes that were discussed. In addition, the discussions have helped the departments responsible for these processes better understand the work ahead and provided material to help document how their products are created. I completed my other tasks utilizing resources available to me and, when necessary, consulting with the subject matter experts. Outputs resulting from my other tasks were: two completed and one partially completed pass through command look-up tables for the fight controllers, significant updates to one of the MDT displays, a spreadsheet containing data on what is included in the CST-100 public data, a tool to create a csv file with specific information from spreadsheets containing command data, a command script for the November MCC-ASIL testing which resulted in a successful test day identifying several potential issues, and notes from one of the TCVB meetings that was used to keep the teams up to date on what was discussed and decided. I have learned a great deal working at NASA these last four months. I was able to meet and work with amazing individuals, further develop my technical knowledge, expand my knowledge base regarding human spaceflight, and contribute to the CST-100 missions. My work at NASA has strengthened my desire to continue my education in order to make further contributions to the field, and has given me the opportunity to see the advantages of a career at NASA.

Fanourakis, Sofia↗