Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Network monitoring”

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 577 records · Page 32
All sourcesNASA NTRSDOE OSTI
NASA NTRS2018

Observations of the Interaction and Transport of Fine Mode Aerosols With Cloud and/or Fog in Northeast Asia From Aerosol Robotic Network and Satellite Remote Sensing

Analysis of Sun photometer measured and satellite retrieved aerosol optical depth (AOD) datahas shown that major aerosol pollution events with very highfine mode AOD (>1.0 in midvisible) in theChina/Korea/Japan region are often observed to be associated with significant cloud cover. This makesremote sensing of these events difficult even for high temporal resolution Sun photometer measurements.Possible physical mechanisms for these events that have high AOD include a combination of aerosolhumidification, cloud processing, and meteorological covariation with atmospheric stability andconvergence. The new development of Aerosol Robotic Network Version 3 Level 2 AOD with improved cloudscreening algorithms now allow for unprecedented ability to monitor these extremefine mode pollutionevents. Further, the spectral deconvolution algorithm (SDA) applied to Level 1 data (L1; no cloud screening)provides an even more comprehensive assessment offine mode AOD than L2 in current and previous dataversions. Studying the 2012 winter-summer period, comparisons of Aerosol Robotic Network L1 SDA dailyaveragefine mode AOD data showed that Moderate Resolution Imaging Spectroradiometer satellite remotesensing of AOD often did not retrieve and/or identify some of the highestfine mode AOD events in thisregion. Also, compared to models that include data assimilation of satellite retrieved AOD, the L1 SDAfinemode AOD was significantly higher in magnitude, particularly for the highest AOD events that were oftenassociated with significant cloudiness.

Eck, T. F.↗
NASA NTRS1976

DSN ground communications facility

The Ground Communications Facility (GCF) is one of the three functional elements of the Deep Space Network (DSN) and provides the capability required for the transmission, reception, and monitoring of voice and data communications between the various locations of the DSN. The GCF uses common carrier circuits interconnected to specialized switching, terminal, and monitor equipment, integrated into a world-wide system, and operated in support of space flight missions. The five subsystems of GCF (Teletype, Voice, High-Speed, Wideband, and Monitor) are described. The Office of Tracking and Data Acquisition of the Jet Propulsion Laboratory provides the technical direction and systems management of the GCF and acts as the representative of NASCOM for communications switching functions on the west coast.

Glenn, M. S.↗
NASA NTRS1977

Evaluation of DSN data processing with 7200-b/s GCF high-speed data interfaces

Test results confirm that the Deep Space Station (DSS) and Network Operations Control Center (NOCC) processing of telemetry, command, radio metric, and monitor data with the existing DSN Mark III-75 configuration will be unaffected by the recent change of the Ground Communications Facility (GCF) high-speed data subsystem to a clock rate of 7,200 bits per second.

Thorman, H. C.↗
NASA NTRS1978

DSS 13 antenna subsystem automation

Unattended station operation was implemented that permitted full operational control from the network operations center (NOCC). Sensors were installed in the mechanical subsystem to monitor critical functions and to permit automated premission checkout of the subsystem, automated reaction to component failure, and identification of failed components under control of the antenna pointing computer. This monitoring installation is a prototype for monitoring equipment to be installed throughout the DSN.

Phillips, H.↗
NASA NTRS1996

Fiber-Optic Distribution Of Pulsed Power To Multiple Sensors

Optoelectronic systems designed according to time-sharing scheme distribute optical power to multiple integrated-circuit-based sensors in fiber-optic networks. Networks combine flexibility of electronic sensing circuits with advantage of electrical isolation afforded by use of optical fibers instead of electrical conductors to transmit both signals and power. Fiber optics resist corrosion and immune to electromagnetic interference. Sensor networks of this type useful in variety of applications; for example, in monitoring strains in aircraft, buildings, and bridges, and in monitoring and controlling shapes of flexible structures.

Kirkham, Harold↗
NASA NTRS1998

