Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “COMMAND SYSTEM”

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 1,225 records · Page 68
All sourcesNASA NTRSDOE OSTI
DOE OSTI2020

SpackDev: Multi-Package Development with Spack

High Energy Physics (HEP) software environments often involve ~ hundreds of external packages and libraries, and similar numbers of experiment-specific, science-critical packages—many under continuous development. Managing coherent releases of the external software stack is challenging enough, but managing the highly-collaborative—and distributed—development of a large body of code against such a stack adds even more complexity and room for error. Spack is a popular Python-based package management tool with a specific focus on the needs of High Performance Computing (HPC) systems and system administrators whose strength is orchestrating the discrete download, build, testing, and installation of pre-packaged or tagged third-party software against similarly stable dependencies. As such it is becoming increasingly popular within HEP as that community makes increasing use of HPC facilities, and as efforts to develop future HPC systems utilize Spack to provide scientific software on those platforms. SpackDev is a system to facilitate the simultaneous development of interconnected sets of packages. Intended to handle packages without restriction to one internal build system, SpackDev is integrated with Spack as a command extension in order to leverage features such as dependency calculations and build system configuration, and is generally applicable outside HEP. We describe SpackDev’s features and development over the last two years, initial experience using SpackDev in the context of the LArSoft liquid argon detector toolkit, and work remaining before it can be considered a fully-functional multi-package build system for HEP experiments utilizing Spack.

Green, Chris↗
NASA NTRS2009

R4SA for Controlling Robots

The R4SA GUI mentioned in the immediately preceding article is a userfriendly interface for controlling one or more robot(s). This GUI makes it possible to perform meaningful real-time field experiments and research in robotics at an unmatched level of fidelity, within minutes of setup. It provides such powerful graphing modes as that of a digitizing oscilloscope that displays up to 250 variables at rates between 1 and 200 Hz. This GUI can be configured as multiple intuitive interfaces for acquisition of data, command, and control to enable rapid testing of subsystems or an entire robot system while simultaneously performing analysis of data. The R4SA software establishes an intuitive component-based design environment that can be easily reconfigured for any robotic platform by creating or editing setup configuration files. The R4SA GUI enables event-driven and conditional sequencing similar to those of Mars Exploration Rover (MER) operations. It has been certified as part of the MER ground support equipment and, therefore, is allowed to be utilized in conjunction with MER flight hardware. The R4SA GUI could also be adapted to use in embedded computing systems, other than that of the MER, for commanding and real-time analysis of data.

Aghazarian, Hrand↗
NASA NTRS2011

Project Report: Automatic Sequence Processor Software Analysis

The Mission Planning and Sequencing (MPS) element of Multi-Mission Ground System and Services (MGSS) provides space missions with multi-purpose software to plan spacecraft activities, sequence spacecraft commands, and then integrate these products and execute them on spacecraft. Jet Propulsion Laboratory (JPL) is currently is flying many missions. The processes for building, integrating, and testing the multi-mission uplink software need to be improved to meet the needs of the missions and the operations teams that command the spacecraft. The Multi-Mission Sequencing Team is responsible for collecting and processing the observations, experiments and engineering activities that are to be performed on a selected spacecraft. The collection of these activities is called a sequence and ultimately a sequence becomes a sequence of spacecraft commands. The operations teams check the sequence to make sure that no constraints are violated. The workflow process involves sending a program start command, which activates the Automatic Sequence Processor (ASP). The ASP is currently a file-based system that is comprised of scripts written in perl, c-shell and awk. Once this start process is complete, the system checks for errors and aborts if there are any; otherwise the system converts the commands to binary, and then sends the resultant information to be radiated to the spacecraft.

sequencing↗
NASA NTRS2022

How to Build a Rover: An Overview of the Mars 2020 Mission’s Vehicle System Testbed

