Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Communication traces”

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 37 records · Page 2

On the Information Content of Program Traces

Program traces are used for analysis of program performance, memory utilization, and communications as well as for program debugging. The trace contains records of execution events generated by monitoring units inserted into the program. The trace size limits the resolution of execution events and restricts the user's ability to analyze the program execution. We present a study of the information content of program traces and develop a coding scheme which reduces the trace size to the limit given by the trace entropy. We apply the coding to the traces of AIMS instrumented programs executed on the IBM SPA and the SCSI Power Challenge and compare it with other coding methods. Our technique shows size of the trace can be reduced by more than a factor of 5.

Frumkin, Michael↗

Trace-Driven Debugging of Message Passing Programs

In this paper we report on features added to a parallel debugger to simplify the debugging of parallel message passing programs. These features include replay, setting consistent breakpoints based on interprocess event causality, a parallel undo operation, and communication supervision. These features all use trace information collected during the execution of the program being debugged. We used a number of different instrumentation techniques to collect traces. We also implemented trace displays using two different trace visualization systems. The implementation was tested on an SGI Power Challenge cluster and a network of SGI workstations.

Frumkin, Michael↗

Efficient Tracing for On-the-Fly Space-Time Displays in a Debugger for Message Passing Programs

In this work we describe the implementation of a practical mechanism for collecting and displaying trace information in a debugger for message passing programs. We introduce a trace format that is highly compressible while still providing information adequate for debugging purposes. We make the mechanism convenient for users to access by incorporating the trace collection in a set of wrappers for the MPI (message passing interface) communication library. We implement several debugger operations that use the trace display: consistent stoplines, undo, and rollback. They all are implemented using controlled replay, which executes at full speed in target processes until the appropriate position in the computation is reached. They provide convenient mechanisms for getting to places in the execution where the full power of a state-based debugger can be brought to bear on isolating communication errors.

Hood, Robert↗

Space Link Extension (SLE) Emulation for High-Throughput Network Communication

As the data rate requirements for space communications increases, signicant stressis placed not only on the wireless satellite communication links, but also on the groundnetworks which forward data from end-users to remote ground stations. These wide areanetwork (WAN) connections add delay and jitter to the end-to-end satellite communicationlink, eects which can have signicant impacts on the wireless communication link. It isimperative that any ground communication protocol can react to these eects such that theground network does not become a bottleneck in the communication path to the satellite.In this paper, we present our SCENIC Emulation Lab testbed which was developed to testthe CCSDS SLE protocol implementations proposed for use on future NASA communica-tion networks. Our results show that in the presence of realistic levels of network delay,high-throughput SLE communication links can experience signicant data rate throttling.Based on our observations, we present some insight into why this data throttling happens,and trace the probable issue back to non-optimal blocking communication which is sup-ported by the CCSDS SLE API recommended practices. These issues were presented aswell to the SLE implementation developers which, based on our reports, developed a newrelease for SLE which we show xes the SLE blocking issue and greatly improves the pro-tocol throughput. In this paper, we also discuss future developments for our end-to-endemulation lab and how these improvements can be used to develop and test future spacecommunication technologies.

Networking↗

Space Link Extension (SLE) Emulation for High-Throughput Network Communication

As the data rate requirements for space communications increases, significant stress is placed not only on the wireless satellite communication links, but also on the ground networks which forward data from end-users to remote ground stations. These wide area network (WAN) connections add delay and jitter to the end-to-end satellite communication link, effects which can have significant impacts on the wireless communication link. It is imperative that any ground communication protocol can react to these effects such that the ground network does not become a bottleneck in the communication path to the satellite. In this paper, we present our SCENIC Emulation Lab testbed which was developed to test the CCSDS SLE protocol implementations proposed for use on future NASA communication networks. Our results show that in the presence of realistic levels of network delay, high-throughput SLE communication links can experience significant data rate throttling. Based on our observations, we present some insight into why this data throttling happens, and trace the probable issue back to non-optimal blocking communication which is sup-ported by the CCSDS SLE API recommended practices. These issues were presented as well to the SLE implementation developers which, based on our reports, developed a new release for SLE which we show fixes the SLE blocking issue and greatly improves the protocol throughput. In this paper, we also discuss future developments for our end-to-end emulation lab and how these improvements can be used to develop and test future space communication technologies.

Networking↗

Performance Measurement, Visualization and Modeling of Parallel and Distributed Programs

