Search NASA⌕ Search

SEARCH · Search NASA

Results for “JPL projects”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS1989

Centralized database for interconnection system design

A database application called DFACS (Database, Forms and Applications for Cabling and Systems) is described. The objective of DFACS is to improve the speed and accuracy of interconnection system information flow during the design and fabrication stages of a project, while simultaneously supporting both the horizontal (end-to-end wiring) and the vertical (wiring by connector) design stratagems used by the Jet Propulsion Laboratory (JPL) project engineering community. The DFACS architecture is centered around a centralized database and program methodology which emulates the manual design process hitherto used at JPL. DFACS has been tested and successfully applied to existing JPL hardware tasks with a resulting reduction in schedule time and costs.

Billitti, Joseph W.↗
NASA NTRS2016

JPL Technology Readiness Assessment Guideline

New capabilities in spaceflight missions are enabled by new technologies. Transitioning new technology to spaceflight elements is difficult and introduces risk, but finding the right balance between benefit and risk leads to scientific advancements and novel space missions. A clear understanding of the risks of new technology can create an environment where innovation is nurtured rather than avoided. The Technology Readiness Level (TRL) was developed as a metric for the maturity of new technology, but, in the past, assessing the TRL was often done informally and inconsistently. This frequently led to discrepancies between the TRL as perceived by the technologist and that perceived by a project. JPL has developed a guideline for their projects to provide a basis for a consistent Technology Readiness Assessment (TRA). Highlights of this guideline are presented here. It is anticipated that the implementation of this guideline will enable the hand-off from technologists to project engineers leading to greater acceptance of technologies by flight projects. On completion of a satisfactory TRA, an agreement can be made between the parties on the maturation plan required for successful infusion of the technology into a flight mission.

Frerking, Margaret A.↗
NASA NTRS2007

Triaxial Probe Magnetic Data Analysis

The Triaxial Magnetic Moment Analysis software uses measured magnetic field test data to compute dipole and quadrupole moment information from a hardware element. It is used to support JPL projects needing magnetic control and an understanding of the spacecraft-generated magnetic fields. Evaluation of the magnetic moment of an object consists of three steps: acquisition, conditioning, and analysis. This version of existing software was extensively rewritten for easier data acquisition, data analysis, and report presentation, including immediate feedback to the test operator during data acquisition. While prior JPL computer codes provided the same data content, this program has a better graphic display including original data overlaid with reconstructed results to show goodness of fit accuracy and better appearance of the report graphic page. Data are acquired using three magnetometers and two rotations of the device under test. A clean acquisition user interface presents required numeric data and graphic summaries, and the analysis module yields the best fit (least squares) for the magnetic dipole and/or quadrupole moment of a device. The acquisition module allows the user to record multiple data sets, selecting the best data to analyze, and is repeated three times for each of the z-axial and y-axial rotations. In this update, the y-axial rotation starting position has been changed to an option, allowing either the x- or z-axis to point towards the magnetometer. The code has been rewritten to use three simultaneous axes of magnetic data (three probes), now using two "rotations" of the device under test rather than the previous three rotations, thus reducing handling activities on the device under test. The present version of the software gathers data in one-degree increments, which permits much better accuracy of the fit ted data than the coarser data acquisition of the prior software. The data-conditioning module provides a clean data set for the analysis module. For multiple measurements at a given degree, the first measurement is used. For omitted measurements, the missing field is estimated by linear interpolation between the two nearest measurements. The analysis module was rewritten for the dual rotation, triaxial probe measurement process and now has better moment estimation accuracy, based on the finer one degree of data acquisition resolution. The magnetic moments thus computed are used as an input to summarize the total spacecraft field.

Shultz, Kimberly↗
NASA NTRS1987

The JPL functional requirements tool

Planetary spacecraft are complex vehicles which are built according to many thousands of requirements. Problems encountered in documenting and maintaining these requirements led to the current attempt to reduce or eliminate these problems by a computer automated data base Functional Requirements Tool. The tool developed at JPL and in use on several JPL Projects is described. The organization and functionality of the Tool, together with an explanation of the data base inputs, their relationships, and use are presented. Methods of interfacing with external documents, representation of tables and figures, and methods of approval and change processing are discussed. The options available for disseminating information from the Tool are identified. The implementation of the Requirements Tool is outlined, and the operation is summarized. The conclusions drawn from this work is that the Requirements Tool represents a useful addition to the System Engineer's Tool kit, it is not currently available elsewhere, and a clear development path exists to expand the capabilities of the Tool to serve larger and more complex projects.

