Alleged German Atrocities. England\u27s Most Effective Weapon.

p. cm

USAir: Balancing Terminal Facilities and Runway Capacity at Pittsburgh

As a result of expansion and acquisition, USAir has experienced major growth in flight operations. In an effort to accommodate this expansion, a major construction project, called the Midfield Terminal project, is underway at USAir\u27s major hub, Greater Pittsburgh International Airport (PIT). The Midfield Terminal will result in a 60 percent increase in gate capacity for USAir and lower operating costs due to its location. However, increased gates infer increased flight frequencies. PIT already operates near capacity during peak periods and runway expansion has only been discussed. This paper evaluates the conditions of USAir at PIT with regard to the lack of landing facilities and gate expansion. There will be a dire need for additional runway capacity at PIT if USAir is to take advantage of the additional gates and the cost savings associated with those gates. Suggestions are made to avoid a critical imbalance of airport facilities

On Verifying Causal Consistency

Causal consistency is one of the most adopted consistency criteria for distributed implementations of data structures. It ensures that operations are executed at all sites according to their causal precedence. We address the issue of verifying automatically whether the executions of an implementation of a data structure are causally consistent. We consider two problems: (1) checking whether one single execution is causally consistent, which is relevant for developing testing and bug finding algorithms, and (2) verifying whether all the executions of an implementation are causally consistent. We show that the first problem is NP-complete. This holds even for the read-write memory abstraction, which is a building block of many modern distributed systems. Indeed, such systems often store data in key-value stores, which are instances of the read-write memory abstraction. Moreover, we prove that, surprisingly, the second problem is undecidable, and again this holds even for the read-write memory abstraction. However, we show that for the read-write memory abstraction, these negative results can be circumvented if the implementations are data independent, i.e., their behaviors do not depend on the data values that are written or read at each moment, which is a realistic assumption.Comment: extended version of POPL 201

IMPAC: An Integrated Methodology for Propulsion and Airframe Control

The National Aeronautics and Space Administration is actively involved in the development of enabling technologies that will lead towards aircraft with new/enhanced maneuver capabilities such as Short Take-Off Vertical Landing (STOVL) and high angle of attack performance. Because of the high degree of dynamic coupling between the airframe and propulsion systems of these types of aircraft, one key technology is the integration of the flight and propulsion control. The NASA Lewis Research Center approach to developing Integrated Flight Propulsion Control (IFPC) technologies is an in-house research program referred to as IMPAC (Integrated Methodology for Propulsion and Airframe Control). The goals of IMPAC are to develop a viable alternative to the existing integrated control design methodologies that will allow for improved system performance and simplicity of control law synthesis and implementation, and to demonstrate the applicability of the methodology to a supersonic STOVL fighter aircraft. Based on some preliminary control design studies that included evaluation of the existing methodologies, the IFPC design methodology that is emerging at the Lewis Research Center consists of considering the airframe and propulsion system as one integrated system for an initial centralized controller design and then partitioning the centralized controller into separate airframe and propulsion system subcontrollers to ease implementation and to set meaningful design requirements for detailed subsystem control design and evaluation. An overview of IMPAC is provided and detailed discussion of the various important design and evaluation steps in the methodology are included