SEARCH · Search NASA

Results for “command process”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 1,189 records · Page 66

All sources NASA NTRS DOE OSTI

DOE OSTI2025

Datum: A Scientific Metadata Catalog

The data catalog market is currently flooded with a myriad of different products, but none serve the scientific community well. There are cloud-native tools like Databricks, Snowflake,to on-premise solutions like Collibra and Datahub. The common failing of all these tools however, is their inability to serve the scientific data community directly. Most catalogs are targeted towards financial, health, or user data - not sensor or scientific domain data. They also prioritize integrations that often don’t exist or are just starting to be used in the scientific realm - all while ignoring common scientific tools and file types. Datum is a catalog which targets the scientific data directly, including the tools and networks in which those tools are used. We work with the producers and consumers of the data where they are, targeting cloud and on-premise with a focus on classified networks. Datum is an Erlang/Elixir application. Technical Features Note: The features listed below are still under development and may change, slightly, upon final delivery of the product. File Formats - Datum has the ability to read additional metadata and provides processing pipelines for the following file formats: Plain Text, PDF, LaTeX, HTML, Open Document Format (.odt), XML, CSV/TSV (and other standard delimiters), OpenDocument Database and Spreadsheets, Geo-Referenced TIFF, Common Data Format, HDF/HDF5, LabView TDMS, Excel, DeltaTables, Parquet, Apache Iceberg, Apache Hudi and many others. Metadata Collection - Scanners for the local and networked file systems and cloud storage providers. Network integration with common databases such as MSSQL and MySQL. User Plugin System - Users are able to provide either file processing, metadata extraction, or sampling plugins in the programming language of their choice. Authentication/Authorization -: OIDC integration, SCIM provisioning and EntraID integration out of the box. Full user and group management system with a “least privilege” operating mode. Governance - Customizable data governance platform; dictate and enforce required metadata, enforce data embargos, and enforce user agreements and NDAs before data access. Ability to create health checks on data, rejecting abandoned or poorly curated data and automatically removing it from the search index. Ability for users to submit corrections. Search - Semantic search is a first class citizen. No licenses to expensive, external software required. Integrated use of vectors and vector-based search allows for AI agent integration at all levels of operation. Metadata Model - Display and control data’s lineage and connections to other data and data directories. Data is modeled after a filesystem - an organization instantly recognizable and navigable by most any user. CLI and SDK - Ships with a Command Line Interface (CLI) tool and with a fully-featured Python SDK. This allows for rapid and programmatic use of Datum by every level of user. Minimal Infrastructure - Datum ships as a single executable file and can be run on any operating system and most CPU architectures. Datum has no reliance on external databases, search indexing tools, or other outside services - and it runs equally well on edge computing devices, cloud services, or in a clustered HPC environment.

darrington, john↗

NASA NTRS1998

STS-87 Mission Highlights Resources Tape

The STS-87 mission the flight crew, Commander Kevin R. Kregel, Pilot Steven W. Lindsey, Mission Specialists Winston E. Scott, Kalpana Chawla, and Takao Doi, and Payload Specialist Leonid K. Kadenyuk present an overview of there mission. STS-87 will fly the United States Microgravity Payload (USMP-4), the Spartan-201, the Orbital Acceleration Research Experiment (OARE), the EVA Demonstration Flight Test 5 (EDFT-05). The objective of the observations are to investigate the mechanisms causing the heating of the solar corona and the acceleration of the solar wind which originates in the corona. While flying separately in the cargo bay, the Orbital Acceleration Research Experiment (OARE) is an integral part of USMP-04. It is a highly sensitive instrument designed to acquire and record data of low-level aerodynamic acceleration along the orbiter's principal axes in the free-molecular flow regime at orbital altitudes and in the transition regime during re-entry. OARE data will support advances in space materials processing by providing measurements of the low-level, low frequency disturbance environment affecting various microgravity experiments. OARE data will also support advances in orbital drag prediction technology by increasing the understanding of the fundamental flow phenomena in the upper atmosphere.

