Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “COMMAND MODULE”

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 631 records · Page 35

SIERRA/Aero Theory Manual - Version 5.8

SIERRA/Aero is a compressible fluid dynamics program intended to solve a wide variety compressible fluid flows including transonic and hypersonic problems. This document describes the commands for assembling a fluid model for analysis with this module, henceforth referred to simply as Aero for brevity. Aero is an application developed using the SIERRA Toolkit (STK). The intent of STK is to provide a set of tools for handling common tasks that programmers encounter when developing a code for numerical simulation. For example, components of STK provide field allocation and management, and parallel input/output of field and mesh data. These services also allow the development of coupled mechanics analysis software for a massively parallel computing environment.

71 CLASSICAL AND QUANTUM MECHANICS, GENERAL PHYSIC↗

SIERRA/Aero User Manual (V.5.10)

SIERRA/Aero is a compressible fluid dynamics program intended to solve a wide variety compressible fluid flows including transonic and hypersonic problems. This document describes the commands for assembling a fluid model for analysis with this module, henceforth referred to simply as Aero for brevity. Aero is an application developed using the SIERRA Toolkit (STK). The intent of STK is to provide a set of tools for handling common tasks that programmers encounter when developing a code for numerical simulation. For example, components of STK provide field allocation and management, and parallel input/output of field and mesh data. These services also allow the development of coupled mechanics analysis software for a massively parallel computing environment.

97 MATHEMATICS AND COMPUTING↗

SIERRA/Aero Theory Manual - V.5.10

SIERRA/Aero is a compressible fluid dynamics program intended to solve a wide variety compressible fluid flows including transonic and hypersonic problems. This document describes the commands for assembling a fluid model for analysis with this module, henceforth referred to simply as Aero for brevity. Aero is an application developed using the SIERRA Toolkit (STK). The intent of STK is to provide a set of tools for handling common tasks that programmers encounter when developing a code for numerical simulation. For example, components of STK provide field allocation and management, and parallel input/output of field and mesh data. These services also allow the development of coupled mechanics analysis software for a massively parallel computing environment.

42 ENGINEERING↗

Deep Space Telecommunications Systems Engineering

Descriptive and analytical information useful for the optimal design, specification, and performance evaluation of deep space telecommunications systems is presented. Telemetry, tracking, and command systems, receiver design, spacecraft antennas, frequency selection, interference, and modulation techniques are addressed.

Yuen, J. H.↗

Deep space telecommunication systems engineering

Descriptive and analytical information useful for the optimal design, specification, and performance evaluation of deep space telecommunications systems is presented. Telemetry, tracking, and command systems, receiver design, spacecraft antennas, frequency selection, interference, and modulation techniques are addressed. Previously announced in STAR as N83-22226

Yuen, J. H.↗

STS-102 Crew Activity Report/Flight Day 7 Highlights

Footage shows STS-102 Mission Specialist Andy Thomas, Expedition 1 crewmember Sergei Krikalev, and Expedition 2 crewmember Susan Helms transferring supplies from the Leonardo Module to the International Space Station (ISS). Then STS-102 Commander Jim Wetherbee joins the crew of Expedition 2 (James Voss, Susan Helms, and Yuriy Usachev) for an on-orbit interview, where they answer questions about the spacewalks performed by Voss and Helms and about living on the ISS.

Source record↗

STS-100 Crew Activity Report: Flight Day 8 Highlights

On this eighth day of the STS-100 Endeavour mission, Mission Specialists Chris Hadfield and Scott Parazynski are seen preparing for and performing their spacewalks as they check the connections between the Destiny Laboratory Module and the Canadian Robotic Arm, remove an early communications antenna from the Unity Module, and confirm power connections for the Canadian Robotic Arm. Commander Kent Rominger is seen during a workout on Endeavour's ergometer.

Source record↗

Electromagnetic Interference Assessment of CDMA and GSM Wireless Phones to Aircraft Navigation Radios

To address the concern for cellular phone electromagnetic interference (EMI) to aircraft radios, a radiated emission measurement process for CDMA (IS-95) and GSM (ETSI GSM 11.22) wireless handsets was developed. Spurious radiated emissions were efficiently characterized from devices tested in either a semi-anechoic or reverberation chamber, in terms of effective isotropic radiated power. Eight representative handsets (4 GSM, 4 CDMA) were commanded to operate while varying their radio transmitter parameters (power, modulation, etc.). This report provides a detailed description of the measurement process and resulting data, which may subsequently be used by others as a basis of consistent evaluation for cellular/PCS phones, Bluetooth, IEEE802.11b, IEEE802.11a, FRS/GMRS radios, and other portable transmitters. Aircraft interference path loss (IPL) and navigation radio interference threshold data from numerous reference documents, standards, and NASA partnerships were compiled. Using this data, a preliminary risk assessment is provided for CDMA and GSM wireless phone interference to aircraft localizer, Glideslope, VOR, and GPS radio receivers on typical transport airplanes. The report identifies where existing data for device emissions, IPL, and navigation radio interference thresholds needs to be extended for an accurate risk assessment for wireless transmitters in aircraft.

