SEARCH · Engineering Papers

Results for “operator”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 991 records · Page 55

All sources NASA NTRS DOE OSTI

NASA NTRS1992

Time warp operating system version 2.7 internals manual

The Time Warp Operating System (TWOS) is an implementation of the Time Warp synchronization method proposed by David Jefferson. In addition, it serves as an actual platform for running discrete event simulations. The code comprising TWOS can be divided into several different sections. TWOS typically relies on an existing operating system to furnish some very basic services. This existing operating system is referred to as the Base OS. The existing operating system varies depending on the hardware TWOS is running on. It is Unix on the Sun workstations, Chrysalis or Mach on the Butterfly, and Mercury on the Mark 3 Hypercube. The base OS could be an entirely new operating system, written to meet the special needs of TWOS, but, to this point, existing systems have been used instead. The base OS's used for TWOS on various platforms are not discussed in detail in this manual, as they are well covered in their own manuals. Appendix G discusses the interface between one such OS, Mach, and TWOS.

Source record↗

NASA NTRS1993

Airport surface operations requirements analysis

This report documents the results of the Airport Surface Operations Requirements Analysis (ASORA) study. This study was conducted in response to task 24 of NASA Contract NAS1-18027. This study is part of NASA LaRC's Low Visibility Surface Operations program, which is designed to eliminate the constraints on all-weather arrival/departure operations due to the airport/aircraft ground system. The goal of this program is to provide the capability for safe and efficient aircraft operations on the airport surface during low visibility conditions down to zero. The ASORA study objectives were to (1) develop requirements for operation on the airport surface in visibilities down to zero; (2) survey and evaluate likely technologies; (3) develop candidate concepts to meet the requirements; and (4) select the most suitable concept based on cost/benefit factors.

Groce, John L.↗

NASA NTRS1993

Radioastron flight operations

Radioastron is a space-based very-long-baseline interferometry (VLBI) mission to be operational in the mid-90's. The spacecraft and space radio telescope (SRT) will be designed, manufactured, and launched by the Russians. The United States is constructing a DSN subnet to be used in conjunction with a Russian subnet for Radioastron SRT science data acquisition, phase link, and spacecraft and science payload health monitoring. Command and control will be performed from a Russian tracking facility. In addition to the flight element, the network of ground radio telescopes which will be performing co-observations with the space telescope are essential to the mission. Observatories in 39 locations around the world are expected to participate in the mission. Some aspects of the mission that have helped shaped the flight operations concept are: separate radio channels will be provided for spacecraft operations and for phase link and science data acquisition; 80-90 percent of the spacecraft operational time will be spent in an autonomous mode; and, mission scheduling must take into account not only spacecraft and science payload constraints, but tracking station and ground observatory availability as well. This paper will describe the flight operations system design for translating the Radioastron science program into spacecraft executed events. Planning for in-orbit checkout and contingency response will also be discussed.

Altunin, V. I.↗

NASA NTRS1993

Making adaptable systems work for mission operations: A case study

The Advanced Multimission Operations System (AMMOS) at NASA's Jet Propulsion Laboratory is based on a highly adaptable multimission ground data system (MGDS) for mission operations. The goal for MGDS is to support current flight project science and engineering personnel and to meet the demands of future missions while reducing associated operations and software development costs. MGDS has become a powerful and flexible mission operations system by using a network of heterogeneous workstations, emerging open system standards, and selecting an adaptable tools-based architecture. Challenges in developing adaptable systems for mission operations and the benefits of this approach are described.

Holder, Barbara E.↗

NASA NTRS1993

An approach to the design of operations systems