This paper presents a methodology for debugging the performance of message-passing programs on both tightly coupled and loosely coupled distributed-memory machines. The AIMS (Automated Instrumentation and Monitoring System) toolkit, a suite of software tools for measurement and analysis of performance, is introduced and its application illustrated using several benchmark programs drawn from the field of computational fluid dynamics. AIMS includes (i) Xinstrument, a powerful source-code instrumentor, which supports both Fortran77 and C as well as a number of different message-passing libraries including Intel's NX Thinking Machines' CMMD, and PVM; (ii) Monitor, a library of timestamping and trace -collection routines that run on supercomputers (such as Intel's iPSC/860, Delta, and Paragon and Thinking Machines' CM5) as well as on networks of workstations (including Convex Cluster and SparcStations connected by a LAN); (iii) Visualization Kernel, a trace-animation facility that supports source-code clickback, simultaneous visualization of computation and communication patterns, as well as analysis of data movements; (iv) Statistics Kernel, an advanced profiling facility, that associates a variety of performance data with various syntactic components of a parallel program; (v) Index Kernel, a diagnostic tool that helps pinpoint performance bottlenecks through the use of abstract indices; (vi) Modeling Kernel, a facility for automated modeling of message-passing programs that supports both simulation -based and analytical approaches to performance prediction and scalability analysis; (vii) Intrusion Compensator, a utility for recovering true performance from observed performance by removing the overheads of monitoring and their effects on the communication pattern of the program; and (viii) Compatibility Tools, that convert AIMS-generated traces into formats used by other performance-visualization tools, such as ParaGraph, Pablo, and certain AVS/Explorer modules.

Yan, Jerry C.↗

Performance Data Gathering and Representation from Fixed-Size Statistical Data

The two commonly-used performance data types in the super-computing community, statistics and event traces, are discussed and compared. Statistical data are much more compact but lack the probative power event traces offer. Event traces, on the other hand, are unbounded and can easily fill up the entire file system during program execution. In this paper, we propose an innovative methodology for performance data gathering and representation that offers a middle ground. Two basic ideas are employed: the use of averages to replace recording data for each instance and 'formulae' to represent sequences associated with communication and control flow. The user can trade off tracing overhead, trace data size with data quality incrementally. In other words, the user will be able to limit the amount of trace data collected and, at the same time, carry out some of the analysis event traces offer using space-time views. With the help of a few simple examples, we illustrate the use of these techniques in performance tuning and compare the quality of the traces we collected with event traces. We found that the trace files thus obtained are, indeed, small, bounded and predictable before program execution, and that the quality of the space-time views generated from these statistical data are excellent. Furthermore, experimental results showed that the formulae proposed were able to capture all the sequences associated with 11 of the 15 applications tested. The performance of the formulae can be incrementally improved by allocating more memory at runtime to learn longer sequences.

Yan, Jerry C.↗

Path Profiles of Cn2 Derived from Radiometer Temperature Measurements and Geometrical Ray Tracing

Atmospheric turbulence has significant impairments on the operation of Free-Space Optical (FSO) communication systems, in particular temporal and spatial intensity fluctuations at the receiving aperture resulting in power surges and fades, changes in angle of arrival, spatial coherence degradation, etc. The refractive index structure parameter Cn2 is a statistical measure of the strength of turbulence in the atmosphere and is highly dependent upon vertical height. Therefore to understand atmospheric turbulence effects on vertical FSO communication links such as space-to-ground links, it is necessary to specify Cn2 profiles along the atmospheric propagation path. To avoid the limitations on the applicability of classical approaches, propagation simulation through geometrical ray tracing is applied. This is achieved by considering the atmosphere along the optical propagation path as a spatial distribution of spherical bubbles with varying relative refractive index deviations representing turbulent eddies. The relative deviations of the refractive index are statistically determined from altitude-dependent and time-varying temperature fluctuations, as measured by a microwave profiling radiometer. For each representative atmosphere ray paths are analyzed using geometrical optics, which is particularly advantageous in situations of strong turbulence where there is severe wavefront distortion and discontinuity. The refractive index structure parameter is then determined as a function of height and time.

Atmospheric turbulence↗

Mise en Scene: Conversion of Scenarios to CSP Traces for the Requirements-to-Design-to-Code Project

