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,081 records · Page 60

All sources NASA NTRS DOE OSTI

NASA NTRS2002

STS-112 Crew Interviews: Ashby

STS-112 Mission Commander Jeffrey Ashby is seen during this preflight interview, answering questions about his inspiration in becoming an astronaut and his career path and provides an overview of the mission. Ashby outlines his role in the mission in general, and specifically during the docking and extravehicular activities (EVAs). He describes the payload (S1 truss) and the importance that the S1 truss will have in the development of the International Space Station (ISS). Ashby discusses the delivery and installation of the S1 truss scheduled to be done in the planned EVAs in some detail. He touches on the use and operation of the Canadarm 2 robotic arm in this process and outlines what supplies will be exchanged with the resident crew of the ISS during transfer activities. He ends with his thoughts on the value of the ISS in fostering international cooperation.

Source record↗

NASA NTRS1992

Domain specific software architectures: Command and control

GTE is the Command and Control contractor for the Domain Specific Software Architectures program. The objective of this program is to develop and demonstrate an architecture-driven, component-based capability for the automated generation of command and control (C2) applications. Such a capability will significantly reduce the cost of C2 applications development and will lead to improved system quality and reliability through the use of proven architectures and components. A major focus of GTE's approach is the automated generation of application components in particular subdomains. Our initial work in this area has concentrated in the message handling subdomain; we have defined and prototyped an approach that can automate one of the most software-intensive parts of C2 systems development. This paper provides an overview of the GTE team's DSSA approach and then presents our work on automated support for message processing.

Braun, Christine↗

NASA NTRS2008

Situational Lightning Climatologies for Central Florida: Phase III

This report describes work done by the Applied Meteorology Unit (AMU) to add composite soundings to the Advanced Weather Interactive Processing System (AWIPS). This allows National Weather Service (NWS) forecasters to compare the current atmospheric state with climatology. In a previous phase, the AMU created composite soundings for four rawinsonde observation stations in Florida, for each of eight flow regimes. The composite soundings were delivered to the NWS Melbourne (MLB) office for display using the NSHARP software program. NWS MLB requested that the AMU make the composite soundings available for display in AWIPS. The AMU first created a procedure to customize AWIPS so composite soundings could be displayed. A unique four-character identifier was created for each of the 32 composite soundings. The AMU wrote a Tool Command Language/Tool Kit (TcVTk) software program to convert the composite soundings from NSHARP to Network Common Data Form (NetCDF) format. The NetCDF files were then displayable by AWIPS.

Barrett, Joe H., III↗

NASA NTRS2007

Cost-Benefit Analysis for Alternatives to Aliphatic Isocyanate Polyurethanes

NASA and Air Force Space Command (AFSPC) have similar missions and therefore similar facilities and structures in similar environments. The standard practice for protecting metallic substrates in atmospheric environments is the application of an applied coating system. The most common topcoats used in coating systems are polyurethanes that contain isocyanates. Isocyanates are classified as potential human carcinogens and are known to cause cancer in animals. The primary objective of this effort was to demonstrate and validate alternatives to aliphatic isocyanate polyurethanes resulting in one or more isocyanate-free coatings qualified for use at AFSPC and NASA installations participating in this project. This Cost-Benefit Analysis (CBA) quantifies the estimated capital and process costs of coating alternatives and cost savings relative to the current coatings. The estimates in this CBA are to be used for assessing the relative merits of the selected alternatives. The actual economic effects at any specific facility will depend on the alternative material or technology implemented, the number of actual applications converted, future workloads, and other factors . The participants initially considered eighteen (18) alternative coatings as described in the Potential Alternatives Report entitled Potential Alternatives Report for Validation of Alternatives to Aliphatic Isocyanate Polyurethanes, prepared by ITB. Of those, 8 alternatives were selected for testing in accordance with the Joint Test Protocol entitled Joint Test Protocol for Validation of Alternatives to Aliphatic Isocyanate Polyurethanes, and the Field Test Plan entitled Field Evaluations Test Plan for Validation of Alternatives 10 Aliphatic Isocyanate Polyurethanes, both of which were prepared by ITB. A joint Test Report entitled Joint Test Report for Validation of Alternatives to Aliphatic Isocyanate Polyurethanes, prepared by ITB, documents the results of the laboratory and field testing, as well as any test modifications made during the execution of the testing. The coatings selected for evaluation in this CBA are shown in the table below. Only one control coating system is considered in this analysis. These coatings were either downselected for Phase II or performed well enough to be included in the Qualified Products List in the NASA technical standard NASA-STD-5008, Protective Coating of Carbon Steel, Stainless Steel, and Aluminum on Launch Structures, Facilities, and Ground Support Equipment.