While NASA’s Mars rover Perseverance continues to make groundbreaking achievements on the Red Planet, its twin is hard at work here on Earth. The Operational Perseverance Twin for the Integration of Mechanisms and Instruments Sent to Mars, or OPTIMISM, is the Mars 2020 Vehicle System Testbed (VSTB) rover operated by NASA Jet Propulsion Laboratory (JPL) in Pasadena, California. OPTIMISM’s home is the JPL Mars Yard; an outdoor field with red soil that simulates the terrain encountered by Perseverance. The VSTB is a full-scale engineering model of the flight rover, serving a number of functions to ensure mission operations can continue smoothly and on schedule. The VSTB possesses instrumentation, computers, mechanisms, cameras, and a Mobility subsystem that are nearly identical to its extraterrestrial twin. Its high fidelity allows the rover to be a highly effective tool to fully test system functionality and performance prior to commanding the flight rover. The early stages of building OPTIMISM began a few months prior to Perseverance departing JPL for Cape Canaveral, FL in early 2020. Electrical integration of the flight system avionics, and compatibility checkouts of the electrical ground support equipment ensured that the foundation of the electrical system was operational and in place. Next, the internal harnessing was installed and compatibility checks of the rover instrumentation and mechanisms were performed to confirm the system was prepared for full buildup. Finally, mechanical assembly of the rover chassis with its external components completed the integration of the system before it was moved to the Mars Yard for its initial phase of testing to perform verification & validation (V&V) of the Mobility subsystem requirements. By the time Perseverance landed at Jezero Crater in February 2021, the first phase of VSTB operations was underway. Surface guidance, navigation, and control (SGNC) testing for the Mobility subsystem ensured functionality and performance requirements were met for various capabilities such as visual odometry (VO), mapping, and automatic navigation (AutoNav). Subsequent integration of the robotic arm (RA) onto the VSTB enabled the V&V campaign for surface sampling operations (SSO) to commence. As the mission’s engineering operations (EO) have gotten underway, the VSTB has been utilized for an array of purposes including troubleshooting software anomalies, and performing dry-runs for first time activities (FTAs) prior to sending the commands to Perseverance. OPTIMISM will continue to serve mission critical functions as long as Perseverance is roving the Red Planet.

Rojas, Jose Trujillo↗
DOE OSTI2017

A Game Changer: Electrifying Remote Communities by Using Isolated Microgrids

Microgrids, as self-contained entities, are of increasing interest in modern electric grids. Microgrids provide a sustainable solution to aggregate distributed energy resources (DERs) [e.g., photovoltaics (PVs), wind turbines], energy storage, and loads in a localized manner, especially in distribution systems. As a controllable unit, a microgrid can manage and balance the source and load power inside it to ensure stable and reliable operation. Moreover, through coordination with upper-level control systems, it can be dispatched and respond to the control commands issued by the central controller in the distribution system-in other words, a system that is effectively a distribution management system (DMS).

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
DOE OSTI2015

QQACCT

batchacct provides convenient library and command-line access to batch system accounting data for GridEngine and SLURM schedulers. It can be used to perform queries useful for data analysis of the accounting data alone or for integrative analysis in the context of a larger query.

Jacobsen, Douglas↗
DOE OSTI2018

An Introduction to UNIX, Emacs, Latex, and Python

This document is designed to give a brief introduction to the UNIX Operating System, Emacs, Latex, and Python. Section 1 focuses on UNIX, and presents the basics of the file system, a variety of common commands, and a handful of slightly more in depth topics. Section 2 introduces Emacs and its somewhat unusual keyboard controls. In Section 3, the basics of creating a document in Latex are demonstrated. Finally, Section 4 provides the foundation needed to begin programming in Python.

97 MATHEMATICS AND COMPUTING↗
NASA NTRS1971

New Apollo lunar communications

Apollo lunar surface S band communications and TV systems and equipment, including ground commanded TV assembly

Sawyer, R. S.↗
NASA NTRS1971

Guidance system operations plan for manned cm earth orbital and lunar missions using program Colossus 3. Section 2: Data links

The data links for use with the guidance system operations plan for manned command module earth orbital and lunar missions using program Colossus 3 are presented. The subjects discussed are: (1) digital uplink to CMC, (2) command module contiguous block update, (3) CMC retrofire external data update, (4) CMC digital downlink, and (5) CMC entry update.

Hamilton, M. H.↗
NASA NTRS1975

Astronomy Spacelab payloads

