Search NASA⌕ Search

SEARCH · Search NASA

Results for “Capsule networks”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

14 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2019

Challenges Using the Linux Network Stack for Real-Time Communication

Starting in the early 2000s, human-in-the-loop (HITL) simulation groups at NASA and the Air Force Research Lab began using the Linux network stack for some real-time communication. More recently, SpaceX has adopted Ethernet as the primary bus technology for its Falcon launch vehicles and Dragon capsules. As the Linux network stack makes its way from ground facilities to flight critical systems, it is necessary to recognize that the network stack is optimized for communication over the open Internet, which cannot provide latency guarantees. The Internet protocols and their implementation in the Linux network stack contain numerous design decisions that favor throughput over determinism and latency. These decisions often require workarounds in the application or customization of the stack to maintain a high probability of low latency on closed networks, especially if the network must be fault tolerant to single event upsets.

Madden, Michael M.↗
NASA NTRS2000

NASA Participation in the ISAS MUSES C Asteroid Sample Return Mission

NASA and Japan's Institute of Space and Astronautical Science (ISAS) have agreed to cooperate on the first mission to collect samples from the surface of an asteroid and return them to Earth for in-depth study. The MUSES-C mission will be launched on a Japanese MV launch vehicle in January 2002 from Kagoshima Space Center, Japan, toward a touchdown on the asteroid Nereus in September 2003. A NASA-provided miniature rover will conduct in-situ measurements on the surface. The asteroid samples will be returned to Earth by MUSES-C via a parachute-borne recovery capsule in January 2006. NASA and ISAS will cooperate on several aspects of the mission, including mission support and scientific analysis. In addition to providing the rover, NASA will arrange for the testing of the MUSES-C re-entry heat shield at NASA/Ames Research Center, provide supplemental Deep Space Network tracking of the spacecraft, assist in navigating the spacecraft and provide arrangements for the recovery of the sample capsule at a landing site in the U. S. Scientific coinvestigators from the U.S. and Japan will share data from the instruments on the rover and the spacecraft. They will also collaborate on the investigations of the returned samples. With a mass of about I kg, the rover experiment will be a direct descendant of the technology used to build the Sojourner rover. The rover will carry three science instruments: a visible imaging camera, a near-infrared point spectrometer and an alpha X ray spectrometer. The solarpowered rover will move around the surface of Nereus collecting imagery data which are complimentary to the spacecraft investigation. The imaging system will be capable of making surface texture, composition, and morphology measurements at resolutions better than 1 cm. The rover will transmit this data to the spacecraft for relay back to Earth. Due to the microgravity environment on Nereus, the rover has been designed to right itself in case it flips over. Solar panels on all sides of the rover will ensure that enough power will always be available to the rover to activate the motors needed to turn over. Posable struts will allow the rover to position its chassis such that the camera can be pointed straight down at the surface or straight up at the sky. The presentation will describe the mission, scientific objectives and current state of the rover in detail.

Jones, Ross↗
NASA NTRS2011

Hayabusa Re-Entry: Trajectory Analysis and Observation Mission Design

On June 13th, 2010, the Hayabusa sample return capsule successfully re-entered Earth s atmosphere over the Woomera Prohibited Area in southern Australia in its quest to return fragments from the asteroid 1998 SF36 Itokawa . The sample return capsule entered at a super-orbital velocity of 12.04 km/sec (inertial), making it the second fastest human-made object to traverse the atmosphere. The NASA DC-8 airborne observatory was utilized as an instrument platform to record the luminous portion of the sample return capsule re-entry (~60 sec) with a variety of on-board spectroscopic imaging instruments. The predicted sample return capsule s entry state information at ~200 km altitude was propagated through the atmosphere to generate aerothermodynamic and trajectory data used for initial observation flight path design and planning. The DC- 8 flight path was designed by considering safety, optimal sample return capsule viewing geometry and aircraft capabilities in concert with key aerothermodynamic events along the predicted trajectory. Subsequent entry state vector updates provided by the Deep Space Network team at NASA s Jet Propulsion Laboratory were analyzed after the planned trajectory correction maneuvers to further refine the DC-8 observation flight path. Primary and alternate observation flight paths were generated during the mission planning phase which required coordination with Australian authorities for pre-mission approval. The final observation flight path was chosen based upon trade-offs between optimal viewing requirements, ground based observer locations (to facilitate post-flight trajectory reconstruction), predicted weather in the Woomera Prohibited Area and constraints imposed by flight path filing deadlines. To facilitate sample return capsule tracking by the instrument operators, a series of two racetrack flight path patterns were performed prior to the observation leg so the instruments could be pointed towards the region in the star background where the sample return capsule was expected to become visible. An overview of the design methodologies and trade-offs used in the Hayabusa re-entry observation campaign are presented.