The MultiMission Control Team (MMCT) consists of mission controllers which provides Real-Time operations support for the Mars Observer project. The Real-Time Operations task is to insure the integrity of the ground data system, to insure that the configuration is correct to support the mission, and to monitor the spacecraft for the Spacecraft Team. Operations systems are typically developed by adapting operations systems from previous projects. Problems tend to be solved empirically when they are either anticipated or observed in testing. This development method has worked in the past when time was available for extensive Ops testing. In the present NASA budget environment, a more cost conscious design approach has become necessary. Cost is a concern because operations is an ongoing, continuous activity. Reducing costs entails reducing staff. Reducing staffing levels potentially increases the risk of mission failure. Therefore, keeping track of the risk level is necessary.

Chafin, Roy L.↗

NASA NTRS1993

PILOT: An intelligent distributed operations support system

The Real-Time Data System (RTDS) project is exploring the application of advanced technologies to the real-time flight operations environment of the Mission Control Centers at NASA's Johnson Space Center. The system, based on a network of engineering workstations, provides services such as delivery of real time telemetry data to flight control applications. To automate the operation of this complex distributed environment, a facility called PILOT (Process Integrity Level and Operation Tracker) is being developed. PILOT comprises a set of distributed agents cooperating with a rule-based expert system; together they monitor process operation and data flows throughout the RTDS network. The goal of PILOT is to provide unattended management and automated operation under user control.

Rasmussen, Arthur N.↗

NASA NTRS1993

Deep Space Network (DSN), Network Operations Control Center (NOCC) computer-human interfaces

The Network Operations Control Center (NOCC) of the DSN is responsible for scheduling the resources of DSN, and monitoring all multi-mission spacecraft tracking activities in real-time. Operations performs this job with computer systems at JPL connected to over 100 computers at Goldstone, Australia and Spain. The old computer system became obsolete, and the first version of the new system was installed in 1991. Significant improvements for the computer-human interfaces became the dominant theme for the replacement project. Major issues required innovating problem solving. Among these issues were: How to present several thousand data elements on displays without overloading the operator? What is the best graphical representation of DSN end-to-end data flow? How to operate the system without memorizing mnemonics of hundreds of operator directives? Which computing environment will meet the competing performance requirements? This paper presents the technical challenges, engineering solutions, and results of the NOCC computer-human interface design.

Ellman, Alvin↗

NASA NTRS1993

HISPASAT launch and early operations phases: Computation and monitoring of geostationary satellite positioning

Since 1974, CNES, the French National Space Agency, has been involved in the geostationary launch and early operations phases (LEOP) of moving satellites from a transfer orbit delivered by a launcher to a geostationary point. During the operations and their preparation, the Flight Dynamics Center (FDC), part of CNES LEOP facilities, is in charge of the space mechanics aspects. What is noteworthy about the Spanish HISPASAT satellite positioning is that all the operations were performed on the customer's premises, and consequently the FDC was duplicated in Madrid, Spain. The first part of this paper is the FDC presentation: its role, its hardware configuration, and its space dynamics ground control system called MERCATOR. The second part of this paper details the preparation used by the FDC for the HISPASAT mission: hardware and software installation in Madrid, integration with the other entities, and technical and operational qualifications. The third part gives results concerning flight dynamics aspects and operational activities.

Brousse, Pascal↗

NASA NTRS1993

Expert diagnostics system as a part of analysis software for power mission operations

The operation of interplanetary spacecraft at JPL has become an increasingly complex activity. This complexity is due to advanced spacecraft designs and ambitious mission objectives which lead to operations requirements that are more demanding than those of any previous mission. For this reason, several productivity enhancement measures are underway at JPL within mission operations, particularly in the spacecraft analysis area. These measures aimed at spacecraft analysis include: the development of a multi-mission, multi-subsystem operations environment; the introduction of automated tools into this environment; and the development of an expert diagnostics system. This paper discusses an effort to integrate the above mentioned productivity enhancement measures. A prototype was developed that integrates an expert diagnostics system into a multi-mission, multi-subsystem operations environment using the Galileo Power / Pyro Subsystem as a testbed. This prototype will be discussed in addition to background information associated with it.

Harris, Jennifer A.↗

NASA NTRS1991

