Search NASA⌕ Search

SEARCH · Search NASA

Results for “Event sequence”

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 19 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS1973

Event sequence detector

An event sequence detector is described with input units, each associated with a row of bistable elements arranged in an array of rows and columns. The detector also includes a shift register which is responsive to clock pulses from any of the units to sequentially provide signals on its output lines each of which is connected to the bistable elements in a corresponding column. When the event-indicating signal is received by an input unit it provides a clock pulse to the shift register to provide the signal on one of its output lines. The input unit also enables all its bistable elements so that the particular element in the column supplied with the signal from the register is driven to an event-indicating state.

Hanna, M. F.↗
NASA NTRS1973

Event-sequence detector

Detector consists of matrix of storage elements which are activated by coincidence of failure-voltage pulses and clock pulses. Clock frequency used for event sequence detector can be selected to provide time resolution demanded by test at hand.

Hanna, M. F.↗
NASA NTRS1994

Cusp/cleft auroral activity in relation to solar wind dynamic pressure, interplanetary magnetic field B(sub z) and B(sub y)

Continuous optical observations of cusp/cleft auroral activities within approximately equal to 09-15 MLT and 70-76 deg magnetic latitude are studied in relation to changes in solar wind dynamic pressure and interplanetary magnetic field (IMF) variability. The observed latitudinal movements of the cusp/cleft aurora in response to IMF B(sub z) changes may be explained as an effect of a variable magnetic field intensity in the outer dayside magnetosphere associated with the changing intensity of region 1 field-aligned currents and associated closure currents. Ground magnetic signatures related to such currents were observed in the present case (January 10, 1993). Strong, isolated enhancements in solar wind dynamic pressure (Delta p/p is greater than or equal to 0.5) gave rise to equatorward shifts of the cusp/cleft aurora, characteristic auroral transients, and distinct ground magnetic signatures of enhanced convection at cleft latitudes. A sequence of auroral events of approximately equal to 5-10 min recurrence time, moving eastward along the poleward boundary of the persistent cusp/cleft aurora in the approximately equal to 10-14 MLT sector, during negative IMF B(sub z) and B(sub y) conditions, were found to be correlated with brief pulses in solar wind dynamic pressure (0.1 is less than Delta p/p is less than 0.5). Simultaneous photometer observations from Ny Alesund, Svalbard, and Danmarkshavn, Greenland, show that the events often appeared on the prenoon side (approximately equal to 10-12 MLT), before moving into the postnoon sector in the case we study here, when IMF B(sub y) is less than 0. In other cases, similar auroral event sequences have been observed to move westward in the prenoon sector, during intervals of positive B(sub y). Thus a strong prenoon/postnoon asymmetry of event occurence and motion pattern related to the IMF B(sub y) polarity is observed. We find that this category of auroral event sequence is stimulated bursts of electron precipitation that originate from magnetosheath plasma that has accessed that dayside magnetosphere in the noon or near-noon sector, possibly at high latitudes, partly governed by the IMF orientation as well as by solar wind dynamic pressure pulses.

Sandholt, P. E.↗
NASA NTRS2024

Discrete Event Simulation-Based Timeline Validation Using R2U2

The Gateway Vehicle Systems Manager (VSM), the top-level software control system in a distributed, hierarchical Autonomous System Management Architecture is, like most modern spacecraft software control systems, heavily data-driven. For example, schedules (timelines) will be developed on the ground and, due to the high degree of autonomy, contain complex procedures involving conditional branching, variable timing, and resource contention resolution. In order to verify that an uploaded timeline will function correctly, it is necessary to explore the feasible set of possible executions. While it is possible to test a timeline using a mission simulation, the complexity of the system and duration of a timeline limits the number of trials and therefore the test coverage. To address this problem, the VSM team is using a discrete event system model that can rapidly generate from a timeline sets of event sequences using Monte Carlo techniques. To achieve rapid and trustworthy checking of the event sequences, we use an offline version of the runtime model checking tool R2U2. This presentation describes the approach the VSM team is using to implement the discrete event simulation and evaluate event sequences using R2U2. The presentation will discuss: 1. Description of the timelines by VSM in the context of VSM operations 2. Expansion of a timeline into a sequence of atomic events 3. Adjustment, in the Monte Carlo environment, of an event sequence to account for uncertainty, external events, and failures 4. Definition of R2U2 input and mission-time linear temporal logic files 5. Generation and use of R2U2 verdict sequences 6. Lessons learned and future work

