DOCSLIB.ORG

Aerophysics Research Corporation Jtn-11 Technical Note

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Aerophysics Research Corporation Jtn-11 Technical Note NASA CR- AEROPHYSICS RESEARCH CORPORATION JTN-11 TECHNICAL NOTE (NASA-CR-141598) THE ENGINEERING DESIGN N75-1711 INTEGRATION (EDIN) SYSTEM (Aerophysics Research Corp., Houston Tex.) 239 p HC CSCL 09B Unclas G3/61 09633 THE ENGINEERING DESIGN INTEGRATION (EDIN) SYSTEM by: C. R. Glatt, G. N. Hirsch, G. E. Alford, W. N. Colquitt and S. J. Reiners prepared for: NATIONAL AERONAUTICS AND SPACE ADMINISTRATION Johnson Space Center Houston Texas 77058 Reproduced by NATIONAL TECHNICAL INFORMATION SERVICE US Department of Commerce Springfield, VA. 22151 'jis Cnoe N-OT ICE THIS DOCUMENT HAS BEEN REPRODUCED FROM THE BEST COPY FURNISHED US BY THE SPONSORING AGENCY. ALTHOUGH IT IS RECOGNIZED THAT CER- TAIN PORTIONS ARE ILLEGIBLE, IT IS BEING RE- LEASED IN THE INTEREST OF MAKING AVAILABLE AS MUCH INFORMATION AS POSSIBLE. 3. Recipient's Catalog No. 1. Report No2.2. Govern ent Accession No. NASA CR- 4.Title and Subtit!e 5. Report Date THE ENGINEERING DESIGN INTEGRATION (EDIN) SYSTEM. 6. Performing Organization Code 8. Performing Organization Report No. 7. Author(s) C. R. Glatt, G. N. Hirsch, G. E. Alford, W. N. Colquitt and S. J. Reiners 10. Work UnitNo. 9. Performing Organization Name and Address Aerophysics Research Corporation 11. Contract or Grant No. 18100 Nassau Bay Drive, #147 .Houston, Texas 77058 NAS9-13584 13. Type of Report and Period Covered 12. Sponsoring Agency Name and Address Contractor Report National Aeronautics and Space Administration- Agency Code Lyndon B. Johnson Space Center 14. Sponsoring 15. Supplementary Notes 16. Abstract The report provides a description of the Engineering :Design Integration (EDIN) System as it exists at Johnson Space Center. A discussion of the EDIN System capabilities and-applications are presented. 17. Key Words (Suggested by Author(s)) 18. Distribution Statement Design, synthesis, executive, Unclassified - Unlimited EDIN, data base, design simula- tion, multiple programming. 19. Securit;y Jlaif. (of this report) 20. Security Classif.(of this page) 21. Uncla;si fied Unclassified ior soloby the National Tchnical Information Service, Springfield, Virginia 22151 AEROPHYSICS RESEARCH CORPORATION . JTN-11 TECHNICAL NOTE THE ENGINEERING DESIGN INTEGRATION (EDIN) SYSTEM by: C. R. Glatt, G. N. Hirsch, G. E. Alford, W. N. Colquitt and S. J. Reiners prepared for: NATIONAL AERONAUTICS AND SPACE ADMINISTRATION Johnson Space Center Houston Texas 77058 December 1974 PREFACE This report describes the Engineering Design Integration (EDIN) system in operation at Johnson Space Center (JSC) at the com- pletion of the contract NAS9-13584, "Extended Optimal Design Integration (Extended ODIN) Computer Program." The study was carried out in the period from June 1973, through December 1974, with funds provided by the National Aeronautics and Space Admin- istration, Johnson Space Center, Engineering Analysis Division, Launch Analysis Section. The report specifically describes the Univac 1110, Exec 8 EDIN system at JSC. Earlier systems adapted to the CDC 6600 have been installed at the NASA Ames Research Center facility, the USAF Flight Dynamics Laboratory facility and the Langley Research Center facility. The original ODIN system was initially developed during 1971 and 1972 under parallel contracts with the National Aeronautics and Space Administration, LRC (NAS1-10692) and the USAF Flight Dynamics Laboratory (F33615-71-C-1480). The original system was developed for CDC 6000 series computers but the system has since been converted to the Univac 1100 series computer under contract (NAS9-12829) to NASA Johnson Space Center. The present contract (NAS9-13584) resulted in the expansion of the EDIN technology library, the development of a number of general and special purpose utilities, the development of a geometry technology module and an executive data processor. Numerous applications of the software developed have been accomplished, some of which are presented herein. iii TABLE OF CONTENTS Page SUMMARY.................. ... ............................. 1 INTRODUCTION................................................3 Study Objectives...................................... Study Approach ...................................... 4 THE.EDIN SYSTEM .............................. 6 THE COMPUTER ..... .. ........................ 6 Computer Operating System.................... ....... 6 The Executive System (Exec 8)..................8 System Processors ............................. 12 Language Processors........................... 13 Utility Processors ............................. 13 Subroutine Libraries...........................14 Applications Programs......................... 15 Computer Concepts and Definitions .................. 15 Absolute Element...............................15 Collection.................................... 15 Element ....................................... 15 Language Processor............................ 15 Program ....................................... 16 Processor...........................................16 Relocatable Element........................... 16 Symbolic Element..............................16 Catalogued File...............................16 Cycle ......................................... 16 Data Base...................................... 17 Data File.....................................17 External File Name ............................ 17 File .................... .................... 17 Internal File Name.............................17 Master File Directory ......................... 17 Private File..................................17 Program File..................................17 Public File ......................................17 Project............. .......................... 17 Qualifier....................................17 SDF Format .................................. 18 Temporary Program File (TPF$) ................. 18 Temporary File ................................. 18 Run Stream Concept.................................18 File Names and Element Names ....................... 19 Executive Control Statements ....................... 20 Control Statement Format....................... 20 Label Field.................................... 20 Operation Fields...............................21 Operand Fields............................... 21 Transparent Control Statements ................ 21 v PRECEDING PAGE BLANK NOT pTME TABLE OF CONTENTS (Continued) Page Summary of Control Statements...................21 File Utility Routines................... ............... 22 Systems Symbolic Processors ......................... 26 ELT Processor ......... o.................26 Data Processor .................. ..... ... .......26 ED Processor ................................... 27 CULL Processor..................................27 LIST Processor.................................27 The Collector ........................................29 DATA MANAGEMENT SYSTEM .................. .................. 31 DMAN Software Package..............................33 DMAN Usage ................... ............ 34 A Discussion of IT...............................35 A Discussion of IOP............................35 The DLG Processor...................................37 DLG Usage ...... ................................ 38 Control Statement..........................38 Option Specifications......................38 Syntax Definition.........................40 Summary of DLG Directives..................40 Descriptions of Control Directives.........41 Processor Interface ................ ........... 45 Usage......................... ............. 45 Restrictions ............................. 46 Technology Module Interface Package..................47 PROGRAM LIBRARY ................................................... 50 Geometry ....... ................................. 50 Aerodynamics, Stability and Control .................. 50 Propulsion...................................51 Mass and Volumetric Properties.......................51 Performance.................................. .52 Thermodynamics........ ............................ 52 Structures................... ........................ 53 Cost............ ....... .................. ........... 53 Environmental Protection .............................53 ABLATOR: One Dimensional Analysis of the Transient Response of Thermal Protection Systems..........54 ACMOTAN: Linear Aircraft Motion Analysis............54 AESOP: Automated Engineering and Scientific Optimization Program............................55 AFSP: Automated Flutter Solution Procedure..........55 AIRFOIL: A Program for Generating Geometric and Aerodynamic Characteristics of Airfoil Sections.55 ATOPII: Atmospheric Trajectory Optimization.........56 COAP: Combat Optimization and Analysis Program......56 CONPLOT: Aircraft Configuration Plot................57 DAPCA: Development and Production Cost of Aircraft..57 vi TABLE OF CONTENTS (Continued) Page DATCOM: Configuration Design Analysis Program (TRW) ................ .... .......... .............. 57 DATCOM2: Configuration Design Analysis Program (MDAC) ........... ...... ...... ............... 57 ENCYCL: Design Point Performance of Turbojet and Turbofan Engine ................................ 58 GENENG: A Program for.Calculating Design and Off- Design Performance for Turbojet and Turbofan Engines...............................................58 GENENGII: A Program for Calculating Design and Off- Design Performance of Two and Three Spool Turbofans with as many as Three Nozzles.........58 GEOMETRY: Body Coordinate Generator ................ 59 HABACP: Hypersonic
Load more