Analysis of the human operator subsystems

Except in low-bandwidth systems, knowledge of the human operator transfer function is essential for high-performance telerobotic systems. This information has usually been derived from detailed analyses of tracking performance, in which the human operator is considered as a complete system rather than as a summation of a number of subsystems, each of which influences the operator's output. Studies of one of these subsystems, the limb mechanics system, demonstrate that large parameter variations can occur that can have a profound effect on the stability of force-reflecting telerobot systems. An objective of this research was to decompose the performance of the human operator system in order to establish how the dynamics of each of the elements influence the operator's responses.

Jones, Lynette A.↗

NASA NTRS1994

Mars Pathfinder mission operations concepts

The Mars Pathfinder Project plans a December 1996 launch of a single spacecraft. After jettisoning a cruise stage, an entry body containing a lander and microrover will directly enter the Mars atmosphere and parachute to a hard landing near the sub-solar latitude of 15 degrees North in July 1997. Primary surface operations last for 30 days. Cost estimates for Pathfinder ground systems development and operations are not only lower in absolute dollars, but also are a lower percentage of total project costs than in past planetary missions. Operations teams will be smaller and fewer than typical flight projects. Operations scenarios have been developed early in the project and are being used to guide operations implementation and flight system design. Recovery of key engineering data from entry, descent, and landing is a top mission priority. These data will be recorded for playback after landing. Real-time tracking of a modified carrier signal through this phase can provide important insight into the spacecraft performance during entry, descent, and landing in the event recorded data is never recovered. Surface scenarios are dominated by microrover activity and lander imaging during 7 hours of the Mars day from 0700 to 1400 local solar time. Efficient uplink and downlink processes have been designed to command the lander and microrover each Mars day.

Sturms, Francis M., Jr.↗

NASA NTRS1994

Designing an autonomous environment for mission critical operation of the EUVE satellite

Since the launch of NASA's Extreme Ultraviolet Explorer (EUVE) satellite in 1992, there has only been a handful of occurrences that have warranted manual intervention in the EUVE Science Operations Center (ESOC). So, in an effort to reduce costs, the current environment is being redesigned to utilize a combination of off-the-shelf packages and recently developed artificial intelligence (AI) software to automate the monitoring of the science payload and ground systems. The successful implementation of systemic automation would allow the ESOC to evolve from a seven day/week, three shift operation, to a seven day/week one shift operation. First, it was necessary to identify all areas considered mission critical. These were defined as follows: (1) The telemetry stream must be monitored autonomously and anomalies identified. (2) Duty personnel must be automatically paged and informed of the occurrence of an anomaly. (3) The 'basic' state of the ground system must be assessed. (4) Monitors should check that the systems and processes needed to continue in a 'healthy' operational mode are working at all times. (5) Network loads should be monitored to ensure that they stay within established limits. (6) Connectivity to Goddard Space Flight Center (GSFC) systems should be monitored as well, not just for connectivity of the network itself but also for the ability to transfer files. (7) All necessary peripheral devices should be monitored. This would include the disks, routers, tape drives, printers, tape carousel, and power supplies. (8) System daemons such as the archival daemon, the Sybase server, the payload monitoring software, and any other necessary processes should be monitored to ensure that they are operational. (9) The monitoring system needs to be redundant so that the failure of a single machine will not paralyze the monitors. (10) Notification should be done by means of looking though a table of the pager numbers for current 'on call' personnel. The software should be capable of dialing out to notify, sending email, and producing error logs. (11) The system should have knowledge of when real-time passes and tape recorder dumps will occur and should know that these passes and data transmissions are successful. Once the design criteria were established, the design team split into two groups: one that addressed the tracking, commanding, and health and safety of the science payload and another group that addressed the ground systems and communications aspects of the overall system.

Abedini, Annadiana↗

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 NTRS1994

On the convergence of local approximations to pseudodifferential operators with applications