Source record↗

NASA NTRS1994

Models of Human Information Requirements: "When Reasonable Aiding Systems Disagree"

Aircraft flight management and Air Traffic Control (ATC) automation are under development to maximize the economy of flight and to increase the capacity of the terminal area airspace while maintaining levels of flight safety equal to or better than current system performance. These goals are being realized by the introduction of flight management automation aiding and operations support systems on the flight deck and by new developments of ATC aiding systems that seek to optimize scheduling of aircraft while potentially reducing required separation and accounting for weather and wake vortex turbulence. Aiding systems on both the flight deck and the ground operate through algorithmic functions on models of the aircraft and of the airspace. These models may differ from each other as a result of variations in their models of the immediate environment. The resultant flight operations or ATC commands may differ in their response requirements (e.g. different preferred descent speeds or descent initiation points). The human operators in the system must then interact with the automation to reconcile differences and resolve conflicts. We have developed a model of human performance including cognitive functions (decision-making, rule-based reasoning, procedural interruption recovery and forgetting) that supports analysis of the information requirements for resolution of flight aiding and ATC conflicts. The model represents multiple individuals in the flight crew and in ATC. The model is supported in simulation on a Silicon Graphics' workstation using Allegro Lisp. Design guidelines for aviation automation aiding systems have been developed using the model's specification of information and team procedural requirements. Empirical data on flight deck operations from full-mission flight simulation are provided to support the model's predictions. The paper describes the model, its development and implementation, the simulation test of the model predictions, and the empirical validation process. The model and its supporting data provide a generalizable tool that is being expanded to include air/ground compatibility and ATC crew interactions in air traffic management.

Corker, Kevin↗

NASA NTRS2006

Solid Modeling of Crew Exploration Vehicle Structure Concepts for Mass Optimization

Parametric solid and surface models of the crew exploration vehicle (CEV) command module (CM) structure concepts are developed for rapid finite element analyses, structural sizing and estimation of optimal structural mass. The effects of the structural configuration and critical design parameters on the stress distribution are visualized, examined to arrive at an efficient design. The CM structural components consisted of the outer heat shield, inner pressurized crew cabin, ring bulkhead and spars. For this study only the internal cabin pressure load case is considered. Component stress, deflection, margins of safety and mass are used as design goodness criteria. The design scenario is explored by changing the component thickness parameters and materials until an acceptable design is achieved. Aluminum alloy, titanium alloy and an advanced composite material properties are considered for the stress analysis and the results are compared as a part of lessons learned and to build up a structural component sizing knowledge base for the future CEV technology support. This independent structural analysis and the design scenario based optimization process may also facilitate better CM structural definition and rapid prototyping.

Mukhopadhyay, Vivek↗

NASA NTRS2009

Case Study of Using High Performance Commercial Processors in a Space Environment

The purpose of the Space Shuttle Cockpit Avionics Upgrade project was to reduce crew workload and improve situational awareness. The upgrade was to augment the Shuttle avionics system with new hardware and software. A major success of this project was the validation of the hardware architecture and software design. This was significant because the project incorporated new technology and approaches for the development of human rated space software. An early version of this system was tested at the Johnson Space Center for one month by teams of astronauts. The results were positive, but NASA eventually cancelled the project towards the end of the development cycle. The goal to reduce crew workload and improve situational awareness resulted in the need for high performance Central Processing Units (CPUs). The choice of CPU selected was the PowerPC family, which is a reduced instruction set computer (RISC) known for its high performance. However, the requirement for radiation tolerance resulted in the reevaluation of the selected family member of the PowerPC line. Radiation testing revealed that the original selected processor (PowerPC 7400) was too soft to meet mission objectives and an effort was established to perform trade studies and performance testing to determine a feasible candidate. At that time, the PowerPC RAD750s where radiation tolerant, but did not meet the required performance needs of the project. Thus, the final solution was to select the PowerPC 7455. This processor did not have a radiation tolerant version, but faired better than the 7400 in the ability to detect failures. However, its cache tags did not provide parity and thus the project incorporated a software strategy to detect radiation failures. The strategy was to incorporate dual paths for software generating commands to the legacy Space Shuttle avionics to prevent failures due to the softness of the upgraded avionics.