Lewis, Pattie↗

NASA NTRS2008

Displaying Composite and Archived Soundings in the Advanced Weather Interactive Processing System

This presentation describes work done by the Applied Meteorology Unit (AMU) to add composite soundings to the Advanced Weather Interactive Processing System (AWIPS). This allows National Weather Service (NWS) forecasters to compare the current atmospheric state with climatology. In a previous task, the AMU created composite soundings for four rawinsonde observation stations in Florida, for each of eight flow regimes. The composite soundings were delivered to the NWS Melbourne (MLB) office for display using the NSHARP software program. NWS MLB requested that the AMU make the composite soundings available for display in AWIPS. The AMU first created a procedure to customize AWIPS so composite soundings could be displayed. A unique four-character identifier was created for each of the 32 composite soundings. The AMIU wrote a Tool Command Language/Tool Kit (TclITk) software program to convert the composite soundings from NSHARP to Network Common Data Form (NetCDF) format. The NetCDF files were then displayable by AWIPS.

Barrett, Joe H., III↗

NASA NTRS2018

Imaging for Hypersonic Experimental Aeroheating Testing (IHEAT) Version 4.0: User Manual

The IHEAT v4.0 software is a data reduction code for global thermography data acquired in the NASA Langley Aerothermodynamics Laboratory (LAL) hypersonic wind tunnels. IHEAT uses red and green color-intensity data from two-dimensional images of wind tunnel models to compute temperatures and heat-transfer rates using a semi-infinite, one-dimensional heat transfer approximation at each image pixel. Multiple automated tools in IHEAT v4.0 decrease the time required to reduce the data from a phosphor thermography wind tunnel run. Data at one or all of the image pixel locations can be exported to computer files for further analysis. The prior version of IHEAT, v3.2, was written in PV-WAVE® (now owned by Rogue Wave® Software) in 1994 and was limited in functionality to fit within the memory constraints of the available computers at the time. IHEAT v4.0 is written in MATLAB® by MathWorks® and contains several new features that leverage the increase in available memory of the current computers. A Piecewise tool permits the user to extract data along a segmented line cut that can follow interesting features in the image better than the single, straight line cuts that were possible with the legacy Length and Profile tools. The new Load Run and Batch tools facilitate batch processing by loading in all of the input files and images for a run at the same time. Load Run permits the user to process the available run images manually, while Batch automatically saves heat transfer data from all of the images based on the analysis previously performed on a single frame. IHEAT v4.0 also can automatically calculate the temporal collapse of reference line cuts from the time history heating data for a run to indicate the appropriate frame to reduce for each run. The IHEAT v4.0 source code was compiled into a standalone executable file that can be accessed remotely from several computers with different operating systems, simultaneously. The software is run through the MATLAB® Compiler Runtime engine, and therefore, IHEAT does not require a software license to run. Any software commands executed in the IHEAT v4.0 code will not affect other similar applications running on the same machine. Similarly, changes to the parent software do not affect a compiled code. These features of IHEAT v4.0 are improvements over the legacy v3.2 code, which required regular maintenance to avoid losing functionality as the PVWAVE ® programming language was upgraded.

Mason, Michelle L.↗

NASA NTRS1991

A distributed Petri Net controller for a dual arm testbed