Giffin, Geoff↗
NASA NTRS1990

Application of CCSDS packet telemetry recommendations by JPL

The Consultative Committee for Space Data Systems (CCSDS) has adopted three Recommendations dealing with telemetry for conventional missions: Packet Telemetry, Telemetry Channel Coding and Time Code Formats. The currently flying JPL spacecraft were designed prior to the adoption of these Recommendations. Future JPL missions will be compatible, as will the Deep Space Network and Space Flight Operations Center. This paper discusses ways in which application of the Recommendations causes or allows functions to be done differently from previous JPL projects, including the impact on timing and on telemetry adaptability.

Moyd, K. I.↗
NASA NTRS1992

Modeling and initialization of a segmented telescope

The closely integrated design effort entailed by such prospective NASA-JPL project hardware as the Large Deployable Reflector, encompassing controls, dynamics, structures, optics, and thermal considerations, has prompted the development of the Figure Control Simulation, or 'FCSim' simulation program. This code is presently demonstrated for the case of a 7-segment, 3.65-m diameter primary mirror designed for 100-800 micron wavelengths. The optical component of the analysis can handle multispectral images, extended sources, image smear due to structural jitter, and mirror segment surface irregularities.

Sirlin, Samuel W.↗
NASA NTRS2002

Quantitative software models for the estimation of cost, size, and defects

The presentation will provide a brief overview of the SQI measurement program as well as describe each of these models and how they are currently being used in supporting JPL project, task and software managers to estimate and plan future software systems and subsystems.

software metrics process improvement↗
NASA NTRS2004

JPL Facilities and Software for Collaborative Design: 1994 - Present

The viewgraph presentation provides an overview of the history of the JPL Project Design Center (PDC) and, since 2000, the Center for Space Mission Architecture and Design (CSMAD). The discussion includes PDC objectives and scope; mission design metrics; distributed design; a software architecture timeline; facility design principles; optimized design for group work; CSMAD plan view, facility design, and infrastructure; and distributed collaboration tools.

project design center↗
NASA NTRS2008

The Interim: Until You Achieve an Operationally Responsive Ground System

