Search NASA⌕ Search

SEARCH · Search NASA

Results for “Abstract”

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.

At least 1,171 records · Page 65

Transit Reconfigurable Exerciser - Intern Exit Abstract

The Transit Resistive Exerciser (TREX) was developed during a 16 week period in which a clutch device filled with smart material was built and began the testing phase. The clutch serves as a passive method of creating resistance. When paired with a series of springs, the device creates a rowing machine also capable of resistive exercise configurations. The device has loading profiles similar to the exercise devices used on the International Space Station today. The prototype created was designed in a modular fashion to support parallel development on various aspects of the project. Hardware and software are currently in development and make use of commercially available parts. Similar technologies have been used in the automotive industry but have never been explored in the context of countermeasure systems for space flight. If the work done leads to successful testing and further development, this technology has the potential to cut the size and weight of exercise devices by an order of magnitude or more.

Gebara, Christine A.↗

Compilation of Abstracts for SC12 Conference Proceedings

1 A Breakthrough in Rotorcraft Prediction Accuracy Using Detached Eddy Simulation; 2 Adjoint-Based Design for Complex Aerospace Configurations; 3 Simulating Hypersonic Turbulent Combustion for Future Aircraft; 4 From a Roar to a Whisper: Making Modern Aircraft Quieter; 5 Modeling of Extended Formation Flight on High-Performance Computers; 6 Supersonic Retropropulsion for Mars Entry; 7 Validating Water Spray Simulation Models for the SLS Launch Environment; 8 Simulating Moving Valves for Space Launch System Liquid Engines; 9 Innovative Simulations for Modeling the SLS Solid Rocket Booster Ignition; 10 Solid Rocket Booster Ignition Overpressure Simulations for the Space Launch System; 11 CFD Simulations to Support the Next Generation of Launch Pads; 12 Modeling and Simulation Support for NASA's Next-Generation Space Launch System; 13 Simulating Planetary Entry Environments for Space Exploration Vehicles; 14 NASA Center for Climate Simulation Highlights; 15 Ultrascale Climate Data Visualization and Analysis; 16 NASA Climate Simulations and Observations for the IPCC and Beyond; 17 Next-Generation Climate Data Services: MERRA Analytics; 18 Recent Advances in High-Resolution Global Atmospheric Modeling; 19 Causes and Consequences of Turbulence in the Earths Protective Shield; 20 NASA Earth Exchange (NEX): A Collaborative Supercomputing Platform; 21 Powering Deep Space Missions: Thermoelectric Properties of Complex Materials; 22 Meeting NASA's High-End Computing Goals Through Innovation; 23 Continuous Enhancements to the Pleiades Supercomputer for Maximum Uptime; 24 Live Demonstrations of 100-Gbps File Transfers Across LANs and WANs; 25 Untangling the Computing Landscape for Climate Simulations; 26 Simulating Galaxies and the Universe; 27 The Mysterious Origin of Stellar Masses; 28 Hot-Plasma Geysers on the Sun; 29 Turbulent Life of Kepler Stars; 30 Modeling Weather on the Sun; 31 Weather on Mars: The Meteorology of Gale Crater; 32 Enhancing Performance of NASAs High-End Computing Applications; 33 Designing Curiosity's Perfect Landing on Mars; 34 The Search Continues: Kepler's Quest for Habitable Earth-Sized Planets.

HPC↗

EVA Glove Sensor Feasbility II Abstract

The main objectives for the glove project include taking various measurements from human subjects during and after they perform different tasks in the glove box, acquiring data from these tests and determining the accuracy of these results, interpreting and analyzing this data, and using the data to better understand how hand injuries are caused during EVAs.1 Some of these measurements include force readings, temperature readings, and micro-circulatory blood flow.1 The three glove conditions tested were ungloved (a comfort glove was worn to house the sensors), Series 4000, and Phase VI. The general approach/procedure for the glove sensor feasibility project is as follows: 1. Prepare test subject for testing. This includes attaching numerous sensors (approximately 50) to the test subject, wiring, and weaving the sensors and wires in the glove which helps to keep everything together. This also includes recording baseline moisture data using the Vapometer and MoistSense. 2. Pressurizing the glove box. Once the glove box is pressurized to the desired pressure (4.3 psid), testing can begin. 3. Testing. The test subject will perform a series of tests, some of which include pinching a load cell, making a fist, pushing down on a force plate, and picking up metal pegs, rotating them 90 degrees, and placing them back in the peg board. 4. Post glove box testing data collection. After the data is collected from inside the glove box, the Vapometer and MoistSense device will be used to collect moisture data from the subject's hand. 5. Survey. At the conclusion of testing, he/she will complete a survey that asks questions pertaining to comfort/discomfort levels of the glove, glove sizing, as well as offering any additional feedback.

