81 20 8242 https://digitalprojects.uah.edu/files/original/4/4287/spc_nick_000598_000602.pdf 8ad5f6d85ab6d11e83fd63b36f01ec3d Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Col. John C. Nickerson, Jr. Papers Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context spc_nick_000598_000602 Title A name given to the resource "Senior Officers Oral History Program." Description An account of the resource A project of the U.S. Army Military History Institute, this contains the interview of Dr. John L. McDaniel by Lieutenant Colonel Joseph W. Camp, Jr. from 1985. The interview is about the US Army's first satellite into space. McDaniel brings up the case of Colonel Nickerson relative to the interview. This document contains only the portion of the interview that mentions Colonel Nickerson. Creator An entity primarily responsible for making the resource Camp, Joseph W., Jr. Date A point or period of time associated with an event in the lifecycle of the resource 1905-06-07 Temporal Coverage Temporal characteristics of the resource. 1980-1989 Subject The topic of the resource Courts-martial and courts of inquiry--United States Defense information, Classified Intermediate-range ballistic missiles Jupiter missile Leaks (Disclosure of information) Huntsville (Ala.) Madison County (Ala.) Carlisle (Pa.) Type The nature or genre of the resource Documents Text Source A related resource from which the described resource is derived Col. John C. Nickerson, Jr. Papers Box 2, Series 5, Folder 5 University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource spc_nick_2021_03 https://digitalprojects.uah.edu/files/original/121/7898/r03_01-01.pdf 66270650c568e1fe02610d5a7bfeed12 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Series 03: Roberts Collection - UAH Title A name given to the resource Series 03: Roberts Collection - UAH Description An account of the resource All additional papers have been incorporated into already existing UAH records in the Archives. Still Image A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context r03_01-01 Source A related resource from which the described resource is derived Frances Cabaniss Roberts Collection Series 3, Box 1, Folder 1 University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Title A name given to the resource Frances C. Roberts Letters from UAH, 1950 - 1953 Relation A related resource r03-210915 Creator An entity primarily responsible for making the resource Campbell, George W. Hoffman, Philip G. (Philip Guthrie), 1915-2008Morton, J.R. Morton, J.R. Temporal Coverage Temporal characteristics of the resource. 1950-1959 Subject The topic of the resource Education, Higher History Roberts, Frances C. Teachers' contracts University of Alabama in Huntsville Type The nature or genre of the resource Correspondence Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. https://digitalprojects.uah.edu/files/original/186/14132/Discover_Space_with_a_Canadian_Astronaut_001.pdf 84e900d6b07a5d85202fb27729214949 PDF Text Text Canadian Space Agency Agence spatiale canadienne Space with a Canadian Astronaut Discover Marc Garneau STS-41G, STS-77 and STS-97 Bob Thirsk STS-78 Bjarni Tryggvason STS-85 Roberta Bondar Steve MacLean STS-42 Chris Hadfield STS-52 STS-74 and STS-100 Dave Williams STS-90 F O R M O R E O N T H E S E M I S S I O N S , V I S I T : w w w . s p a c e . g c . c a "YVADFIELQ" 1u CHRONOLOGY OF CANADIAN ASTRONAUT MISSIONS m- .Srk/ W • - rPSiini 4 Marc Garneau: STS-41G Roberta Bondar: STS-42 Payload Specialist Steve MacLean: STS-52 Payload Specialist Chris Hadfield: STS-74 Marc Garneau: STS-77 October 5 to 13,1984 Payload Specialist January 22 to 30,1992 Mission Specialist October 22 to November 1,1992 Mission Specialist November 12 to 20,1995 May 19 to 29,1996 Robert (Bob) Thirsk: STS-78 Bjarni Tryggvason: STS-85 Payload Specialist Payload Specialist June 20 to July 7,1996 August 7 to 19,1997 i -• i f \ * / ( *3T ccqzccd Cr~ v A , "• :,f i Dave Williams: STS-90 Julie Payette: STS-96 Mission Specialist Marc Garneau: STS-97 Mission Specialist April 17 to May 3,1998 Mission Specialist May 27 to June 6,1999 Mission Specialist November 30 to December 11, 2000 April 19 to May 1, 2001 Chris Hadfield: STS-100 SPACE SCIENCE AND EXPLORATION SPACE FOR CANADIANS �Agence spatiale canadienne Canadian Space Agency Decouvrez espace en compagnie astronautes canadiens STS-41G, STS-77 et STS-97 Bob Thirsk STS-78 Bjarni Tryggvason STS-85 Chris Hadfield Steve MacLean Roberta Bondar Marc Garneau STS-74 et STS-100 STS-52 STS-42 Dave Williams STS-90 SCIENCES SPATIALES ET EXPLORATION L'ESPACE AU SERVICE DES CANADIENS HISTORIQUE OES MISSIONS DES ASTRONAUTES CANADIENS Steve MacLean : STS-52 Chris Hadfield : STS-74 Marc Garneau : STS-77 Robert (Bob) Thirsk : STS-78 Bjarni Tryggvason : STS-85 Dave Williams : STS-90 Marc Garneau : STS-41G Roberta Bondar: STS-42 Specialiste de charge utile Specialiste de mission Specialiste de mission Specialiste de charge utile Specialiste de charge utile Specialiste de mission Specialiste de charge utile Specialiste de charge utile Du 22 au 30 janvier 1992 Du 22 octobre au 1 er novembre 1992 Du 12 au 20 novembre 1995 Du 20 juin au 7 juillet 1996 Du 7 au 19 aout 1997 Du 17 avril au 3 mai 1998 Du 5 au 13 octobre 1984 Du 19 au 29 mai 1996 Chris Hadfield : STS-100 Julie Payette: STS-96 Marc Garneau : STS-97 Specialiste de mission Specialiste de mission Specialiste de mission Du 27 mai au 6 juin 1999 Du 30 novembre au 11 decembre 2000 Du 19 avril au 1 er mai 2001 Canada � Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Government Documents Posters Title A name given to the resource Government Documents Posters Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Discover_Space_with_a_Canadian_Astronaut Title A name given to the resource Discover Space with a Canadian Astronaut FOR MORE ON THESE MISSIONS, VISIT: www.space.gc.ca Description An account of the resource Poster featuring photos and names of Canadian Astronauts. Chronology of Canadian Astronaut Missions included at the bottom of the poster. One side of the poster is in english, while the other side is the same information, but in French. Creator An entity primarily responsible for making the resource Canadian Space Agency Subject The topic of the resource Canadian Space Agency Astronauts Aeronautics Type The nature or genre of the resource Posters Still Image Source A related resource from which the described resource is derived The University of Alabama in Huntsville M. Louis Salmon Library Government Documents Posters Case 1, Drawer 1 Language A language of the resource en/fr Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource GovDocs https://digitalprojects.uah.edu/files/original/20/10547/Satudraf_112508121151.pdf ea959f0ae4686aee36ab9f77291f075b Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Saturn V Collection Relation A related resource <a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener">View the Saturn V Collection finding aid in ArchivesSpace</a> Identifier An unambiguous reference to the resource within a given context Saturn V Collection Description An account of the resource <p>The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html">here,<span> </span></a><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html">here,<span> </span></a>and<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html">here.</a>) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.</p> <p>Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.</p> <p>A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.</p> Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Satudraf_112508121151.pdf spc_stnv_000708 Title A name given to the resource "Saturn: draft." Description An account of the resource Report on the history of the Saturn program. Creator An entity primarily responsible for making the resource Canright, R. B. Date A point or period of time associated with an event in the lifecycle of the resource 1960-09-14 Temporal Coverage Temporal characteristics of the resource. 1960-1969 Subject The topic of the resource Saturn project History Type The nature or genre of the resource Text Reports Source A related resource from which the described resource is derived Saturn V Collection University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Is Part Of A related resource in which the described resource is physically or logically included. Is part of: NASA HQ Miscellaneous Correspondence August 1968. Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource spc_stnv_000700_000724 https://digitalprojects.uah.edu/files/original/109/7555/r01c01-19.pdf 20b54a4f76e985a03a16a552290c73e4 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Series 01, Subseries C: Cabaniss Personal Correspondence Title A name given to the resource Series 01, Subseries C: Cabaniss Personal Correspondence Description An account of the resource Subseries C, Cabaniss Personal Correspondence (CPC), consists of correspondence from letters from friends, relatives, and their children. Most of the family correspondence involves these children and families of S. D. Cabaniss, and his brothers and sisters who appeared to have been enormous burdens in these difficult years. These papers are sorted "to whom," "from whom," and then chronologically. Still Image A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context r01c01-19 Title A name given to the resource Cantrill, ____ to Cabaniss, Charles Eugene Relation A related resource r01c-210910 Creator An entity primarily responsible for making the resource Cantrill, William Temporal Coverage Temporal characteristics of the resource. 1860-1869 Subject The topic of the resource Decatur (Ala.) Huntsville (Ala.) Health Convalescence Pneumonia Type The nature or genre of the resource Correspondence Post card Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Source A related resource from which the described resource is derived Frances C. Roberts Collection, Series 1, Subseries C, Box 1, Folder 19, University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama https://digitalprojects.uah.edu/files/original/128/8737/r06_01-10.pdf b2427e3239079cc9b417acc8b45b9100 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Series 06: Pettus Family Title A name given to the resource Series 06: Pettus Family Still Image A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context r06_01-10 Source A related resource from which the described resource is derived Series 6, Box 1, Folder 10 Title A name given to the resource Colcock, Charles J. to Pettus, Richard E. (genealogy correspondence), 1905 - 1927 Relation A related resource r06-211007 Description An account of the resource Contains a series of correspondence between Charles J. Colcock and Richard E. Pettus regarding the writing, funding and publishing Charles' manuscript. Creator An entity primarily responsible for making the resource Carpenter, Charles Colcock J. Pettus, Richard E. Date A point or period of time associated with an event in the lifecycle of the resource 1904 1905 1909-06-14 1913-09-04 1927 Temporal Coverage Temporal characteristics of the resource. 1900-1910 1910-1919 1920-1929 Subject The topic of the resource Manuscript preparation (Authorship) Writing Fund raising Type The nature or genre of the resource Correspondence Envelope Is Part Of A related resource in which the described resource is physically or logically included. Frances Cabaniss Roberts Collection Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. https://digitalprojects.uah.edu/files/original/213/15009/wsig-jack-ellis-letter.pdf 865c937b3f11f8e29cb20dca5de12424 PDF Text Text � Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context RCEU Documenting the History of UAH’s Women’s, Gender, and Sexuality Studies Program Title A name given to the resource RCEU Documenting the History of UAH’s Women’s, Gender, and Sexuality Studies Program Description An account of the resource Documenting the history and evolution of UAH's Women's, Gender, and Sexuality Studies program. Covers the conception of the program in 1995 and how the program evolved throughout its current iteration. Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Women's Studies Interest Group Invite to Jack Ellis Creator An entity primarily responsible for making the resource Carpenter, Sandra Clark, Sheri Dittmar, Mary L. Finley, Nancy Jane, 1951- Norman, Rose (Rose Lynn) Pollard, Elizabeth (Elizabeth Ann) Subject The topic of the resource Women's studies Identifier An unambiguous reference to the resource within a given context Women's Studies Interest Group Invite to Jack Ellis Description An account of the resource The Women's Studies Interest Group reaches out to Jack Ellis to gain his support in their activities. Date A point or period of time associated with an event in the lifecycle of the resource 1992-07-16 Format The file format, physical medium, or dimensions of the resource electronic mail, correspondence Source A related resource from which the described resource is derived Women's Studies Collection, University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. https://digitalprojects.uah.edu/files/original/20/1142/spc_stnv_000058.pdf 79b702f9bdc6ea6564e33c8dd71d4eb5 PDF Text Text IBM Report No. 66-894-0008 ALL DIGITAL SIMULATION O F SATURN I, IB AND V BOOST VEHICLE AND GUIDANCE AND CONTROL SYSTEMS 8 L - .. - .' W. D. Carson R. E. Poupard T. D. Steele F. W. Eubank INTERNATIONAL BUSINESS MACHINES CORPORATION Federal Systems Division Space Systems Center Huntsville, Alabama - .. I * . I. ' . - I .' J . June , 1966 �ALL DIGITAL SIMULATION OF SATURN I, IB AND V BOOST VEHICLE AND GUIDANCE AND CONTROL SYSTEMS F. W. Eubank by W. D. Carson, R. E. Poupard T. D. EXeele International Business Machines Corporation Federal Systems Division Space Systems Center .* I. INTRODUCTION The Saturn V launch vehicle i s being developed by The National Aeronautics and Space Administration's George C. Marshall Space Flight Center for Project Apollo; Saturn I and Saturn IB vehicles are providing the early testing and support for Project Apollo. The nerve center of the Saturn is its guidance and control system. An airborne digital complter provides the link which closes both the guidance and control loops, making verification of the flight computer program of vital importance. During a powered flight this onboard digital computer program can be divided into four major parts: a) b) c) d) guidance, including navigation, control, vehicle sequencing, and computer telemetry. Each of these major computer functions must be verified and tested prior t o launch, and many procedures a r e currently used. They include open loop tests of the flight hardware, closed loop studies (using a laboratory model of the flight computer with both analog and digital models of the Saturn vehicle), and an alldigital simulation of both the flight computer and the Saturn vehicle. Each has i t s own advantages, and those of the all-digital simulation a r e summarized briefly in ;he following discussion. Simulation is defined a s the analog or digital comniter implementation of a set of equations which =present some usually complex portion of the physical ~ o r l d(system). Simulation has followed the development of computers, a s it would be impossible to simulate most systems without a computer. In aerospace work the need for simulation is particularly acute since enormous expenditures a r e required to produce prototype o r engineering models. In many cases these models a r e unavailable, and the first flight is the first test. Simulation provides answers similar to those obtainedfrom exhaustive laboratory tests of an engineering model. ' ~ e d l e ~R. , S. , Digital Computer and Control Engineering, McGraw-Hill, 1960, p. 143. . Huntsville, Alabama The all-digital simulation described here consists of a marriage between two separate simulators. The first simulator is a digital flight computer model called Simulational Interpretivel:Routine by Tedley, since it makes the IBM 7094 at$ Processing System appear to be the flight computer. It copies the flight computer in word length, instruction execution, and timing. In this case the flight computer is either the ASC-15 (Saturn o r the Launch Vehicle Digital Computer (Saturn IB and V). The second simulator is a mathematical model of the Saturn vehicle and the remaining guidance and control hardware. It contains the six-degree-of-freedom equations of motion representing the Saturn rigid body dynamics. Hence, the name 6D is often applied to the simulator which also contains a model of the Saturn control system and a set of calculations designed to represent the inertial platform. The essential guidance and control interfaces a r e simulated in enough detail to permit analysis of the Saturn vehicle closed-loop guidance and control performance.. The simulation requires the flight computer model to perform the flight sequencing a s in actual flight, and provides the flight computer model with the appropriate sequencing command responses. Flight computer telemetry i s recorded a s the simulated flight progresses, permitting postflight analysis of the flight program a s in actual flight. In some applications, discussed in Sections 11. A and IU. B, the detailed flight-computer model i s not required and is replaced by a simpler model called the FORTRAN guidance model. This all-digital simulator has advantages over other flight program tests. It is closed loop but has no hardware interface problems a s it is entirely contained in one computer and in one program. Tedious programming requirements a r e eliminated a s simulation requires no real-time operation. Studies performed on this simulator a r e repeatable, and can include numerous flight perturbations with minor programming effort. The simulator i s readily accessible to more than one analyst at a time; user maintenance is at a minimum. While it is recognized that all-digital simulation may not be the best solution for every simulation problem, i t s usefulness has been established for the Saturn guidance system studies and analyses. ,The basic const&ction and use of this simulator i s the subiect of this note. The treatment will be general but specific enough to provide a useful insight to a complicated simulation problem. / SUPPLEMENT TO IEEE TRANSACTIONS ON AEROSPACE AND ELECTRONIC SYSTEMS VOL. AES2. NO. 4 JULY.1966 809 �11. SIMULATOR DESCRIPTION As mentioned in the Introduction, there a r e two simulators involved - the Launch Vehicle Digital Computer (LVDC) simulator, and the Saturn vehicle simulator (6D). Figure 11.1 shows a general block diagram of the combined simulation. A. LVDC Simulator A brief discussion of the onboard digital computer functions i s required for a better understanding of the LVDC simulator. Four major functions pkrformed by the LVDC are: a) b) ' c) d) quidance and navigation, control sequencing, and telemetry. The quidance loop is closed through the LVDC. An inertial platform provides the LVDC with measured velocity changes. The computer must then add gravitational velocity changes to the measured quantities and perform the required integrations to obtain the current vector position and velocity. The guidance equations use positon, velocity, magnitude of acceleration, and time to generate steering commands, which a r e the desired platform gimbal angles. These desired angles a r e the output of the guidance equations and serve as the input to the computer control calculations. . - The control loop is also closed through the LVDC. The -desired gimbal angles from the guidance routine are subtracted from the measured gimbal angles obtained from the platform. These differences a r e transformed to body-fixed coordinates and issued at a high rate (25/sec) a s attitude errors to the analog control computer, closing the control loop. Vehicle sequencing consists of discrete signals issued by the LVDC through a stage switch selector to provide necessary switching functions to the various Saturn stages. All sequencing is performed by the L M C . The telemetry functions require that certain words be telemetered periodically from the computer to aid in real-time evaluation of the vehicle performance and provide data for mission control decisions, postflight evaluation. ---.. -and . In order to test the digital' program designed for use in the LVDC, it is necessary to have.a model of the flight computer which will: a) execute the flight program instructions exactly a s the hardware, b) carry out all arithmetic operations with precisely the same accuracy as the flight computer, and c) preserve communication and timing. The Simulational Interpretive Routine designed to do this is called a "bit-by-bit" (BBB) simulator since its computations compare exactly, digital-bit-by-digitalbit, with the LVDC computations. The BBB model simulates the LVDC memory, initializes all locations (just as they would be initialized in flight), decodes instructions, and executes them sequentially a s dictated by the flight progyam. Any instruction errors in the flight program (Section El. A describes some typical errors) will show the same symptoms in the simulator a s in flight. Any detected instruction of data errors cab be corrected in the BBB model by appropriate memory changes at the beginning of a run, providing a test of proposed changes. The input/output data paths connecting the flight computer a r e simulated, permitting a study of timing o r data-handling problems in the communication interfaces. The four primary computer tasks outlined above (guidance, control, sequencing, and telemetry) must be verified before each flight using the BBB model. Even with this detailed simulation, the cause, or even the presence of an error, is not always obvious. The simulation remains a tool of the analyst - not a replacement for him. Two modes of operation a r e possible for the BBB simulator. In preflight studies, when the flight program must be exercised with guidance and control loops closed, the LVDC output quantities are fed to the 6D, and appropriate flight inputs a r e determined. Figure II. 1 shows the principal communications interfaces. The BBB model requires discrete signals, gimbal angles, and velocity data as inputs. Its outputs consist of attitude-error signals, flight sequencing discretes to the 6D, and telemetry data. In postilight evaluation (the second mode of operation), the inputs a r e already available from flight data, so all outputs a r e recorded simply for comparison with flight results. The use of the BBB simulator i s open loop in this mode. A FORTRAN model of the LVDC is used for guidance and navigation studies, to determine range of variables for scaling the LVDC flight program, to evaluate failure effects studies, and for all other studies which do not require the BBB simulation of the LVDC flight program. To ensure a n adequate model for preliminary flight program design and checkout, however, all essential LVDC flight program algorithms a r e included. �Two important advantages of the FORTRAN model the BBB model are: a I ~ r g ereduction in computer time necessary to complete a simulation run, which implies a larger number of runs for a given time, and the computer language used in writing the simulator. AS the name implies, the FORTRAN model is written in FORTRAN which allows the model to be changed and i s understood by more analysts thail the L W C flight-program language. B. 6D Simulator The 6D simulator must take the outputs from the LVDC model (either BBB or FORTRAN) and process them to compute the inputs to the LVDC. These communications were discussed in a previous paragraph (page 2) and a r e shown in Figure 11.1. Proceeding around the loop in Figure 11.1, the LVDC model issues attitude e r r o r commands to the control computer. They a r e filtered and combined with attitude-rate commands and load-relief signals from body -mounted accelerometers to produce engine gimbal commands. These commands a r e transmitted by the actuator model to the vehicle simulator where rotational and translational accelerations a r e computed. The characteristics of the vehicle's physical environment (aerodynamics and gravitation) a r e calculated and their effects included in the equations of motion. The rotational and translational accelerations a r e integrated for use in models of the inertial platform, the vehicle-mounted accelerometers, and the rate gyros. The 6D computations of position and velocity serve as standards with which the LVDC navigation quantities may be compared. The 6D discussion is divided into three parts: the launch vehicle and its environment, the inertial platform, and the control and actuator systems. 1. Launch Vehicle. T l i e S a t k IB boost vehicle is shown in Figure II. 2 and consists of two stages. The first (S-IB) stage is powered by eight Rocketdyne H-1 engines which generate a total thrust of 1.6-million pounds. The four inboard engines a r e clustered around the vehicle's centerline and a r e canted such that the thrust vector of each engine points through the approximate vehicle center of gravity at liftoff. The outer four engines a r e gimballed for control purposes and are also canted. The second (S-IVB) stage is Powered by a single Rocketdyne 52 engine which i s mounted on the vehicle's centerline and gimballed for Pitch and yaw control. Roll control i s achieved by reaction jets mounted on the S-WB stage. The launch vehicle simulation i s conveniently @videdinto five parts: a) the rigid bddy equations of motion, b) aerodytiamics, c) gravitation, d) propulsion and mass characteristics, and e) the vehicle-mounted sensors. a. Equations of Motion. m e vehicle is assumed to be a rigid body and, consequently, has sixdegrees-of-freedom-three rotational and three translational. The equations of motion were derived from the principles of Newtonian Mechanics. The velocity of the center of gravity relative to the body is small compared to the vehicle inertial velocity and is neglected. The external forces (excepting gravitational forces) a r e summed with respect to a set of coordinates originating a t the center of gravity, and extending along the vehicle's pitch, kaw, and roll axes. The resultant force i s then divlded by the total vehicle mass to obtain acceleration. This acceleration i s transformed to an inertial frame where i t is summed with gravitational acceleration and integrated to obtain true inertial velocity. The integration scheme is a modified form of trapezoidal integration, and double precision is used for computation of most integrals. The rotational equations of motion a r e simplified by making use of the vehicle's geometric and mass symmetry about the longitudinal (roll) axis. It is assumed that the vehicle's pitch and yaw axes a r e aligned with the principal axes of inertia. These equations a r e solved in the body frame by summing the external moments, dividing by the appropriate moment of inertia, and adding coupling between axes. b. Aerodynamics. There a r e aerodynamic forces acting on the vehicle as a result of its passage through the atmosphere. The vehicle is launched from a specified site located on the rotating earth, and the atmosphere is assumed to rotate with the earth. The characteristics of the atmosphere a r e obtained from Patrick Air Force Base Standard Atmosphere (1963) as a function of altitude. The logitudinal aerodynamic force equation can be developed from knowledge of these characteristics and the priciple of Bernoulli. An additional term is added to account for the base drag due to the vacuum created a t the base of the vehicle. The linearized normal force equation is an empirical equation proportional to the aerodynamic normal force coefficient which also depends upon atmosphere characteristics, principally the Mach number. Both the longitudinal and the normal force equations use the relative velocity d the vehicle, which is the vector difference in the vehicle's inertial velocity and the atmosphere's inertial velocity (earth's rotation and wind velocity). Wrnd velocity may be excluded or modified by programmer option. The vehicle" center of gravity (cg) and center of pressure (cp) a r e not at the same point; and, since the aerodynamic h c e s may be assumed to act at the center of pressure, a turning moment i s created about the center of gravity. Wind tunnel measurements yield TRONIC SYSTEMS VOL. A@-2, NO. 4 JULY, 1966 �D.O. 9 *B iB t' 4 E' 6 eP - -._ Discrete Outputs Steering Commands (Attitude Errors) Body Fixed Translational Acceleration - Body Fixed Accelerometer O u t p t s Body Fixed Rate G y o Outputs Engine Gimbal Angles Platform Accelerometer Outputs - - Body Fixed Rotational Velocities Platform Gimbal (Attitude) Angles Figure 11.1. General Block Diagram of the 6D Simulation SUPPLEMENT TO IEEE TRANSACTIONS ON AEROSPACE AND EL.ECTRONIC S Y S E M S VOL. AFS-2, NO. 4 JULY. 1966 �craft S-NB O n e 1-2 Engine 200,000 Lb. Tl~rust S-IB Eight H-1 Engines 200,000Lb Thmst Each . Figure 11.2. Saturn I-B Vehicle SUPPLEMENT TO IEEE TRANSACTIONS ON AEROSPACE AND ELECTRONIC SYSTEMS VOL. AES-2, NO. 4 JULY. 1966 �empirical data for the center of pressure location relative to the engine gimbal plane. The moment a r m is calculated from the knowledge of the center of gravity location which is fixed by the knowledge of the vehicle's m a s s distribution. For the calculation of the aerodynamic moments the center of pressure is assumed to be located on the vehicle's roll axis. c. Gravitation. The gravitational acceleration is calculated in the 6D, combined with other accelerations; and the resulting acceleration is integrated t o provide essentially error-free velocities and positions for con~parisonwith LVDC navigation quantities. The method employed for gravitation calculations is similar to the methodused by the Saturn flight programs, except that the equations include four t e r m s in a Fischer ellipsoid model2 of the earth's gravitational field instead of two. d. Thrust-Mass Characteristics. Engine thrust and vehicle mass characteristics (i. e. , cg location, moments of inertia, etc.) a r e obtained from the Propulsion and Vehicle Engineering Laboratory, Marshall Space Flight Center. The data a r e generated in a detailed simulation of the Saturn propulsion system. This simulation employs empirical equations and uses measurements taken from static-test firings. The thrust and m a s s data a r e updated for each vehicle to provide accurate results from the 6D without actually including an extensive propulsion system simulation. The individual engine thrust vectors a r e resolved through the engine gimbal and cant angles and a r e summed to obtain a resultant force acting at the vehicle's center of gravity. Based on engine and vehicle geometry the turning moments a r e calculated f o r use i n the rotational equations of motion. e. Vehicle Sensors. Saturn' s control system employs two types of vehicle-mounted sensors: rate gyros for stability both stages) and accelerometers for wind-load relief (first stage of Saturn IB only), The outputsfrom the vehicle equations of motion a r e utilized directly to simulate the outputs of these sensors. Corrections for the signals measured by accelerometers not mounted a t the vehicle's center of gravity a r e also added when necessary. 2. Inertial Platform. The platform simulator is used t o simulate the outputs obtained from the Bendix ST-124M stabilized inertial platform during flight. The ST-124M is a three-gimbal platform having a n innerto-outer gimbal order of pitch, yaw, and roll. These ' ~ i s c h e r , I., "An Astrogeodetic World Datum from Geoidal Heights Based on the Flattening f = 1/298.3, I f JOURNAL OF GEOPHYSICAL RESEARCH, Vol. 65, NO. 7, July 1960, pp. 2067-2076. 814 gimbals provide angular measurements for attitude control of the vehicle through the LVDC and the flight control computer. These measurements a r e used, also, to provide a body coordinate to inertial coordinate system transformation matrix and to simulate the outp~its of the integrating accelerometers. The model has provisions to include platform e r r o r s a s well a s gimbal angle misalignments and accelerometer failures. 3. Flight Control Computer and Actuator Dmamics. The Saturn's flight control cornouter and " related subsystems a r e analog and must be represented digitally in the 6D simulation. The flight control computer combines inputs f r o m the rate gyros, control accelerometers, and tf?e LVDC to generate a gimbal commaiid t o the control-engine actuators. The control computer filters, amplifies, and sums these i n p ~ t s . The gains and filters a r e changed periodically during flight by switches activated by discrete outputs from the LVDC. The pitch, yaw, and roll signals a r e then a p propriately combined to provide inputs to the hydraulic actuator system which positions the control engines. The engine gimbal angles a r e limited to simulate the physical stops mounted on each control engine. The data describing the filters and the hydraulic actuator system a r e usually given a s linear transfer functions in t e r m s of the Laplace variable. The use of such data assumes that linear differential equations wilI adequately describe the behavior of a system represented in this manner. Studies were made to show that a Z-form approximation to the inverse Laplace transform will provide adequate filter representation and actuator outputs for the range of input frequencies that a r e of interest (2 - 3 c p s ) 3 ~ 45.~ Since the vehicle was assumed to be rigid, no bending and sloshing models a r e included. The Z-form theory i s utilized in a separate program to obtain coefficients of difference (recursion) equations to represent the filters and the engine actuator system. Gain changes, a s well a s filter changes, a r e made wherever commanded by the LVDC. Scarson, W. D. , "Digital Simulation of Analog Subsystems - A Numerical Example, "Astrionics Internal Note M-ASTR-IN-63-26, Astrionics Division, George C. Marshall Space Flight Center, Huntsville, Alabama, September 16, 1963. 4 ~ o u ,Julius T., Digital and Sampled-Data Control Systems, - New York: McGraw-Hill Book Company, ' ~ a ~ a z z i n iJ. , R., and Franklin, G. F., SampledData Control Systems, McGraw-Hill Book Company, Inc. , New York, 1958. SUPPLEMENT TO IEEE TRANSACTIONS ON AEROl;PACE AND ELECTRONIC SYSTEMS VOL. AES-2, NO. 4 JULY, 1966 �IU. SIMULATOR DE\ 'ELOPMENT AND USES A. Early Application and Development The use of an all-digital simulator for Saturn preflight evaluation started with the SA-5 flight, the f i r s t Saturn I, Block I1 vehicle. This vehicle was the f i r s t of the Saturns to attempt two-stage flight (S-IV secozd stage) and f i r s t to c a r r y a l o ~ ga digital flight computer, although the digital computer operated open loop on this flight. Early in 1963 work began to combine the already existing digital simulations of the flight computer (ASC-15) and the vehicle (6D). These simulators had been developed, independently, for altogether different applications than combined simulation, although both operated on the IBM 7094. Several problems were encountered immediately. A common clock and a communication interface (internal to the IBM 7094) had to be established. Certain parts of the 6D required a fixed-time operation interval, notably the digital representation of the control system, whereas the ASC-1 gave and received outputs and inputs at varying times. Additionally, it was necessary to decide which mcdel would lead the other; i.e., should the 6D integrate from t to t + A t , and then the ASC-15 catch up, o r vice versa. - These problems were resolved by decisions made early in the program. A convenient choice for the common clock was the ASC-15 computer time. This choice (made s;?ecifically f o r the ASC-15 drum-storage machine) has proven satisfactory, even with the newer core computer(LVDC), and is still in use. The ASC-15 required two types of inputs and generated two types of outputs. Discrete inputs and outputs were used for vehicle sequencing, and their occurrence times during a computation cycle were flight dependent, whereas measurements and computed commands always occurred a t the same time in each computation cycle independent of the flight. The communication interface controlled the flow of both kinds of information between simulators. This was accomplished, in the case of discrete inputs and outputs, by testing appropriate registers for changes each time the interface routine was entered. In the second c a s e , measured and computed data were transferred by clocks into the appropriate location in each simulator. Each data block was transferred only once per computation cycle. The communications interface was used to fix the integration step size for the 6D and to control the relative timing between the simulators. At the end of each ASC-15 drum revolution, the ASC-15 simulator transferred control to the communications block, where the decision was made whether the 6D should be called to catch up with the ASC-15. Thus, the 6D integration step size was fixed to be an integer multiple of the drum revolution time, and the ASC-15 was selected to lead the 6D in r e a l time. Implicit in the decision to communicate discrete inputs and outputs a t one drum revolution intervals i s the contention that no closer determination of event times than one drum revolution is required. This contention i s true for all vehicle sequencing except the S-IV engine cutoff signal. In this instance, the cutoff signal is issued in a loop much shorter than one drum revolution, and this special discrete required communication between simulators on a word-time basis (1/64 of a drum revolution) near cutoff. Once cutoff was detected, the 6D simulator fdjusted i t s step size to permit computation of the vqhicle state a t the cutoff time. In short, the communication block served a s data manager for control of information transfer and for time keeping between the 6D and ASC-15 simulations. While these decisions regarding timing and communications were being made and modified by experience, the combined simulation was proving i t s usefulness in flight program checkout for the SA-6 flight. Four types of e r r o r s were found in early checkout runs; two were flight program e r r o r s and two were simulator e r r o r s which appeared to be flight program e r r o r s . The first type of e r r o r s were coding e r r o r s made in the preparstion of the ASC-15 flight program and a r e inevitable on tasks of this magnitude with time limitation. Their detection was the primary reason f o r construction of the combined simulation. Typical e r r o r s of this type included improper coefficients for guidance and navigation computations, erroneous initial conditions, and incorrect sine and cosine subroutine computations. The second type of e r r o r s could be called conceptual e r r o r s in the flight program. Discovered by the combined simulation, they included gaps in the velocity computation which caused the vehicle to m i s s the desired cutoff velocity and scaling of some quantities resulting in lloverflowllof their fixed-point representation under certain circumstances. F o r instance, in the SA-6 flight program, flight time was scaled so that if it exceeded 656 seconds, i t would s t a r t over; i . e . , 657 seconds would appear in the computer a s 1 second. This scaling was adequate for most flight conditions since nominal flight time was 610 seconds, but it could be exceeded under some extreme - but possible flight perturbations. When exceeded, the guidance system failed to provide accurate steering commands, and the vehicle failed to achieve the desired orbital conditions. Conceptual e r r o r s involved e r r o r s a t a level above simple coding e r r o r s . They may occur when last-minute mission changes impose unforeseen operating conditions upon the flight program. Thus, they a r e potentially present in every flight program. SUPPLEMENT TO IEEE TRANSACTIONS ON .4EROSPACE AND ELECTRONIC SYSTEMS VOL. AES-2, NO. 4 JULY,1966 �The f i r s t two types of e r r o r s , if undiscovered, could have caused severe mission degradation o r even failure. At the time these e r r o r s were discovered in the SA-6 flight program, the flight program had successfully passedmost of i t s other checkout procedures; and it is unlikely that many of the e r r o r s would have been found by other means. Therefore, although the combined digital simulation was not originally considered vital in the program checkout procedure, it soon became the most reliable and thorough flight program checkout tool in use.. The third e r r o r source uncovered in the studies was in the communications block described above. Timing problems were particularly difficult to isolate and cure. One problem cast considerable suspicion on the ASC-15 implementation of the cross-range steering equations. E r r o r s of types one o r two above were suspected; but, in truth, a one computation cycle transport l a g in execution of the command was being introduced by the communication block. This transport lag caused a decrease in the system's stability margin which was causing the undesirable behavior. . A fourth type of e r r o r was uncovered when attempts m) were made to determine the source of wlargeM(200 navigation e r r o r s observed by comparing the separate 6D and ASC-15 values of the vehicle's position near cutoff. Once again, programming o r conceptual e r r o r s were suspected, but these were eliminated in succession until such an explanation was illogical. Since the source of the e r r o r was not the flight program, the two simulators were suspected. The e r r o r was finally traced to the 6D, heretofore accepted a s "perfect. " Correction of the 6D decreased the navigation differences to an explainable 30 meters a t cutoff. Thus, e r r o r s in the simulators themselves were the fourth type found . Complete acceptance of both the airborne digital computer and all-digital checkout occurred after the SA-6 flight. This particular flight had an unexpected, unplanned, early engine shutdown in the f i r s t stage. The guidance implementation in the ASC-15 corrected for the perturbation and succeeded in placing the vehicle in the proper orbit. Of the system tests, the all-digital simulation alone had: a) discovered certain scaling problems which would have prevented proper program operation in the event of an early-engine shutdown, and b) subsequently, verified that the corrected flight program would successfully handle any engine shutdown condition. B. Simulator Uses The basic 6D vehicle simulator is used with and without the BBB LVDC model. When used without the BBB s i m u l ~ t o r ,a FORTRAN representation of the equations solved by the LVDC is substituted. In this configuration, the simulator is used for studies such a s the determination of the best form for implementation of navigation, guidance, and control equations in the LVDC. The primary uses of the over-all simulation (GD/BBB) a r e for verification of the flight program and f o r postflight evaluation of the guidance system. The BBB simulator is also used alone without the 6D vehicle portion in the postflight evaluation effort. \; 'I 1. Studies and Analysis. The 6 ~ / ~ 0 ~ T ~ A ~ m o d is normally used for all studies and analyses. This version executes in approximately one-half real time on the IBM 7094 11. Examples of studies performed with the regular 6D are: a) verification of logic used to initiate vehicle sequences, b) navigation and guidance accuracy, c) consumption of roll attitude control system fuel, d) verification of backup and e r r o r path logic in the flight program, e ) determination of acceptable methods for guidance during mixture ratio shift in the 52 engine, and f) algorithm studies. A variation of this GD/FORTRAN configuration i s used for simulation of free fall o r orbital flight. This version is used for verification of the proposed orbital navigation scheme, determination of three axis attitude control system fuel consumption, and determination of times of passage over ground stations. These studies a r e performed in several phases, requiring slightly different versions of the basic simulation. In the initial studies, a simplified FORTRAN model of the guidance computer i s adequate to study stability problems and basic implementation methods. Later studies require that exact algorithms be used in the FORTRAN model to study the accuracy problem, algorithm convergence, and scaling. Accuracy estimates a r e obtained by comparison with an ideal guidance scheme, based on calculus of variations, and an ideal vehicle. Vehicle attitude during the orbital mission phase is maintained by a reaction jet control system. The attitude control scheme (i .e , logical decisions, SUPPLEMENT TO IEEE TRANSACTIONS ON AEROZ)PACE AND ELECTRONIC SYSTEMS . VOL. AES-2, NO 4 JULY. 1966 �computation of e r r o r commands, etc .), i s implemented in the LVDC. Considerations such a s control scheme, implementation, and limit cycles have a significant effect on fuel tank size. These a r e important considerations from a weight and volume standpoint. The vehicle simulation i s used for these studies to select the best compromise between control scheme and implementation and fuel consumption required to maintain the vehicle attitude within acceptable bounds. The FORTRAN model is adequate, although algorithms must be included in the simulation. It can be seen that the several versions of the basic simulator a r e used quite extensively and all are necessary to adequately define and specify the guidance computer program necessary to perform a given mission for a particular vehicle. 2 . Flight Program Verification. After the flight program specifications a r e completely defined and the program written, a systematic procedure is necesslry to verify that the finished program meets the specifications and is adequate to handle expected perturbations. There hs a general agreement that, once the program speciflcations a r e defined, the flight program must not limit mission success. That is, any vehicle failures o r perturbations that a r e sufficient to fail the flight program will already have caused a mission failure. The flight program must be written to accommodate uncertainties in vehicle parameters and certain noncritical hardware failures that do not cause a mission failure. Examples of vehicle perturbations include uncertainties in fuel load, vehicle mass, center of gravity location, m a s s flow rates, engine specific impulse, and thrust misalignments. ,In addition to these vehicle uncertainties, specifications, such a s accomplishment of mission objectives with a failure of one first-stage engine after a specified time from liftoff, may exist. Mission objectives must also be met if certain discrete inputs to the LVDC a r e either missed by the computer o r not issued by the vehicle's stages. Therefore, backups must be provided in the flight program for these discretes. The capability of the flight program to compensate for these vehicle failures and uncertainties, and meet required cutoff conditions a t the same time, must be verified. A systematic procedure f o r this verification has been established using the vehicle simulation combined with the BBB guidance computer simulation. In order to verify that the flight program was correctly written, it must be used in this effort. Therefore, the actual flight program tape is loaded into the BBB simulator. This verification also provides an opportunity to detect and correct any programming, scaling, o r constant e r r o r s in the actual flight program. Simulator runs a r e made with vehicle failures and uncertainties inserted singly and in combination to simulate the worst possible conditions under which the flight program can reasonably be expected to perform. Between twenty and thirty pertarbation runs a r e necessary with the simulator to completely verify the program operation. The ability of the vehicle to achieve stated mission objectives, such as a pre-determined orbit o r specified impact area, is evaluated. In addition to verifying proper operation of the flight program, this procedure yields an e s t k a t e of guidance and control system performance that is necessary in postflight evaiuation of the guidance and control system. Both the nominal behavior of each guidance and control variable and the variations a r e available from which a predicted flight envelope can be drawn. 3. Postflight Evduation. Although the simulator described here has ~ o kte n used for postflight analysis of the guidance and comtrol s y s t b , an equivalent simulator was used f o r this purpose on the Saturn I , Block I1 vehicles. The two configurations used in this analysis a r e the full ~I)/P)BB simulator and the BBB simulator alone. The primary posfflight use of the GD/BBB simulator i s im malfunction analysis. The computations done inflight a r e reconstructed to determine if the guidance computer performed correctly under the circumstances. This application was r e quired only once on the Saturn I , Block I1 s e r i e s when an engine failed during first-stage burn. That particular flight (SA-6) was reconstructed by two methods: a) a trial-and-error method of thrust and mass flow rate adjuskment in the remaining engines, and b) using actual reconstructed thrust and center of gravity data from the postflight propulsion analysis. Results from both methods agreed closely, both with each other and with telemetry reconstruction of the flight, a t f i r s t stage cutoff. Table 111. B. 1 compares each of four sets of positions and velocities with the computer telemetered positions at f i r s t stage cutoff. The four sets of points were obtained a s follows: case 1 corresponds to method 1 above. That is, the telemetered position and velocity values a r e compared with a GD/BBB simulation in which thrust and mass flow rates have been adjusted. Case 2 compares telemetered quantities with a ~ D / B B Brun a s described in method 2. Case 3 compares telemetry data with range tracking information. Case 4, the worst of the lot, makes a oomparison between the telemetered quantities and the output of a GD/BBB simulation in which thrust and mass flow rate for the failed engine alone had been modified. All differences shown in the table, except Case 4, were less than 1% of the actual position o r velocity. Differences for Case 4 ranged to slightly over 2%. This example illustrates that the simulator can be used to reconstruct flight conditions quite closely and is useful in determining whether or not the guidance SUPPLEMENT T O IEEE TRANSACTIONS O N AEROSPACE AND ELECT RONIC SYSTEMS VOL. AES-2, NO. 4 JULY, 1966 817 �computer operated correctly after the malfunction. It also demonstrates the good agreement between 6D simulation of the vehicle and the actual vehicle performance. The second application of the simulator in postflight analysis requires the use of the BBB simulator alone. In this application the correct operation of the guidance computer hardware i s determined by using actual telemetered flight con~puterinputs a s simulator inputs. The simulated computer is then allowed to compute for one computation cycle, and the data generated by the simulator is compared to corresponding data from flight computer telemetry. If these data do not compare bit f o r bit, the cause is determined. if the cause is in the computer hardware, a more detailed analysis of the computer operation during that computation cycle will follow in an attempt to pinpoint the hardware failure. Only the data telemetered fromthe guidance computer can be compared in this manner, which impliss that every operation of the guidance comput5r cannot be monitored using this technique. Table 111. B . 2 shows the amount of data examined with this procedure f o r two typical Saturn I , Block I1 vehicles. Not all telemetered data can be compared since a portion of the data a r e input data, and other data yield information on hardware operation that is not simulated. This analysis tool is not a guaranteed method of locating computer faults. However, it will permit the determination of the a r e a of possible malfunctions in the computer. In addition,!it increases confidence in the proper operation of the h i d a n c e computer during a flight. TABLE 111. B. 1 COMPARISON OF TRAJECTORY RECONSTRUCTION DATA IN PLANE VELOCITY ERROR DIFFERENCES Y X DATA SOURCE IN PLANE POSITION ERROR DIFFERENCES Y X Case 1 0.132% 0.537% 0.176% 0.315% Case 2 0.135% 0.293% 0.035% 0.223% 0.057% 0.187% 0.078% 0.095% 1.680% 0.576% 2.040% Case 3 - Case 4 Case 1: Case 2: Case 3: Case 4: - 0.782% Trial and e r r o r adjustment of thrust and mass flow rate. Thrust and mass data from postflight propulsion analysis. Range tracking data. Reduction of total thrust and mass flow rate only to account for failed engine. Comparison a t f i r s t stage cutoff. SUPPLEMENT TO IEEE TRANSACTIONS ON AEROSPACE AND ELECTRONIC SYSTEMS - VOL. AES-2, NO. A JULY. 1 9 h h �f, I I T Research I n s t i t u t e (NAS8-20129), Low T h r u s t P r e p a r a t i o n of t h e f i n a l r e p o r t i s a l s o beginning on t h i s c o n t r a c t w i t h some s m a l l c o n s i d e r a t i o n being g i v e n t o t h e e f f e c t of o b l a t e n e s s and t h e three-dimensional guidance problem, B r i e f e x e r c i s e of a s p i r a l d e s c e n t guidance scheme, based on s t e a d y - s t a t e c i r c u l a r v e l o c i t y c o n d i t i o n s being maintained throughout t h e f l i g h t t o provide a v e l o c i t y r e f e r e n c e o r c o r r e l a t e d v e l o c i t y , has been r e p o r t e d , g, Republic A v i a t i o n (NAS8-20130), O p t i m i z a t i o n Theory and C e l e s t i a l Mechanics The bimonthly p r o g r e s s r e p o r t f o r March and A p r i l on t h i s c o n t r a c t i n d i c a t e s t h a t t h e major p o r t i o n of work under t h i s cont r a c t has been completed. D r , MorrisBn i n d i c a t e s f u r t h e r t h a t t h e remaining time i n t h e c o n t r a c t w i l l be used i n c l e a r i n g up d e t a i l s , checking r e s u l t s and p r e p a r a t i o n of t h e % i n a l r e p o r t , No d i f f i c u l t i e s i n completing the c o n t r a c t on s c h e d u l e a r e a n t i c i p a t e d . h, Vanderbil t U n i v e r s i t y (NAS8-203711, A p p l i c a t i o n s of COV t o T r a j e c t o r y Problems The p r o g r e s s r e p o r t f o r A p r i l on t h i s c o n t r a c t i n d i c a t e s t h a t work was continued on t h e m u l t i - s t a g e t r a j e c t o r y o p t i m i z a t i o n problem i n i t i a t e d under t h e preceding c o n t r a c t NAS8-2619, Work was a l s o i n i t i a t e d , through s t u d i e s of s t e e p e s t d e s c e n t and v a r i o u s o t h e r d i r e c t methods, t o improve computational procedures i n d i r e c t methods, D r , Boyce f n d i c a t e s t h a t work w i l l c o n t i n u e i n t h e same a r e a s d u r i n g t h e n e x t r e p o r t i n g p e r i o d . D. O p t i m i z a t i o n Theory Branch 1, In-House a t t e m p t s t o f i n d f i x e d feedback g a i n s producing p e r f o r m n c e comparable t o t h e optimum time r e s p o n s e of a system s u b j e c t e d t o d e t e r m i n i s t i c A s u i t a b l e i t e r a t i o n technique f o r s o l v i n g t h e n o n l i n e a r disturbances d i f f e r e n t i a l e q u a t i o n s and two-point boundary v a l u e problems has n o t been found; however, f i r s t a t t e m p t s a t a p p l y i n g a quas i - l i n e a r i z a t i o n method f o r s o l u t i o n of s u c h problems have g i v e n promising r e s u l t s , . 2. Contractors a. Northrop Schedule Order #1 Objectives: (1) To i n v e s t i g a t e load r e l i e f systems f o r t h e S a t u r n V/Voyager, and ( 2 ) t o determine t h e a p p l i c a b i l i t y of l e a r n i n g systems t o b o o s t e r c o n t r o l and o f f - l i n e problem s o l v i n g , � Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Saturn V Collection Relation A related resource <a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener">View the Saturn V Collection finding aid in ArchivesSpace</a> Identifier An unambiguous reference to the resource within a given context Saturn V Collection Description An account of the resource <p>The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html">here,<span> </span></a><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html">here,<span> </span></a>and<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html">here.</a>) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.</p> <p>Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.</p> <p>A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.</p> Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context spc_stnv_000058 Title A name given to the resource "All Digital Simulation of Saturn I, IB, and V: Boost Vehicle and Guidance Control Systems." Alternative Title An alternative name for the resource. The distinction between titles and alternative titles is application-specific. IBM No. 66-894-0008 Description An account of the resource The introduction notes, "The Saturn V launch vehicle is being developed by the National Aeronautics and Space Administration's George C. Marshall Space Flight Center for Project Apollo; Saturn I and Saturn IB vehicles are providing the early testing and support for Project Apollo. The nerve center of the Saturn is its guidance and control system. An airborne digital computer provides the link which closes both the guidance and control loops,making verification of the flight computer program of vital importance. During a powered flight this onboard digital computer program can be divided into four major parts:a) guidance, including navigation, b) control, c) vehicle sequencing, and d) computer telemetry." Creator An entity primarily responsible for making the resource Carson, W. D. Eubank, F. W. Poupard, R. E. Steele, T. D. International Business Machines Corporation. Federal Systems Division Date A point or period of time associated with an event in the lifecycle of the resource 1966-07-01 Temporal Coverage Temporal characteristics of the resource. 1960-1969 Subject The topic of the resource Saturn Project (U.S.) Project Apollo (U.S.) Saturn launch vehicles Airborne/spaceborne computers Apollo spacecraft Computerized simulation Digital simulation Type The nature or genre of the resource Reports Text Source A related resource from which the described resource is derived Saturn V Collection Box 17, Folder 60 University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource spc_stnv_000051_000074 https://digitalprojects.uah.edu/files/original/20/10377/someselephysanthandhumaengrdata_030807101534.pdf 4415d4e7b93cf0a49e72951ef1414b8a Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Saturn V Collection Relation A related resource <a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener">View the Saturn V Collection finding aid in ArchivesSpace</a> Identifier An unambiguous reference to the resource within a given context Saturn V Collection Description An account of the resource <p>The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html">here,<span> </span></a><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html">here,<span> </span></a>and<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html">here.</a>) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.</p> <p>Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.</p> <p>A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.</p> Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context someselephysanthandhumaengrdata_030807101534.pdf spc_stnv_000831 Title A name given to the resource "Some select physiological, anthropometric, and human engineering data useful in vehicle design and logistic problems of space flight operations." Description An account of the resource Report No. DSP-TM-2-60 31 p.; Pages which were blank (not scanned): 2, 26, 28 Creator An entity primarily responsible for making the resource Carter, J.W. Date A point or period of time associated with an event in the lifecycle of the resource 1960-02-24 Temporal Coverage Temporal characteristics of the resource. 1960-1969 Subject The topic of the resource Saturn project Astronautics--Human factors Space flight--Physiological aspects Engineering Type The nature or genre of the resource Text Memorandums Source A related resource from which the described resource is derived Saturn V Collection Box 4, Folder 32 University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource spc_stnv_000825_000849 Is Referenced By A related resource that references, cites, or otherwise points to the described resource. http://libarchstor.uah.edu:8081/repositories/2/archival_objects/16599 https://digitalprojects.uah.edu/files/original/204/14537/IMG_2602.jpg 5316ea6b629fe64415732bbee1c26101 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context HON 399 Research in London Title A name given to the resource HON 399 Research in London Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Photo of The Palmerstone Gold Chocolate Cups Description An account of the resource This is a photo of The Palmertstone Gold Chocolate Cups. This photo was taken during the UAH Study Abroad to London. These cups are located at the British Museum. These cups were created by John Cartier in 1700. Creator An entity primarily responsible for making the resource Cartier, John Foltz, Sarah Date A point or period of time associated with an event in the lifecycle of the resource 1700 Subject The topic of the resource Gold Cups Rings Source A related resource from which the described resource is derived The British Museum, 2005,0604.2 Is Part Of A related resource in which the described resource is physically or logically included. Sir Hans Sloane: Inventor of Chocolate Milk? by Sarah Foltz, HON 399, Research in London, Spring 2024 Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. HON 399 Honors College Student Projects Study Abroad https://digitalprojects.uah.edu/files/original/109/7554/r01c01-20.pdf 81067c3e54528841a5c86fb5bb887790 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Series 01, Subseries C: Cabaniss Personal Correspondence Title A name given to the resource Series 01, Subseries C: Cabaniss Personal Correspondence Description An account of the resource Subseries C, Cabaniss Personal Correspondence (CPC), consists of correspondence from letters from friends, relatives, and their children. Most of the family correspondence involves these children and families of S. D. Cabaniss, and his brothers and sisters who appeared to have been enormous burdens in these difficult years. These papers are sorted "to whom," "from whom," and then chronologically. Still Image A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context r01c01-20 Title A name given to the resource Carver, ____ to Cabaniss, Charles Eugene, 1869? Relation A related resource r01c-210910 Creator An entity primarily responsible for making the resource Carver Temporal Coverage Temporal characteristics of the resource. 1860-1869 Subject The topic of the resource Neighborhoods Love Rural life Corn as food Cotton Type The nature or genre of the resource Correspondence Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Source A related resource from which the described resource is derived Frances C. Roberts Collection, Series 1, Subseries C, Box 1, Folder 20, University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama https://digitalprojects.uah.edu/files/original/20/11044/desconofgroddasinsat1BVESE_020108113351.pdf 1e360b54140cd77106e2d18e828e9fa3 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Saturn V Collection Relation A related resource <a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener">View the Saturn V Collection finding aid in ArchivesSpace</a> Identifier An unambiguous reference to the resource within a given context Saturn V Collection Description An account of the resource <p>The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html">here,<span> </span></a><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html">here,<span> </span></a>and<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html">here.</a>) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.</p> <p>Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.</p> <p>A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.</p> Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context desconofgroddasinsat1BVESE.pdf spc_stnv_000229 Title A name given to the resource "Design Concepts of Ground DDAS in Saturn 1B/V ESE." Description An account of the resource In the Saturn IB/V programs the sheer quantity of data required for computer processing and ESE display makes it necessary to provide an efficient data acquisition system. For much of the data originating in the launcher this requirement is satisfied by the Ground Digital Data Acquisition System (DDAS). This paper provides a technical description of the Ground DDAS with emphasis placed on the unique design concepts of this telemetry system. Creator An entity primarily responsible for making the resource Casby, J. P. Patton, F. T. Petcher, M. B. Date A point or period of time associated with an event in the lifecycle of the resource 1967-01-01 Temporal Coverage Temporal characteristics of the resource. 1960-1969 Subject The topic of the resource Saturn project Data acquisition Astronautics--Communication systems Saturn 1B launch vehicles Saturn 5 launch vehicles Telemetry Type The nature or genre of the resource Text Essays Source A related resource from which the described resource is derived Saturn V Collection Box 20, Folder 2 University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource spc_stnv_000225_000249 Is Referenced By A related resource that references, cites, or otherwise points to the described resource. <a href="http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17585"> View this item in ArchivesSpace </a> https://digitalprojects.uah.edu/files/original/20/10979/funcmanainnasa[HHN-53]_073007162103.pdf.pdf 37af98a4c037da8f82efe2680a2426e8 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Saturn V Collection Relation A related resource <a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener">View the Saturn V Collection finding aid in ArchivesSpace</a> Identifier An unambiguous reference to the resource within a given context Saturn V Collection Description An account of the resource <p>The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html">here,<span> </span></a><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html">here,<span> </span></a>and<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html">here.</a>) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.</p> <p>Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.</p> <p>A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.</p> Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context funcmanainnasa(HHN-53)_073007162103.pdf spc_stnv_000308 Title A name given to the resource "Functional Management in NASA." Alternative Title An alternative name for the resource. The distinction between titles and alternative titles is application-specific. HHN-53 Description An account of the resource This is a Comment Edition of Historical Note No. 53 prepared by a summer employee of the NASA Historical Staff (APPH). The author has agreed to integrate comments and corrections submitted by critical readers, a normal process of validation for all historical reports and studies. Creator An entity primarily responsible for making the resource Casper, Jonathan D. Date A point or period of time associated with an event in the lifecycle of the resource 1965-08-01 Temporal Coverage Temporal characteristics of the resource. 1960-1969 Subject The topic of the resource Saturn project History Industrial management Type The nature or genre of the resource Text Historical Reviews Source A related resource from which the described resource is derived Saturn V Collection Box 14, Folder 45 University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource spc_stnv_000300_000324 Is Referenced By A related resource that references, cites, or otherwise points to the described resource. <a href="http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17192"> View this item in ArchivesSpace </a> https://digitalprojects.uah.edu/files/original/20/10661/Propkey.pdf 824e40e231750ce5bd9e09b3e28305fe Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Saturn V Collection Relation A related resource <a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener">View the Saturn V Collection finding aid in ArchivesSpace</a> Identifier An unambiguous reference to the resource within a given context Saturn V Collection Description An account of the resource <p>The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html">here,<span> </span></a><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html">here,<span> </span></a>and<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html">here.</a>) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.</p> <p>Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.</p> <p>A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.</p> Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Propkey.pdf spc_stnv_000629 Title A name given to the resource "Propulsion : the key to space travel." Description An account of the resource Cover has: P. D. Castenholz and H. K. Griggs, Advanced Systems, Advanced Projects Department. D. W. Hege, Manager, Advanced Projects. Paper regarding the importance of propulsion technology and the future missions that would require advancements in that field. Creator An entity primarily responsible for making the resource Castenholz, P. D. Date A point or period of time associated with an event in the lifecycle of the resource 1963-05-01 Temporal Coverage Temporal characteristics of the resource. 1960-1969 Subject The topic of the resource Saturn project Propulsion Spacecraft propulsion Space vehicles--Propulsion systems Space flight Type The nature or genre of the resource Text Essays Source A related resource from which the described resource is derived Saturn V Collection Box 8, Folder 29 University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource spc_stnv_000625_000649 Is Referenced By A related resource that references, cites, or otherwise points to the described resource. http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17326 https://digitalprojects.uah.edu/files/original/20/10840/mateinspacexpl_080107092258.pdf 5714c04402b5bab2ffc99dcb096624f2 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Saturn V Collection Relation A related resource <a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener">View the Saturn V Collection finding aid in ArchivesSpace</a> Identifier An unambiguous reference to the resource within a given context Saturn V Collection Description An account of the resource <p>The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html">here,<span> </span></a><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html">here,<span> </span></a>and<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html">here.</a>) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.</p> <p>Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.</p> <p>A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.</p> Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context mateinspacexpl_080107092258.pdf spc_stnv_000441 Title A name given to the resource "Materials in space exploration." Description An account of the resource This paper presents a general review of major structural alloys that have been used in liquid rockets and space vehicles, the current state-of-the-art as applied to the Apollo launch vehicle systems, and discusses some materials currently under development for future requirements in vehicles for space exploration. Some aspects of the importance of corrosion resistant materials and suitable protective measures are discussed, as applied to both flight hardware and associated ground support equipment. Creator An entity primarily responsible for making the resource Cataldo, C. E. Date A point or period of time associated with an event in the lifecycle of the resource 1965-10-21 Temporal Coverage Temporal characteristics of the resource. 1960-1969 Subject The topic of the resource Saturn project Apollo project Liquid propellant rockets Space vehicles Spacecraft construction materials Type The nature or genre of the resource Text Speeches Source A related resource from which the described resource is derived Saturn V Collection University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource spc_stnv_000425_000449 https://digitalprojects.uah.edu/files/original/20/10973/fligcontcompsatspaveh_051107114001.pdf fa184ce60c8c0a7c8882b45209b98aff Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource Saturn V Collection Relation A related resource <a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener">View the Saturn V Collection finding aid in ArchivesSpace</a> Identifier An unambiguous reference to the resource within a given context Saturn V Collection Description An account of the resource <p>The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html">here,<span> </span></a><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html">here,<span> </span></a>and<span> </span><a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html">here.</a>) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.</p> <p>Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.</p> <p>A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.</p> Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context fligcontcompsatspaveh_051107114001.pdf spc_stnv_000302 Title A name given to the resource "Flight Control Computer for Saturn Space Vehicles." Description An account of the resource The flight control computer for Saturn receives attitude signals from the stable platform, rate signals from rate gyros or lead networks, and angle-of-attack information from body-fixed accelerometers or other sensors. Creator An entity primarily responsible for making the resource Caudle, John M. (John Milton), 1921- Colbert, Donald C Date A point or period of time associated with an event in the lifecycle of the resource 1962-10-01 Temporal Coverage Temporal characteristics of the resource. 1960-1969 Subject The topic of the resource Saturn project Saturn launch vehicles Flight control Type The nature or genre of the resource Text Reports Source A related resource from which the described resource is derived Saturn V Collection Box 7, Folder 31 University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Relation A related resource spc_stnv_000300_000324 Is Referenced By A related resource that references, cites, or otherwise points to the described resource. <a href="http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17263"> View this item in ArchivesSpace </a> https://digitalprojects.uah.edu/files/original/108/7029/r01b03-05.pdf f6c616fabcd20f418153e64d69af6346 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Series 01, Subseries B: Cabaniss Professional Business Title A name given to the resource Series 01, Subseries B: Cabaniss Professional Business Description An account of the resource Sub series B (CPB) deals with a small, but active, legal practice of Septimus Cabaniss with his various partners, who included men considered to be outstanding lawyers in the state, from the 1890s to 1938 at the office on the town Square. He studied law in Huntsville under Silas Parsons and practiced law with Leroy Pope Walker, Robert C. Brickell, and Francis P. Ward. These papers are sorted by year, except when an obvious grouping of an estate is evident. The papers continue through professional activities at the Madison County Courthouse including those of his son, James Budd Cabaniss, and his daughter, Fanny Cabaniss, who were clerks of the Chancery Court and a few papers of his son, Septimus, Jr., who owned a bookstore for a brief period. Still Image A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context r01b03-05 Title A name given to the resource Legal and court documents, 1853 Relation A related resource r01b-210907 Creator An entity primarily responsible for making the resource Cavett, Moses Temporal Coverage Temporal characteristics of the resource. 1850-1859 Subject The topic of the resource Debt Banks and banking Travel Medical care Check cashing Blacksmithing Type The nature or genre of the resource Estate Receipts Promissory notes Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Source A related resource from which the described resource is derived Frances C. Roberts Collection, Series 1, Subseries B, Box 3, Folder 5, University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama https://digitalprojects.uah.edu/files/original/120/7852/r02h05-05.pdf 7e861526943c38f7a547cc3aa60983b2 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context Series 02, Subseries H: Mementos, photos, and cards Title A name given to the resource Series 02, Subseries H: Mementos, photos, and cards Still Image A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context r02h05-05 Source A related resource from which the described resource is derived Frances Cabaniss Roberts Collection Series 2, Subseries H, Box 5, Folder 5 University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama Title A name given to the resource Frances C. Roberts Photos, Friend and miscellaneous Relation A related resource r02h-210915 Creator An entity primarily responsible for making the resource Caylor, Mary Jane Roberts, Frances C. Temporal Coverage Temporal characteristics of the resource. 1980-1989 Subject The topic of the resource Awards Portraits Professional correspondence Roberts, Frances C. Type The nature or genre of the resource Correspondence Photographs Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. https://digitalprojects.uah.edu/files/original/207/14701/hiv-incidence-2023-04.jpg eacc4861110d0f72c897922cb0ecedb6 Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Title A name given to the resource RCEU Faith Based AIDS Responses in 1980s and 1990s Alabama Creator An entity primarily responsible for making the resource Morgon Newquist Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context hiv-incidence-2023-04 Title A name given to the resource HIV Incidence in the United States 2021 Description An account of the resource A chart of the new HIV infections in the United States in 2021 by geographic region Creator An entity primarily responsible for making the resource Center for Disease Control Publisher An entity responsible for making the resource available hiv.gov Date A point or period of time associated with an event in the lifecycle of the resource 2023-12-07 Temporal Coverage Temporal characteristics of the resource. 2020-2029 Subject The topic of the resource HIV (Viruses) AIDS (Disease) Source A related resource from which the described resource is derived US Statistics, HIV.gov https://www.hiv.gov/hiv-basics/overview/data-and-trends/statistics Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections. Type The nature or genre of the resource Charts https://digitalprojects.uah.edu/files/original/129/9105/r07_03-04.pdf a28b41378bdf2d2794fc93cd3cb4dbe3 Still Image A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials. Dublin Core The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/. Identifier An unambiguous reference to the resource within a given context r07_03-04 Source A related resource from which the described resource is derived Series 7, Box 3, Folder 4 Title A name given to the resource Historic Places in Central Alabama, A Preliminary Inventory, 1973 Relation A related resource r07-211013 Description An account of the resource This section contains a report cataloging historical events and sites in different counties in Alabama. One section centers around different Native American tribes and their histories/developments. Creator An entity primarily responsible for making the resource Central Alabama Regional Planning and Development Commission Date A point or period of time associated with an event in the lifecycle of the resource 1973 Temporal Coverage Temporal characteristics of the resource. 1970-1979 Subject The topic of the resource Native Americans Historic markers Historic sites Dwellings Wars Counties--Alabama Historic buildings Type The nature or genre of the resource Booklets Sketches Maps Surveys Lists Charts Drawings Photographs Language A language of the resource en Rights Information about rights held in and over the resource This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.