Monitoring and performance assessment of GNSS inter-constellation timescale biases
No abstract provided
SEARCH · Search NASA
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.
No abstract provided
Explore the source record for details and available documents.
The design of pebble bed reactors (PBRs) and their method of operation align more closely with statistical approaches used in manufacturing and process control than traditional safeguards statistical approaches. The reason is PBRs will employ a nondestructive assay (NDA) measurement (burnup measurement system [BUMS]) that is part of the fuel handling system supporting discharge decisions in addition to the reactor code which monitor performance. The integration of these two approaches provides the opportunity to monitor reactor performance statistically for both operations and safeguards in ways not achievable using other reactor designs. For light water reactors (LWRs), knowledge about reactor code performance in predicting irradiated special nuclear material (SNM) content historically was only achieved from special measurement campaigns or from fuel reprocessing. Conversely, through statistical comparison of the BUMS with the reactor code-predicted values, PBRs can achieve this in real time. The resulting SNM distribution is an indicator of reactor performance because factors such as transit time and path of the pebble fuel through the reactor determine the plutonium production and uranium depletion. By analyzing the predicted and measured values, opportunities exist to adjust operating parameters, fuel design, and other characteristics to optimize performance and fuel utilization. From a safeguards perspective, this approach also provides the information necessary to validate declared values and evaluate whether the reactor is being operated as expected. This paper outlines statistical approaches for PBRs that can be used to support both operations and safeguards.
The Inductive Monitoring System (IMS) software developed at Ames Research Center uses artificial intelligence and data mining techniques to build system-monitoring knowledge bases from archived or simulated sensor data. This information is then used to detect unusual or anomalous behavior that may indicate an impending system failure. Currently helping analyze data from systems that help fly and maintain the space shuttle and the International Space Station (ISS), the IMS has also been employed by data classes are then used to build a monitoring knowledge base. In real time, IMS performs monitoring functions: determining and displaying the degree of deviation from nominal performance. IMS trend analyses can detect conditions that may indicate a failure or required system maintenance. The development of IMS was motivated by the difficulty of producing detailed diagnostic models of some system components due to complexity or unavailability of design information. Successful applications have ranged from real-time monitoring of aircraft engine and control systems to anomaly detection in space shuttle and ISS data. IMS was used on shuttle missions STS-121, STS-115, and STS-116 to search the Wing Leading Edge Impact Detection System (WLEIDS) data for signs of possible damaging impacts during launch. It independently verified findings of the WLEIDS Mission Evaluation Room (MER) analysts and indicated additional points of interest that were subsequently investigated by the MER team. In support of the Exploration Systems Mission Directorate, IMS is being deployed as an anomaly detection tool on ISS mission control consoles in the Johnson Space Center Mission Operations Directorate. IMS has been trained to detect faults in the ISS Control Moment Gyroscope (CMG) systems. In laboratory tests, it has already detected several minor anomalies in real-time CMG data. When tested on archived data, IMS was able to detect precursors of the CMG1 failure nearly 15 hours in advance of the actual failure event. In the Aeronautics Research Mission Directorate, IMS successfully performed real-time engine health analysis. IMS was able to detect simulated failures and actual engine anomalies in an F/A-18 aircraft during the course of 25 test flights. IMS is also being used in colla
A microcomputer based automatic test system was developed for the daily performance monitoring of wind energy system time domain (WEST) analyzer. The test system consists of a microprocessor based controller and hybrid interface unit which are used for inputing prescribed test signals into all WEST subsystems and for monitoring WEST responses to these signals. Performance is compared to theoretically correct performance levels calculated off line on a large general purpose digital computer. Results are displayed on a cathode ray tube or are available from a line printer. Excessive drift and/or lack of repeatability of the high speed analog sections within WEST is easily detected and the malfunctioning hardware identified using this system.
Operators can be poor monitors of automation if they are engaged concurrently in other tasks. However, in previous studies of this phenomenon the automated task was always presented in the periphery, away from the primary manual tasks that were centrally displayed. In this study we examined whether centrally locating an automated task would boost monitoring performance during a flight-simulation task consisting of system monitoring, tracking and fuel resource management sub-tasks. Twelve nonpilot subjects were required to perform the tracking and fuel management tasks manually while watching the automated system monitoring task for occasional failures. The automation reliability was constant at 87.5% for six subjects and variable (alternating between 87.5% and 56.25%) for the other six subjects. Each subject completed four 30 min sessions over a period of 2 days. In each automation reliability condition the automation routine was disabled for the last 20 min of the fourth session in order to simulate catastrophic automation failure (0 % reliability). Monitoring for automation failure was inefficient when automation reliability was constant but not when it varied over time, replicating previous results. Furthermore, there was no evidence of resource or speed accuracy trade-off between tasks. Thus, automation-induced failures of monitoring cannot be prevented by centrally locating the automated task.
This lecture note discusses the role of computer modelling in the design, development, and validation of a performance monitoring system. The basic requirements of an engine health monitoring system are discussed in the context of the user environment. A form of model based on stage characteristics provides the basis for describing engine measurements. Faults are modelled in accordance with empirical data obtained from tests conducted at the stage level. The model is used to investigate various parameters that provide unambiguous identification of the fault in question. Fault libraries have been developed for field use.
This annotated Request for Proposal (RFP) template includes an Energy Management and Information System (EMIS) technology specification, an ongoing services specification, RFP evaluation criteria, and more. It is designed to guide building professionals through the specification, procurement, and selection of an EMIS or related building performance monitoring and diagnostic technology.
The performance monitoring aspect of maintenance, characteristic of the engine health monitoring system are discussed. An overview of the system activities is presented and a summary of programs for improved monitoring in the 1980's are discussed.
NASA's exploration program envisions the utilization of a Deep Space Habitat (DSH) for human exploration of the space environment in the vicinity of Mars and/or asteroids. Communication latencies with ground control of as long as 20+ minutes make it imperative that DSH operations be highly autonomous, as any telemetry-based detection of a systems problem on Earth could well occur too late to assist the crew with the problem. A DSH-based development program has been initiated to develop and test the automation technologies necessary to support highly autonomous DSH operations. One such technology is a fault management tool to support performance monitoring of vehicle systems operations and to assist with real-time decision making in connection with operational anomalies and failures. Toward that end, we are developing Advanced Caution and Warning System (ACAWS), a tool that combines dynamic and interactive graphical representations of spacecraft systems, systems modeling, automated diagnostic analysis and root cause identification, system and mission impact assessment, and mitigation procedure identification to help spacecraft operators (both flight controllers and crew) understand and respond to anomalies more effectively. In this paper, we describe four major architecture elements of ACAWS: Anomaly Detection, Fault Isolation, System Effects Analysis, and Graphic User Interface (GUI), and how these elements work in concert with each other and with other tools to provide fault management support to both the controllers and crew. We then describe recent evaluations and tests of ACAWS on the DSH testbed. The results of these tests support the feasibility and strength of our approach to failure management automation and enhanced operational autonomy.
A performance measurement system which provides both a means of monitoring performance and a resource to support management decision making is described. The process of performance indicator development is discussed and typical indicators are described. The paper concludes with a summary of some of the lessons learned in applying productivity measurements to engineering services tasks and in automating data collection, evaluation and interpretation.
Helicopter Health Usage Monitoring Systems (HUMS) must provide reliable, real-time performance monitoring of helicopter operating parameters to prevent damage of flight critical components. Helicopter transmission diagnostics are an important part of a helicopter HUMS. In order to improve the reliability of transmission diagnostics, many researchers propose combining two technologies, vibration and oil monitoring, using data fusion and intelligent systems. Some benefits of combining multiple sensors to make decisions include improved detection capabilities and increased probability the event is detected. However, if the sensors are inaccurate, or the features extracted from the sensors are poor predictors of transmission health, integration of these sensors will decrease the accuracy of damage prediction. For this reason, one must verify the individual integrity of vibration and oil analysis methods prior to integrating the two technologies. This research focuses on comparing the capability of two vibration algorithms, FM4 and NA4, and a commercially available on-line oil debris monitor to detect pitting damage on spur gears in the NASA Glenn Research Center Spur Gear Fatigue Test Rig. Results from this research indicate that the rate of change of debris mass measured by the oil debris monitor is comparable to the vibration algorithms in detecting gear pitting damage.
Over the past decade, high performance computing has evolved rapidly; systems based on commodity microprocessors have been introduced in quick succession from at least seven vendors/families. Porting codes to every new architecture is a difficult problem; in particular, here at NASA, there are many large CFD applications that are very costly to port to new machines by hand. The LCM ("Legacy Code Modernization") Project is the development of an integrated parallelization environment (IPE) which performs the automated mapping of legacy CFD (Fortran) applications to state-of-the-art high performance computers. While most projects to port codes focus on the parallelization of the code, we consider porting to be an iterative process consisting of several steps: 1) code cleanup, 2) serial optimization,3) parallelization, 4) performance monitoring and visualization, 5) intelligent tools for automated tuning using performance prediction and 6) machine specific optimization. The approach for building this parallelization environment is to build the components for each of the steps simultaneously and then integrate them together. The demonstration will exhibit our latest research in building this environment: 1. Parallelizing tools and compiler evaluation. 2. Code cleanup and serial optimization using automated scripts 3. Development of a code generator for performance prediction 4. Automated partitioning 5. Automated insertion of directives. These demonstrations will exhibit the effectiveness of an automated approach for all the steps involved with porting and tuning a legacy code application for a new architecture.
The Kepler spacecraft is in a heliocentric Earth-trailing orbit, continuously observing ~160,000 select stars over ~115 square degrees of sky using its photometer containing 42 highly sensitive CCDs. The science data from these stars, consisting of ~6 million pixels at 29.4-minute intervals, is downlinked only every ~30 days. Additional low-rate Xband communications contacts are conducted with the spacecraft twice a week to downlink a small subset of the science data. This paper describes how we assess and monitor the performance of the photometer and the pointing stability of the spacecraft using such a sparse data set.
Integrated subsystem health diagnostics is an area where major improvements have been identified for potential implementation into the design of new reusable launch vehicles (RLVs) in order to reduce life cycle costs, to increase safety margins, and to improve mission reliability. This talk summarizes a joint effort between NASA Ames and industry partners to develop rapid non-contact diagnostic tools for health and performance monitoring of thermal protection systems (TPS) on future RLVs. The specific goals for TPS health monitoring are to increase the speed and reliability of TPS inspections for improved operability at lower cost. The technology being developed includes a 3-D laser scanner for examining the exterior surface of the TPS, and a subsurface microsensor suite for monitoring the health and performance of the TPS. The sensor suite consists of passive overlimit sensors and sensors for continuous parameter monitoring in flight. The sensors are integrated with radio-frequency identification (RFID) microchips to enable wireless communication of-the sensor data to an external reader that may be a hand-held scanner or a large portal. Prototypes of the laser system and both types of subsurface sensors have been developed. The laser scanner was tested on Shuttle Orbiter Columbia and was able to dimension surface chips and holes on a variety of TPS materials. The temperature-overlimit microsensor has a diameter under 0.05 inch (suitable for placement in gaps between ceramic TPS tiles) and can withstand 700 F for 15 minutes.
Development of onboard checkout equipment and performance monitoring capability for space shuttles - Vol. 1
The computer software used for telecommunications performance analysis and monitoring is discussed. The utilization of the TPAP analysis program for the Viking 1975 project and the Voyager 1977 project is described. The functional and design requirements for the successor system, TPAS, are also given.
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 lack 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 have to be terminated. In this paper, we propose an innovative methodology for monitoring and trace representation that offers a middle ground. The user can trace-off trace data size vs. quality incrementally. Specifically, 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 for the entire execution. With the help of a few CFD examples, we illustrate the use of our technique in performance tuning. We also compare quantitatively, the quality of the traces we collected vs. event traces.