ISIS users manual
A user manual for the interactive software invocation system (ISIS) is presented. The operational concepts and syntax of the interactive programming language are documented.
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.
A user manual for the interactive software invocation system (ISIS) is presented. The operational concepts and syntax of the interactive programming language are documented.
The OTV configurations, operations and requirements planned for the period from the 1980's to the 1990's were reviewed and a propellant transfer experiment was designed that would support the needs of these advanced OTV operational concepts. An overall integrated propellant management technology plan for all NASA centers was developed. The preliminary cost estimate (for planning purposes only) is $56.7 M, of which approximately $31.8 M is for shuttle user costs.
Shuttle missions have usually been viewed as being devoted to a single mission mode. But full utilization of the STS capabilities as a platform for space research dictates a flexible strategy toward payload integration and mission design. Simple interfaces, single disciplines, and large design and resource margins point the way toward larger payload integration and operation costs. Payloads for early missions (i.e., OSTA-1, OSS-1, and MEA) are used as illustrations to support this argument. The implications of this approach for future NASA plans as well as for new STS operational concepts are considered.
The study was conducted in three phases: a functional requirements phase; a functional architecture phase; and a design plan phase. The major emphasis was on the functional architecture phase and the approaches used for its functional hierarchy, operations concept, and interfaces.
The technical feasibility of the Satellite Power System (SPS) is discussed. The development of feasible operational concepts and conceptualization of specific construction tasks are examined. The logic flow of functional analyses of both the rectenna and the satellite is illustrated. Constraints placed upon the construction processes and equipment by the satellite design are outlined. The construction tasks, when defined and combined into an integrated schedule establish, a time line for construction mass flow demands to be satisfied by the space transportation systems. An example of satellite constructive demands and HLLV delivery capabilities is given.
Results are reported of an opinion survey of selected individuals at the decision-making level within the five major manufacturers of transport aircraft in the United States and Europe. Opinions were obtained concerning both possible and probable existence of over 50 compatibility-related characteristics of transport aircraft in use in the years 1990, 2000, and 2010. The maximum size of aircraft is expected to increase, at a roughly uniform rate, to the year 2010 by 85 percent in passengers, 55 percent in airfreighter payload, and 35 percent in gross weight weight. Companion to the expected growth in payloads and gross weight was the identification of probable increases in aircraft geometrical dimensions and component capability, and use of fully double-decked passenger compartments. Wing span will increase considerably more than normally expected to provide wings of higher aspect ratio. New aircraft features coming into probable use include large turboprops, synthetic jet-A fuel, winglets, wake-vortex-reducing devices and laminar flow control. New operational concepts considered probable include steep approaches, high-speed turnoffs, and taxiway towing for the aircraft, plus passenger bypass of the terminal building, expedited handling of belly cargo and an intermodal cargo container for the payloads.
A 9-element focal plane detector array and signal processing electronics was developed and delivered in December 1977. It was integrated into a thermal infrared imaging system using LSI microprocessor image processing and CRT display. After three years of laboratory operation, the focal plane has demonstrated high reliability and performance. On the basis of the 9-channel breadboard, the 90-element Aircraft Pushbroom IR/CCD Focal Plane Development Program was funded in October 1977. A follow-on program was awarded in July 1979, for the construction of a field test instrument and image processing facility. The objective of this project was to demonstrate thermal infrared pushbroom hard-copy imagery. It is pointed out that the successful development of the 9-element and 90-element thermal infrared hybrid imaging systems using photoconductive (Hg,Cd)Te has verified the operational concept of 8 to 14 micrometer pushbroom scanners.
In November 1981 the first scientific payload was carried on board the second flight of the Space Shuttle. The principal instrument on that flight was a synthetic aperture radar. This paper is concerned with the operational concepts developed to achieve the objective of terrestrial geologic mapping by radar from earth orbit for this mission. Computer software was developed as an aid to mission design prior to the mission and as a replanning tool used during the mission: The first step in the development of software for future missions where such tools will become indispensable to meet the apparently contradictory objectives of complex observations and low cost.
The Tracking and Data Relay Satellite System (TDRSS) Network (TN) has been developed to provide services to all NASA User spacecraft in near-earth orbits. Three inter-relating entities will provide these services. The TN has been transformed from a network continuously changing to meet User specific requirements to a network which is flexible to meet future needs without significant changes in operational concepts. Attention is given to the evolution of the TN network, the TN capabilities-space segment, forward link services, tracking services, return link services, the three basic capabilities, single access services, multiple access services, simulation services, the White Sands Ground Terminal, the NASA communications network, and the network control center.
This paper discusses the status of NASA's efforts to define the scope of a space station program. It presents NASA's rationale for a space station, architectural, technological and operational concepts that would enhance its capabilities, status of planning, how it would be used, opportunities for commercialization, and the potential for international participation in the program.
Several new facilities for ultraviolet astronomy are under construction or study for launch within the coming decade. These include the Hubble Space Telescope to be launched in 1986 with instruments for spectroscopy, imaging, and photopolarimetry in the ultraviolet; the ASTRO Spacelab payload, also to be launched in 1986 with a similar range of instrumentation; STARLAB, a combined Canadian, Australian and U.S. mission concentrating primarily on imagery; and the Far Ultraviolet Spectroscopic Explorer (FUSE), which was renamed COLUMBUS. COLUMBUS is currently under study by NASA and ESA as a future joint mission for spectroscopic studies of astrophysical plasmas covering a temperature range from approximately 10 to the 3rd power to approximately 10 to the 7th power k. In order to achieve this objective, the optics should be optimized for wavelengths below 1200 Angstroms, with a total wavelength range from approximately 2000 to approximately 100 Angstroms. The operational concept will be based on experience with IUE, but changes in communications techniques since IUE was designed suggest some interesting new approaches to observing.
In the Astro mission series (initial flight planned for March, 1986), the Shuttle will be used as a dedicated stellar astronomy observatory. A modified Spacelab pallet is to be used for the Astro payload, which will consist of three ultraviolet (UV) telescopes and a wide field camera mounted together on a single gimbal mount called the Inertial Pointing System (IPS). Three flights of 7-10 days duration are to be made with the same payload at intervals of 8-9 months. Previous experience has shown that changes in design requirements are inevitable, and the evolution of operational concepts will effect changes in scheduling algorithm software. For these reasons, the design goals of the Astron algorithm and its family of auxiliary software modules have been related to functional modularity, constraint flexibility, user friendliness, and 'light' input requirements. Attention is given to hardware characteristics, environmental constraints, the basic criteria function, 'Cinderella' logic, counters and constraints, and scheduling trends.
The objective is to develop a systematic approach for defining and evaluating alternative strategies for developing data processing and management systems. Various techniques and systems engineering tools are integrated to develop and present to the analysts and users an early definition of services desired along with probable and compatible operations concepts. Information is presented in the form of outlines, graphs and charts.
A software development plan is presented for the definition, design, and implementation of the Space Station (SS) Payload Mission Planning System (MPS). This plan is an evolving document and must be updated periodically as the SS design and operations concepts as well as the SS MPS concept evolve. The major segments of this plan are as follows: an overview of the SS MPS and a description of its required capabilities including the computer programs identified as configurable items with an explanation of the place and function of each within the system; an overview of the project plan and a detailed description of each development project activity breaking each into lower level tasks where applicable; identification of the resources required and recommendations for the manner in which they should be utilized including recommended schedules and estimated manpower requirements; and a description of the practices, standards, and techniques recommended for the SS MPS Software (SW) development.
Activities performed to match ground aperture requirements for the Neptune encounter in August 1989 with the expected capabilities of the JPL Deep Space Network (DSN) are discussed. Ground aperture requirements, DSN capabilities, and the capabilities of other agencies are reviewed. The design and configurations of the receiver subsystem, combiner subsystem, monitor and control subsystem, recording subsystem, and supporting subsystems are described. The implementation of the Very Large Array-Goldstone Telemetry Array is discussed, and the differences involved with the Parkes-Canberra Telemetry Array implementation are highlighted. The operational concept is addressed.
The High Resolution Imaging Spectrometer (HIRIS) and Moderate Resolution Imaging Spectrometer (MODIS) Data Systems Working Group was formed in September 1988 with representatives of the MODIS Data System Study Group and the HIRIS Project Data System Design Group to collaborate in the development of requirements on the EosDIS necessary to meet the science objectives of the two facility instruments. A major objective was to identify and promote commonality between the HIRIS and MODIS data systems, especially from the science users' point of view. A goal was to provide a base set of joint requirements and specifications which could easily be expanded to a Phase-B representation of the needs of the science users of all EOS instruments. This document describes the points of commonality and difference between the Level-II Requirements, Operations Concepts, and Systems Specifications for the ground data systems for the MODIS and HIRIS instruments at their present state of development.
The design and implementation, in Ada, of the Fault Detection, Isolation, and Reconfiguration (FDIR) Manager for the triply redundant, tightly synchronized, Fault Tolerant Processor (FTP) are covered. It also examines the suitability of Ada, in the context of the FTP, for real time control tasks. The operational concepts behind the FTP are explained, and the structure of the resultant Ada code is discussed.
The Tracking and Data Relay Satellite System (TDRSS) is an integral part of the overall NASA Space Network (SN) that will continue to evolve into the 1990's. Projections for the first decade of the 21st century indicate the need for an SN evolution that must accommodate growth int he LEO user population and must further support the introduction of new/improved user services. A central ingredient of this evolution is an Advanced TDRSS (ATDRSS) follow-on to the current TDRSS that must initiate operations by the late 1990's in a manner that permits an orderly transition from the TDRSS to the ATDRSS era. An SN/ATDRSS architectural and operational concept that will satisfy the above goals is being developed. To this date, an SN/ATDRSS baseline concept was established that provides users with an end-to-end data transport (ENDAT) service. An expanded description of the baseline ENDAT concept, from the user perspective, is provided with special emphasis on the TDRSS/ATDRSS evolution. A high-level description of the end-to-end system that identifies the role of ATDRSS is presented; also included is a description of the baseline ATDRSS architecture and its relationship with the TDRSS 1996 baseline. Other key features of the ENDAT service are then expanded upon, including the multiple grades of service, and the RF telecommunications/tracking services to be available. The ATDRSS service options are described.