Cassell, Alan M.↗
NASA NTRS2018

Nasa's Launch Communications Ground Segment for the 21st Century Florida Spaceport

The National Aeronautics and Space Administration (NASA) Near Earth Network (NEN) Project is implementing a new launch communications ground segment to provide services for the next generation of human and robotic space exploration systems. It will deliver unique and advanced capabilities to accelerate the transformation of Kennedy Space Center into a multi-user spaceport in cooperation with the United States Air Force (USAF). The project has leveraged commercial technologies and remote operations concepts matured in NASAs orbiting satellite ground systems to achieve dramatic lifecycle cost efficiencies as compared to the space shuttle-era ground segment. The purpose of this paper is to discuss the development history, capabilities and anticipated use cases of the NEN Launch Communications Segment (NEN LCS).The NASA Kennedy Space Center is co-located with the USAF Eastern Launch Range at Cape Canaveral, Florida. The USAF operates two launch communications ground stations, but they are not designed to transmit voice, commands or other data to the launch vehicle or astronauts. The bi-directional uplink-downlink communications responsibility for human missions has historically resided with the Goddard Space Flight Center in Greenbelt, Maryland. Several market analyses and feasibility studies investigating concepts to provide NASAs next generation launch communications services were performed during the Constellation Program prior to its cancellation in 2009, and as part of the Kennedy Space Centers follow-on efforts to transform itself into a 21st century multi-user spaceport. In 2012, the Kennedy Space Center and the USAF 45th Space Wing jointly led a study to analyze the market needs of current and future launch systems and assess the operational deficiencies of the Eastern Range infrastructure. The study team issued several recommendations, two of which ultimately became driving operational capability requirements for the NEN LCS: increased telemetry data rates of at least 20 Mbps, and S-band uplink capability. Additional capabilities identified in the requirements development process include spread spectrum modulation support, LDPC 12 and 78 error correction codes, support for IRIG-106 and CCSDS data formats, automated best source selection, and Space Link Extension (SLE) services for data distribution. The NEN LCS is comprised of two permanent ground stations, the new Kennedy Uplink Station (KUS) and refurbished Ponce de Leon (PDL) station. Both stations are remotely operated from the Global Monitor and Control Center at Wallops Flight Facility. This core architecture is extensible through host-tenant arrangements with the U.S. Air Force and deployable assets, enabling agile, tailored and robust solutions to meet the needs of civil, commercial or military customers. The NEN LCS has three use cases:1.To provide agile, tailored and robust launch communications solutions to Florida spaceport customers2.To provide orbital communications services to near-earth customers 3.To provide an experimental proving ground for Space Mobile Network concepts and technologies The NEN LCS driving mission is to support the bi-directional link with the Orion crew capsule and two 20 Mbps telemetry links from the Space Launch System core stage on Exploration Mission-1, the first integrated flight of NASAs flagship human exploration systems.

Roberts, Christopher J.↗
NASA NTRS2006

Interfacing with USSTRATCOM and UTTR during Stardust Earth Return

The Stardust Sample Return Capsule separated from the main spacecraft four hours prior to atmospheric entry. Between this time and the time at which the SRC touched down at the Utah Test and Training Range, two organizations external to JPL were involved in tracking the Sample Return Capsule. Orbit determination for the Stardust spacecraft during deep space cruise, the encounters of asteroid Annefrank and comet Wild 2, and the final approach to Earth used X-band radio metric Doppler and range data obtained through the Deep Space Network. The SRC lacked the electronics needed for coherently transponded radio metric tracking, so the DSN was not able to track the SRC after it separated from the main spacecraft. Although the expected delivery accuracy at atmospheric entry was well within the capability needed to target the SRC to the desired ground location, it was still desirable to obtain direct knowledge of the SRC trajectory in case of anomalies. For this reason U.S. Strategic Command was engaged to track the SRC between separation and atmospheric entry. Once the SRC entered the atmosphere, ground sensors at UTTR were tasked to acquire the descending SRC and maintain track during the descent in order to determine the landing location, to which the ground recovery team was then directed. This paper discusses organizational interfaces, data products, and delivery schedules, and the actual tracking operations are described.