The "Requirements-to-Design-to-Code" (R2D2C) project at NASA's Goddard Space Flight Center is based on deriving a formal specification expressed in Communicating Sequential Processes (CSP) notation from system requirements supplied in the form of CSP traces. The traces, in turn, are to be extracted from scenarios, a user-friendly medium often used to describe the required behavior of computer systems under development. This work, called Mise en Scene, defines a new scenario medium (Scenario Notation Language, SNL) suitable for control-dominated systems, coupled with a two-stage process for automatic translation of scenarios to a new trace medium (Trace Notation Language, TNL) that encompasses CSP traces. Mise en Scene is offered as an initial solution to the problem of the scenarios-to-traces "D2" phase of R2D2C. A survey of the "scenario" concept and some case studies are also provided.

Carter. John D.↗

Relay Communications Support to the ExoMars Schiaparelli Lander

The European Space Agency’s ExoMars Trace Gas Orbiter (TGO) arrived at Mars on October 19, 2016, three days after releasing the Schiaparelli Lander on a ballistic trajectory to Meridiani Planum. During the separation event, and subsequently during Schiaparelli’s Entry, Descent, and Landing (EDL), the NASA-provided Electra UHF payload onboard TGO was used to record signals from the Schiaparelli Lander for post-processing on the ground to recover both tracking of the lander’s carrier signal and reconstruction of the lander’s 8 kb/s telemetry. In addition, ESA’s Mars Express orbiter also recorded the Schiaparelli signal, with ground post-processing providing independent tracking of the lander carrier signal, and the Giant Metrewave Radio Telescope near Pune, India was configured to provide real-time detection of the lander carrier signal. While an anomaly in the latter stages of EDL led to loss of the lander, these critical event data sets, and in particular the telemetry reconstruction enabled by the TGO Electra recording, proved essential in enabling detailed diagnosis of the anomaly. And while the loss of the lander during EDL precluded the planned surface relay operations, the preparations for that activity provide important lessons learned for future Mars relay support scenarios.

Edwards, Charles D., Jr.↗

Medical Monitoring during Short Radius Centrifugation in Bed-rested Subjects

The artificial gravity pilot project was designed to investigate the efficacy of daily exposure to a Gz acceleration gradient for counteracting the physiologic decrements induced by prolonged bed rest. A short radius centrifuge was used to produce a Gz gradient such that 1 g was applied at the level of the subject s heart and 2.5 g at the feet. For inclusion in the study, subjects were required to complete a 75-minute screening spin on the centrifuge. During the study, each active treatment subject was scheduled for a 60-minute spin each day for 20 consecutive days. During centrifugation, subjects were continuously monitored by a physician for signs and symptoms of pre-syncope, motion sickness, arrhythmias, joint/muscle pain and any other unanticipated problems. The physician was also present to provide emergency care in the case of a medical emergency. Cameras mounted on the centrifuge were used to provide a means of observing the subject s face and torso. Audio communication was continuously maintained. Other monitoring tools included two-lead EKG tracings, pulse oximetry, intermittent sphygmomanometer readings, lights in the peripheral visual field, and continuous blood pressure readout from a tonometry device. Thirty screening runs were attempted using twenty-seven subjects. Seven of these runs were terminated early for symptoms of pre-syncope, motion sickness, or GI distress. A total of eight subjects completed the active treatment arm of the study. Of the 160 centrifuge runs that were scheduled for these eight treatment subjects, 152 were completed, seven were terminated early, and one was not attempted. Of the seven early terminations, four were related to symptoms of pre-syncope, one to leg pain, one to GI discomfort, and one to equipment failure. Three terminations for adverse symptoms occurred on the first treatment day. Three terminations occurred on day nineteen of treatment and within 24 hours after scheduled soleus and quadriceps muscle biopsies. We have summarized the relative usefulness of the information obtained by the various monitoring modalities in making a decision to terminate a centrifuge run. The video and audio communication information was essential to the decision-making process. Heart rate and EKG tracings are considered valuable, even though no spins were terminated due to significant arrhythmias. The tonometer device was generally not reliable in this application. Our observations suggest that subjects may be less tolerant of centrifugation just after starting bed rest and after invasive procedures.

Reinertson, Randal↗

Psychological stress measurement through voice output analysis

Audio tape recordings of selected Skylab communications were processed by a psychological stress evaluator. Strip chart tracings were read blind and scores were assigned based on characteristics reported by the manufacturer to indicate psychological stress. These scores were analyzed for their empirical relationships with operational variables in Skylab judged to represent varying degrees of situational stress. Although some statistically significant relationships were found, the technique was not judged to be sufficiently predictive to warrant its use in assessing the degree of psychological stress of crew members in future space missions.

Older, H. J.↗

Implications of Automotive and Trucking On-Board Information Systems for General Aviation Cockpit Weather Systems