Ferguson, Roscoe C.↗

NASA NTRS2014

NASA GRC UAS Project - Communications Modeling and Simulation Development Status

The integration of Unmanned Aircraft Systems (UAS) in the National Airspace represents new operational concepts required in civil aviation. These new concepts are evolving as the nation moves toward the Next Generation Air Transportation System (NextGen) under the leadership of the Joint Planning and Development Office (JPDO), and through ongoing work by the Federal Aviation Administration (FAA). The desire and ability to fly UAS in the National Air Space (NAS) in the near term has increased dramatically, and this multi-agency effort to develop and implement a national plan to successfully address the challenges of UAS access to the NAS in a safe and timely manner is well underway. As part of the effort to integrate UAS in the National Airspace, NASA Glenn Research Center is currently involved with providing research into Communications systems and Communication system operations in order to assist with developing requirements for this implementation. In order to provide data and information regarding communication systems performance that will be necessary, NASA GRC is tasked with developing and executing plans for simulations of candidate future UAS command and control communications, in line with architectures and communications technologies being developed and or proposed by NASA and relevant aviation organizations (in particular, RTCA SC-203). The simulations and related analyses will provide insight into the ability of proposed communications technologies and system architectures to enable safe operation of UAS, meeting UAS in the NAS project goals (including performance requirements, scalability, and interoperability), and ultimately leading to a determination of the ability of NextGen communication systems to accommodate UAS. This presentation, compiled by the NASA GRC Modeling and Simulation team, will provide an update to this ongoing effort at NASA GRC as follow-up to the overview of the planned simulation effort presented at ICNS in 2013. The objective of presentation will be to describe the progress made in developing both a NAS-Wide simulation architecture application and the detailed radiocomm system models for this research, and will present interim data and information compiled in the process of developing these simulation capabilities to date.

Modeling and Simulation↗

NASA NTRS2011

Ares I-X Range Safety Simulation and Analysis IV and V

NASA s Ares I-X vehicle launched on a suborbital test flight from the Eastern Range in Florida on October 28, 2009. NASA generated a Range Safety (RS) product data package to meet the RS trajectory data requirements defined in the Air Force Space Command Manual (AFSPCMAN) 91-710. Some products included were a nominal ascent trajectory, ascent flight envelopes, and malfunction turn data. These products are used by the Air Force s 45th Space Wing (45SW) to ensure public safety and to make flight termination decisions on launch day. Due to the criticality of the RS data, an independent validation and verification (IV&V) effort was undertaken to accompany the data generation analyses to ensure utmost data quality and correct adherence to requirements. As a result of the IV&V efforts, the RS product package was delivered with confidence that two independent organizations using separate simulation software generated data to meet the range requirements and yielded similar results. This document captures the Ares I-X RS product IV&V analysis, including the methodology used to verify inputs, simulation, and output data for certain RS products. Additionally a discussion of lessons learned is presented to capture advantages and disadvantages to the IV&V processes used.

Merry, Carl M.↗

NASA NTRS2014

Automating the SMAP Ground Data System to Support Lights-Out Operations

The Soil Moisture Active Passive (SMAP) Mission is a first tier mission in NASA's Earth Science Decadal Survey. SMAP will provide a global mapping of soil moisture and its freeze/thaw states. This mapping will be used to enhance the understanding of processes that link the terrestrial water, energy, and carbon cycles, and to enhance weather and forecast capabilities. NASA's Jet Propulsion Laboratory has been selected as the lead center for the development and operation of SMAP. The Jet Propulsion Laboratory (JPL) has an extensive history of successful deep space exploration. JPL missions have typically been large scale Class A missions with significant budget and staffing. SMAP represents a new area of JPL focus towards low cost Earth science missions. Success in this new area requires changes to the way that JPL has traditionally provided the Mission Operations System (MOS)/Ground Data System (GDS) functions. The operation of SMAP requires more routine operations activities and support for higher data rates and data volumes than have been achieved in the past. These activities must be addressed by a reduced operations team and support staff. To meet this challenge, the SMAP ground data system provides automation that will perform unattended operations, including automated commanding of the SMAP spacecraft.