Recommended publications
  • Desktop Cyber 2.1 Operator\S and User\S Guide
    čťťťĘĘťť DPOUSPMGSFBLT PSH '(6.723&<%(5 23(5$725¶6$1'86(5¶6*8,'( &'&23(5$7,1*6<67(06 0(&&126365 90001100 2 i INDEX OF CONSOLE COMMANDS Command Mode Page Command Mode Page * DSD 2-15 LOCK DSD 2-13 Account Management DSD 2-22 LOGOFF DSD 2-13 ASSIGN DSD 2-12 MESSAGE DSD 2-13 AUTO DSD 2-12 MOVE O26 2-21 BLITZ DSD 2-12 O26 DIS 2-18 CFO DSD 2-12 O26 Special Keys O26 2-19 CHECK POINT SYSTEM DSD 2-12 OFF DSD 2-14 CKP DSD 2-12 OFFSW DSD 2-14 COMMENT DSD 2-12 ON DSD 2-14 COPY O26 2-21 ONSW DSD 2-14 D O26 2-21 OUT O26 2-21 DCP DIS 2-18 OVERRIDE DSD 2-14 DEBUG DSD 2-12 P O26 2-21 DIAL DSD 2-13 PURGE DSD 2-14 DIS DSD 2-13 RCP DIS 2-18 DIS O26 2-20 READ O26 2-20 DIS Displays DIS 2-16 REWIND O26 2-20 DISABLE DSD 2-13 RNR O26 2-21 DROP DSD 2-13 RNS DIS 2-18 DROP DIS 2-18 ROLLIN DSD 2-14 DROP O26 2-20 ROLLOUT DSD 2-14 DSD Displays DSD 2-9 ROLLOUT DIS 2-19 ELS DIS 2-18 RS O26 2-21 ENA DIS 2-18 STEP DSD 2-14 ENABLE DSD 2-13 SUI DIS 2-19 ENB DIS 2-18 SUN DIS 2-19 ENP DIS 2-18 UCC O26 2-21 ENS DIS 2-18 UNLOAD DSD 2-15 ENX DIS 2-18 UNLOCK DSD 2-15 FILE O26 2-20 UNSTEP DSD 2-15 FORM DSD 2-13 VSN DSD 2-15 GO DSD 2-13 WARN DSD 2-15 HOLD DIS 2-18 WRITE O26 2-21 IDLE DSD 2-13 X DSD 2-15 KILL DSD 2-13 XDIS O26 2-20 L O26 2-21 XDROP O26 2-20 LOAD Operator 2-41 Interface 90001100 A REVISION RECORD REVISION DESCRIPTION 1 Change bars will be made in the text to reflect edits made before the first production (1-1-2005) release.
    [Show full text]
  • Chippewa Operating System
    Chippewa Operating System The Chippewa Operating System often called COS was the operating system for the CDC 6600 supercomputer, generally considered the first super computer in the world. The Chippewa was initially developed as an experimental system, but was then also deployed on other CDC 6000 machines. The Chippewa Operating System often called COS is the discontinued operating system for the CDC 6600 supercomputer, generally considered the first super computer in the world. The Chippewa was initially developed as an experimental system, but was then also deployed on other CDC 6000 machines. The Chippewa was a rather simple job control oriented system derived from the earlier CDC 3000 which later influenced Kronos and SCOPE. The name of the system was based on the Chippewa Falls research and The Chippewa Operating System often called COS was the operating system for the CDC 6600 supercomputer, generally considered the first super computer in the world.[1] The Chippewa was initially developed as an experimental system, but was then also deployed on other CDC 6000 machines.[2]. Bibliography. Peterson, J. B. (1969). CDC 6600 control cards, Chippewa Operating System. U.S. Dept. of the Interior. Categories: Operating systems. Supercomputing. Wikimedia Foundation. 2010. The Chippewa Operating System often called COS was the operating system for the CDC 6600 supercomputer, generally considered the first super computer in the world.[1] The Chippewa was initially developed as an experimental system, but was then also deployed on other CDC 6000 machines.[2]. This operating system at Control Data Corporation was distinct from and preceded the Cray Operating System (also called COS) at Cray.
    [Show full text]
  • A Look at Some Compilers MATERIALS from the DRAGON BOOK and WIKIPEDIA MICHAEL WOLLOWSKI
    2/11/20 A Look at some Compilers MATERIALS FROM THE DRAGON BOOK AND WIKIPEDIA MICHAEL WOLLOWSKI EQN oTakes inputs like “E sub 1” and produces commands for text formatter TROFF to produce “E1” 1 2/11/20 EQN EQN oTreating EQN as a language and applying compiler technologies has several benefits: oEase of implementation. oLanguage evolution. In response to user needs 2 2/11/20 Pascal Developed by Nicolas Wirth. Generated machine code for the CDC 6000 series machines To increase portability, the Pascal-P compiler generates P-code for an abstract stack machine. One pass recursive-descent compiler Storage is organized into 4 areas: ◦ Code for procedures ◦ Constants ◦ Stack for activation records ◦ Heap for data allocated by the new operator. Procedures may be nested, hence, activation record for a procedure contains both access and control links. CDC 6000 series The first member of the CDC 6000 series Was the supercomputer CDC 6600, Designed by Seymour Cray and James E. Thornton Introduced in September 1964 Performed up to three million instructions per second, three times faster than the IBM Stretch, the speed champion for the previous couple of years. It remained the fastest machine for five years until the CDC 7600 Was launched. The machine Was Freon refrigerant cooled. Control Data manufactured about 100 machines of this type, selling for $6 to $10 million each. 3 2/11/20 CDC 6000 series By Steve Jurvetson from Menlo Park, USA - Flickr, CC BY 2.0, https://commons.Wikimedia.org/w/index.php?curid=1114605 CDC 205 CDC 205 DKRZ 4 2/11/20 CDC 205 CDC 205 Wiring, davdata.nl Pascal 5 2/11/20 Pascal One of the compiler Writers states about the use of a one-pass compiler: ◦ Easy to implement ◦ Imposes severe restrictions on the quality of the generated code and suffers from relatively high storage requirements.
    [Show full text]
  • Use of High Perfo Nce Networks and Supercomputers Ime Flight Simulation
    USE OF HIGH PERFO NCE NETWORKS AND SUPERCOMPUTERS IME FLIGHT SIMULATION Jeff I. Cleveland EE Project Engineer 3 National Aeronautics and Space Ad I Langley Research Center Nampton, Virginia 23681-0001 ABSTRACT In order to meet the stringent time-critical requirements for real-time man-in-the-loop flight simulation, computer processing operations must be consistent in processing time and be completed in as short a time as possible. These operations include simulation mathematical model computation and data inputloutput to the shulators. En 1986, in response to increased demands for flight simulation performance, NASA's Langley Research Center (LaRC), working with the contractor, developed extensions to the Computer Automated Measurement and Control (CAMAC) technology which resulted in a factor of ten increase in the effective bandwidlla and reduced latency of modules necessary for simulator communication. This technology extension is being used by more than 80 leading technological developers in the United States, Canada, and Europe. Included among the commercial applications are nuclear process control, power grid analysis, process monitoring, real-lime simulation, and radar data acquisition. Personnel at LaRC are completing the development of the use of supercomputers for mathematical model computation to support real-time flight simulation. This includes the development of a real-time operating system and development of specialized software and hardwxe for the simulator network. This paper describes the data acquisition technology and the development of supek-eompu~ng for flight simulation. INTRODUCTION NASA's Langley Research Center (LaRC) has used real-time flight simulation to support aerodynmic, space, and hardware research for over forty years.
    [Show full text]
  • UCC Aug 1971.Pdf (338.3Kb Application/Pdf)
    /V1Iw 9' c r-;.._:[:) N TABLE OF CONTENTS -------- uuuu uuuu 0 Timesharing p. 2 uuuu uuuu T MNF & BATCH users p. 3 uuuu uuuu E Ombudsman Appointment p. 4 uuuu uuuu s SPSS & OMNITAB p. 4 uuuu uuuu New Documentation p. 5 uuuu uuuu & Fall Quarter Short Courses p. 5 uuuu uuuu uuuu uuuu c uuuu uuuu 0 uuuuuuuuuuuuuuuuu **********HOLIDAY HOURS************* M * * uuuuuuuuuuuuuuuuu M :* UCC will be closed from 2~00 P.M.:* uuuuuuuuuuuuuuuuu E : Saturday, September 4, through : uuuuuuuuuuuuuuuuu N : 6:00 P.M. Monday, September 6. : T * * s ************************************ N 0 ccccccccccccccccc T NEW! KEYPUNCH INTERPRETERS-------·-- ccccccccccccccccc E ccccccccccccccccc s The interpreter previously owned ccccccccccccccccc by ucc was recently returned to IBM when it wore out. The replacement ecce & ecce interpreter has been the source of ecce c some complaints since, although faster, it interprets at most only two holes ecce 0 per column and spreads out the print­ ecce M ing of the columns so that they are ccccccccccccccccc M not above the punched column. ucc ccccccccccccccccc E admits it made an error and will again ccccccccccccccccc N lease an IBM 026-21 interpreter to ccccccccccccccccc T s give exact printing. Until the new machine arrives, we will use the N current IBM 552 Interpreter for 0 interpreting. T ccccccccccccccccc E ccccccccccccccccc s ccccccccccccccccc ccccccccccccccccc & ecce ecce Cm.1MENTS NOTES & COMMENTS NOTES & COMMENTS ecce 0 Volume 5, Number 8 ecce M August, 1971 ecce M ccccccccccccccccc E University com9uter Center ccccccccccccccccc N University of Minnesota ccccccccccccccccc T ccccccccccccccccc s N 0 August, 1971 NOTES & COMMENTS page 2 _____ _ A NEY.l TIMESHARING SYSTEM An interactive statewide educational timesharing network will be established in September when Control Data Corporation delivers to UCC a computer with at least the power of a CDC CYBER 72.
    [Show full text]
  • S N 0 B 0 L N
    S N 0 B 0 L n AT THE UNIVERSITY OF MINNESOTA TABLE OF CONTENTS 1. INTRODUCTION page 1 2. SN0B0L4 AS A PROGRAMMING LANGUAGE page 2 2.1 History page 2 2.2 Uses page 2 2.3 Implementations page 2 2.4 SN0B0L4 Semantics page 3 2.5 Program Syntax and Semantics page 4 3. SN0B0L4 FACILITIES AT THE UNIVERSITY OF MINNESOTA page 9 3.1 History page 9 3.2 Current Faci1i t ies page 9 3.3 Future Possibi1Ities page 10 4. COLORADO SNOBOL VERSION 3.10 page 11 4.1 Implementation Features page 11 4.2 Datatypes page 11 4.3 Primitive Functions and Predicates page 12 4.4 Keywords page 13 4.5 Input/Output page 13 5. RUNNING PROGRAMS UNDER COLORADO SNOBOL page 16 5.1 Program Preparation page 16 5.2 The SNOBOL Command page 17 5.3 Command Sequences page 18 5.4 Listing Controls page 18 5.5 Hints for Effective Usage page 19 5.6 Error Messages page 19 Appendix A: Summary of Differences Between Colorado and CAL SNOBOL page 20 Appendix B: Example Programs page 23 References page 29 PREFACE This document is intended to provide information to assist in using the local implementations of SN0B0L4 in a batch environment at the University of Minnesota. Emphasis is put on one implementation, Colorado SNOBOL 3.10, which is a SN0B0L4 processor essentially identical to standard SN0B0L4. A second processor, CAL 6000 SNOBOL, is also described in part here. For a complete description of CAL 6000 SNOBOL, see the UCC publication entitled "CAL 6000 SNOBOL at the University of Minnesota"; this publication emphasizes interactive uses.
    [Show full text]
  • Computing Division Two-Year Operational Plan FY 1981 — 1982
    LA-8725-MS UC-32 Issued: February 1981 Computing Division Two-Year Operational Plan FY 1981 — 1982 Prepared by Robert H. Ewald, Division Leader W. Jack Worlton, Associate Division Leader Margery McCormick, Editor •••'\ ACKNOWLEDGMENTS This plan is the work of many people in C Division. We wish to thank our Group and Division Leaders who worked so closely with C Division Office to develop the plan, and the C Division people who provided input to the plan. Special thanks are due Marjorie Blackwel'L, Computer Documentation Group, who entered all the original text and cheerfully entered all the revisions as well; and to Virginia Romero and Betty Hewett, Computer Documentation Group, and Vdma Payne1, Computer Graphics Group, who prepared the computer-generated figures. iv EXECUTIVE SUMMARY This plan provides users of the Los Alamos Central Computing Facility (CCF) and the Integrated Computer Network (ICN) with C Division's software and hardware plans for the next two years. In FY 1980 we completed a large number of projects, including the following. • Adopted ? change-control mechanism to better control ICN changes and provide a more stable computing environment. • Defined levels of support for our software and began defining ICN standard utilities and libraries. • Installed the second Cray-1 and moved a second CDC 7600 to the Open partition. • Implemented CTSS on both Cray-Is and provided the Los Alamos standard libraries, utilities, and documentation. • Placed distributed processors on line and provided a standard set of software. • Implemented the Print and Graphics Express Station (PAGES). PAGES now automatically controls all three FR80s and the two Versatec plotters as an integrated part of the Network.
    [Show full text]
  • Nos Version 1 Time-Sharing User's Reference Manual
    6-0435500"'.)"'" ~ 1:\ CONT~OL DATA \ \::I r:::J CO~OR<\TION = NOS VERSION 1 TIME-SHARING USER'S REFERENCE MANUAL CDC® COMPUTER SYSTEMS: CYBER 170 SERIES CYBER 70 MODELS 71, 72, 73, 74 6000 SERIES COMMAND INDEX Command Description Page ACCESS Selects ACCESS subsystem 4-8 APL Selects APL interactive interpreter 4-12 APPEND Adds file(s) to end of specified indirect access permanent file 5-6 ASCII Selects full ASCII or correspondence character set (128 characters) 4-3 ATTACH Provides access to direct access permanent files 5-6 AUTO Automatically generates line numbers 4-3 I BASIC Selects BASIC subsystem 4-9 BATCH Selects batch subsystem 8-1 BEGIN Initiates processing of CCL procedure 4-12 BINARY Selects binary input mode 4-13 BRIEF Suppresses all full and partial headers 4-5 BYE Logs user out of the system and disconnects the terminal 4-14 CALL Initiates processing of a KCL procedure 4-14 CATLIST Lists permanent file catalog information 5-13 CHANGE Changes attributes of a permanent file 5-9 m CHARGE Enters charge and project number for accounting 4-16 CLEAR Releases local files 4-16 CONVERT Converts character sets (63/64) A-I Lists abbreviated system status 4-16 CSET Selects terminal character set mode (ASCII or norm'a!) 4-5 DAYFILE Lists system's record of user's time-sharing activity 4-16 DEBUG Activates, terminates, or resumes CYBER Interactive I Debug mode 4-19 DEFINE Crea tes direct access permanent files 5-9 DIAL Sends messages to interactive terminal 4-19 0 EDIT Selects Text Editor 4-19 ENQUIRE Lists system and job status information
    [Show full text]
  • LISP Reference Manual CDC -6000
    THE UNIVERSITY OF TEXAS AT AUSTIN Computation Center LISP Reference Manual CDC -6000 01 (R) (QR) (I" QR) CCUM2 00 w DEC 1975 DEC 75 LISP Reference Manual LISP Reference Manual CDC - 6000 Computation Center University of Texas at Austin Austin, Texas 78712 LISP Reference Manual DEC 75 The Computation Center will appreciate any comments about this manual which may be used to improve its usefulness in later editions. In comments concerning errors, additions, deletions, or omissions, please include the date of the manual and, for each item, the number of the page involved. Comments should be addressed to: Editor, Computation Center, University of Texas at Austin, Austin, Texas 78712. ii DEC 75 LISP Reference Manual Acknowledgements This manual is extensively based on the manual written by Dr. E. M. Greenawa 1 t for the ear 1 ier version of the UT LISP sys tern. The Computation Center expresses its appreciation to Robert A. Amsler, Jonathon Slocum, and Nabry Tyson for their ass is ta nee in revising the manual to reflect the current LISP system and for producing a machine-readable preliminary form of the the manual. ii i DEC 75 LISP Reference Manual TABLE OF CONTENTS 1. INTRODUCTION, 1 2. USING TIIE LISP SYSTEM, 3 2.1 THE LISP CONTROL COMMAND, 3 2.2 INPUT FORMAT FOR UT LISP, 9 2.3 LISP SYSTEM OUTPUT, 11 3. DATA FORMATS, 13 3. 1 INPUT FORMATS I 13 3.1.1 Lexical Classes, 13 3.1.2 Literal Atoms, 14 3.1.2.1 Standard Literal Atoms, 14 3.1.2.2 Special Literal Atoms, 15 3.1.2.3 Additional Notes on Literal Atoms, 16 3.
    [Show full text]
  • Nastran Computer Resource Management for the Matrix Decomposition Modules
    NASTRAN COMPUTER RESOURCE MANAGEMENT FOR THE MATRIX DECOMPOSITION MODULES Charles W. Bolt Computer Sciences Corporation SUMMARY Detai 1ed computer resource measurements of the NASTRAN mat ri x decomposi- t<en spill logic were made using a software input/output monitor. These measurements showed that, in general, job cost can be reduced by avoiding spi 11. The results indicated that job cost can be minimized by using dynamic memory management. A prototype memory management system is being implemented and evaluated for the CDC CYBER computer. INTRODUCTION The early large structural analysis programs were designed for second- generation computer systems that were severely core-limited, requiring struc- tural programmers to develop ingenious strategies for using mass storage to extend the range of solvable problems. It was for such a computer that NASTRAN was initially developed, and the matrix decomposition code with its efficient spill logic was a singular achievement in numerical analysis software. As NASTRAN was implemented on third generation computers which a'llowed multi- programming, such as the UNIVAC 1108 and the CDC 6000 series, it remained expedient to use as little central memory as possible in order to maximize over- all system efficiency. However, present day computers such as the CDC CYBER 175 and the UNIVAC 1110 have very large, fast, low-cost semiconductor memories, and excessive mass storage usage can rapidly degrade overall system efficiency and increase job cost. It therefore becomes important for the user to select an optimutn memory region size for his problem. In order to accurately assess the effects of memory region size on I/D utilization aqd job cost, a software monitor was developed to measure I/@ volumes by file on CDC CYBER computers.
    [Show full text]
  • United States Patent (19) 11 Patent Number: 5,440,749 Moore Et Al
    USOO544O749A United States Patent (19) 11 Patent Number: 5,440,749 Moore et al. 45 Date of Patent: Aug. 8, 1995 54 HIGH PERFORMANCE, LOW COST 4,713,749 12/1987 Magar et al. ........................ 395/375 MCROPROCESSOR ARCHITECTURE 4,714,994 12/1987 Oklobdzija et al. ................ 395/375 4,720,812 1/1988 Kao et al. ............................ 395/700 75 Inventors: Charles H. Moore, Woodside; 4,772,888 9/1988 Kimura .......... ... 340/825.5 Russell H. Fish, III, Mt. View, both 4,777,591 10/1988 Chang et al. ........................ 395/800 of Calif. 4,787,032 11/1988 Culley et al. ........................ 364/200 - 4,803,621 2/1989 Kelly ................................... 395/400 (73) Assignee: Nanotronics Corporation, Eagle 4,860,198 8/1989 Takenaka ... ... 364/DIG. Point, Oreg. 4,870,562 9/1989 Kimoto ...... ... 364/DIG. 1 4,931,986 6/1990 Daniel et al. ........................ 395/550 21 Appl. No.: 389,334 5,036,460 7/1991 Takahira ............................. 395/425 22 Filed: Aug. 3, 1989 5,070,451 12/1991 Moore et al. ....................... 395/375 5,127,091 6/1992 Bonfarah ............................. 395/375 511 Int. Cl'................................................ GO6F 9/22 52 U.S. Cl. .................................... 395/800; 364/931; OTHER PUBLICATIONS 364/925.6; 364/937.1; 364/965.4; (2. Intel 80386 Programmer's Reference Manual, 1986. 58) Field of Search ................ 395/425,725,775, 800 Attorney,Primary ExaminerAgent, or Firm-CooleyDavid Y. Eng Godward Castro 56) References Cited Huddleson & Tatum U.S. PATENT DOCUMENTS 57 ABSTRACT 3,603,934 9/1971 Heath ........................... 364/DIG. 4,003,033 1/1977 O'Keefe et al.
    [Show full text]
  • April 30, 2004 the CDC-3300 and 6000 Series
    CMPSCI 201 – Spring 2004 – © Professor William T. Verts Lecture #33 – April 30, 2004 The CDC-3300 and 6000 Series Continuing on in “Bizarre Architectures Week” we look at two machines from the 1960s, both strongly influenced by Seymour Cray before he left Control Data Corporation (CDC) to form his own company. Both machines were very powerful computers, and were considered to be supercomputers in their day. By today’s standards they are very underpowered. Part of the lesson of examining these two machines is that neither observes the “standard” design rules implicit in essentially all modern machines. Modern processors all use a word that is eight bits or an even power of eight bits in length, all use two’s complement binary arithmetic with occasional BCD augmentation, and except for some machines that still use EBCDIC nearly all use ASCII or the Unicode superset of ASCII as their character set. While these design rules are implicit today, early machines were designed with very different criteria. Only as alternatives were explored and discarded over time did we converge on the current approaches. The CDC-3300 For example, the CDC-3300 was a 24-bit architecture, using one’s complement binary arithmetic, with two accumulators labeled A and Q, and two or three banks of 32K of 24-bit magnetic core memory. Accumulator A was the main accumulator, and Q was a “quotient register” partially dedicated to handling multiplications and divisions. In addition, there were four 15-bit index registers used for memory offsets into arrays (actually, there were only three physical index registers R1, R2, and R3; “register” R0 didn’t actually exist and therefore always had the value zero).
    [Show full text]