Ely, Jay J.↗

Wireless Phone Threat Assessment and New Wireless Technology Concerns for Aircraft Navigation Radios

To address the concern for cellular phone electromagnetic interference to aircraft radios, a radiated emission measurement process was developed for two dominant digital standards of wireless handsets. Spurious radiated emissions were efficiently characterized from devices tested in either a semi-anechoic or reverberation chamber, in terms of effective radiated power. Eight representative handsets (four from each digital standard) were commanded to operate while varying their radio transmitter parameters (power, modulation, etc.). This report provides a detailed description of the measurement process and resulting data, which may subsequently be used by others as a basis of consistent evaluation of other portable transmitters using a variety of wireless transmission protocols. Aircraft interference path loss and navigation radio interference threshold data from numerous reference documents, standards, and NASA partnerships were compiled. Using these data, a preliminary risk assessment is provided for wireless phone interference to aircraft Localizer, Glideslope, Very High Frequency Omni directional Range, and Global Positioning Satellite radio receivers on typical transport airplanes. The report identifies where existing data for device emissions, interference path loss, and navigation radio interference thresholds need to be extended for an accurate risk assessment for wireless transmitters in aircraft.

Ely, Jay J.↗

DSN Beowulf Cluster-Based VLBI Correlator

The NASA Deep Space Network (DSN) requires a broadband VLBI (very long baseline interferometry) correlator to process data routinely taken as part of the VLBI source Catalogue Maintenance and Enhancement task (CAT M&E) and the Time and Earth Motion Precision Observations task (TEMPO). The data provided by these measurements are a crucial ingredient in the formation of precision deep-space navigation models. In addition, a VLBI correlator is needed to provide support for other VLBI related activities for both internal and external customers. The JPL VLBI Correlator (JVC) was designed, developed, and delivered to the DSN as a successor to the legacy Block II Correlator. The JVC is a full-capability VLBI correlator that uses software processes running on multiple computers to cross-correlate two-antenna broadband noise data. Components of this new system (see Figure 1) consist of Linux PCs integrated into a Beowulf Cluster, an existing Mark5 data storage system, a RAID array, an existing software correlator package (SoftC) originally developed for Delta DOR Navigation processing, and various custom- developed software processes and scripts. Parallel processing on the JVC is achieved by assigning slave nodes of the Beowulf cluster to process separate scans in parallel until all scans have been processed. Due to the single stream sequential playback of the Mark5 data, some ramp-up time is required before all nodes can have access to required scan data. Core functions of each processing step are accomplished using optimized C programs. The coordination and execution of these programs across the cluster is accomplished using Pearl scripts, PostgreSQL commands, and a handful of miscellaneous system utilities. Mark5 data modules are loaded on Mark5 Data systems playback units, one per station. Data processing is started when the operator scans the Mark5 systems and runs a script that reads various configuration files and then creates an experiment-dependent status database used to delegate parallel tasks between nodes and storage areas (see Figure 2). This script forks into three processes: extract, translate, and correlate. Each of these processes iterates on available scan data and updates the status database as the work for each scan is completed. The extract process coordinates and monitors the transfer of data from each of the Mark5s to the Beowulf RAID storage systems. The translate process monitors and executes the data conversion processes on available scan files, and writes the translated files to the slave nodes. The correlate process monitors the execution of SoftC correlation processes on the slave nodes for scans that have completed translation. A comparison of the JVC and the legacy Block II correlator outputs reveals they are well within a formal error, and that the data are comparable with respect to their use in flight navigation. The processing speed of the JVC is improved over the Block II correlator by a factor of 4, largely due to the elimination of the reel-to-reel tape drives used in the Block II correlator.

Rogstad, Stephen P.↗

Space vehicle with customizable payload and docking station

A "black box" space vehicle solution may allow a payload developer to define the mission space and provide mission hardware within a predetermined volume and with predetermined connectivity. Components such as the power module, radios and boards, attitude determination and control system (ADCS), command and data handling (C&DH), etc. may all be provided as part of a "stock" (i.e., core) space vehicle. The payload provided by the payload developer may be plugged into the space vehicle payload section, tested, and launched without custom development of core space vehicle components by the payload developer. A docking station may facilitate convenient development and testing of the space vehicle while reducing handling thereof.