Results of the NY-Alesund ozone measurements intercomparison NAOMI

Worldwide, about ten Differential Absorption Lidars are used for long-term monitoring of stratospheric ozone. These systems are an important component of the Network for the Detection of Stratospheric Change. Although DIALs are self-calibrating in principle, regular intercomparisons with other ozone-lidars, microwave radiometers or ozone-sondes are highly desirable to ensure high data quality at a well known level. The Network for the Detection of Stratospheric Change (NDSC) validation policy suggests that such intercomparisons be "blind", meaning all participants submit their data to an impartial referee, without seeing results from the other participants. Here we report on the "blind" intercomparison taking place from January 20th to February 10th 1998 at Ny-Alesund, Spitsbergen (78.92 deg N, 11.95 deg E). Participating groups were from the Alfred Wegener Institute, Potsdam, operating the NDSC DIAL system at Ny-Alesund, from the University of Bremen operating the NDSC microwave radiometer for ozone profiling at Ny-Alesund, and the NASA Goddard Space Flight Center group with the "NDSC travelling standard" STROZ-LITE. The first author acted as the impartial referee. Also used for the intercomparison were data from ECC-6A/Vaisala RS80 ozone sondes routinely launched at Ny-Alesund by the AWI group. A 1% KI solution (3 ml) and the 1986 ECC pump correction (1.092 at 5 hPa) are used. The ECC-data were available to all participants during the campaign and thus were not "blind". Table 1 summarizes the expected performance of the instruments participating in the ozone intercomparison reported in this paper.

Steinbrecht, W.↗
NASA NTRS2008

Safe Upper-Bounds Inference of Energy Consumption for Java Bytecode Applications

Many space applications such as sensor networks, on-board satellite-based platforms, on-board vehicle monitoring systems, etc. handle large amounts of data and analysis of such data is often critical for the scientific mission. Transmitting such large amounts of data to the remote control station for analysis is usually too expensive for time-critical applications. Instead, modern space applications are increasingly relying on autonomous on-board data analysis. All these applications face many resource constraints. A key requirement is to minimize energy consumption. Several approaches have been developed for estimating the energy consumption of such applications (e.g. [3, 1]) based on measuring actual consumption at run-time for large sets of random inputs. However, this approach has the limitation that it is in general not possible to cover all possible inputs. Using formal techniques offers the potential for inferring safe energy consumption bounds, thus being specially interesting for space exploration and safety-critical systems. We have proposed and implemented a general frame- work for resource usage analysis of Java bytecode [2]. The user defines a set of resource(s) of interest to be tracked and some annotations that describe the cost of some elementary elements of the program for those resources. These values can be constants or, more generally, functions of the input data sizes. The analysis then statically derives an upper bound on the amount of those resources that the program as a whole will consume or provide, also as functions of the input data sizes. This article develops a novel application of the analysis of [2] to inferring safe upper bounds on the energy consumption of Java bytecode applications. We first use a resource model that describes the cost of each bytecode instruction in terms of the joules it consumes. With this resource model, we then generate energy consumption cost relations, which are then used to infer safe upper bounds. How energy consumption for each bytecode instruction is measured is beyond the scope of this paper. Instead, this paper is about how to infer safe energy consumption estimations assuming that those energy consumption costs are provided. For concreteness, we use a simplified version of an existing resource model [1] in which an energy consumption cost for individual Java opcodes is defined.

Navas, Jorge↗
NASA NTRS2011

Interface Supports Multiple Broadcast Transceivers for Flight Applications