Verification↗
NASA NTRS1996

Sequence-of-events-driven automation of the deep space network

In February 1995, sequence-of-events (SOE)-driven automation technology was demonstrated for a Voyager telemetry downlink track at DSS 13. This demonstration entailed automated generation of an operations procedure (in the form of a temporal dependency network) from project SOE information using artificial intelligence planning technology and automated execution of the temporal dependency network using the link monitor and control operator assistant system. This article describes the overall approach to SOE-driven automation that was demonstrated, identifies gaps in SOE definitions and project profiles that hamper automation, and provides detailed measurements of the knowledge engineering effort required for automation.

Hill, R., Jr.↗
NASA NTRS1996

Sequence-of-Events-Driven Automation of the Deep Space Network

In February 1995, sequence-of-events (SOE)-driven automation technology was demonstrated for a Voyager telemetry downlink track at DSS 13. This demonstration entailed automated generation of an operations procedure (in the form of a temporal dependency network) from project SOE information using artificial intelligence planning technology and automated execution of the temporal dependency network using the link monitor and control operator assistant system. This article describes the overall approach to SOE-driven automation that was demonstrated, identifies gaps in SOE definitions and project profiles that hamper automation, and provides detailed measurements of the knowledge engineering effort required for automation.

Hill, R., Jr.↗
NASA NTRS1994

The Sequence of Events generator: A powerful tool for mission operations

The functions and features of the sequence of events (SOE) and flight operations procedures (FOP) generator developed and used at DLR/GSOC for the positioning of EUTELSAT 2 satellites are presented. The SOE and FOP are the main operational documents that are prepared for nominal as well as for non-nominal mission execution. Their structure and application are described. Both of these documents are generated, validated, and maintained by a common software tool. Its main features and advantages are demonstrated. The tool has been improved continuously over the last 5 years. Due to its flexibility it can easily be applied to other projects and new features may be added.

Wobbe, Hubertus↗
NASA NTRS2008

Replacement Sequence of Events Generator

The soeWINDOW program automates the generation of an ITAR (International Traffic in Arms Regulations)-compliant sub-RSOE (Replacement Sequence of Events) by extracting a specified temporal window from an RSOE while maintaining page header information. RSOEs contain a significant amount of information that is not ITAR-compliant, yet that foreign partners need to see for command details to their instrument, as well as the surrounding commands that provide context for validation. soeWINDOW can serve as an example of how command support products can be made ITAR-compliant for future missions. This software is a Perl script intended for use in the mission operations UNIX environment. It is designed for use to support the MRO (Mars Reconnaissance Orbiter) instrument team. The tool also provides automated DOM (Distributed Object Manager) storage into the special ITAR-okay DOM collection, and can be used for creating focused RSOEs for product review by any of the MRO teams.

Fisher, Forest↗
NASA NTRS2003

[Columbia Sensor Diagrams]

A two dimensional graphical event sequence of the time history of relevant sensor information located in the left wing and wheel well areas of the Space Shuttle Columbia Orbiter is presented. Information contained in this graphical event sequence include: 1) Sensor location on orbiter and its associated wire bindle in X-Y plane; 2) Wire bundle routing; 3) Description of each anomalous sensor event; 4) Time annotation by (a) GMT, (b) time relative to LOS, (c) time history bar, and (d) ground track; and 5) Graphical display of temperature rise (based on delta temperature from point it is determined to be anomalous).