33 ADVANCED PROPULSION SYSTEMS↗

Space vehicle with customizable payload and docking station

A “black box” space vehicle solution may allow a payload developer to define the mission space and provide mission hardware within a predetermined volume and with predetermined connectivity. Components such as the power module, radios and boards, attitude determination and control system (ADCS), command and data handling (C&DH), etc. may all be provided as part of a “stock” (i.e., core) space vehicle. The payload provided by the payload developer may be plugged into the space vehicle payload section, tested, and launched without custom development of core space vehicle components by the payload developer. A docking station may facilitate convenient development and testing of the space vehicle while reducing handling thereof.

Judd, Stephen↗

Making or Breaking a Rover: System Engineering Parameters On-Board the Mars 2020 Perseverance Rover

On February 18, 2021, Perseverance, NASA’s Jet Propulsion Laboratory’s (JPL’s) Mars 2020 Rover, successfully landed on Mars with all systems nominal, despite the risk surrounding the over 200,000 internal flight parameters that had to be properly configured. The Perseverance team defines these parameters as software variables that are configurable, commandable and retrievable from Earth. In 2015, the Mars 2020 project leaders focused on improving systems engineering of parameters based on their experiences from parameter management on previous Mars rovers (Curiosity, Opportunity, Spirit, and Pathfinder) and parameter failures of past missions, such as the mission-ending parameter of the Mars Climate Orbiter. The new rigorous development process allowed for efficient certification and effective implementation of the parameters, allowing the rover to approach and land on the red planet (the most challenging phase of the mission) with zero parameter issues. Although successful, the Perseverance team learned many lessons for how to better manage parameters for the continued surface operations of the Mars 2020 mission and future missions. This paper will discuss eight parameter-management topics for the Perseverance Mission. The first is parameter definition: how we define parameters on our mission, where they are physically located on the vehicle, and why we have so many of them. The second topic is the updated parameter flight software module from Curiosity, including details on the 99% reduction in parameter commands, new bulk configuration capabilities, and improved parameter traceability. The third topic is parameter selection for different mission phases; this includes improving and tweaking our preferred parameter settings until they become certification candidates and managing parameter configurations based on test venue throughout the mission life cycle. The fourth topic is our flight certification process; this includes certification of flight values for four different epochs in the mission: Launch, Entry Decent and Landing (EDL) - 6days, Landing + 5 Sols (Martian Days, still on Cruise Flight Software), and once are on Surface Flight Software (FSW). The fifth topic covers in-flight command implementation, along with details on testing, validation, and verification of those commands. In the sixth section, we will explain our use of open-source management tools, including how we used GitHub for version control and management approvals. The seventh topic will describe the ground tools used in operations, including capabilities of the in-house built tool called Parasol. The eighth and final topic will dig into lessons learned for improving parameter management in the future of this mission and others.

Roth, Brian↗

Making or Breaking a Rover- Systems Engineering Parameters On-Board the Mars 2020 Perseverance Rover

On February 18, 2021, Perseverance, NASA’s Jet Propulsion Laboratory’s (JPL’s) Mars 2020 Rover, successfully landed on Mars with all systems nominal, despite the risk surrounding the over 200,000 internal flight parameters that had to be properly configured. The Perseverance team defines these parameters as software variables that are configurable, commandable and retrievable from Earth. In 2015, the Mars 2020 project leaders focused on improving systems engineering of parameters based on their experiences from parameter management on previous Mars rovers (Curiosity, Opportunity, Spirit, and Pathfinder) and parameter failures of past missions, such as the mission-ending parameter of the Mars Climate Orbiter. The new rigorous development process allowed for efficient certification and effective implementation of the parameters, allowing the rover to approach and land on the red planet (the most challenging phase of the mission) with zero parameter issues. Although successful, the Perseverance team learned many lessons for how to better manage parameters for the continued surface operations of the Mars 2020 mission and future missions. This paper will discuss eight parameter-management topics for the Perseverance Mission. The first is parameter definition: how we define parameters on our mission, where they are physically located on the vehicle, and why we have so many of them. The second topic is the updated parameter flight software module from Curiosity, including details on the 99% reduction in parameter commands, new bulk configuration capabilities, and improved parameter traceability. The third topic is parameter selection for different mission phases; this includes improving and tweaking our preferred parameter settings until they become certification candidates and managing parameter configurations based on test venue throughout the mission life cycle. The fourth topic is our flight certification process; this includes certification of flight values for four different epochs in the mission: Launch, Entry Decent and Landing (EDL) - 6days, Landing + 5 Sols (Martian Days, still on Cruise Flight Software), and once are on Surface Flight Software (FSW). The fifth topic covers in-flight command implementation, along with details on testing, validation, and verification of those commands. In the sixth section, we will explain our use of open-source management tools, including how we used GitHub for version control and management approvals. The seventh topic will describe the ground tools used in operations, including capabilities of the in-house built tool called Parasol. The eighth and final topic will dig into lessons learned for improving parameter management in the future of this mission and others.