GDS↗

NASA NTRS2016

Modeling in the State Flow Environment to Support Launch Vehicle Verification Testing for Mission and Fault Management Algorithms in the NASA Space Launch System

Analysis methods and testing processes are essential activities in the engineering development and verification of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS). Central to mission success is reliable verification of the Mission and Fault Management (M&FM) algorithms for the SLS launch vehicle (LV) flight software. This is particularly difficult because M&FM algorithms integrate and operate LV subsystems, which consist of diverse forms of hardware and software themselves, with equally diverse integration from the engineering disciplines of LV subsystems. M&FM operation of SLS requires a changing mix of LV automation. During pre-launch the LV is primarily operated by the Kennedy Space Center (KSC) Ground Systems Development and Operations (GSDO) organization with some LV automation of time-critical functions, and much more autonomous LV operations during ascent that have crucial interactions with the Orion crew capsule, its astronauts, and with mission controllers at the Johnson Space Center. M&FM algorithms must perform all nominal mission commanding via the flight computer to control LV states from pre-launch through disposal and also address failure conditions by initiating autonomous or commanded aborts (crew capsule escape from the failing LV), redundancy management of failing subsystems and components, and safing actions to reduce or prevent threats to ground systems and crew. To address the criticality of the verification testing of these algorithms, the NASA M&FM team has utilized the State Flow environment6 (SFE) with its existing Vehicle Management End-to-End Testbed (VMET) platform which also hosts vendor-supplied physics-based LV subsystem models. The human-derived M&FM algorithms are designed and vetted in Integrated Development Teams composed of design and development disciplines such as Systems Engineering, Flight Software (FSW), Safety and Mission Assurance (S&MA) and major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GN&C), Thrust Vector Control (TVC), liquid engines, and the astronaut crew office. Since the algorithms are realized using model-based engineering (MBE) methods from a hybrid of the Unified Modeling Language (UML) and Systems Modeling Language (SysML), SFE methods are a natural fit to provide an in depth analysis of the interactive behavior of these algorithms with the SLS LV subsystem models. For this, the M&FM algorithms and the SLS LV subsystem models are modeled using constructs provided by Matlab which also enables modeling of the accompanying interfaces providing greater flexibility for integrated testing and analysis, which helps forecast expected behavior in forward VMET integrated testing activities. In VMET, the M&FM algorithms are prototyped and implemented using the same C++ programming language and similar state machine architectural concepts used by the FSW group. Due to the interactive complexity of the algorithms, VMET testing thus far has verified all the individual M&FM subsystem algorithms with select subsystem vendor models but is steadily progressing to assessing the interactive behavior of these algorithms with LV subsystems, as represented by subsystem models. The novel SFE applications has proven to be useful for quick look analysis into early integrated system behavior and assessment of the M&FM algorithms with the modeled LV subsystems. This early MBE analysis generates vital insight into the integrated system behaviors, algorithm sensitivities, design issues, and has aided in the debugging of the M&FM algorithms well before full testing can begin in more expensive, higher fidelity but more arduous environments such as VMET, FSW testing, and the Systems Integration Lab7 (SIL). SFE has exhibited both expected and unexpected behaviors in nominal and off nominal test cases prior to full VMET testing. In many findings, these behavioral characteristics were used to correct the M&FM algorithms, enable better test coverage, and develop more effective test cases for each of the LV subsystems. This has improved the fidelity of testing and planning for the next generation of M&FM algorithms as the SLS program evolves from non-crewed to crewed flight, impacting subsystem configurations and the M&FM algorithms that control them. SFE analysis has improved robustness and reliability of the M&FM algorithms by revealing implementation errors and documentation inconsistencies. It is also improving planning efficiency for future VMET testing of the M&FM algorithms hosted in the LV flight computers, further reducing risk for the SLS launch infrastructure, the SLS LV, and most importantly the crew.