We consider the approximation of a class pseudodifferential operators by sequences of operators which can be expressed as compositions of differential operators and their inverses. We show that the error in such approximations can be bounded in terms of L(1) error in approximating a convolution kernel, and use this fact to develop convergence results. Our main result is a finite time convergence analysis of the Engquist-Majda Pade approximants to the square root of the d'Alembertian. We also show that no spatially local approximation to this operator can be convergent uniformly in time. We propose some temporally local but spatially nonlocal operators with better long time behavior. These are based on Laguerre and exponential series.

Hagstrom, Thomas↗

NASA NTRS1996

Remote manual operator for space station intermodule ventilation valve

The Remote Manual Operator (RMO) is a mechanism used for manual operation of the Space Station Intermodule Ventilation (IMV) valve and for visual indication of valve position. The IMV is a butterfly-type valve, located in the ventilation or air circulation ducts of the Space Station, and is used to interconnect or isolate the various compartments. The IMV valve is normally operated by an electric motor-driven actuator under computer or astronaut control, but it can also be operated manually with the RMO. The IMV valve RMO consists of a handle with a deployment linkage, a gear-driven flexible shaft, and a linkage to disengage the electric motor actuator during manual operation. It also provides visual indication of valve position. The IMV valve RMO is currently being prepared for qualification testing.

Guyaux, James R.↗

NASA NTRS1996

Performance of a spacecraft DC-DC converter breadboard modified for low temperature operation

A 1OW 3OV/5.OV push-pull dc-dc converter breadboard, designed by the Jet Propulsion Laboratory (JPL) with a +50 C to +5 C operating range for the Cassini space probe, was characterized for lower operating temperatures. The breadboard converter which failed to operate for temperatures below -125 C was then modified to operate at temperatures approaching that of liquid nitrogen (LN2). Associated with this low operating temperature range (greater than -196 C) was a variety of performance problems such as significant change in output voltage, converter switching instability, and failure to restart at temperatures below -154 C. An investigation into these problems yielded additional modifications to the converter which improved low temperature performance even further.

Gerber, Scott S.↗

NASA NTRS1996

UNIX-based operating systems robustness evaluation

Robust operating systems are required for reliable computing. Techniques for robustness evaluation of operating systems not only enhance the understanding of the reliability of computer systems, but also provide valuable feed- back to system designers. This thesis presents results from robustness evaluation experiments on five UNIX-based operating systems, which include Digital Equipment's OSF/l, Hewlett Packard's HP-UX, Sun Microsystems' Solaris and SunOS, and Silicon Graphics' IRIX. Three sets of experiments were performed. The methodology for evaluation tested (1) the exception handling mechanism, (2) system resource management, and (3) system capacity under high workload stress. An exception generator was used to evaluate the exception handling mechanism of the operating systems. Results included exit status of the exception generator and the system state. Resource management techniques used by individual operating systems were tested using programs designed to usurp system resources such as physical memory and process slots. Finally, the workload stress testing evaluated the effect of the workload on system performance by running a synthetic workload and recording the response time of local and remote user requests. Moderate to severe performance degradations were observed on the systems under stress.

Chang, Yu-Ming↗

NASA NTRS1996

Enhancing the ACE control center for the multiple uses of spacecraft integration and test and mission and science operations

In relation to the mandate to reduce space mission development and operations costs, the advanced composition explorer (ACE) will use a version of the Transportable Payload Operations Control Center (TPOCC) for its mission operations. It was determined during the phase B of the ACE project that a potential existed for substantial savings if the adaptation of the TPOCC for the ACE mission operations could include its adaptation for use as the primary component in the ground support equipment for the integration and testing of the ACE spacecraft, and for use as the basic component in the ACE science center. The implementation of this approach required the enhancement of the TPOCC requirements, changes in the development schedule and changes in the allocation and activities of the personnel responsible for the development of ACE operations. It is discussed how these issues, and the problems that arose, were addressed.

Snow, Frank↗