This thesis describes the design and functionality of a Distributed Petri Net Controller (DPNC). The controller runs under X Windows to provide a graphical interface. The DPNC allows users to distribute a Petri Net across several host computers linked together via a TCP/IP interface. A sub-net executes on each host, interacting with the other sub-nets by passing a token vector from host to host. One host has a command window which monitors and controls the distributed controller. The input to the DPNC is a net definition file generated by Great SPN. Thus, a net may be designed, analyzed and verified using this package before implementation. The net is distributed to the hosts by tagging transitions that are host-critical with the appropriate host number. The controller will then distribute the remaining places and transitions to the hosts by generating the local nets, the local marking vectors and the global marking vector. Each transition can have one or more preconditions which must be fulfilled before the transition can fire, as well as one or more post-processes to be executed after the transition fires. These implement the actual input/output to the environment (machines, signals, etc.). The DPNC may also be used to simulate a Great SPN net since stochastic and deterministic firing rates are implemented in the controller for timed transitions.

Bjanes, Atle↗

NASA NTRS1977

Digital control of high performance aircraft using adaptive estimation techniques

In this paper, an adaptive signal processing algorithm is joined with gain-scheduling for controlling the dynamics of high performance aircraft. A technique is presented for a reduced-order model (the longitudinal dynamics) of a high performance STOL aircraft. The actual controller views the nonlinear behavior of the aircraft as equivalent to a randomly switching sequence of linear models taken from a preliminary piecewise-linear fit of the system nonlinearities. The adaptive nature of the estimator is necessary to select the proper sequence of linear models along the flight trajectory. Nonlinear behavior is approximated by effective switching of the linear models at random times, with durations reflecting aircraft motion in response to pilot commands.

Van Landingham, H. F.↗

NASA NTRS1984

Pilot's Desk Flight Station

Aircraft flight station designs have generally evolved through the incorporation of improved or modernized controls and displays. In connection with a continuing increase in the amount of information displayed, this process has produced a complex and cluttered conglomeration of knobs, switches, and electromechanical displays. The result was often high crew workload, missed signals, and misinterpreted information. Advances in electronic technology have now, however, led to new concepts in flight station design. An American aerospace company in cooperation with NASA has utilized these concepts to develop a candidate conceptual design for a 1995 flight station. The obtained Pilot's Desk Flight Station is a unique design which resembles more an operator's console than today's cockpit. Attention is given to configuration, primary flight controllers, front panel displays, flight/navigation display, approach charts and weather display, head-up display, and voice command and response systems.

Sexton, G. A.↗

NASA NTRS1974

Human vs autonomous control of planetary roving vehicles

Supervisory or semiautonomous control has some compelling advantages over step-by-step human command and verification for the operation of roving vehicles on remote planetary surfaces. There are also disadvantages in relation to the complex system that must be mobilized and the chain of events that must be enacted to conduct a mission. Which of the two control methods is better on technical grounds may not be the deciding factor in its acceptance or rejection. Some of the issues that affect changes in spacecraft design and operation are summarized. To accelerate the movement toward more autonomous machines, it will be necessary to understand and to address the problems that such autonomy will create for other elements of the control system and for the control process.

Whitney, W. M.↗

NASA NTRS1993

International testing of a Mars rover prototype

Tests on a prototype engineering model of the Russian Mars 96 Rover were conducted by an international team in and near Death Valley in the United States in late May, 1992. These tests were part of a comprehensive design and testing program initiated by the three Russian groups responsible for the rover development. The specific objectives of the May tests were: (1) evaluate rover performance over different Mars-like terrains; (2) evaluate state-of-the-art teleoperation and autonomy development for Mars rover command, control and navigation; and (3) organize an international team to contribute expertise and capability on the rover development for the flight project. The range and performance that can be planned for the Mars mission is dependent on the degree of autonomy that will be possible to implement on the mission. Current plans are for limited autonomy, with Earth-based teleoperation for the nominal navigation system. Several types of television systems are being investigated for inclusion in the navigation system including panoramic camera, stereo, and framing cameras. The tests used each of these in teleoperation experiments. Experiments were included to consider use of such TV data in autonomy algorithms. Image processing and some aspects of closed-loop control software were also tested. A micro-rover was tested to help consider the value of such a device as a payload supplement to the main rover. The concept is for the micro-rover to serve like a mobile hand, with its own sensors including a television camera.