In this study, current characteristics and future developments of Intelligent Transportation Systems (ITS) in the automobile and trucking industry are investigated to identify the possible implications of such systems for General Aviation (GA) cockpit weather systems. First, ITS are explained based on tracing their historical development in various countries. Then, current systems and the enabling communication technologies are discussed. Finally, a market analysis for GA is included.

Sireli, Yesim↗

Automated Instrumentation, Monitoring and Visualization of PVM Programs Using AIMS

We present views and analysis of the execution of several PVM (Parallel Virtual Machine) codes for Computational Fluid Dynamics on a networks of Sparcstations, including: (1) NAS Parallel Benchmarks CG and MG; (2) a multi-partitioning algorithm for NAS Parallel Benchmark SP; and (3) an overset grid flowsolver. These views and analysis were obtained using our Automated Instrumentation and Monitoring System (AIMS) version 3.0, a toolkit for debugging the performance of PVM programs. We will describe the architecture, operation and application of AIMS. The AIMS toolkit contains: (1) Xinstrument, which can automatically instrument various computational and communication constructs in message-passing parallel programs; (2) Monitor, a library of runtime trace-collection routines; (3) VK (Visual Kernel), an execution-animation tool with source-code clickback; and (4) Tally, a tool for statistical analysis of execution profiles. Currently, Xinstrument can handle C and Fortran 77 programs using PVM 3.2.x; Monitor has been implemented and tested on Sun 4 systems running SunOS 4.1.2; and VK uses XIIR5 and Motif 1.2. Data and views obtained using AIMS clearly illustrate several characteristic features of executing parallel programs on networked workstations: (1) the impact of long message latencies; (2) the impact of multiprogramming overheads and associated load imbalance; (3) cache and virtual-memory effects; and (4) significant skews between workstation clocks. Interestingly, AIMS can compensate for constant skew (zero drift) by calibrating the skew between a parent and its spawned children. In addition, AIMS' skew-compensation algorithm can adjust timestamps in a way that eliminates physically impossible communications (e.g., messages going backwards in time). Our current efforts are directed toward creating new views to explain the observed performance of PVM programs. Some of the features planned for the near future include: (1) ConfigView, showing the physical topology of the virtual machine, inferred using specially formatted IP (Internet Protocol) packets: and (2) LoadView, synchronous animation of PVM-program execution and resource-utilization patterns.

Mehra, Pankaj↗

Design for the Structure and the Mechanics of Moballs