Melone, Kate↗

System Level Analysis of a Water PCM HX Integrated Into Orion's Thermal Control System Abstract

In a cyclical heat load environment such as low Lunar orbit, a spacecraft's radiators are not sized to reject the full heat load requirement. Traditionally, a supplemental heat rejection device (SHReD) such as an evaporator or sublimator is used to act as a "topper" to meet the additional heat rejection demands. Utilizing a Phase Change Material (PCM) heat exchanger (HX) as a SHReD provides an attractive alternative to evaporators and sublimators as PCM HXs do not use a consumable, thereby leading to reduced launch mass and volume requirements. In continued pursuit of water PCM HX development an Orion system level analysis was performed using Thermal Desktop for a water PCM HX integrated into Orion's thermal control system and in a 100km Lunar orbit. The study analyzed 1) placing the PCM on the Internal Thermal Control System (ITCS) versus the External Thermal Control System (ETCS) 2) use of 30/70 PGW verses 50/50 PGW and 3) increasing the radiator area in order to reduce PCM freeze times. The analysis showed that for the assumed operating and boundary conditions utilizing a water PCM HX on Orion is not a viable option. Additionally, it was found that the radiator area would have to be increased over 20% in order to have a viable water‐based PCM HX.

Navarro, Moses↗

Requirements-Driven Log Analysis Extended Abstract

Imagine that you are tasked to help a project improve their testing effort. In a realistic scenario it will quickly become clear, that having an impact is diffcult. First of all, it will likely be a challenge to suggest an alternative approach which is significantly more automated and/or more effective than current practice. The reality is that an average software system has a complex input/output behavior. An automated testing approach will have to auto-generate test cases, each being a pair (i; o) consisting of a test input i and an oracle o. The test input i has to be somewhat meaningful, and the oracle o can be very complicated to compute. Second, even in case where some testing technology has been developed that might improve current practice, it is then likely difficult to completely change the current behavior of the testing team unless the technique is obviously superior and does everything already done by existing technology. So is there an easier way to incorporate formal methods-based approaches than the full edged test revolution? Fortunately the answer is affirmative. A relatively simple approach is to benefit from possibly already existing logging infrastructure, which after all is part of most systems put in production. A log is a sequence of events, generated by special log recording statements, most often manually inserted in the code by the programmers. An event can be considered as a data record: a mapping from field names to values. We can analyze such a log using formal methods, for example checking it against a formal specification. This separates running the system for analyzing its behavior. It is not meant as an alternative to testing since it does not address the important in- put generation problem. However, it offers a solution which testing teams might accept since it has low impact on the existing process. A single person might be assigned to perform such log analysis, compared to the entire testing team changing behavior.

log analysis↗

Internal Versus External DSLs for Trace Analysis: Extended Abstract

This tutorial explores the design and implementation issues arising in the development of domain-specific languages for trace analysis. It introduces the audience to the general concepts underlying such special-purpose languages building upon the authors' own experiences in developing both external domain specific languages and systems, such as EAGLE, HAWK, RULER and LOGSCOPE, and the more recent internal domain-specific language and system TRACECONTRACT within the SCALA language.

domain specific language (DSL)↗

Internship Abstract - Aerosciences and Flight Mechanics Intern

Mars is a hard place to land on, but my internship with NASA's Aerosciences & Flight Mechanics branch has shown me the ways in which men and women will one day land safely. I work on Mars Aerocapture, an aeroassist maneuver that reduces the fuel necessary to "capture" into Martian orbit before a descent. The spacecraft flies through the Martian atmosphere to lose energy through heating before it exits back into space, this time at a slower velocity and in orbit around Mars. Spacecraft will need to maneuver through the Martian atmosphere to accurately hit their orbit, and they will need to survive the generated heat. Engineering teams need simulation data to continue their designs, and the guidance algorithm that ensures a proper orbit insertion needs to be refined - two jobs that fell to me at the summer's start. Engineers within my branch have developed two concept aerocapture vehicles, and I run simulations on their behavior during the maneuver. I also test and refine the guidance algorithm. I spent the first few weeks familiarizing myself with the simulation software, troubleshooting various guidance bugs and writing code. Everything runs smoothly now, and I recently sent my first set of trajectory data to a Thermal Protection System group so they can incorporate it into their heat-bearing material designs. I hope to generate plenty of data in the next few weeks for various engineering groups before my internship ends mid-August. My major accomplishment so far is improving the guidance algorithm. It is a relatively new algorithm that promises higher accuracy and fuel efficiency, but it hasn't undergone extensive testing yet. I've had the opportunity to work with the principal developer - a professor at Iowa State University - to find and fix several issues. I was also assigned the task of expanding the branch's aerodynamic heating simulation software. I am excited to do this because engineers in the future will use my work to generate meaningful data and make design decisions. My internship has taught me to how to teach myself. There are no tutors, study sessions or professor office hours. When I am given an assignment I am expected to figure out how to accomplish it, and I have grown in my problem solving abilities. My summer experience has reinforced my drive to work at NASA, and I can definitely see myself working full time on the aerocapture project, or something similar.