A wireless avionics interface provides a mechanism for managing multiple broadcast transceivers. This interface isolates the control logic required to support multiple transceivers so that the flight application does not have to manage wireless transceivers. All of the logic to select transceivers, detect transmitter and receiver faults, and take autonomous recovery action is contained in the interface, which is not restricted to using wireless transceivers. Wired, wireless, and mixed transceiver technologies are supported. This design s use of broadcast data technology provides inherent cross strapping of data links. This greatly simplifies the design of redundant flight subsystems. The interface fully exploits the broadcast data link to determine the health of other transceivers used to detect and isolate faults for fault recovery. The interface uses simplified control logic, which can be implemented as an intellectual-property (IP) core in a field-programmable gate array (FPGA). The interface arbitrates the reception of inbound data traffic appearing on multiple receivers. It arbitrates the transmission of outbound traffic. This system also monitors broadcast data traffic to determine the health of transmitters in the network, and then uses this health information to make autonomous decisions for routing traffic through transceivers. Multiple selection strategies are supported, like having an active transceiver with the secondary transceiver powered off except to send periodic health status reports. Transceivers can operate in round-robin for load-sharing and graceful degradation.

Block, Gary L.↗
NASA NTRS2015

When the Sky Falls NASA's Response to Bright Bolide Events Over Continental USA

Being the only U.S. Government entity charged with monitoring the meteor environment, the Meteoroid Environment Office (MEO) has deployed a network of allsky and wide field meteor cameras, along with the appropriate software tools to quickly analyze data from these systems. However, the coverage of this network is still quite limited, forcing the incorporation of data from other cameras posted to the internet in analyzing many of the fireballs reported by the public and media. Information on these bright events often needs to be reported to NASA Headquarters by noon the following day; thus a procedure has been developed that determines the analysis process for a given fireball event based on the types and amount of data available. The differences between these analysis processes are shown by looking at four meteor events that the MEO responded to, all of which were large enough to produce meteorites.

Blaauw, R. C.↗
NASA NTRSDate not supplied

High Sensitive and Low Power Nanosensors for Space and Terrestrial Applications

Nanotechnology offers the ability to work at the molecular level, atom by atom, to create large structures with fundamentally new molecular organization. It is essentially concerned with materials, devices, and systems whose structures and components exhibit novel and significantly improved physical, chemical and biological properties, phenomena, and process control due to their nanoscale size. A nanosensor technology has been developed at NASA Ames using nanostructure, single walled carbon nanotubes (SWNTs). The nanosensors have achieved low detection limit of chemicals in the concentration range of ppm to ppb. Due to large surface area, low surface energy barrier and high thermal and mechanical stability, nanostructured chemical sensors offer higher sensitivity, lower power consumption and a more robust solution than most state-of-the-art systems making them attractive for space and terrestrial applications. An example of a sensor module, the first space flown nano device, will be introduced in this presentation. Such sensors have drawn attention from space community for global weather monitoring, space exploration, life search in the universe, and launch pad fuel leak detection and in-flight cabin air and life support system monitoring, and engine operation monitoring. Additionally, the wireless capability of such sensors can be leveraged to network mobile and fixed-base detection and warning systems for civilian population centers, military bases and battlefields, as well as other high-value or high-risk assets and areas in industry.

Jing Li↗
NASA NTRS2012

Analysis of the March 30, 2011 Hail Event at Shuttle Launch Pad 39A

The Kennedy Space Center (KSC) Hail Monitor System, a joint effort of the NASA KSC Physics Lab and the KSC Engineering Services Contract (ESC) Applied Technology Lab, was first deployed for operational testing in the fall of 2006. Volunteers from the Community Collaborative Rain, Hail, and Snow Network (CoCoRaHS) in conjunction with Colorado State University have been instrumental in validation testing using duplicate hail monitor systems at sites in the hail prone high plains of Colorado. The KSC Hail Monitor System (HMS), consisting of three stations positioned approximately 500 ft from the launch pad and forming an approximate equilateral triangle, as shown in Figure 1, was first deployed to Pad 39B for support of STS-115. Two months later, the HMS was deployed to Pad 39A for support of STS-116. During support of STS-117 in late February 2007, an unusually intense (for Florida standards) hail event occurred in the immediate vicinity of the exposed space shuttle and launch pad. Hail data of this event was collected by the HMS and analyzed. Support of STS-118 revealed another important application of the hail monitor system. Ground Instrumentation personnel check the hail monitors daily when a vehicle is on the launch pad, with special attention after any storm suspected of containing hail. If no hail is recorded by the HMS, the vehicle and pad inspection team has no need to conduct a thorough inspection of the vehicle immediately following a storm. On the afternoon of July 13, 2007, hail on the ground was reported by observers at the Vertical Assembly Building (VAB) and Launch Control Center (LCC), about three miles west of Pad 39A, as well as at several other locations at KSC. The HMS showed no impact detections, indicating that the shuttle had not been damaged by any of the numerous hail events which occurred on that day.