Trevino, Luis↗

NASA NTRSDate not supplied

Highlights of NASA’s Orbital Debris Program Office In Situ and Laboratory Measurements

NASA’s Orbital Debris Program Office (ODPO) maintains various returned spacecraft materials, capabilities, and facilities used for in situ and laboratory measurements that directly support orbital debris environmental models. In situ measurements include the analysis of exposed and returned hardware surfaces. These surfaces serve as passive sensors for the small-sized micrometeoroid and orbital debris (MMOD) flux below the sensitivity of ground-based radar and optical sensors. Various instruments and techniques are used to determine the size and depth of selected impact features, and – if feasible – the composition of the projectile material. Analysis of the impactor residues enables the differentiation of MM and OD for debris below 1 mm to support modeling the OD environment. In addition, projectiles identified as OD can be further differentiated in low-, medium-, and high- density impactors based on chemical analyses. In addition to in situ measurements, the ODPO has also worked in collaboration with the U.S. Space Force Space Systems Command (formerly the U.S. Air Force Space and Missile Systems Center), the Aerospace Corporation, and the University of Florida on a laboratory-based hypervelocity impact test, DebriSat, conducted at the Air Force Arnold Engineering Development Complex in 2014. The resulting data from this impact test series are being analyzed to assess the fragments’ sizes/masses, materials/densities, shapes, and other parameters of interest. The DebriSat project provides the data needed to update NASA’s breakup models and size estimation models using the simulated orbital breakup of a modern, low Earth orbit spacecraft. Ultimately, over 200,000 fragments from this impact test will be stored at NASA Johnson Space Center (JSC) and further analyzed by the ODPO. This project will also use machine learning techniques to infer physical parameters of fragments embedded in the soft-catch foam used in the impact experiment. Applied to X-ray imagery of the foam panels, these techniques promise to minimize human-in-the-loop processes for fragment extraction and physical characterization. A brief overview of this project and data collected will be presented. Lastly, the ODPO provides various capabilities hosted at NASA JSC for optical inspections and measurements using a variety of techniques and scientific instrumentation to support both in situ and laboratory measurements. The ODPO’s Optical Measurement Center (OMC) is an advanced facility for photometric and spectroscopic laboratory measurements of targets, including fragments from the DebriSat project. The OMC simulates telescopic observations by using space-like illumination conditions and source-target-sensor orientation techniques. Additionally, the OMC is uniquely equipped to acquire pseudo-bidirectional reflectance distribution data for broadband photometric measurements, thus removing aspect angle dependencies that can affect target size estimates using the optical size estimation model. Narrow-band surface material characterization using spectroscopic instrumentation gives insight into how the albedo parameter – also important in the optical size estimation model – may vary depending on the state of the material. The OMC also performs simulations of photometric measurements using optical ray-tracing software to model the OMC optical throughput. In addition to the OMC, the ODPO houses a start-of-the-art Fragment Analysis Facility that uses multiple microscopic inspection instruments to support in situ measurements and material characterization. An overview of both facilities will be highlighted in this paper.

Orbital Debris↗

NASA NTRSDate not supplied

Highlights of NASA’s Orbital Debris Program Office In Situ and Laboratory Measurements

Orbital Debris↗

NASA NTRS2008

Mars Interoperability 2008-2015: Options for Relay Orbiter Support to Mars Bound Assets