Rangel, John↗

Wear-Out Sensitivity Analysis Project Abstract

During the course of the Summer 2015 internship session, I worked in the Reliability and Maintainability group of the ISS Safety and Mission Assurance department. My project was a statistical analysis of how sensitive ORU's (Orbital Replacement Units) are to a reliability parameter called the wear-out characteristic. The intended goal of this was to determine a worst case scenario of how many spares would be needed if multiple systems started exhibiting wear-out characteristics simultaneously. The goal was also to determine which parts would be most likely to do so. In order to do this, my duties were to take historical data of operational times and failure times of these ORU's and use them to build predictive models of failure using probability distribution functions, mainly the Weibull distribution. Then, I ran Monte Carlo Simulations to see how an entire population of these components would perform. From here, my final duty was to vary the wear-out characteristic from the intrinsic value, to extremely high wear-out values and determine how much the probability of sufficiency of the population would shift. This was done for around 30 different ORU populations on board the ISS.

Harris, Adam↗

0.625" FPPW Abstract

Friction Pull Plug Welding (FPPW) is a solid‐state process that is the primary close out method for Self‐ Reacting Friction Stir Welding (SR‐FSW). This process uses a servo hydraulic machine to spin an aluminum plug to several thousand revolutions per minute and pull the plug with several thousand pound force into an aluminum piece of material. This process, which has been around for approximately a decade, has proven to be a very difficult process to develop. There are large number of variables with interactions and correlations that are difficult to detect. Historically this method only provided good results on aluminum material up to 0.327" thick. The SLS rocket required weld land configurations of up to 0.625" thick. This not only pushed the limits of the process but also of the tools procured for materials 1/2 as thick. Ultimate Tensile Results was typically the response used for FPPW input variables. The problem was there were multiple processes including, welding, post weld machining, Non Destructive Evaluation, specimen fabrication and mechanical testing between the FPPW inputs and the mechanical test results. This only compiled the list of variables and made the process of FPPW even more difficult to develop. This presentation and paper describes the new process development methodology, which uses the FPPW tool's feedback to observe the process and develop it systematically. It captures 6 months and 600 plugs worth of work using only the tool's feedback as a response to the process. This presentation describes the solution to the issue, a solution whose methodology could apply to a variety of other processes.

Littell, Justin↗

Summer 2015 Internship Abstract

Green fluorescent protein (GFP) visually shows the expression of proteins by fluorescing when exposed to certain wavelengths of light. The GFP in this experiment was used to identify cells actively releasing viruses. The experiment focused on the effect of microgravity on the GFP expression of Akata B-cells infected with Epstein Barr Virus (EBV). Two flasks were prepared with 30 million cells each and two bioreactors were prepared with 50 million cells each. All four cultures were incubated for 16 days and fed every four days. Cellometer readings were taken on the feeding days to find cell size, viability, and GFP expression. In addition, the cells were treated with Propodium monoazide (PMA) and run through real time PCR to determine viral load on the feeding days. On the International Space Station air samples are taken to analyze the bacterial and fungal organisms in the air. The Sartorius Portable Airport is being investigated for potential use on the ISS to analyze for viral content in the air. Multiple samples were taken around Johnson Space Center building 37 and in Clear Lake Pediatric Clinic. The filter used was the gelatin membrane filter and the DNA was extracted directly from the filter. The DNA was then run through real time PCR for Varicella Zoster Virus (VZV) and EBV as well as GAPDH to test for the presence of DNA. The results so far have shown low DNA yield and no positive results for VZV or EBV. Further inquiry involves accurately replicating an atmosphere with high viral load from saliva as would be found on the ISS to run the air sampler in. Another line of research is stress hormones that may be correlated to the reactivation of latent viruses. The stress hormones from saliva samples are analyzed rather than blood samples. The quantity found in saliva shows the quantity of the hormones actually attached to cells and causing a reaction, whereas in the blood the quantity of hormones is the total amount released to cause a reaction. The particular hormones tested for were cortisol, alpha-amylase, and DHEA. The DHEA was very high in the two control samples tested. Regularly, samples came into the lab from local clinics to be tested for various viruses. Saliva, blood, body scrapes, and tears were received from the clinics and then run for VZV, EBV, and Human Simplex Virus 1 (HSV-1) with the results then reported back to the clinician. Blood, saliva, and urine from astronauts were also tested for viruses and logged. In addition, several cell cultures were brought up and grown, including adherent Human Lung Fibroblast (HFL) cells infected with VZV, and Akata B-cells infected with EBV.