Lane, John E.↗
NASA NTRS2007

Suborbital Telepresence and Over-the-Horizon Networking

A viewgraph presentation describing the suborbital telepresence project utilizing in-flight network computing is shown. The topics include: 1) Motivation; 2) Suborbital Telepresence and Global Test Range; 3) Tropical Composition, Cloud, and Climate Coupling Experiment (TC4); 4) Data Sets for TC4 Real-time Monitoring; 5) TC-4 Notional Architecture; 6) An Application Integration View; 7) Telepresence: Architectural Framework; and 8) Disruption Tolerant Networks.

Freudinger, Lawrence C.↗
NASA NTRS1994

Automated Instrumentation, Monitoring and Visualization of PVM Programs Using AIMS

We present views and analysis of the execution of several PVM codes for Computational Fluid Dynamics on a network of Sparcstations, including (a) NAS Parallel benchmarks CG and MG (White, Alund and Sunderam 1993); (b) a multi-partitioning algorithm for NAS Parallel Benchmark SP (Wijngaart 1993); and (c) an overset grid flowsolver (Smith 1993). 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 (a) Xinstrument, which can automatically instrument various computational and communication constructs in message-passing parallel programs; (b) Monitor, a library of run-time trace-collection routines; (c) VK (Visual Kernel), an execution-animation tool with source-code clickback; and (d) Tally, a tool for statistical analysis of execution profiles. Currently, Xinstrument can handle C and Fortran77 programs using PVM 3.2.x; Monitor has been implemented and tested on Sun 4 systems running SunOS 4.1.2; and VK uses X11R5 and Motif 1.2. Data and views obtained using AIMS clearly illustrate several characteristic features of executing parallel programs on networked workstations: (a) the impact of long message latencies; (b) the impact of multiprogramming overheads and associated load imbalance; (c) cache and virtual-memory effects; and (4significant 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: (a) ConfigView, showing the physical topology of the virtual machine, inferred using specially formatted IP (Internet Protocol) packets; and (b) LoadView, synchronous animation of PVM-program execution and resource-utilization patterns.

Mehra, Pankaj↗
NASA NTRS2008

Hail Disrometer Array for Launch Systems Support

Prior to launch, the space shuttle might be described as a very large thermos bottle containing substantial quantities of cryogenic fuels. Because thermal insulation is a critical design requirement, the external wall of the launch vehicle fuel tank is covered with an insulating foam layer. This foam is fragile and can be damaged by very minor impacts, such as that from small- to medium-size hail, which may go unnoticed. In May 1999, hail damage to the top of the External Tank (ET) of STS-96 required a rollback from the launch pad to the Vehicle Assembly Building (VAB) for repair of the insulating foam. Because of the potential for hail damage to the ET while exposed to the weather, a vigilant hail sentry system using impact transducers was developed as a hail damage warning system and to record and quantify hail events. The Kennedy Space Center (KSC) Hail Monitor System, a joint effort of the NASA and University Affiliated Spaceport Technology Development Contract (USTDC) Physics Labs, was first deployed for operational testing in the fall of 2006. Volunteers from the Community Collaborative Rain. Hail, and Snow Network (CoCoRaHS) in conjunction with Colorado State University were and continue to be active in testing duplicate hail monitor systems at sites in the hail prone high plains of Colorado. The KSC Hail Monitor System (HMS), consisting of three stations positioned approximately 500 ft from the launch pad and forming an approximate equilateral triangle (see Figure 1), was deployed to Pad 39B for support of STS-115. Two months later, the HMS was deployed to Pad 39A for support of STS-116. During support of STS-117 in late February 2007, an unusual hail event occurred in the immediate vicinity of the exposed space shuttle and launch pad. Hail data of this event was collected by the HMS and analyzed. Support of STS-118 revealed another important application of the hail monitor system. Ground Instrumentation personnel check the hail monitors daily when a vehicle is on the launch pad, with special attention after any storm suspected of containing hail. If no hail is recorded by the HMS, the vehicle and pad inspection team has no need to conduct a thorough inspection of the vehicle immediately following a storm. On the afternoon of July 13, 2007, hail on the ground was reported by observers at the VAB, about three miles west of Pad 39A, as well as at several other locations around Kennedy Space Center. The HMS showed no impact detections, indicating that the shuttle had not been damaged by any of the numerous hail events which occurred that day.

Lane, John E.↗
NASA NTRS1994

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↗
NASA NTRS2005

Middleware Evaluation and Benchmarking for Use in Mission Operations Centers

Middleware technologies have been promoted as timesaving, cost-cutting alternatives to the point-to-point communication used in traditional mission operations systems. However, missions have been slow to adopt the new technology. The lack of existing middleware-based missions has given rise to uncertainty about middleware's ability to perform in an operational setting. Most mission architects are also unfamiliar with the technology and do not know the benefits and detriments to architectural choices - or even what choices are available. We will present the findings of a study that evaluated several middleware options specifically for use in a mission operations system. We will address some common misconceptions regarding the applicability of middleware-based architectures, and we will identify the design decisions and tradeoffs that must be made when choosing a middleware solution. The Middleware Comparison and Benchmark Study was conducted at NASA Goddard Space Flight Center to comprehensively evaluate candidate middleware products, compare and contrast the performance of middleware solutions with the traditional point- to-point socket approach, and assess data delivery and reliability strategies. The study focused on requirements of the Global Precipitation Measurement (GPM) mission, validating the potential use of middleware in the GPM mission ground system. The study was jointly funded by GPM and the Goddard Mission Services Evolution Center (GMSEC), a virtual organization for providing mission enabling solutions and promoting the use of appropriate new technologies for mission support. The study was broken into two phases. To perform the generic middleware benchmarking and performance analysis, a network was created with data producers and consumers passing data between themselves. The benchmark monitored the delay, throughput, and reliability of the data as the characteristics were changed. Measurements were taken under a variety of topologies, data demands, and data characteristics, using several middleware products. All results were compared to systems using traditional point-to-point socket communication. By comparing performance results under Merent settings, inferences could be made about each middleware's ability to meet certain requirements of the GPM mission. The second phase simulated a middleware-based mission operations center. Actual mission support tools were either used or simulated to create real world demands on the middleware. Network and computer demands were watched closely to verify that no specific idiosyncrasies of mission operations activities would prove unsupportable by the middleware. In our presentation, we will address some commonly accepted misconceptions concerning middleware in mission support architectures. Specifically, we will focus on the perception that middleware solutions are too slow or impose too much overhead for real-time mission operations, and that middleware solutions are too expensive for small

Antonucci, Rob↗
NASA NTRS2008

International Lunar Network (ILN) Anchor Nodes

This slide presentation reviews what we know about the interior and surface of the moon and the need to establish a robotic set of geophysical monitoring stations on the surface of the Moon for the purpose of providing significant scientific value to the exploration of the Moon. The ILN Anchor Nodes will provide the backbone of the network in a way that accomplishes new science and allows other nodes to be flexible contributors to the network.

Cohen, Barbara A.↗
NASA NTRS1976

Monitoring solar radiation: The ERDA program

An overview of the Energy Research and Development Administration planned insolation data network is described. The design of the network is predicated on an analysis and definition of user requirements. Research and analysis projects covering data collection, forecasting and extrapolation are presented.

Koomanoff, F. A.↗