Kemurjian, Alexsandr Leonovich↗

NASA NTRS1994

An avionics scenario and command model description for Space Generic Open Avionics Architecture (SGOAA)

This paper presents a description of a model for a space vehicle operational scenario and the commands for avionics. This model will be used in developing a dynamic architecture simulation model using the Statemate CASE tool for validation of the Space Generic Open Avionics Architecture (SGOAA). The SGOAA has been proposed as an avionics architecture standard to NASA through its Strategic Avionics Technology Working Group (SATWG) and has been accepted by the Society of Automotive Engineers (SAE) for conversion into an SAE Avionics Standard. This architecture was developed for the Flight Data Systems Division (FDSD) of the NASA Johnson Space Center (JSC) by the Lockheed Engineering and Sciences Company (LESC), Houston, Texas. This SGOAA includes a generic system architecture for the entities in spacecraft avionics, a generic processing external and internal hardware architecture, and a nine class model of interfaces. The SGOAA is both scalable and recursive and can be applied to any hierarchical level of hardware/software processing systems.

Stovall, John R.↗

NASA NTRS1997

Wavelet Analyses of F/A-18 Aeroelastic and Aeroservoelastic Flight Test Data

Time-frequency signal representations combined with subspace identification methods were used to analyze aeroelastic flight data from the F/A-18 Systems Research Aircraft (SRA) and aeroservoelastic data from the F/A-18 High Alpha Research Vehicle (HARV). The F/A-18 SRA data were produced from a wingtip excitation system that generated linear frequency chirps and logarithmic sweeps. HARV data were acquired from digital Schroeder-phased and sinc pulse excitation signals to actuator commands. Nondilated continuous Morlet wavelets implemented as a filter bank were chosen for the time-frequency analysis to eliminate phase distortion as it occurs with sliding window discrete Fourier transform techniques. Wavelet coefficients were filtered to reduce effects of noise and nonlinear distortions identically in all inputs and outputs. Cleaned reconstructed time domain signals were used to compute improved transfer functions. Time and frequency domain subspace identification methods were applied to enhanced reconstructed time domain data and improved transfer functions, respectively. Time domain subspace performed poorly, even with the enhanced data, compared with frequency domain techniques. A frequency domain subspace method is shown to produce better results with the data processed using the Morlet time-frequency technique.

Martin J Brenner↗

NASA NTRS2005

STS-114: Discovery Mission Status Briefing (incl. Statement from Cmdr. Collins and Crew)

Commander Eileen Collins and crew briefly thanked everyone who worked hard to get the Shuttle back in space, and dedicated the mission to the Columbia crew as she bids their first "good night" to the Mission Control Room in Houston. Video continues with the Mission Status Briefing by Phil Engelauf, STS-114 Mission Operations Representative, and John Shannon, Manager of the Space Shuttle Operations and Integration. Phil noted that launching and ascent had gone extremely well, the crews and the flight control team performed well and the vehicle performed exceptionally as well. The launch is the beginning of a 12 day mission period. John details the tasks of the Engineering team processing the radar data taken during ascent and checking frame by frame the imagery from both on vehicle imagery and ground imagery. John further detailed the two debris event from ascent video clips of tile loss and an unidentified material falling off from the external tank; the release of TYVEK covers, and bird impact on the external tank nose cone. Tile shearing, tile damage, tile repair, landing gear door seals, repair capabilities, debris assessment, safety, inspections criteria, data acquisitions and data analysis were topics covered with the News media.

Source record↗

NASA NTRS2006

STS-121: Discovery End of Mission Crew Briefing