Smith, Courtney↗

Z-2 Threaded Insert Design and Testing Abstract

The Z-2 Prototype Planetary Extravehicular Space Suit Assembly is a continuation of NASA's Z series of spacesuits. The Z-2 is another step in the NASA's technology development roadmap leading to human exploration of the Martian surface. To meet a more challenging set of requirements than previous suit systems standard design features, such as threaded inserts, have been re-analyzed and improved. NASA's Z-2 prototype space suit contains several components fabricated from an advanced hybrid composite laminate consisting of IM10 carbon fiber and fiber glass. One requirement NASA levied on the suit composites was the ability to have removable, replaceable helicoil inserts to which other suit components would be fastened. An approach utilizing bonded in inserts with helicoils inside of them was implemented. The design of the interface flanges of the composites allowed some of the inserts to be a "T" style insert that was installed through the entire thickness of the laminate. The flange portion of the insert provides a mechanical lock as a redundancy to the adhesive aiding in the pullout load that the insert can withstand. In some locations it was not possible to utilize at "T" style insert and a blind insert was used instead. These inserts rely completely on the bond strength of the adhesive to resist pullout. It was determined during the design of the suit that the inserts did not need to withstand loads induced from pressure cycling but instead tension induced from torqueing the screws to bolt on hardware which creates a much higher stress on them. Bolt tension is determined by dividing the torque on the screw by a k value multiplied by the thread diameter of the bolt. The k value is a factor that accounts for friction in the system. A common value used for k for a non-lubricated screw is 0.2. The k value can go down by as much as 0.1 if the screw is lubricated which means for the same torque, a much larger tension could be placed on the bolt and insert. This paper summarizes testing that was performed to determine a k value for helicoil inserts in the Z2 suit and how the insert design was modified to resist a higher pull out tension.

Rhodes, RIchard↗

T-38 Primary Flight Display Prototyping and HIVE Support Abstract & Summary

This fall I worked in EV3 within NASA's Johnson Space Center in The HIVE (Human Integrated Vehicles & Environments). The HIVE is responsible for human in the loop testing, getting new technologies in front of astronauts, operators, and users early in the development cycle to make the interfaces more human friendly. Some projects the HIVE is working on includes user interfaces for future spacecraft, wearables to alert astronauts about important information, and test beds to simulate mock missions. During my internship I created a prototype for T-38 aircraft displays using LabVIEW, learned how to use microcontrollers, and helped out with other small tasks in the HIVE. The purpose of developing a prototype for T-38 Displays in LabVIEW is to analyze functions of the display such as navigation in a cost and time effective manner. The LabVIEW prototypes allow Ellington Field AOD to easily make adjustments to the display before hardcoding the final product. LabVIEW was used to create a user interface for simulation almost identical to the real aircraft display. Goals to begin the T-38 PFD (Primary Flight Display) prototype included creating a T-38 PFD hardware display in a software environment, designing navigation for the menu's, incorporating vertical and horizontal navigation bars, and to add a heading bug for compass controls connected to the HSI (Horizontal Situation Indicator). To get started with the project, measurements of the entire display were taken. This enabled an accurate model of the hardware display to be created. Navigation of menu's required some exploration of different buttons on the display. The T-38 simulator and aircraft were used for examining the display. After one piece of the prototype was finished, another trip of to the simulator took place. This was done until all goals for the prototype were complete. Some possible integration ideas for displays in the near future are autopilot selection, touch screen displays, and crew member preferences. Complete navigation, control, and function customization will be achievable once a display is fully developed. Other than the T-38 prototyping, I spent time learning how to design small circuits and write code for them to function. This was done by adding electronic circuit components to breadboard and microcontroller then writing code to speak to those components through the microcontroller. I went through an Arduino starter kit to build circuits and code software that allowed the hardware to act. This work was planned to assist in a lighting project this fall but another solution was discovered for the lighting project. Other tasks that I assisted with, included hands on work such as mock-up construction/removal, logic analyzer repairs, and soldering with circuits. The unique opportunity to be involved work with NASA has significantly changed my educational and career goals. This opportunity has only opened the door to my career with engineering. I have learned over the span of this internship that I am fascinated by the type of work that NASA does. My desire to work in the aerospace industry has increased immensely. I hope to return to NASA to be more involved in the advancement of science, engineering, and spaceflight. My interests for my future education and career lie in NASA’s work - pioneering the future in space exploration, scientific discovery and aeronautics research.