Source record↗
NASA NTRS2015

Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios

Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis. This approach becomes difficult when failure propagation paths change as a function of the system operation. Additionally, if the propagation paths represent interactions among even a modest number of components, the scenario count becomes combinatorially intractable. This paper presents an alternate approach for quantifying the probability of failure propagation in such a case. Rather than explicitly defining scenario sequences, simple physical models are created for each of the components. In this way, only the physical states and rules of component interactions must be defined, rather than event sequences for each individual scenario. Initiating failures are introduced into the system, either randomly or as defined by relative likelihood, and the failures cascade through the system via the interaction rules. This process is repeated using Monte Carlo methods and, as a result, the most probable scenarios “self-evolve” in terms of both sequence path and frequency. This approach was applied to failures occurring in the engine compartment of a space launch vehicle with four liquid rocket engines and four high-pressure helium tanks. Each engine was modeled with key components, such as turbomachinery, combustion chamber, propellant lines, and additional support systems. Three test cases were conducted with different high-energy engine failures. End results of interest included an additional engine-out failure and tank burst, which represent the loss-of-mission (LOM) and loss-of-crew (LOC) failure environments, respectively. Observations show that almost every scenario outcome is unique and that many scenarios involve complex chain reactions that are difficult to predict. This validates the usefulness of the modeling approach in assessing the overall risks to the crew during a launch vehicle abort.

Rocket Engine↗
NASA NTRS2005

A Search for Meteor Shower Signatures in the LDEF IDE Data

For 346 days after the deployment of the LDEF satellite on April 7, 1984, the tape recorder belonging to the Interplanetary Dust Experiment (DE) stored information on over 15,000 impacts made by submicron and larger-size particles on its metal oxide silicon (MOS) detectors. These detectors were mounted on trays facing in six orthogonal directions - LDEF ram and trailing edge, the poles of the LDEF orbit (north and south), and radially inward (towards the Earth) and outward (towards space). The 13.1 second time resolution provided by the IDE electronics, combined with the high sensitivity of the MOS detectors and large collecting area (approximately 1 sq.m) of the experiment, conclusively showed that the small particle environment at the LDEF altitude of 480 km was highly time-variable, with particle fluxes spanning over four orders of magnitude. A large number of the 15,000 impacts recorded by IDE occurred in groups, which were of two types - the spikes, single, isolated events of high intensity and the multiple orbit event sequences (MOES), which were series of events separated in time by integer multiples of the LDEF orbital period. Even though the spikes were generally more intense, the MOES could be quite long-lived, some lasting for many days. A previous paper by Cooke et al. attributed the MOES to impacts by man-made debris particles in orbits intersecting that of LDEF. The 20 day longevity of one of these events - termed the May Swarm - led to the suggestion that the debris particles must be con- stantly replenished by their source, as the orbits of micron sized particles will rapidly decay under the influence of radiation pressure and other non-gravitational forces, entering Earth's atmosphere after only a few revolutions. However, the date of onset of the May Swarm (May 22) and the long duration of this event may indicate a possible correlation with the annual Arietid meteor shower, which peaks around June 8. As this seemed to hold the promise of a less artificial explanation than a satellite or rocket body continuously dribbling debris, it was decided to take a fresh look at parts of the IDE data set in an attempt to detect meteor showers within the impact record.

Cooke, William J.↗
NASA NTRS1994

A software architecture for automating operations processes

The Operations Engineering Lab (OEL) at JPL has developed a software architecture based on an integrated toolkit approach for simplifying and automating mission operations tasks. The toolkit approach is based on building adaptable, reusable graphical tools that are integrated through a combination of libraries, scripts, and system-level user interface shells. The graphical interface shells are designed to integrate and visually guide a user through the complex steps in an operations process. They provide a user with an integrated system-level picture of an overall process, defining the required inputs and possible output through interactive on-screen graphics. The OEL has developed the software for building these process-oriented graphical user interface (GUI) shells. The OEL Shell development system (OEL Shell) is an extension of JPL's Widget Creation Library (WCL). The OEL Shell system can be used to easily build user interfaces for running complex processes, applications with extensive command-line interfaces, and tool-integration tasks. The interface shells display a logical process flow using arrows and box graphics. They also allow a user to select which output products are desired and which input sources are needed, eliminating the need to know which program and its associated command-line parameters must be executed in each case. The shells have also proved valuable for use as operations training tools because of the OEL Shell hypertext help environment. The OEL toolkit approach is guided by several principles, including the use of ASCII text file interfaces with a multimission format, Perl scripts for mission-specific adaptation code, and programs that include a simple command-line interface for batch mode processing. Projects can adapt the interface shells by simple changes to the resources configuration file. This approach has allowed the development of sophisticated, automated software systems that are easy, cheap, and fast to build. This paper will discuss our toolkit approach and the OEL Shell interface builder in the context of a real operations process example. The paper will discuss the design and implementation of a Ulysses toolkit for generating the mission sequence of events. The Sequence of Events Generation (SEG) system provides an adaptable multimission toolkit for producing a time-ordered listing and timeline display of spacecraft commands, state changes, and required ground activities.

