Microcomputer versus mainframe simulations: A case study

The research was conducted to two parts. Part one consisted of a study of the feasibility of running the Space Transportation Model simulation on an office IBM-AT. The second part was to design simulation runs so as to study the effects of certain performance factors on the execution of the simulation model. The results of this research are given in the two reports which follow: Microcomputer vs. Mainframe Simulation: A Case Study and Fractional Factorial Designs of Simulation Runs for the Space Transportation System Operations Model. In the first part, a DOS batch job was written in order to simplify the execution of the simulation model on an office microcomputer. A comparison study was then performed of running the model on NASA-Langley's mainframe computer vs. running on the IBM-AT microcomputer. This was done in order to find the advantages and disadvantages of running the model on each machine with the objective of determining if running of the office PC was practical. The study concluded that it was. The large number of performance parameters in the Space Transportation model precluded running a full factorial design needed to determine the most significant design factors. The second report gives several suggested fractional factorial designs which require far fewer simulation runs in order to determine which factors have significant influence on results

Oscillator strength trends in group IVb homologous ions

Shock tube data are used to examine the systematic f value behavior in prominent visible transition arrays (ns-np, np-(n+l)s, np-nd) for the homologous emitter sequence Si 11, Ge 11, Sn 11, and Pb 11. Regularities found for these data are compared with trends in lighter elements. Agreements and s disparities with theoretical and experimental oscillator strengths from the literature are noted

General purpose simulation system of the data management system for space shuttle mission 18

The simulation program of the science and engineering data management system for the space shuttle is presented. The programming language used was General Purpose Simulation System V (OS). The data flow was modeled from its origin at the experiments or subsystems to transmission from the space shuttle. Mission 18 was the particular flight chosen for simulation. First, the general structure of the program is presented and the trade studies which were performed are identified. Inputs required to make runs are discussed followed by identification of the output statistics. Some areas for model modifications are pointed out. A detailed model configuration, program listing and results are included

Quantum Circuits Architecture

We present a method for optimizing quantum circuits architecture. The method is based on the notion of "quantum comb", which describes a circuit board in which one can insert variable subcircuits. The method allows one to efficiently address novel kinds of quantum information processing tasks, such as storing-retrieving, and cloning of channels.Comment: 10 eps figures + Qcircuit.te

General purpose simulation system of the data management system for Space Shuttle mission 18

A simulation program for the flow of data through the Data Management System of Spacelab and Space Shuttle was presented. The science, engineering, command and guidance, navigation and control data were included. The programming language used was General Purpose Simulation System V (OS). The science and engineering data flow was modeled from its origin at the experiments and subsystems to transmission from Space Shuttle. Command data flow was modeled from the point of reception onboard and from the CDMS Control Panel to the experiments and subsystems. The GN&C data flow model handled data between the General Purpose Computer and the experiments and subsystems. Mission 18 was the particular flight chosen for simulation. The general structure of the program is presented, followed by a user's manual. Input data required to make runs are discussed followed by identification of the output statistics. The appendices contain a detailed model configuration, program listing and results

Atomic spectroscopy with the shock tube

Spectroscopy of light atoms and ions and transition probability determinations using gas-driven shock tub

Surface behaviour of the pairing gap in semi-infinite nuclear matter

The $^1S_0$-pairing gap in semi-infinite nuclear matter is evaluated microscopically using the effective pairing interaction recently found explicitly in the coordinate representation starting from the separable form of the Paris NN-potential. Instead of direct iterative solution of the gap equation, a new method proposed by V.A.Khodel, V.V.Khodel and J.W.Clark was used which simplifies the procedure significantly. The gap $\Delta$ obtained in our calculations exibits a strong variation in the surface region with a pronounced maximum near the surface.Comment: 9 pages, 2 ps figure

Computer programs for reduction of microphotometer data

Five computer programs for analyzing magnetic tape recordings of digital data from microphotomete

Alfven-Wave Studies On Pretext

Fusion Research Cente

Safe abstractions of data encodings in formal security protocol models

When using formal methods, security protocols are usually modeled at a high level of abstraction. In particular, data encoding and decoding transformations are often abstracted away. However, if no assumptions at all are made on the behavior of such transformations, they could trivially lead to security faults, for example leaking secrets or breaking freshness by collapsing nonces into constants. In order to address this issue, this paper formally states sufficient conditions, checkable on sequential code, such that if an abstract protocol model is secure under a Dolev-Yao adversary, then a refined model, which takes into account a wide class of possible implementations of the encoding/decoding operations, is implied to be secure too under the same adversary model. The paper also indicates possible exploitations of this result in the context of methods based on formal model extraction from implementation code and of methods based on automated code generation from formally verified model