The moball is envisioned to be a round, self-powered, and wind-driven multifunctioning sensor used in the Gone with the Wind ON-Mars (GOWON) [http://www.lpi.usra.edu/meetings/ marsconcepts2012/pdf/4238.pdf]: A Wind-Driven Networked System of Mobile sensors on Mars. The moballs would have sensing, processing, and communication capabilities. The moballs would perform in situ detection of key environmental elements such as vaporized water, trace gases, wind, dust, clouds, light and UV exposure, temperature, as well as minerals of interest, possible biosignatures, surface magnetic and electric fields, etc. The embedded various low-power micro instruments could include a Multispectral Microscopic Imager (to detect various minerals), a compact curved focal plane array camera (UV/Vis/NIR) with a large field of view, a compact UV/Visible spectrometer, a micro-weather station, etc. The moballs could communicate with each other and an orbiter. Their wind- or gravity-driven rolling movement could be used to harvest and store electric energy. They could also generate and store energy using the sunlight, when available, and the diurnal temperature variations on Mars. The moballs would be self-aware of their (and their neighbors ) positions, energy storage, and memory availability; they would have processing power and could intelligently cooperate with neighboring moballs by distributing tasks, sharing data, and fusing information. The major advantages of using the wind-driven and spherical moball network over rovers or other fixed sensor webs to explore Mars would be: (1) moballs could explore a much larger expanse of Mars in a much faster fashion, (2) they could explore the difficult terrains such as steep slopes and sand dunes, and (3) they would be self-energy- generating and could work together and move around autonomously. The challenge in designing the structure and the mechanics of the moball would be that it should be sturdy enough to withstand the impact of its initial fall, as well as other impacts from obstacles in its way. A mechanism would be needed that could enable hundreds of moballs to be carried while they would be deflated and compact, then would inflate them just after deploying them to their drop site. Furthermore, the moballs should also be light enough to allow them to move easily over obstacles by force of the wind. They also should have some kind of maneuvering mechanism in place to help them avoid very hazardous sharp objects or events, and to enable them to get closer to the objects of interest. The structure of the moballs was designed so that they would have different layers. The outer layer should comprise a sturdy, yet light, polymer that could withstand both the impact of the initial drop, as well as the impact of the different obstacles it would encounter while traversing the surface of Mars. This polymer should not deteriorate with the 100 K daily temperature swings on Mars. The inner layer should consist of a very light gas such as nitrogen or helium. In terms of maneuvering, six very light weights placed at strategic locations would give moballs the ability to turn, or even hop, over hazardous (e.g., sharp) obstacles, or even initiate a movement (before getting more help from the wind to be carried around) when stuck. Maneuvering would be necessary in order to get closer to objects of interest. If the weights would be allowed to move freely, they could also be used to generate energy.

Davoodi, Faranak↗

Optimizing Lunar Map Partitioning for Multipath Fade Loss Analyses

A methodology is presented pertaining to the run-time optimization of quasi-optical ray-tracing simulations. These shooting-and-bouncing ray methods are used for assessing multipath fade loss in cislunar communication links. Our approach employs partitioning lunar terrain maps in shapes that approximate two-dimensional projections of Fresnel zone cross-sections. This technique drastically reduces computational run-time without causing significant loss of simulation accuracy.

Digital elevation models↗

Constructing Space-Time Views from Fixed Size Statistical Data: Getting the Best of Both Worlds

Many performance monitoring tools are currently available to the super-computing community. The performance data gathered and analyzed by these tools fall under two categories: statistics and event traces. Statistical data is much more compact but lacks the probative power event traces offer. Event traces, on the other hand, can easily fill up the entire file system during execution such that the instrumented execution may have to be terminated half way through. In this paper, we propose an innovative methodology for performance data gathering and representation that offers a middle ground. The user can trade-off tracing overhead, trace data size vs. data quality incrementally. In other words, the user will be able to limit the amount of trace collected and, at the same time, carry out some of the analysis event traces offer using spacetime views for the entire execution. Two basic ideas are employed: the use of averages to replace recording data for each instance and "formulae" to represent sequences associated with communication and control flow. With the help of a few simple examples, we illustrate the use of these techniques in performance tuning and compare the quality of the traces we collected vs. event traces. We found that the trace files thus obtained are, in deed, small, bounded and predictable before program execution and that the quality of the space time views generated from these statistical data are excellent. Furthermore, experimental results showed that the formulae proposed were able to capture 100% of all the sequences associated with 11 of the 15 applications tested. The performance of the formulae can be incrementally improved by allocating more memory at run-time to learn longer sequences.

Schmidt, Melisa↗

NASA’s Top Human System Research and Technology Needs for Mars

NASA is working with industry and international partners to return humans to the Moon and to eventually enable humans to explore Mars. Within NASA, several organizations work together to identify, prioritize, fund, execute, and operationalize the research and technology development (R&TD) that will be necessary to enable crew health and performance (CHP) during these future missions. These organizations include flight programs, the Health and Medical Technical Authority (HMTA), the Human Research Program, the Space Technology Mission Directorate, System Capability Leadership Teams, and other organizations, many of which existed for several years prior to the creation of the Moon-to-Mars (M2M) Program Office in 2023. A variety of constructs, vocabularies, and processes exist for managing risks and supporting strategic planning across these organizations. For example, M2M objectives, program risks, human system risks, human research gaps, capability gaps, and envisioned futures are all constructs currently used within NASA to identify and prioritize R&TD needs. These strategic planning constructs are evolving to allow M2M objectives and R&TD investments to be aligned and traced at a detailed level. A recognized need exists among stakeholder organizations to identify and communicate the highest CHP R&TD priorities in a unified and digestible way that addresses the perspectives of NASA’s CHP community. To achieve this, the HMTA arranged a series of discussions with representatives of NASA’s CHP community, during which the 8 highest priority CHP capabilities that will enable human missions to Mars, referred to as the “top human system capability needs for Mars”, were identified. The list includes Earth-independent human operations; Mars-duration food system; Mars-duration effects on human physiology; risk mitigations for vehicle atmospheres; computational injury and anthropometric models; exploration exercise countermeasures; individual variability in responses to spaceflight; and sensorimotor countermeasures. Existing tools and processes for strategic planning and risk management were evaluated, as well as the technical practicalities, cost, and schedule feasibility associated with potential R&TD investments in different capability need areas. This capability needs report is not owned by any one NASA organization and does not replace existing strategic or program planning processes; rather it aims to complement and inform them with a unified set of community generated priorities. These top capability needs will be re-evaluated periodically based on R&TD progress and the evolving M2M architecture.

technology gaps↗