Utah Test and Training Range (UTTR)↗
NASA NTRS2008

A GPS Receiver for Lunar Missions

Beginning with the launch of the Lunar Reconnaissance Orbiter (LRO) in October of 2008, NASA will once again begin its quest to land humans on the Moon. This effort will require the development of new spacecraft which will safely transport people from the Earth to the Moon and back again, as well as robotic probes tagged with science, re-supply, and communication duties. In addition to the next-generation spacecraft currently under construction, including the Orion capsule, NASA is also investigating and developing cutting edge navigation sensors which will allow for autonomous state estimation in low Earth orbit (LEO) and cislunar space. Such instruments could provide an extra layer of redundancy in avionics systems and reduce the reliance on support and on the Deep Space Network (DSN). One such sensor is the weak-signal Global Positioning System (GPS) receiver "Navigator" being developed at NASA's Goddard Space Flight Center (GSFC). At the heart of the Navigator is a Field Programmable Gate Array (FPGA) based acquisition engine. This engine allows for the rapid acquisition/reacquisition of strong GPS signals, enabling the receiver to quickly recover from outages due to blocked satellites or atmospheric entry. Additionally, the acquisition algorithm provides significantly lower sensitivities than a conventional space-based GPS receiver, permitting it to acquire satellites well above the GPS constellation. This paper assesses the performance of the Navigator receiver based upon three of the major flight regimes of a manned lunar mission: Earth ascent, cislunar navigation, and entry. Representative trajectories for each of these segments were provided by NASA. The Navigator receiver was connected to a Spirent GPS signal generator, to allow for the collection of real-time, hardware-in-the-loop results for each phase of the flight. For each of the flight segments, the Navigator was tested on its ability to acquire and track GPS satellites under the dynamical environment unique to that trajectory.

Bamford, William A.↗
NASA NTRSDate not supplied

Surviving and Thriving in Space and on Earth's Oceans - Human Logistics and Sustainability Comparisons and Considerations

The human species has a yearning for exploration as evidenced by the extensive historical ocean voyages and expeditions which have led to a massive advancement in the scientific and geodetic knowledge about planet Earth. These global explorations via the oceans have also had strategic, economic, cultural and religious implications and impacts, which have drastically changed the state of humanity and its condition. The transportation network created by ships traveling across the oceans has been supplemented by other transportation networks on land and in the air, creating a global economy that, in general, has improved the human condition leading to better health, longer lives, lower child mortality, better education, political freedom, higher gross national product (GNP) and improved hygiene. The logical extension of this societal trend is to extend the transportation network and human civilization into outer space, beyond the cradle of planet Earth. Our solar system contains vast amounts of natural resources which can be harnessed and used to bootstrap a space economy and related infrastructure by using advanced technologies. Sailing journeys from hundreds of years ago required large vessels and large crews, (in comparison with today’s space capsules). Modern sailors of today are able to complete large voyages, in small vessels, with a minimal crew, comparable in magnitude to modern space travel. This paper will use a systems engineering approach (e.g. using the NASA Human Integration Design Handbook (HIDH), NASA-SP-2010-3407, 2010 and the “Advanced Life Support Baseline Values and Assumptions Document, (BVAD)” NASA-CR-2004-208941, 2004.), to examine and compare the logistics and sustainability aspects of a small crew traveling on Earth's oceans in sailing vessels versus humans traveling in space. The “Mālama Honua Worldwide Voyage” of the Hokule’a, a replica of an ancient Hawaiian double hulled sailing canoe, will be used as a case study. This is the best comparison case since the Polynesian exploration of the vast (and virtually empty) Pacific Ocean is the closest analogue to modern space travel. “"Both are voyages of exploration.” –Shuttle astronaut Lacy Veach. Minimizing waste and maximizing re-use and re-cycling will lead to more efficient logistics and sustainability. In addition, In-Situ Resource Utilization (ISRU) strategies, based on successful Earth based strategies used for many years by sailors will be considered and evaluated for their usefulness. For example, human logistics for a typical space mission are shown in Table 1 and Table 2 (Lopez et al, 2015). Studies show that typical human water consumption in space is projected to be 3.2 kg/day per crew member as shown in Table 2. Data from human sailing voyages around the globe will be examined. Anecdotal evidence indicates that knowledgeable and well-equipped modern sailors, who conserve water, can comfortably live using 1.5 to 5 kg/day per person. This paper will investigate key logistics and sustainability aspects of living in space and compare them quantitatively to similar aspects of living on ocean faring sailing vessels on Earth. Mutually beneficial observations, advanced technologies and modern considerations will be applied within confines of a remote sailing environment, which could be of immense value to both the space faring community and the ocean sailing community.