Boniface, Andrew↗

[Fall 2015 Abstract by Stephanie Scharf]

This Fall I worked on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the Branch. The purpose of this document is to create a standard process and ensure that the data is collected in the same way, no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own, all while taking notes on the procedure. These notes were used to write the final work instruction, which will become the Branch standard. My second project continued the work of the Summer co-op before me. I tested aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks had been designed by the previous Summer co-op, but there was not much time for testing before he left. We thus ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (Energy Systems Test Area) and are providing very promising results, indicating that safe, high performing (>180 Wh/kg) designs are possible. My main project was a redesign of the LLB (Lightweight Lithium Battery). Another summer intern had done some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the existing design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density, and the rest of the design was up to me. First, I created new heat sink banks in CREO, using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place, and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve > 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options for cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan was to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Cutting open a cell for DPA After photo from oven heat-to-vent test

Scharf, Stephanie↗

The 26th Space Cryogenic Workshop: Overview, Description of Presentations, and List of Abstracts

This is a summary of the 2015 Space Cryogenics Workshop that was held in Phoenix, Arizona, June 24 to 26, 2015. The workshop was organized by David Plachta and Jason Hartwig of the Cryogenics and Fluid Systems Branch at NASA Glenn Research Center, and continued the tradition of bringing together specialists in the field of space cryogenics to discuss upcoming and potential space missions, and the development of technologies that support or-more often-are enabling for the science and exploration goals of the world's space agencies. The workshop consisted of two days of talks and poster sessions, and provided ample opportunity for more informal discussions that foster collaborations and cooperation in the space cryogenics community. Selected papers from the workshop are published in a special issue of Cryogenics, which is expected to be published by the end of 2015.

Numerical modeling↗

Intern Abstract for Spring 2016

The Human Interface Branch - EV3 - is evaluating Organic lighting-emitting diodes (OLEDs) as an upgrade for current displays on future spacecraft. OLEDs have many advantages over current displays. Conventional displays require constant backlighting which draws a lot of power, but with OLEDs they generate light themselves. OLEDs are lighter, and weight is always a concern with space launches. OLEDs also grant greater viewing angles. OLEDs have been in the commercial market for almost ten years now. What is not known is how they will perform in a space-like environment; specifically deep space far away from the Earth's magnetosphere. In this environment, the OLEDs can be expected to experience vacuum and galactic radiation. The intern's responsibility has been to prepare the OLED for a battery of tests. Unfortunately, it will not be ready for testing at the end of the internship. That being said much progress has been made: a) Developed procedures to safely disassemble the tablet. b) Inventoried and identified critical electronic components. c) 3D printed a testing apparatus. d) Wrote software in Python that will test the OLED screen while being radiated. e) Built circuits to restart the tablet and the test pattern, and ensure it doesn't fall asleep during radiation testing. f) Built enclosure that will house all of the electronics Also, the intern has been working on a way to take messages from a simulated Caution and Warnings system, process said messages into packets, send audio packets to a multicast address that audio boxes are listening to, and output spoken audio. Currently, Cautions and Warnings use a tone to alert crew members of a situation, and then crew members have to read through their checklists to determine what the tone means. In urgent situations, EV3 wants to deliver concise and specific alerts to the crew to facilitate any mitigation efforts on their part. Significant progress was made on this project: a) Open channel with the simulated Caution and Warning system to acquire messages. b) Configure audio boxes. c) Grab pre-recorded audio files. d) Packetize the audio stream. A third project that was assigned to implement LED indicator modules for an Omnibus project. The Omnibus project is investigating better ways designing lighting for the interior of spacecraft-both spacecraft lighting and avionics box status lighting indication. The current scheme contains too much of the blue light spectrum that disrupts the sleep cycle. The LED indicator modules are to simulate the indicators running on a spacecraft. Lighting data will be gathered by human factors personal and use in a model underdevelopment to model spacecraft lighting. Significant progress was made on this project: Designed circuit layout a) Tested LEDs at LETF. b) Created GUI for the indicators. c) Created code for the Arduino to run that will illuminate the indicator modules.