The current relay orbiter infrastructure at Mars, in support of the user assets presently at Mars and those scheduled for the 2008 to 2015 time frame, only have a need to store-and-forward the returned data collected by an asset to Earth as a single non-prioritized data file. In the forward direction, the relay orbiters are only required to relay the forward link data, i.e., command sequences, software and configuration information assembled on the ground, to the Asset. There are currently no requirements for status/control messages or files to be sent in the return direction from an Asset to an application located on the Relay, nor are there requirements in the forward direction to send status/control messages or files originating on a Relay to an Asset. In addition there are currently no networking requirements at Mars where data originally sent by an Asset is to be delivered to another user asset. However, we foresee the day when standard services for 1) on-board file prioritization of user asset data by a Relay, 2) control/status message transfer between assets and a Relay, and 3) networking between assets i.e., Asset to Asset message/file transfer via a Relay will be required. Each of these services will require the Relay to be capable of understanding the data type and routing needs of the user asset data and be capable of processing it for these purposes. This paper will focus on the innovative enhancements required to the existing communications infrastructure at Mars to enable these future services.

File Transfer↗

NASA NTRS2018

Nasa's Launch Communications Ground Segment for the 21st Century Florida Spaceport

The National Aeronautics and Space Administration (NASA) Near Earth Network (NEN) Project is implementing a new launch communications ground segment to provide services for the next generation of human and robotic space exploration systems. It will deliver unique and advanced capabilities to accelerate the transformation of Kennedy Space Center into a multi-user spaceport in cooperation with the United States Air Force (USAF). The project has leveraged commercial technologies and remote operations concepts matured in NASAs orbiting satellite ground systems to achieve dramatic lifecycle cost efficiencies as compared to the space shuttle-era ground segment. The purpose of this paper is to discuss the development history, capabilities and anticipated use cases of the NEN Launch Communications Segment (NEN LCS).The NASA Kennedy Space Center is co-located with the USAF Eastern Launch Range at Cape Canaveral, Florida. The USAF operates two launch communications ground stations, but they are not designed to transmit voice, commands or other data to the launch vehicle or astronauts. The bi-directional uplink-downlink communications responsibility for human missions has historically resided with the Goddard Space Flight Center in Greenbelt, Maryland. Several market analyses and feasibility studies investigating concepts to provide NASAs next generation launch communications services were performed during the Constellation Program prior to its cancellation in 2009, and as part of the Kennedy Space Centers follow-on efforts to transform itself into a 21st century multi-user spaceport. In 2012, the Kennedy Space Center and the USAF 45th Space Wing jointly led a study to analyze the market needs of current and future launch systems and assess the operational deficiencies of the Eastern Range infrastructure. The study team issued several recommendations, two of which ultimately became driving operational capability requirements for the NEN LCS: increased telemetry data rates of at least 20 Mbps, and S-band uplink capability. Additional capabilities identified in the requirements development process include spread spectrum modulation support, LDPC 12 and 78 error correction codes, support for IRIG-106 and CCSDS data formats, automated best source selection, and Space Link Extension (SLE) services for data distribution. The NEN LCS is comprised of two permanent ground stations, the new Kennedy Uplink Station (KUS) and refurbished Ponce de Leon (PDL) station. Both stations are remotely operated from the Global Monitor and Control Center at Wallops Flight Facility. This core architecture is extensible through host-tenant arrangements with the U.S. Air Force and deployable assets, enabling agile, tailored and robust solutions to meet the needs of civil, commercial or military customers. The NEN LCS has three use cases:1.To provide agile, tailored and robust launch communications solutions to Florida spaceport customers2.To provide orbital communications services to near-earth customers 3.To provide an experimental proving ground for Space Mobile Network concepts and technologies The NEN LCS driving mission is to support the bi-directional link with the Orion crew capsule and two 20 Mbps telemetry links from the Space Launch System core stage on Exploration Mission-1, the first integrated flight of NASAs flagship human exploration systems.

Roberts, Christopher J.↗

NASA NTRS2012

Cost-Effective Telemetry and Command Ground Systems Automation Strategy for the Soil Moisture Active Passive (SMAP) Mission