Roth, Brian↗

ESCHER: An interactive mesh-generating editor for preparing finite-element input

ESCHER is an interactive mesh generation and editing program designed to help the user create a finite-element mesh, create additional input for finite-element analysis, including initial conditions, boundary conditions, and slidelines, and generate a NEUTRAL FILE that can be postprocessed for input into several finite-element codes, including ADINA, ADINAT, DYNA, NIKE, TSAAS, and ABUQUS. Two important ESCHER capabilities, interactive geometry creation and mesh archival storge are described in detail. Also described is the interactive command language and the use of interactive graphics. The archival storage and restart file is a modular, entity-based mesh data file. Modules of this file correspond to separate editing modes in the mesh editor, with data definition syntax preserved between the interactive commands and the archival storage file. Because ESCHER was expected to be highly interactive, extensive user documentation was provided in the form of an interactive HELP package.

Oakes, W. R., Jr.↗

Profiling the BLAST bioinformatics application for load balancing on high-performance computing clusters

Abstract Background The Basic Local Alignment Search Tool (BLAST) is a suite of commonly used algorithms for identifying matches between biological sequences. The user supplies a database file and query file of sequences for BLAST to find identical sequences between the two. The typical millions of database and query sequences make BLAST computationally challenging but also well suited for parallelization on high-performance computing clusters. The efficacy of parallelization depends on the data partitioning, where the optimal data partitioning relies on an accurate performance model. In previous studies, a BLAST job was sped up by 27 times by partitioning the database and query among thousands of processor nodes. However, the optimality of the partitioning method was not studied. Unlike BLAST performance models proposed in the literature that usually have problem size and hardware configuration as the only variables, the execution time of a BLAST job is a function of database size, query size, and hardware capability. In this work, the nucleotide BLAST application BLASTN was profiled using three methods: shell-level profiling with the Unix “time” command, code-level profiling with the built-in “profiler” module, and system-level profiling with the Unix “gprof” program. The runtimes were measured for six node types, using six different database files and 15 query files, on a heterogeneous HPC cluster with 500+ nodes. The empirical measurement data were fitted with quadratic functions to develop performance models that were used to guide the data parallelization for BLASTN jobs. Results Profiling results showed that BLASTN contains more than 34,500 different functions, but a single function, RunMTBySplitDB, takes 99.12% of the total runtime. Among its 53 child functions, five core functions were identified to make up 92.12% of the overall BLASTN runtime. Based on the performance models, static load balancing algorithms can be applied to the BLASTN input data to minimize the runtime of the longest job on an HPC cluster. Four test cases being run on homogeneous and heterogeneous clusters were tested. Experiment results showed that the runtime can be reduced by 81% on a homogeneous cluster and by 20% on a heterogeneous cluster by re-distributing the workload. Discussion Optimal data partitioning can improve BLASTN’s overall runtime 5.4-fold in comparison with dividing the database and query into the same number of fragments. The proposed methodology can be used in the other applications in the BLAST+ suite or any other application as long as source code is available.

59 BASIC BIOLOGICAL SCIENCES↗

Computer aided control of a mechanical arm

A method for computer-aided remote control of a six-degree-of-freedom manipulator arm involved in the on-orbit servicing of a spacecraft is presented. The control configuration features a supervisory type of control in which each of the segments of a module exchange trajectory is controlled automatically under human supervision, with manual commands to proceed to the next step and in the event of a failure or undesirable outcome. The implementation of the supervisory system is discussed in terms of necessary onboard and ground- or Orbiter-based hardware and software, and a one-g demonstration system built to allow further investigation of system operation is described. Possible applications of the system include the construction of satellite solar power systems, environmental testing and the control of heliostat solar power stations.

Derocher, W. L., Jr.↗

Attitude control of the space construction base: A modular approach

A planar model of a space base and one module is considered. For this simplified system, a feedback controller which is compatible with the modular construction method is described. The systems dynamics are decomposed into two parts corresponding to base and module. The information structure of the problem is non-classical in that not all system information is supplied to each controller. The base controller is designed to accommodate structural changes that occur as the module is added and the module controller is designed to regulate its own states and follow commands from the base. Overall stability of the system is checked by Liapunov analysis and controller effectiveness is verified by computer simulation.

Oconnor, D. A.↗