Gibson, William↗

Internship Abstract and Final Reflection

The primary objective for this internship is the evaluation of an embedded natural language processor (NLP) as a way to introduce voice control into future space suits. An embedded natural language processor would provide an astronaut hands-free control for making adjustments to the environment of the space suit and checking status of consumables procedures and navigation. Additionally, the use of an embedded NLP could potentially reduce crew fatigue, increase the crewmember's situational awareness during extravehicular activity (EVA) and improve the ability to focus on mission critical details. The use of an embedded NLP may be valuable for other human spaceflight applications desiring hands-free control as well. An embedded NLP is unique because it is a small device that performs language tasks, including speech recognition, which normally require powerful processors. The dedicated device could perform speech recognition locally with a smaller form-factor and lower power consumption than traditional methods.

Sandor, Edward↗

Thomas Leps Internship Abstract

An optical navigation system is being flown as the backup system to the primary Deep Space Network telemetry for navigation and guidance purposes on Orion. This is required to ensure Orion can recover from a loss of communication, which would simultaneously cause a loss of DSN telemetry. Images taken of the Moon and Earth are used to give range and position information to the navigation computer for trajectory calculations and maneuver execution. To get telemetry data from these images, the size and location of the moon need to be calculated with high accuracy and precision. The reentry envelope for the Orion EM-1 mission requires the centroid and radius of the moon images to be determined within 1/3 of a pixel 3 sigma. In order to ensure this accuracy and precision can be attained, I was tasked with building precise dot grid images for camera calibration as well as building a hardware in the loop test stand for flight software and hardware proofing. To calibrate the Op-Nav camera a dot grid is imaged with the camera, the error between the image dot location and the actual dot location can be used to build a distortion map of the camera and lens system so that images can be fixed to display truth locations. To build the dot grid images I used the Electro Optics Lab optical bench Bright Object Simulator System, and gimbal. The gimbal was slewed to a series of elevations and azimuths. An image of the collimated single point light source was then taken at each position. After a series of 99 images were taken at different locations the single light spots were extracted from each image and added to a composite image containing all 99 points. During the development of these grids it was noticed that an intermittent error in the artificial "star" locations occurred. Prior to the summer this error was attributed to the gimbal having glitches in it's pointing direction and was going to be replaced, however after further examining the issue I determined it to be a software issue. I have since narrowed the likely source of the error down to a Software Development Kit released by the camera supplier PixeLink. I have since developed a workaround in order to build star grids for calibration until the software bug can be isolated and fixed. I was also tasked with building a Hardware in the Loop test stand in order to test the full Op-Nav system. A 4k screen displays simulated Lunar and Terrestrial images from a possible Orion trajectory. These images are then projected through a collimator and then captured with an Op-Nav camera controlled by an Intel NUC computer running flight software. The flight software then analyzes the images to determine attitude and position, this data is then reconstructed into a trajectory and matched to the simulated trajectory in order to determine the accuracy of the attitude and position estimates. In order for the system to work it needs to be precisely and accurately aligned. I developed an alignment procedure that allows the screen, collimator and camera to be squared, centered and collinear with each other within a micron spatially and 5 arcseconds in rotation. I also designed a rigid mount for the screen that was machined on site in Building 10 by another intern. While I was working in the EOL we received a $500k Orion startracker for alignment procedure testing. Due to my prior experience in electronics development, as an ancillary duty, I was tasked with building the cables required to operate and power the startracker. If any errors are made building these cables the startracker would be destroyed, I was honored that the director of the lab entrusted such a critical component with me. This internship has cemented my view on public space exploration. I always preferred public sector to privatization because, as a scientist, the most interesting aspects of space for me are not necessarily the most profitable. I was concerned that the public sector was faltering however, and that in order to improve human space exploration I would be forced into private sector. I now know that, at least at JSC, human spaceflight is still progressing, and exciting work is still being done. I am now actively seeking employment at JSC after I complete my Ph.D and have met with my branch chiefs and mentor to discuss transitioning to a grad Co-op position.

Leps, Thomas↗