Space↗
NASA NTRS2020

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA’s Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA’s Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V’s desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V’s assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Gerek Whitman↗
NASA NTRS2020

IV&V Assurance Case Design for Artemis II

As human-rated missions like those in NASA's Artemis program continue to grow in both size and complexity, and the role of software in achieving mission objectives expands dramatically, NASA's Independent Verification and Validation (IV&V) Teams face evolving challenges in assuring the safety and performance of the safety- and mission-critical embedded software that is essential to landing astronauts on the surface of the Moon by 2024. Key among these challenges is IV&V's desire to present a cohesive, integrated assurance statement to its stakeholders that encapsulates and summarizes our assurance positions across the integrated Artemis systems and their combined role in support of a safe and successful flight. In order to meet this challenge, the IV&V Teams have begun a transition to using formal assurance case concepts and documentation in the Goal Structuring Notation (GSN) to build an argument in support of software assurance. IV&V recognizes significant benefits to the logical argumentation structure provided by assurance cases and GSN over our current practices for documenting and managing assurance claims. In order to reap these benefits, IV&V is integrating the use of assurance case concepts with our paradigm of follow-the-risk capability based assurance. Because of this, assurance cases created and used by IV&V are distinct from the sort of assurance case created by a development project or embedded software assurance organization. IV&V's assurance cases depend much less upon standards and regulations, and more on evidence captured by IV&V regarding the environment, requirements, design, and implementation. IV&V constructs an independent network of claims based on an independent decomposition of arguments. Based upon the risk posture of these claims and their associated software and software artifacts, IV&V then develops and executes engineering analyses and testing, which provide evidence to either support or refute the claim. This emerging risk-informed assurance case methodology is being put into practice as IV&V plans for support of the Artemis II mission, the first flight of the Orion capsule and Space Launch System with astronauts on board.

Whitman, Gerek↗
NASA NTRS2007

Jet Propulsion Laboratory: Annual Report 2006

Nothing is as gratifying in space exploration as when we are surprised by the unexpected. Much of our work progresses in an orderly way, from concept to plan to creation to finding. But now and then we are caught off-guard by something startlingly new, and it is these moments that make our hearts race and leave us with many of our most compelling memories. And 2006 was an exceptional year for the unforeseen. One of our orbiters shocked many with stark proof that liquid water, the seemingly long-gone force that reshaped so much of the scenery of Mars, still flows there today,at least in occasional bursts. Another spacecraft caught us by surprise with photos of Yellowstone-like geysers on one of Saturn's seemingly nondescript moons, Enceladus. A spaceborne observatory created to plumb the life histories of stars and galaxies showed off a completely unexpected talent when it revealed the day and night faces of a fire and ice planet far beyond our solar system 40 light-years away. A newly launched Earth observer revealed that the clouds that decorate our own planet are not what we thought them to be in many ways. Of course, not all of the high points of the year arrived on our doorstep in such unexpected ways. There was also great drama when missions came off exactly as planned, such as when Stardust's sample return capsule made a flawless landing in the Utah desert, bringing home samples of cometary and interstellar dust. Mars Reconnaissance Orbiter slipped into orbit around the red planet exactly as planned. Numerous other missions and technology programs likewise made great achievements during the year. In all, 17 spacecraft and six instruments were stationed across the solar system, studying our own world, other planets, comets and the deeper universe. All of these achievements were enabled by many teams and systems at the Laboratory. The Deep Space Network of communications complexes across three continents supported all of NASA's solar system missions, and several from our international partners, while looking ahead to reinvent itself for the future. Technologists were at work creating innovations both for NASA missions and terrestrial uses. JPL's community of scientific researchers was equally busy coordinating the science activities of our missions and pursuing independent investigations. None of this would be possible without the support of business and administrative teams dedicated to making the Laboratory's institutional environment as world-class as its technical face, or the public engagement specialists who bring the experience of space to the country's diverse publics. All of our missions in one way or another support our nation's Vision for Space Exploration, which envisages a gradually widening robotic and human presence across the solar system in the years ahead.