Soil Moisture Active Passive (SMAP) is an Earth-orbiting, remote-sensing NASA mission slated for launch in 2014.[double dagger] The ground data system (GDS) being developed for SMAP is composed of many heterogeneous subsystems, ranging from those that support planning and sequencing to those used for real-time operations, and even further to those that enable science data exchange. A full end-to-end automation of the GDS may result in cost savings during mission operations, but it would require a significant upfront investment to develop such comprehensive automation. As demonstrated by the Jason-1 and Wide-field Infrared Survey Explorer (WISE) missions, a measure of "lights-out" automation for routine, orbital pass ground operations can still reduce mission cost through smaller staffing of operators and limited work hours. The challenge, then, for the SMAP GDS engineering team is to formulate an automated operations strategy--and corresponding system architecture--to minimize operator intervention during operations, while balancing the development cost associated with the scope and complexity of automation. This paper discusses the automated operations approach being developed for the SMAP GDS. The focus is on automating the activities involved in routine passes, which limits the scope to real-time operations. A key subsystem of the SMAP GDS--NASA's AMMOS Mission Data Processing and Control System (AMPCS)--provides a set of capabilities that enable such automation. Also discussed are the lights-out pass automations of the Jason-1 and WISE missions and how they informed the automation strategy for SMAP. The paper aims to provide insights into what is necessary in automating the GDS operations for Earth satellite missions.

remote-sensing↗

NASA NTRS2012

Cost-Effective Telemetry and Command Ground Systems Automation Strategy for the Soil Moisture Active Passive (SMAP) Mission

Soil Moisture Active Passive (SMAP) is an Earth-orbiting, remote-sensing NASA mission slated for launch in 2014. The ground data system (GDS) being developed for SMAP is composed of many heterogeneous subsystems, ranging from those that support planning and sequencing to those used for real-time operations, and even further to those that enable science data exchange. A full end-to-end automation of the GDS may result in cost savings during mission operations, but it would require a significant upfront investment to develop such a comprehensive automation. As demonstrated by the Jason-1 and Wide-field Infrared Survey Explorer (WISE) missions, a measure of "lights-out" automation for routine, orbital pass, ground operations can still reduce mission costs through smaller staffing of operators and limiting their working hours. The challenge, then, for the SMAP GDS engineering team, is to formulate an automated operations strategy--and corresponding system architecture -- to minimize operator intervention during routine operations, while balancing the development costs associated with the scope and complexity of automation. This paper discusses the automated operations approach being developed for the SMAP GDS. The focus is on automating the activities involved in routine passes, which limits the scope to real-time operations. A key subsystem of the SMAP GDS -- NASA's AMMOS Mission Data Processing and Control System (AMPCS) -- provides a set of capabilities that enable such automation. Also discussed are the lights-out pass automations of the Jason-1 and WISE missions and how they informed the automation strategy for SMAP. The paper aims to provide insights into what is necessary in automating the GDS operations for Earth satellite missions.

soil moisture↗

NASA NTRS1992

Situation awareness in command and control settings

Many military and civilian operational settings are described as command and control (C2) environments characterized by high information load, extensive team coordination, and communication demands. To address these problems, designers have turned to the application of automation and decision aids. Currently, there are few techniques for assessing the performance of C2 operators with which to guide applications. A need exists for constructs on which to evaluate C2 systems. One possible concept for addressing these issues is that of Situation Awareness (SA). The SA concept and methodologies have developed largely around the cockpit environment. The extension is discussed of the SA concept to a team context related to C2 environments. Then the implications of such an approach for developing a methodology to empirically measure team SA in a C2 environment which should allow for the assessment of SA of both individual operators and overall SA of operational teams. The discussion also focuses on how a knowledge of SA may impact the design and development of systems which optimize rather than maximize information access and processing and, subsequently, improve C2 decision making.

Patterson, Robert W.↗

DOE OSTI2025