Everyone wants to achieve a 'Responsive' Ground Data System (GDS), but that takes time. What do you do in the interim? Our group, called the Integration, Test and Deployment Team (ITD), is a group of responsive engineers whose primary focus is to assist JPL projects to successfully adapt, test, integrate and deploy their ground data system. The team configures and adapts the GDS for a project, so that analysts, engineers and scientist do not need to be experts in the GDS to operate it. The team has developed a human interface to accommodate all types of users. It provides Graphical User Interfaces (GUI's) for those that want GUI's, command line interfaces for those that want control, and selection button interfaces for other users. The cornerstone of a responsive Ground Data System is responsive people. Without individuals who can be aware of a project's changing needs and requirements, how can the GDS become responsive?.

Ground Data System (GDS)↗
NASA NTRS2008

The Interim : until you achieve an operationally responsive ground system

Everyone wants to achieve a 'Responsive' Ground Data System (GDS), but that takes time. What do you do in the interim? Our group, called the Integration, Test and Deployment Team (ITD), is a group of responsive engineers whose primary focus is to assist JPL projects to successfully adapt, test, integrate and deploy their ground data system. The team configures and adapts the GDS for a project, so that analysts, engineers and scientist do not need to be experts in the GDS to operate it. The team has developed a human interface to accommodate all types of users. It provides Graphical User Interfaces (GUI's) for those that want GUI's, command line interfaces for those that want control, and selection button interfaces for other users. The cornerstone of a responsive Ground Data System is responsive people. Without individuals who can be aware of a project's changing needs and requirements, how can the GDS become responsive

ground data system (GDS)↗
NASA NTRS2011

The Use of Modeling for Flight Software Engineering on SMAP

The Soil Moisture Active Passive (SMAP) mission proposes to deploy an Earth-orbiting satellite with the goal of obtaining global maps of soil moisture content at regular intervals. Launch is currently planned in 2014. The spacecraft bus would be built at the Jet Propulsion Laboratory (JPL), incorporating both new avionics as well as hardware and software heritage from other JPL projects. [4] provides a comprehensive overview of the proposed mission

Software architecture↗
NASA NTRS2013

ISSM: Ice Sheet System Model

In order to have the capability to use satellite data from its own missions to inform future sea-level rise projections, JPL needed a full-fledged ice-sheet/iceshelf flow model, capable of modeling the mass balance of Antarctica and Greenland into the near future. ISSM was developed with such a goal in mind, as a massively parallelized, multi-purpose finite-element framework dedicated to ice-sheet modeling. ISSM features unstructured meshes (Tria in 2D, and Penta in 3D) along with corresponding finite elements for both types of meshes. Each finite element can carry out diagnostic, prognostic, transient, thermal 3D, surface, and bed slope simulations. Anisotropic meshing enables adaptation of meshes to a certain metric, and the 2D Shelfy-Stream, 3D Blatter/Pattyn, and 3D Full-Stokes formulations capture the bulk of the ice-flow physics. These elements can be coupled together, based on the Arlequin method, so that on a large scale model such as Antarctica, each type of finite element is used in the most efficient manner. For each finite element referenced above, ISSM implements an adjoint. This adjoint can be used to carry out model inversions of unknown model parameters, typically ice rheology and basal drag at the ice/bedrock interface, using a metric such as the observed InSAR surface velocity. This data assimilation capability is crucial to allow spinning up of ice flow models using available satellite data. ISSM relies on the PETSc library for its vectors, matrices, and solvers. This allows ISSM to run efficiently on any parallel platform, whether shared or distrib- ISSM: Ice Sheet System Model NASA's Jet Propulsion Laboratory, Pasadena, California uted. It can run on the largest clusters, and is fully scalable. This allows ISSM to tackle models the size of continents. ISSM is embedded into MATLAB and Python, both open scientific platforms. This improves its outreach within the science community. It is entirely written in C/C++, which gives it flexibility in its design, and the power/speed that C/C++ allows. ISSM is svn (subversion) hosted, on a JPL repository, to facilitate its development and maintenance. ISSM can also model propagation of rifts using contact mechanics and mesh splitting, and can interface to the Dakota software. To carry out sensitivity analysis, mesh partitioning algorithms are available, based on the Scotch, Chaco, and Metis partitioners that ensure equal area mesh partitions can be done, which are then usable for sampling and local reliability methods.

Larour, Eric↗
NASA NTRS2022

Adapting a Trusted AI Framework to Space Mission Autonomy

As artificial intelligence (AI) is increasingly pro- posed for new and future capabilities in space missions, the question of how to trust AI-enabled space autonomy has been explored. Recently, a collaboration between The Aerospace Corporation (Aerospace) and NASA’s Jet Propulsion Labora- tory (JPL) investigated how Aerospace’s Trusted AI Frame- work could be applied to two JPL projects that planned on lev- eraging AI for critical autonomous tasks. This combined effort led to many insights in the practical implementation of trusted AI along with considerable updates to the Trusted AI Frame- work that tailored its topic threads to space exploration. This document cohesively summarizes the enhanced framework as tailored to space missions as well as estimation of the level of trust required as a function of mission criticality and key stakeholders. The goal of this work is to provide a set of best practices to inform autonomy researchers, flight engineers, mission and proposal reviewers, and instrument and mission principal investigators (PI’s) to drive AI-based autonomy that maximizes trust and lowers the barriers to mission adoption for both science and engineering applications.

Amini, Rashied↗
NASA NTRS2003

Case Study of "Engineering Peer Meetings" in JPL's ST-6 Project

This design process error-proofing case study describes a design review practice implemented by a project manager at NASA Jet Propulsion Laboratory. There are many types of reviews at NASA: required and not, formalized and informal, programmatic and technical. Standing project formal reviews such as the Preliminary Design Review (PDR) and Critical Design Review (CDR) are a required part of every project and mission development. However, the engineering peer reviews that support teams technical work on such projects are often informal, ad hoc, and inconsistent across the organization. This case study discusses issues and innovations identified by a project manager at JPL and implemented in "engineering peer meetings" for his group.

Tumer, Irem Y.↗
NASA NTRS2004

Case Study of 'Engineering Peer Meetings' in JPL's ST-6 Project

This design process error-proofing case study describes a design review practice implemented by a project manager at NASA Jet Propulsion Laboratory. There are many types of reviews at NASA: required and not, formalized and informal, programmatic and technical. Standing project formal reviews such as the Preliminary Design Review (PDR) and Critical Design Review (CDR) are a required part of every project and mission development. However, the engineering peer reviews that support teams technical work on such projects are often informal, ad hoc, and inconsistent across the organization. This case study discusses issues and innovations identified by a project manager at JPL and implemented in 'engineering peer meetings' for his group.

Chao, Lawrence P.↗