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.
Computer program handles data from low-energy nuclear physics experiments which utilize the ND-160 pulse-height analyzer and the PHYLIS computing system. The program allows experimenters to choose from about 50 different basic data-handling functions and to prescribe the order in which these functions will be performed.
An extensible Java(TradeMark) software framework supports the construction and operation of graphical user interfaces (GUIs) for distributed computing systems typified by ground control systems that send commands to, and receive telemetric data from, spacecraft. Heretofore, such GUIs have been custom built for each new system at considerable expense. In contrast, the present framework affords generic capabilities that can be shared by different distributed systems. Dynamic class loading, reflection, and other run-time capabilities of the Java language and JavaBeans component architecture enable the creation of a GUI for each new distributed computing system with a minimum of custom effort. By use of this framework, GUI components in control panels and menus can send commands to a particular distributed system with a minimum of system-specific code. The framework receives, decodes, processes, and displays telemetry data; custom telemetry data handling can be added for a particular system. The framework supports saving and later restoration of users configurations of control panels and telemetry displays with a minimum of effort in writing system-specific code. GUIs constructed within this framework can be deployed in any operating system with a Java run-time environment, without recompilation or code changes.
Development of a permanent data system for SMD tests was studied that would simulate all elements of the shuttle onboard, telemetry, and ground data systems that are involved with spacelab operations. The onboard data system (ODS) and the ground data system (GDS) were utilized. The air-to-ground link was simulated by a hardwired computer-to-computer interface. A patch board system was used on board to select experiment inputs, and the downlink configuration from the ODS was changed by a crew keyboard entry to support each experiment. The ODS provided a CRT display of experiment parameters to enable the crew to monitor experiment performance. An onboard analog system, with recording capability, was installed to handle high rate data and to provide a backup to the digital system. The GDS accomplished engineering unit conversion and limit sensing, and provided realtime parameter display on CRT's in the science monitoring area and the test control area.
Accurate outage location is essential for expediting post-outage power restoration, minimizing outage duration, and enhancing the resilience of distribution networks. With the advent of advanced metering infrastructure, data-driven outage location methods have significantly advanced beyond traditional approaches that rely on manual inspections. However, existing methods still face critical challenges, like reliance on single-source data, limited ability to handle partially observable systems or difficulties with loop networks. To the best of our knowledge, no single approach has comprehensively addressed all of these challenges at once. To this end, this paper proposes a comprehensive multisource data fusion framework for outage locations via probabilistic graph networks. The framework consists of three key phases. First, a novel method for reconstituting distribution networks with loops is developed, transforming looped networks into multiple radial subnetworks that retain all outage causalities of the original network. Second, Bayesian network (BN) models are established for each subnetwork, integrating multiple data sources and network structures. Finally, a joint Gibbs sampling mechanism, featuring forward and backward information flow, is designed to merge data from separate BN models and maximize the utilization of limited evidence, ensuring accurate outage location identification. In conclusion, the framework was validated on two modified public test systems, and comparative studies confirmed its effectiveness.
To improve prediction accuracy, the DebriSat project was conceived by NASA and DoD to update existing standard break-up models. Updating standard break-up models require detailed fragment characteristics such as physical size, material properties, bulk density, and ballistic coefficient. For the DebriSat project, a representative modern LEO spacecraft was developed and subjected to a laboratory hypervelocity impact test and all generated fragments with at least one dimension greater than 2 mm are collected, characterized and archived. Since the beginning of the characterization phase of the DebriSat project, over 130,000 fragments have been collected and approximately 250,000 fragments are expected to be collected in total, a three-fold increase over the 85,000 fragments predicted by the current break-up model. The challenge throughout the project has been to ensure the integrity and accuracy of the characteristics of each fragment. To this end, the post hypervelocity-impact test activities, which include fragment collection, extraction, and characterization, have been designed to minimize handling of the fragments. The procedures for fragment collection, extraction, and characterization were painstakingly designed and implemented to maintain the post-impact state of the fragments, thus ensuring the integrity and accuracy of the characterization data. Each process is designed to expedite the accumulation of data, however, the need for speed is restrained by the need to protect the fragments. Methods to expedite the process such as parallel processing have been explored and implemented while continuing to maintain the highest integrity and value of the data. To minimize fragment handling, automated systems have been developed and implemented. Errors due to human inputs are also minimized by the use of these automated systems. This paper discusses the processes and challenges involved in the collection, extraction, and characterization of the fragments as well as the time required to complete the processes. The objective is to provide the orbital debris community an understanding of the scale of the effort required to generate and archive high quality data and metadata for each debris fragment 2 mm or larger generated by the DebriSat project.
The principal industrial users of land observation satellite systems are the geological industries; oil/gas, mining, and engineering/environmental companies. The primary system used is LANDSAT/MSS. Currently, use is also being made of the limited amounts of SKYLAB photography, SEASAT and SIR-A radar, and the new LANDSAT/TM data available. Although considered experimental, LANDSAT data is now used operationally by several hundred exploration and engineering companies worldwide as a vastly improved geological mapping tool to help direct more expensive geophysical and drilling phases, leading to more efficient decision-making and results. Future needs include global LANDSAT/TM; higher spatial resolution; stereo and radar; improved data handling, processing distribution and archiving systems, and integrated geographical information systems (GIS). For a promising future, governments must provide overall continuity (government and/or private sector) of such systems, insure continued government R and D, and commit to operating internationally under the civil Open Skies policy.
Description of a number of plasma, particle, and field detectors used on rocket investigations in and above the earth's atmosphere. Emphasis is on magnetospheric and solar-interplanetary studies. A balloon-borne X-ray telescope system with 20-min pointing accuracy is discussed. A PCM telemetry system used on both balloons and rockets to handle scientific data is described which includes a simple Doppler ranging system that gives location to 1.5 km. A system to reduce and analyze PCM data on the ground is discussed.
A management construct is described which forms part of an overall landscape ecological planning model which has as a principal objective the extension of the traditional descriptive land use mapping capabilities of geographic information systems into land management realms. It is noted that geographic information systems appear to be moving to more comprehensive methods of data handling and storage, such as relational and hierarchical data management systems, and a clear need has simultaneously arisen therefore for planning assessment techniques and methodologies which can actually use such complex levels of data in a systematic, yet flexible and scenario dependent way. The descriptive of mapping method proposed broaches such issues and utilizes a current New England bioenergy scenario, stimulated by the use of hardwoods for household heating purposes established in the post oil crisis era and the increased awareness of the possible landscape and ecological ramifications of the continued increasing use of the resource.
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.
The CMS[1] experiment manages a large-scale data infrastructure, currently handling over 200 PB of disk and 500 PB of tape storage and transferring more than 1 PB of data per day on average between various WLCG[2] sites. Utilizing Rucio[3] for high-level data management, FTS[4] for data transfers, and a variety of storage and network technologies at the sites, CMS confronts inevitable challenges due to the system’s growing scale and evolving nature. Key challenges include managing transfer and storage failures, optimizing data distribution across different storages based on production and analysis needs, implementing necessary technology upgrades and migrations, and efficiently handling user requests. The data management team has established comprehensive monitoring to supervise this system and has successfully addressed many of these challenges. The team’s efforts aim to ensure data availability and protection, minimize failures and manual interventions, maximize transfer throughput and resource utilization, and provide reliable user support. This paper details the operational experience of CMS with its data management system in recent years, focusing on the encountered challenges, the effective strategies employed to overcome them and the ongoing challenges as we prepare for future demands.
Study tasks for the command and data handling subsystems have been directed to: (1) determining ground data systems, (GDS) interfaces and deep space network (DSN) changes, if required, (2) defining subsystem requirements, (3) surveying existing hardware that could be used or modified to meet subsystem requirements, and (4) establishing a baseline design. Study of the existing GDS led to the conclusion that the Viking configuration GDS can be used with only minor changes required for the Pioneer Venus baseline. Those changes required are associated with providing a predetection recording capability used during probe entry and descent. Subsystem requirements were first formulated with sufficient latitude so that surveys of existing hardware could lead to low cost hardware which, in turn, could modify more narrowly defined subsystem requirements.
The Space Technology-7 (ST-7) Disturbance Reduction System (DRS) is an experiment package aboard the European Space Agency (ESA) LISA Pathfinder spacecraft, launched on December 3, 2015. DRS consists of three primary components: Colloidal MicroNewton Thrusters (CMNTs), an Integrated Avionics Unit (IAU), and flight-software implementing the Command and Data Handling (C&DH) and Dynamic Control System (DCS) algorithms. The CMNTs were designed to provide thrust from 5 to 30 micro Newton, with thrust controllability and resolution of 0.1 micro Newton and thrust noise of 0.1 micro Newton/(square root of (Hz)) in the measurement band from 1-30 mHz. The IAU hosts the C&DH and DCS flight software, as well as interfaces with both the CMNT electronics and the LISA Pathfinder spacecraft. When in control, the DCS uses star tracker attitude data and capacitive or optically-measured position and attitude information from LISA Pathfinder and the LISA Technology Package (LTP) to control the attitude and position of the spacecraft and the two test masses inside the LTP. After completion of the nominal ESA LISA Pathfinder mission, the DRS experiment was commissioned followed by its nominal mission. DRS operations extended over the next five months, interspersed with station keeping, anomaly resolution, and periods where control was handed back to LISA Pathfinder for them to conduct further experiments. The primary DRS mission ended on December 6, 2016, with the experiment meeting all of its Level 1 requirements. The DCS, developed at the NASA Goddard Space Flight Center, consists of five spacecraft control modes and six test mass control modes, combined into six 'DRS Mission Modes'. Attitude Control and Zero-G were primarily used to control the spacecraft during initial handover and during many of the CMNT characterization experiments. The other Mission Modes, Drag Free Low Force, 18-DOF Transitional, and 18-DOF, were used to provide drag-free control of the spacecraft about the test masses. This paper will discuss the performance of these DCS spacecraft and test mass control modes. Flight data will be shown from each mode throughout the mission, both from nominal operations and during various flight experiments. The DCS team also made some changes to controller, filter, and limit parameters during operations; the motivation and results of these changes will be shown and discussed.
Preliminary data of handling, thermal response, propulsion system, noise, and sonic boom for XB-70
Grand Tour missions centralized data handling, describing computer aided telemetry system and self testing and repairing control computer
Results are summarized of a common scientific probe study to explore the atmospheres of Saturn and Uranus. This was a three-month follow-on effort to the Outer Planet Entry Probe System study. The report presents: (1) a summary, conclusions and recommendations of this study, (2) parametric analysis conducted to support the two system definitions, (3) common Saturn/Uranus probe system definition using the Science Advisory Group's exploratory payload and, (4) common Saturn/Uranus probe system definition using an expanded science complement. Each of the probe system definitions consists of detailed discussions of the mission, science, system and subsystems including telecommunications, data handling, power, pyrotechnics, attitude control, structures, propulsion, thermal control and probe-to-spacecraft integration. References are made to the contents of the first three volumes where it is feasible to do so.
An onboard coherent optical data processing system was designed to handle large information content of imagery at high speeds, reduce redundancy in picture transmission, and detect specific image features. Theoretically derived Fourier transform characteristics for simple but representative two dimensional images served as a basis for predicting expected features of actual target images. Fourier transformation and spatial filtering of coherent optical images was accomplished theoretically and in the laboratory. The effect of various parameters such as optical aperature, incidence angles, the transparency assumption, the thin lens approximation on resolution, and performance of the system are predicted and tested.
The Galileo Orbiter differs markedly from its Mariner, Viking and Voyager predecessors in many aspects of its design, as dictated by its unique mission characteristics. Novel design features include a dual spin configuration, long life bipropellant propulsion, radioisotope thermoelectric generators, and a star scanner. Other major changes are related to Space Shuttle Orbiter compatibility. The selection of a distributed data system employing a high speed data bus represents a major advance over Voyager systems. The command, control and data handling functions for the Orbiter are merged into a single software-controlled subsystem. The paramount importance of software development in the design of Galileo subsystems is noted, in view of the requirement for total engineering and science data acquisition process reprogrammability.
The scientific experiments package to be carried by the Proteus system takes the form of an Instrument Load carried into orbit by a Space Shuttle, and there mated to a Proteus spacecraft with the Shuttle's Remote Manipulator System. The Proteus system extends to ground support equipment, development tools, and communications, as well as the orbiting satellites. It is expected that Proteus will be able to triple the number of Explorer missions while staying within the current budgetary allocation for such missions. The Proteus spacecraft encompasses a system interface assembly plug, a data handling module, remote interface units, and a power distribution module.