Miller, Kevin J.↗
NASA NTRS2012

Virtual Machine Language 2.1

VML (Virtual Machine Language) is an advanced computing environment that allows spacecraft to operate using mechanisms ranging from simple, time-oriented sequencing to advanced, multicomponent reactive systems. VML has developed in four evolutionary stages. VML 0 is a core execution capability providing multi-threaded command execution, integer data types, and rudimentary branching. VML 1 added named parameterized procedures, extensive polymorphism, data typing, branching, looping issuance of commands using run-time parameters, and named global variables. VML 2 added for loops, data verification, telemetry reaction, and an open flight adaptation architecture. VML 2.1 contains major advances in control flow capabilities for executable state machines. On the resource requirements front, VML 2.1 features a reduced memory footprint in order to fit more capability into modestly sized flight processors, and endian-neutral data access for compatibility with Intel little-endian processors. Sequence packaging has been improved with object-oriented programming constructs and the use of implicit (rather than explicit) time tags on statements. Sequence event detection has been significantly enhanced with multi-variable waiting, which allows a sequence to detect and react to conditions defined by complex expressions with multiple global variables. This multi-variable waiting serves as the basis for implementing parallel rule checking, which in turn, makes possible executable state machines. The new state machine feature in VML 2.1 allows the creation of sophisticated autonomous reactive systems without the need to develop expensive flight software. Users specify named states and transitions, along with the truth conditions required, before taking transitions. Transitions with the same signal name allow separate state machines to coordinate actions: the conditions distributed across all state machines necessary to arm a particular signal are evaluated, and once found true, that signal is raised. The selected signal then causes all identically named transitions in all present state machines to be taken simultaneously. VML 2.1 has relevance to all potential space missions, both manned and unmanned. It was under consideration for use on Orion.

Riedel, Joseph E.↗
NASA NTRS1975

Apollo experience report: Guidance and control systems: Automated control system for unmanned mission AS-201

The Apollo command module heat shield and Apollo command and service module/Saturn launch vehicle structural integrity were evaluated in an unmanned test flight. An automated control system was developed to provide the mission event sequencing, the real-time ground control interface, and the backup attitude reference system for the unmanned flight. The required mission events, the design logic, the redundancy concept, and the ground-support-equipment concept are described and some development problem areas are discussed. The mission event time line and the real-time ground command list are included to provide an outline of the control system capabilities and requirements. The mission was accomplished with the automated control system, which functioned without flight anomalies.

Holloway, G. F.↗
NASA NTRS1995

LDEF Interplanetary Dust Experiment (IDE) results

The Interplanetary Dust Experiment (IDE) provided high time resolution detection of microparticle impacts on the Long Duration Exposure Facility satellite. Particles, in the diameter range from 0.2 microns to several hundred microns, were detected impacting on six orthogonal surfaces of the gravity-gradient stabilized LDEF spacecraft. The total sensitive surface area was about one square meter, distributed between LDEF rows 3 (Wake or West), 6 (South), 9 (Ram or East), 12 (North), as well as the Space and Earth ends of LDEF. The time of each impact is known to an accuracy that corresponds to better than one degree in orbital longitude. Because LDEF was gravity-gradient stabilized and magnetically damped, the direction of the normal to each detector panel is precisely known for each impact. The 11 1/2 month tape-recorded data set represents the most extensive record gathered of the number, orbital location, and incidence direction for microparticle impacts in low Earth orbit. Perhaps the most striking result from IDE was the discovery that microparticle impacts, especially on the Ram, South, and North surfaces, were highly episodic. Most such impacts occurred in localized regions of the orbit for dozens or even hundreds of orbits in what we have termed Multiple Orbit Event Sequences (MOES). In addition, more than a dozen intense and short-lived 'spikes' were seen in which impact fluxes exceeded the background by several orders of magnitude. These events were distributed in a highly non-uniform fashion in time and terrestrial longitude and latitude.

Oliver, John P.↗