Rotary Inertia Friction Welding of Dissimilar High-Strength 422 Martensitic Stainless Steel and 4140 Low Alloy Steel for Heavy-Duty Engine Piston Fabrication

AISI 422 martensitic stainless steel with superior high temperature performance (oxidation resistance and strength) is under evaluation for replacing current heavy-duty piston crown materials, AISI 4140 martensitic steel and micro alloyed steel (MAS) 38MnSiVS5, to fabricate a multimaterial piston. This multimaterial piston concept further improved power density and fuel economy by allowing heavyduty diesel engines to operate at higher temperatures and pressures. Joining AISI 422 steel piston crowns with AISI 4140 steel piston skirts is a key manufacturing step for this multimaterial piston. However, the significant differences in strength, elevated temperature flow stress, alloy chemistry, and temper resistance between these two martensitic steels cause some weldability issues (cracking) and metallurgical challenges (alloying element migration/segregation) when using conventional fusion-based welding processes. Rotary inertia friction welding (RIFW), a solid-state welding process, has been the preferred method to join 4140 crowns to 4140 skirts (and MAS crowns to MAS skirts) in high-volume production of current heavy-duty diesel engine pistons. It has been used to join these two materials with relatively comparable alloy chemistry to fabricate pistons with MAS skirts and 4140 crowns. Meanwhile, RIFW has also been a preferred method of dissimilar metal welding. However, RIFW of dissimilar high-strength martensitic steels has yet to be widely pursued. The interfacial microstructure complexities created by the thermomechanical process and highly nonequilibrium phase transformations during RIFW are a significant challenge for understanding and predicting their joining behavior and have not been reported in detail. Here, in this work, defect-free AISI 422 steel-AISI 4140 multimaterial pistons were successfully fabricated using the RIFW process. The interfacial microstructure and mechanical properties of dissimilar 422/4140 steel RIFW in the as-welded condition were experimentally studied in detail. The results provide critical baseline information for understanding RIFW mechanisms and guiding subsequent postweld heat treatment (PWHT) practice.

36 MATERIALS SCIENCE↗

NASA NTRS2007

SPARTAN: A High-Fidelity Simulation for Automated Rendezvous and Docking Applications

bd Systems (a subsidiary of SAIC) has developed the Simulation Package for Autonomous Rendezvous Test and ANalysis (SPARTAN), a high-fidelity on-orbit simulation featuring multiple six-degree-of-freedom (6DOF) vehicles. SPARTAN has been developed in a modular fashion in Matlab/Simulink to test next-generation automated rendezvous and docking guidance, navigation,and control algorithms for NASA's new Vision for Space Exploration. SPARTAN includes autonomous state-based mission manager algorithms responsible for sequencing the vehicle through various flight phases based on on-board sensor inputs and closed-loop guidance algorithms, including Lambert transfers, Clohessy-Wiltshire maneuvers, and glideslope approaches The guidance commands are implemented using an integrated translation and attitude control system to provide 6DOF control of each vehicle in the simulation. SPARTAN also includes high-fidelity representations of a variety of absolute and relative navigation sensors that maybe used for NASA missions, including radio frequency, lidar, and video-based rendezvous sensors. Proprietary navigation sensor fusion algorithms have been developed that allow the integration of these sensor measurements through an extended Kalman filter framework to create a single optimal estimate of the relative state of the vehicles. SPARTAN provides capability for Monte Carlo dispersion analysis, allowing for rigorous evaluation of the performance of the complete proposed AR&D system, including software, sensors, and mechanisms. SPARTAN also supports hardware-in-the-loop testing through conversion of the algorithms to C code using Real-Time Workshop in order to be hosted in a mission computer engineering development unit running an embedded real-time operating system. SPARTAN also contains both runtime TCP/IP socket interface and post-processing compatibility with bdStudio, a visualization tool developed by bd Systems, allowing for intuitive evaluation of simulation results. A description of the SPARTAN architecture and capabilities is provided, along with details on the models and algorithms utilized and results from representative missions.

Turbe, Michael A.↗