National Aeronautics and Space Administration (NAS↗
NASA NTRS2008

Surface Landing Site Weather Analysis for Constellation Program

Weather information is an important asset for NASA's Constellation Program in developing the next generation space transportation system to fly to the International Space Station, the Moon and, eventually, to Mars. Weather conditions can affect vehicle safety and performance during multiple mission phases ranging from pre-launch ground processing to landing and recovery operations, including all potential abort scenarios. Meteorological analysis is an important contributor, not only to the development and verification of system design requirements but also to mission planning and active ground operations. Of particular interest are the surface atmospheric conditions at both nominal and abort landing sites for the manned Orion capsule. Weather parameters such as wind, rain, and fog all play critical roles in the safe landing of the vehicle and subsequent crew and vehicle recovery. The Marshall Space Flight Center Natural Environments Branch has been tasked by the Constellation Program with defining the natural environments at potential landing zones. Climatological time series of operational surface weather observations are used to calculate probabilities of occurrence of various sets of hypothetical vehicle constraint thresholds, Data are available for numerous geographical locations such that statistical analysis can be performed for single sites as well as multiple-site network configurations. Results provide statistical descriptions of how often certain weather conditions are observed at the site(s) and the percentage that specified criteria thresholds are matched or exceeded. Outputs are tabulated by month and hour of day to show both seasonal and diurnal variation. This paper will describe the methodology used for data collection and quality control, detail the types of analyses performed, and provide a sample of the results that can be obtained,

Altino, Karen M.↗
NASA NTRS2018

Command and Control Software Development

As NASA’s role in spaceflight operations change, so too does its design priorities. NASA’s flagship venture, the Space Launch System (SLS), is being created primarily to explore deep space. While commercial partners conduct low Earth orbit resupplies, tests, and even transportation of astronauts, NASA can divert more resources to more exciting projects - going back to the moon, or onwards to Mars. In the short term, this goal manifests in the upcoming Exploration Mission-1 (EM-1) test of the SLS, slated for as early as 2019. SLS, with the Orion capsule, will travel farther than any human-rated spacecraft has gone before. As the most powerful launch vehicle ever created, SLS requires many new innovations to ensure mission success. One such technology is the launch control software, which is the focus of this internship. The SLS launch control software is composed of many functions, all of which require rigorous testing to meet the standard of life-critical code. To facilitate easier testing, the first project I undertook was to customize the open-source tool Wireshark to the software team’s needs. Wireshark is a network protocol analyzer that can take in information about custom information packets. The launch control software will have several protocols that are custom to NASA. I ensured that all necessary component files were the correct file type and in the correct structure for Wireshark to compile. Having allowed Wireshark access to understand custom NASA data packets, testers of the launch control software will be able to find anomalies easier.

Wang, Zhengdong↗
NASA NTRS2014

Data Mining of Historical Human Data to Assess the Risk of Injury due to Dynamic Loads

The NASA Occupant Protection Group is charged with ensuring crewmembers are protected during all dynamic phases of spaceflight. Previous work with outside experts has led to the development of a definition of acceptable risk (DAR) for space capsule vehicles. The DAR defines allowable probability rates for various categories of injuries. An important question is how to validate these probabilities for a given vehicle. One approach is to impact test human volunteers under projected nominal landing loads. The main drawback is the large number of subject tests required to attain a reasonable level of confidence that the injury probability rates would meet those outlined in the DAR. An alternative is to mine existing databases containing human responses to impact. Testing an anthropomorphic test device (ATD) at the same human‐exposure levels could yield a range of ATD responses that would meet DAR. As one aspect of future vehicle validation, the ATD could be tested in the vehicle's seat and suit configuration at nominal landing loads and compared with the ATD responses supported by the human data set. This approach could reduce the number of human‐volunteer tests NASA would need to conduct to validate that a vehicle meets occupant protection standards. METHODS: The U.S. Air Force has recorded hundreds of human responses to frontal, lateral, and spinal impacts at many acceleration levels and pulse durations. All of this data are stored on the Collaborative Biomechanics Data Network (CBDN), which is maintained by the Wright Patterson Air Force Base (WPAFB). The test device for human occupant restraint (THOR) ATD was impact tested on WPAFB's horizontal impulse accelerator (HIA) matching human‐volunteer exposures on the HIA to 5 frontal and 3 spinal loading conditions. No human injuries occurred as a result of these impact conditions. Peak THOR response variables for neck axial tension and compression, and thoracic‐spine axial compression were collected. Maximal chest deflection was determined from motion capture video of the impact test. HIC‐ 15 and BRIC were calculated from head acceleration responses. Given the number of human subjects for each test condition a confidence interval of injury probability will be obtained. RESULTS: Results will be discussed in terms of injury‐risk probability estimates based on the human data set evaluated. Also, gaps in the data set will be identified. These gaps could be one of two types. One is areas where additional THOR testing would increase the comparable human data set, thereby improving confidence in the injury probability rate. The other is where additional human testing would assist in obtaining information on other acceleration levels or directions. DISCUSSION: The historical human data showed validity of the THOR ATD for supplemental testing. The historical human data are limited in scope, however. Further data are needed to characterize the effects of sex, age, anthropometry, and deconditioning due to spaceflight on risk of injury

Wells, Jesica↗
NASA NTRS2016

Simulation of Mission Phases

This position with the Simulation and Graphics Branch (ER7) at Johnson Space Center (JSC) provided an introduction to vehicle hardware, mission planning, and simulation design. ER7 supports engineering analysis and flight crew training by providing high-fidelity, real-time graphical simulations in the Systems Engineering Simulator (SES) lab. The primary project assigned by NASA mentor and SES lab manager, Meghan Daley, was to develop a graphical simulation of the rendezvous, proximity operations, and docking (RPOD) phases of flight. The simulation is to include a generic crew/cargo transportation vehicle and a target object in low-Earth orbit (LEO). Various capsule, winged, and lifting body vehicles as well as historical RPOD methods were evaluated during the project analysis phase. JSC core mission to support the International Space Station (ISS), Commercial Crew Program (CCP), and Human Space Flight (HSF) influenced the project specifications. The simulation is characterized as a 30 meter +V Bar and/or -R Bar approach to the target object's docking station. The ISS was selected as the target object and the international Low Impact Docking System (iLIDS) was selected as the docking mechanism. The location of the target object's docking station corresponds with the RPOD methods identified. The simulation design focuses on Guidance, Navigation, and Control (GNC) system architecture models with station keeping and telemetry data processing capabilities. The optical and inertial sensors, reaction control system thrusters, and the docking mechanism selected were based on CCP vehicle manufacturer's current and proposed technologies. A significant amount of independent study and tutorial completion was required for this project. Multiple primary source materials were accessed using the NASA Technical Report Server (NTRS) and reference textbooks were borrowed from the JSC Main Library and International Space Station Library. The Trick Simulation Environment and User Training Materials version 2013.0 release was used to complete the Trick tutorial. Multiple network privilege and repository permission requests were required in order to access previous simulation models. The project was also an introduction to computer programming and the Linux operating system. Basic C++ and Python syntax was used during the completion of the Trick tutorial. Trick's engineering analysis and Monte Carlo simulation capabilities were observed and basic space mission planning procedures were applied in the conceptual design phase. Multiple professional development opportunities were completed in addition to project duties during this internship through the System for Administration, Training, and Education Resources for NASA (SATERN). Topics include: JSC Risk Management Workshop, CCP Risk Management, Basic Radiation Safety Training, X-Ray Radiation Safety, Basic Laser Safety, JSC Export Control, ISS RISE Ambassador, Basic SharePoint 2013, Space Nutrition and Biochemistry, and JSC Personal Protective Equipment. Additionally, this internship afforded the opportunity for formal project presentation and public speaking practice. This was my first experience at a NASA center. After completing this internship I have a much clearer understanding of certain aspects of the agency's processes and procedures, as well as a deeper appreciation from spaceflight simulation design and testing. I will continue to improve my technical skills so that I may have another opportunity to return to NASA and Johnson Space Center.

Carlstrom, Nicholas Mercury↗