Preliminary analyses of four typical Spacelab astronomy payloads have been completed. The payloads consist of instrumentation recommended by NASA and other scientists for early Shuttle missions. Design concepts have been prepared and compatibility with Shuttle and Spacelab verified. Mission parameters that meet payload requirements and efficiently utilize Shuttle resources have been selected. Integrated pointing and stabilization and command and data-handling system concepts have been developed. The results of all these activities indicate that productive astronomy missions can be carried out with Shuttle and Spacelab systems.

Ott, R.↗
NASA NTRS1977

Tracking and data system support for the Viking 1975 mission to Mars. Volume 3: Planetary operations

The support provided by the Deep Space Network to the 1975 Viking Mission from the first landing on Mars July 1976 to the end of the Prime Mission on November 15, 1976 is described and evaluated. Tracking and data acquisition support required the continuous operation of a worldwide network of tracking stations with 64-meter and 26-meter diameter antennas, together with a global communications system for the transfer of commands, telemetry, and radio metric data between the stations and the Network Operations Control Center in Pasadena, California. Performance of the deep-space communications links between Earth and Mars, and innovative new management techniques for operations and data handling are included.

Mudgway, D. J.↗
NASA NTRS1978

Tracking and data system support for the Viking 1975 mission to Mars: Extended mission operations, December 1976 to May 1978, volume 4

The support which was provided by the Deep Space Network to the Viking Extended Mission from December 1976 to May 1978 is described. Tracking and data acquisition support required the continuous operation of a world-wide network of tracking stations with 64-meter and 26-meter diameter antennas, together with a global communications system for the transfer of commands, telemetry, and radio metric data between the stations and the Network Operations Control Center in Pasadena, California. Performance of the deep-space communications links between Earth and Mars, and innovative new management techniques for operations and data handling are included.

Mudgway, D. J.↗
NASA NTRS1981

A model for the control mode man-computer interface dialogue

A four stage model is presented for the control mode man-computer interface dialogue. It consists of context development, semantic development syntactic development, and command execution. Each stage is discussed in terms of the operator skill levels (naive, novice, competent, and expert) and pertinent human factors issues. These issues are human problem solving, human memory, and schemata. The execution stage is discussed in terms of the operators typing skills. This model provides an understanding of the human process in command mode activity for computer systems and a foundation for relating system characteristics to operator characteristics.

Chafin, R. L.↗
NASA NTRS1982

Telecommunications and data acquisition systems support for the Viking 1975 mission to Mars, volume 5

The support provided by the Deep Space Network to the Viking Project from 1 June 1978 to 30 April 1980 is described. The project was supported by the worldwide network of Deep Space Stations with 26- and 64-meter-diameter antennas, together with a ground communications system, for the transmission of commands, telemetry, radio metric data, and operational instructions between the stations and the network operation control center in Pasadena, California. Assistance was substantially less than in the previous phases of the Viking Project in order to provide adequate support to the Pioneer and Voyager Projects.

Larkin, W. E.↗
NASA NTRS1983

Receiver for Antenna Arrays

Diversity reception system combines narrow-band signals from several antennas to yield amplified demodulated signal. System was developed for spacecraft command signals, which typically have bandwidths of few hundred hertz.

Brockman, M. H.↗
NASA NTRS1983

Development of the functional simulator for the Galileo attitude and articulation control system

A simulation program for verifying and checking the performance of the Galileo Spacecraft's Attitude and Articulation Control Subsystem's (AACS) flight software is discussed. The program, which is called Functional Simulator (FUNSIM), provides a simple method of interfacing user-supplied mathematical models coded in FORTRAN which describes spacecraft dynamics, sensors, and actuators; this is done with the AACS flight software, coded in HAL/S (High-level Advanced Language/Shuttle). It is thus able to simulate the AACS flight software accurately to the HAL/S statement level in the environment of a mainframe computer system. FUNSIM also has a command and data subsystem (CDS) simulator. It is noted that the input/output data and timing are simulated with the same precision as the flight microprocessor. FUNSIM uses a variable stepsize numerical integration algorithm complete with individual error bound control on the state variable to solve the equations of motion. The program has been designed to provide both line printer and matrix dot plotting of the variables requested in the run section and to provide error diagnostics.

Namiri, M. K.↗