The crew of the STS-121 Discovery mission is shown during this end of mission briefing. The crewmembers consist of: Stephanie Wilson, mission specialist; Steve Lindsey, commander; Lisa Nowak, mission specialist; Piers Sellers, mission specialist; Mike Fossum, mission specialist; and Mark Kelly, pilot. The briefing opens with Commander Lindsey describing the two major objectives of this mission, which are to accomplish the rest of the return to flight objectives started by STS-114, and to increase the ISS crew to three. He expresses that these objectives were fulfilled. A question and answer period from the news media follows. Lisa Nowak talks about robotics and her experiences during her first flight. Stephanie Wilson also discusses robotics and gives her thoughts about spaceflight. Steve Lindsey discusses the flying qualities of STS-121, spacecraft landing, and weather conditions while in space. Mark Kelly was responsible for the undocking of the Shuttle from the International Space Station, and he elaborates on this process. Spacewalkers Piers Sellers and Mike Fossum discuss testing of the Orbiter Boom Sensor System (OBSS). This system will be used as a platform to make repairs to the Space Shuttle.

Source record↗

NASA NTRS2011

Ares I-X Range Safety Analyses Overview

Ares I-X was the first test flight of NASA's Constellation Program's Ares I Crew Launch Vehicle designed to provide manned access to low Earth orbit. As a one-time test flight, the Air Force's 45th Space Wing required a series of Range Safety analysis data products to be developed for the specified launch date and mission trajectory prior to granting flight approval on the Eastern Range. The range safety data package is required to ensure that the public, launch area, and launch complex personnel and resources are provided with an acceptable level of safety and that all aspects of prelaunch and launch operations adhere to applicable public laws. The analysis data products, defined in the Air Force Space Command Manual 91-710, Volume 2, consisted of a nominal trajectory, three sigma trajectory envelopes, stage impact footprints, acoustic intensity contours, trajectory turn angles resulting from potential vehicle malfunctions (including flight software failures), characterization of potential debris, and debris impact footprints. These data products were developed under the auspices of the Constellation's Program Launch Constellation Range Safety Panel and its Range Safety Trajectory Working Group with the intent of beginning the framework for the operational vehicle data products and providing programmatic review and oversight. A multi-center NASA team in conjunction with the 45th Space Wing, collaborated within the Trajectory Working Group forum to define the data product development processes, performed the analyses necessary to generate the data products, and performed independent verification and validation of the data products. This paper outlines the Range Safety data requirements and provides an overview of the processes established to develop both the data products and the individual analyses used to develop the data products, and it summarizes the results of the analyses required for the Ares I-X launch.

Starr, Brett R.↗

NASA NTRS2011

Ares I-X Range Safety Flight Envelope Analysis

Starr, Brett R.↗

NASA NTRSDate not supplied

Splashdown Visualization of Spent Stages

The state of the art for many Earth-to-orbit trajectory analysis toolsets used at NASA is somewhat dated in terms of the languages they are written in and their user interfaces. Many of these programs are written in languages like Fortran or C that are no longer considered modern in the technology industry, and are command-line based without any means of interpreting the data outputs. This presentation is meant to demonstrate a specific use case for a newly developed web app that visualizes the output data for one of these tools. Specifically, one key usage is to investigate and validate launches for notional multi-stage vehicle concepts to various non-standard high-inclination orbits. Some NASA requirements dictate that trajectories be designed such that no surviving debris lands closer than 200 nautical miles (nm) from foreign landmasses or 27 nm from the continental United States, therefore validating re-entry locations of spent stages is an integral part of the launch planning process. In addition, at programmatic levels it can prove insightful and clarifying for the decision-making process to enhance the technical results of numerical simulations with visualizations. The intent with this tool is to provide the mission analyst and program level management with an intuitive and clear grasp of key information on possible mission scenarios either departing from or arriving at Earth, and in the future, the moon or Mars as well. The software tool was developed with an agile development approach and utilizes the latest frameworks and technologies. The front end uses the React JavaScript library for making a state of the art frontend and a backend based on the Django Python framework for handling data using Python’s powerful and free scientific libraries. In addition, the CesiumJS open-source library is key for visualizing these end-to-end trajectories on a high-resolution Earth model. The presentation will demonstrate the current capability and tested use cases.

Jack Agolli↗