Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Jobs”

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 865 records · Page 48

NASA JSC EV2 Intern Spring 2016 - Jennie Chung

Exploration Mission 2 (EM-2) is a mission to resume the manned exploration of the Solar System. This mission is the first crewed mission of NASA’s Orion on the Space Launch System. The target for EM-2 is to perform a flyby of a captured asteroid in lunar orbit, which NASA plans to launch in 2023. As an intern working with EV-2 – Avionics Systems Division in Johnson Space Center, we are developing flight instrumentation systems for EM-2 (MISL & RFID). The Modular Integrated Stackable Layer (MISL) is a compact space-related computer system that is modular, scalable and reconfigurable. The RFID (radio frequency identification) sensors are used to take lower frequency (TC) type measurements and be able to stream data real-time to an RF (radio frequency) interrogator upon demand. Our job, in EV-2, is to certify, test, manufacture/assemble and deliver flight EM-2 DFI System (MISL & RFID). Our goal is to propose a development effort to design low-mass wire and wireless data acquisition and sensor solutions for EM-2 DFI (Development Flight Instrumentation). The team is tasked to provide the most effective use of 75 pounds to acquire DFI data and to collect sensor data for 100-200 high priority DFI channels (mass driven).

Chung, Jennie↗

A Tailored Concept of Operations for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this project is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services.

Systems↗

NASA Pathways Internship: Spring 2016

I was selected to contribute to the Data Systems and Handling Branch under the Avionics Flight Systems Division at the Lyndon B. Johnson Space Center in Houston, Texas. There I used my knowledge from school, as well as my job experience from the military, to help me comprehend my assigned project and contribute to it. With help from my mentors, supervisors, colleagues, and an excellent NASA work environment, I was able to learn, as well as accomplish, a lot towards my project. Not only did I understand more about embedded systems, microcontrollers, and low-level programming, I also was given the opportunity to explore the NASA community.

Alvarez, Oscar, III↗

OLTARIS - Overview and Recent Updates

The On-Line Tool for the Assessment of Radiation in Space (OLTARIS) is a web-based set of tools and models that allow engineers and scientists to assess the effects of space radiation in spacecraft, habitats, rovers, and spacesuits. The site is intended to be a design tool for those studying the effects of space radiation for current and future missions as well as a research tool for those developing advanced material and shielding concepts. The tools and models are built around the HZETRN radiation transport code and are currently focused on human-related responses. OLTARIS was deployed in 2008. Since that time, many improvements and additional capabilities have been added to the site. The purpose of this poster/presentation is to give an overview of the current capabilities of OLTARIS and focus on the updates to the site since the last workshop presentation in 2014. OLTARIS currently has 240 active accounts - 87 accounts are government (including NASA, ORNL, JPL, AFRL, and FAA), 76 are university professors/researchers/students, and 51 are industry (including Boeing, Space X, Lockheed-Martin, ATK, Northrup Grumman, and Bigelow Aerospace). There have been 14,000 jobs run through OLTARIS since counting began in November 2009. ITAR restrictions were recently reversed, so the site is now available to registered users worldwide.

Sandridge, C. A.↗

Instrumentation & Data Acquisition System (D AS) Engineer

The primary job of an Instrumentation and Data Acquisition System (DAS) Engineer is to properly measure physical phenomenon of hardware using appropriate instrumentation and DAS equipment designed to record data during a specified test of the hardware. A DAS system includes a CPU or processor, a data storage device such as a hard drive, a data communication bus such as Universal Serial Bus, software to control the DAS system processes like calibrations, recording of data and processing of data. It also includes signal conditioning amplifiers, and certain sensors for specified measurements. My internship responsibilities have included testing and adjusting Pacific Instruments Model 9355 signal conditioning amplifiers, writing and performing checkout procedures, writing and performing calibration procedures while learning the basics of instrumentation.

Jackson, Markus Deon↗

Advanced EVA Suit Camera System Development Project

The National Aeronautics and Space Administration (NASA) at the Johnson Space Center (JSC) is developing a new extra-vehicular activity (EVA) suit known as the Advanced EVA Z2 Suit. All of the improvements to the EVA Suit provide the opportunity to update the technology of the video imagery. My summer internship project involved improving the video streaming capabilities of the cameras that will be used on the Z2 Suit for data acquisition. To accomplish this, I familiarized myself with the architecture of the camera that is currently being tested to be able to make improvements on the design. Because there is a lot of benefit to saving space, power, and weight on the EVA suit, my job was to use Altium Design to start designing a much smaller and simplified interface board for the camera's microprocessor and external components. This involved checking datasheets of various components and checking signal connections to ensure that this architecture could be used for both the Z2 suit and potentially other future projects. The Orion spacecraft is a specific project that may benefit from this condensed camera interface design. The camera's physical placement on the suit also needed to be determined and tested so that image resolution can be maximized. Many of the options of the camera placement may be tested along with other future suit testing. There are multiple teams that work on different parts of the suit, so the camera's placement could directly affect their research or design. For this reason, a big part of my project was initiating contact with other branches and setting up multiple meetings to learn more about the pros and cons of the potential camera placements we are analyzing. Collaboration with the multiple teams working on the Advanced EVA Z2 Suit is absolutely necessary and these comparisons will be used as further progress is made for the overall suit design. This prototype will not be finished in time for the scheduled Z2 Suit testing, so my time was also spent creating a case for the original interface board that is already being used. This design is being done by use of Creo 2. Due to time constraints, I may not be able to complete the 3-D printing portion of this design, but I was able to use my knowledge of the interface board and Altium Design to help in the task. As a side project, I assisted another intern in selecting and programming a microprocessor to control linear actuators. These linear actuators will be used to move various increments of polyethylene for controlled radiation testing. For this, we began the software portion of the project using the Arduino's coding environment to control an Arduino Due and H-Bridge components. Along with the obvious learning of computer programs such as Altium Design and Creo 2, I also acquired more skills with networking and collaborating with others, being able to multi-task because of responsibilities to work on various projects, and how to set realistic goals in the work place. Like many internship projects, this project will be continued and improved, so I also had the chance to improve my organization and communication skills as I documented all of my meetings and research. As a result of my internship at JSC, I desire to continue a career with NASA, whether that be through another internship or possibly a co-op. I am excited to return to my university and continue my education in electrical engineering because of all of my experiences at JSC.

Mock, Kyla↗

Holodeck Testbed Project

The main objective of the Holodeck Testbed is to create a cost effective, realistic, and highly immersive environment that can be used to train astronauts, carry out engineering analysis, develop procedures, and support various operations tasks. Currently, the Holodeck testbed allows to step into a simulated ISS (International Space Station) and interact with objects; as well as, perform Extra Vehicular Activities (EVA) on the surface of the Moon or Mars. The Holodeck Testbed is using the products being developed in the Hybrid Reality Lab (HRL). The HRL is combining technologies related to merging physical models with photo-realistic visuals to create a realistic and highly immersive environment. The lab also investigates technologies and concepts that are needed to allow it to be integrated with other testbeds; such as, the gravity offload capability provided by the Active Response Gravity Offload System (ARGOS). My main two duties were to develop and animate models for use in the HRL environments and work on a new way to interface with computers using Brain Computer Interface (BCI) technology. On my first task, I was able to create precise computer virtual tool models (accurate down to the thousandths or hundredths of an inch). To make these tools even more realistic, I produced animations for these tools so they would have the same mechanical features as the tools in real life. The computer models were also used to create 3D printed replicas that will be outfitted with tracking sensors. The sensor will allow the 3D printed models to align precisely with the computer models in the physical world and provide people with haptic/tactile feedback while wearing a VR (Virtual Reality) headset and interacting with the tools. Getting close to the end of my internship the lab bought a professional grade 3D Scanner. With this, I was able to replicate more intricate tools at a much more time-effective rate. The second task was to investigate the use of BCI to control objects inside the hybrid reality ISS environment. This task looked at using an Electroencephalogram (EEG) headset to collect brain state data that could be mapped to commands that a computer could execute. On this Task, I had a setback with the hardware, which stopped working and was returned to the vendor for repair. However, I was still able to collect some data, was able to process it, and started to create correlation algorithms between the electrical patterns in the brain and the commands we wanted the computer to carry out. I also carried out a test to investigate the comfort of the headset if it is worn for a long time. The knowledge gained will benefit me in my future career. I learned how to use various modeling and programming tools that included Blender, Maya, Substance Painter, Artec Studio, Github, and Unreal Engine 4. I learned how to use a professional grade 3D scanner and 3D printer. On the BCI Project I learned about data mining and how to create correlation algorithms. I also supported various demos including a live demo of the hybrid reality lab capabilities at ComicPalooza. This internship has given me a good look into engineering at NASA. I developed a more thorough understanding of engineering and my overall confidence has grown. I have also realized that any problem can be fixed, if you try hard enough, and as an engineer it is your job to not only fix problems but to embrace coming up with solutions to those problems.

Arias, Adriel↗

Next Generation Flight Displays Using HTML5

The Human Integrated Vehicles and Environments (HIVE) lab at Johnson Space Center (JSC) is focused on bringing together inter-disciplinary talent to design and integrate innovative human interface technologies for next generation manned spacecraft. As part of this objective, my summer internship project centered on an ongoing investigation in to building flight displays using the HTML5 standard. Specifically, the goals of my project were to build and demo "flight-like" crew and wearable displays as well as create a webserver for live systems being developed by the Advanced Exploration Systems (AES) program. In parallel to my project, a LabVIEW application, called a display server, was created by the HIVE that uses an XTCE (XML (Extensible Markup Language) Telemetry and Command Exchange) parser and CCSDS (Consultative Committee for Space Data System) space packet decoder to translate telemetry items sent by the CFS (Core Flight Software) over User Datagram Protocol (UDP). It was the webserver's job to receive these UDP messages and send them to the displays. To accomplish this functionality, I utilized Node.js and the accompanying Express framework. On the display side, I was responsible for creating the power system (AMPS) displays. I did this by using HTML5, CSS and JavaScript to create web pages that could update and change dynamically based on the data they received from the webserver. At this point, I have not started on the commanding, being able to send back to the CFS, portion of the displays but hope to have this functionality working by the completion of my internship. I also created a way to test the webserver's functionality without the display server by making a JavaScript application that read in a comma-separate values (CSV) file and converted it to XML which was then sent over UDP. One of the major requirements of my project was to build everything using as little preexisting code as possible, which I accomplished by only using a handful of JavaScript libraries. As a side project, I created a model of the HIVE lab and Building 29 using SketchUp. I obtained the floorplans of the building from the JSC Geographic Information Systems (GIS), which were computer-aided design (CAD) files, and imported them into SketchUp. I then took those floorplans and created a 3D model of the building from them. Working in conjunction with the Hybrid Reality lab in Building 32, the SketchUp model was imported into Unreal Engine for use with the HTC Vive. Using the Vive, I was able to interact with the model I created in virtual reality (VR). The purpose of this side project was to be able to visualize potential lab layouts and mockup designs as they are in development in order to finalize design decisions. Pending approval, the model that I created will be used in the Build-As-You-Test: Can Hybrid Reality Improve the SE/HSI Design Process project in the fall. Getting the opportunity to work at NASA has been one of the most memorable experiences of my life. Over the course of my internship, I improved my programming and web development abilities substantially. I will take all the skills and experiences I have had while at NASA back to school with me in the fall and hope to pursue a career in the aerospace industry after graduating in the spring.

Greenwood, Brian↗

Separating the Influence of Environment from Stress Relaxation Effects on Dwell Fatigue Crack Growth in a Nickel-Base Disk Alloy

Both environmental embrittlement and crack tip visco-plastic stress relaxation play a significant role in determining the dwell fatigue crack growth (DFCG) resistance of nickel-based disk superalloys. In the current study performed on the Low Solvus High Refractory (LSHR) disk alloy, the influence of these two mechanisms were separated so that the effects of each could be quantified and modeled. Seven different microstructural variations of LSHR were produced by controlling the cooling rate and the subsequent aging and thermal exposure heat treatments. Through cyclic fatigue crack growth testing performed both in air and vacuum, it was established that four out of the seven LSHR heat treatments evaluated, possessed similar intrinsic environmental resistance to cyclic crack growth. For these four heat treatments, it was further shown that the large differences in dwell crack growth behavior which still persisted, were related to their measured stress relaxation behavior. The apparent differences in their dwell crack growth resistance were attributed to the inability of the standard linear elastic fracture mechanics (LEFM) stress intensity parameter to account for visco-plastic behavior. Crack tip stress relaxation controls the magnitude of the remaining local tensile stresses which are directly related to the measured dwell crack growth rates. It was hypothesized that the environmentally weakened grain boundary crack tip regions fail during the dwells when their strength is exceeded by the remaining local crack tip tensile stresses. It was shown that the classical creep crack growth mechanisms such as grain boundary sliding did not contribute to crack growth, but the local visco-plastic behavior still plays a very significant role by determining the crack tip tensile stress field which controls the dwell crack growth behavior. To account for the influence of the visco-plastic behavior on the crack tip stress field, an empirical modification to the LEFM stress intensity parameter, Kmax, was developed by incorporating into the formulation the remaining stress level concept as measured by simple stress relaxation tests. The newly proposed parameter, Ksrf, did an excellent job in correlating the dwell crack growth rates for the four heat treatments which were shown to have similar intrinsic environmental cyclic fatigue crack growth resistance.

Dwell crack growth↗

The Role of Cloud Contamination, Aerosol Layer Height and Aerosol Model in the Assessment of the OMI Near-UV Retrievals Over the Ocean

Retrievals of aerosol optical depth (AOD) at 388 nm over the ocean from the Ozone Monitoring Instrument (OMI) two-channel near-UV algorithm (OMAERUV) have been compared with independent AOD measurements. The analysis was carried out over the open ocean (OMI and MODerate-resolution Imaging Spectrometer (MODIS) AOD comparisons) and over coastal and island sites (OMI and AERONET, the AErosol RObotic NETwork). Additionally, a research version of the retrieval algorithm (using MODIS and CALIOP (Cloud-Aerosol Lidar with Orthogonal Polarization) information as constraints) was utilized to evaluate the sensitivity of the retrieval to different assumed aerosol properties. Overall, the comparison resulted in differences (OMI minus independent measurements) within the expected levels of uncertainty for the OMI AOD retrievals (0.1 for AOD less than 0.3, 30% for AOD greater than 0.3). Using examples from case studies with outliers, the reasons that led to the observed differences were examined with specific purpose to determine whether they are related to instrument limitations (i.e., pixel size, calibration) or algorithm assumptions (such as aerosol shape, aerosol height). The analysis confirms that OMAERUV does an adequate job at rejecting cloudy scenes within the instrument's capabilities. There is a residual cloud contamination in OMI pixels with quality flag 0 (the best conditions for aerosol retrieval according to the algorithm), resulting in a bias towards high AODs in OMAERUV. This bias is more pronounced at low concentrations of absorbing aerosols (AOD 388 nm approximately less than 0.5). For higher aerosol loadings, the bias remains within OMI's AOD uncertainties. In pixels where OMAERUV assigned a dust aerosol model, a fraction of them (less than 20 %) had retrieved AODs significantly lower than AERONET and MODIS AODs. In a case study, a detailed examination of the aerosol height from CALIOP and the AODs from MODIS, along with sensitivity tests, was carried out by varying the different assumed parameters in the retrieval (imaginary index of refraction, size distribution, aerosol height, particle shape). It was found that the spherical shape assumption for dust in the current retrieval is the main cause of the underestimate. In addition, it is demonstrated in an example how an incorrect assumption of the aerosol height can lead to an underestimate. Nevertheless, this is not as significant as the effect of particle shape. These findings will be incorporated in a future version of the retrieval algorithm.

aerosols↗

Automated ISS Flight Utilities

During my internship at NASA Johnson Space Center, I worked in the Space Radiation Analysis Group (SRAG), where I was tasked with a number of projects focused on the automation of tasks and activities related to the operation of the International Space Station (ISS). As I worked on a number of projects, I have written short sections below to give a description for each, followed by more general remarks on the internship experience. My first project is titled "General Exposure Representation EVADOSE", also known as "GEnEVADOSE". This project involved the design and development of a C++/ ROOT framework focused on radiation exposure for extravehicular activity (EVA) planning for the ISS. The utility helps mission managers plan EVAs by displaying information on the cumulative radiation doses that crew will receive during an EVA as a function of the egress time and duration of the activity. SRAG uses a utility called EVADOSE, employing a model of the space radiation environment in low Earth orbit to predict these doses, as while outside the ISS the astronauts will have less shielding from charged particles such as electrons and protons. However, EVADOSE output is cumbersome to work with, and prior to GEnEVADOSE, querying data and producing graphs of ISS trajectories and cumulative doses versus egress time required manual work in Microsoft Excel. GEnEVADOSE automates all this work, reading in EVADOSE output file(s) along with a plaintext file input by the user providing input parameters. GEnEVADOSE will output a text file containing all the necessary dosimetry for each proposed EVA egress time, for each specified EVADOSE file. It also plots cumulative dose versus egress time and the ISS trajectory, and displays all of this information in an auto-generated presentation made in LaTeX. New features have also been added, such as best-case scenarios (egress times corresponding to the least dose), interpolated curves for trajectories, and the ability to query any time in the EVADES output. As mentioned above, GEnEVADOSE makes extensive use of ROOT version 6, the data analysis framework developed at the European Organization for Nuclear Research (CERN), and the code is written to the C++11 standard (as are the other projects). My second project is the Automated Mission Reference Exposure Utility (AMREU).Unlike GEnEVADOSE, AMREU is a combination of three frameworks written in both Python and C++, also making use of ROOT (and PyROOT). Run as a combination of daily and weekly cron jobs, these macros query the SRAG database system to determine the active ISS missions, and query minute-by-minute radiation dose information from ISS-TEPC (Tissue Equivalent Proportional Counter), one of the radiation detectors onboard the ISS. Using this information, AMREU creates a corrected data set of daily radiation doses, addressing situations where TEPC may be offline or locked up by correcting doses for days with less than 95% live time (the total amount time the instrument acquires data) by averaging the past 7 days. As not all errors may be automatically detectable, AMREU also allows for manual corrections, checking an updated plaintext file each time it runs. With the corrected data, AMREU generates cumulative dose plots for each mission, and uses a Python script to generate a flight note file (.docx format) containing these plots, as well as information sections to be filled in and modified by the space weather environment officers with information specific to the week. AMREU is set up to run without requiring any user input, and it automatically archives old flight notes and information files for missions that are no longer active. My other projects involve cleaning up a large data set from the Charged Particle Directional Spectrometer (CPDS), joining together many different data sets in order to clean up information in SRAG SQL databases, and developing other automated utilities for displaying information on active solar regions, that may be used by the space weather environment officers to monitor solar activity. I consulted my mentor Dr. Ryan Rios and Dr. Kerry Lee for project requirements and added features, and ROOT developer Edmond Offermann for advice on using the ROOT library. I also received advice and feedback from Dr. Janet Barzilla of SRAG, who tested my code. Besides these inputs, I worked independently, writing all of the code by myself. The code for all these projects is documented throughout, and I have attempted to write it in a modular format. Assuming that ROOT is updated accordingly, these codes are also Y2038-compliant (and Y10K-compliant). This allows the code to be easily referenced, modified and possibly repurposed for non-ISS missions in the future, should the necessary inputs exist. These projects have taught me a lot about coding and software design - I have become a much more skilled C++ programmer and ROOT user, and I also learned to code in Python and PyROOT (and its advantages and disadvantages compared to C++/ ROOT). Furthermore, I have learned about space radiation and radiation modeling, topics that greatly interest me as I pursue a degree in physics. Working alongside experimental physicists like Dr. Rios, I have developed a greater understanding and appreciation for experimental science, something I have always leaned towards but to which I lacked significant exposure. My work in SRAG has also given me the invaluable opportunity to witness the work environment for physicists at NASA, and what a career in academia may look like at a government laboratory such as NASA Johnson Space Center. As I continue my studies and look forward to graduate school and a future career, this experience at NASA has given me a meaningful and enjoyable opportunity to put my skills to use and see what my future career path might hold.

Offermann, Jan Tuzlic↗

NDARC NASA Design and Analysis of Rotorcraft - Input, Appendix 4

The NDARC code performs design and analysis tasks. The design task involves sizing the rotorcraft to satisfy specified design conditions and missions. The analysis tasks can include off-design mission performance analysis, flight performance calculation for point operating conditions, and generation of subsystem or component performance maps. The principal tasks (sizing, mission analysis, flight performance analysis) are shown in the figure as boxes with heavy borders. Heavy arrows show control of subordinate tasks. The aircraft description consists of all the information, input and derived, that denes the aircraft. The aircraft consists of a set of components, including fuselage, rotors, wings, tails, and propulsion. This information can be the result of the sizing task; can come entirely from input, for a fixed model; or can come from the sizing task in a previous case or previous job. The aircraft description information is available to all tasks and all solutions. The sizing task determines the dimensions, power, and weight of a rotorcraft that can perform a specified set of design conditions and missions. The aircraft size is characterized by parameters such as design gross weight, weight empty, rotor radius, and engine power available. The relations between dimensions, power, and weight generally require an iterative solution. From the design flight conditions and missions, the task can determine the total engine power or the rotor radius (or both power and radius can be fixed), as well as the design gross weight, maximum takeoff weight, drive system torque limit, and fuel tank capacity. For each propulsion group, the engine power or the rotor radius can be sized. Missions are defined for the sizing task, and for the mission performance analysis. A mission consists of a number of mission segments, for which time, distance, and fuel burn are evaluated. For the sizing task, certain missions are designated to be used for design gross weight calculations; for transmission sizing; and for fuel tank sizing. The mission parameters include mission takeoff gross weight and useful load. For specified takeoff fuel weight with adjustable segments, the mission time or distance is adjusted so the fuel required for the mission equals the takeoff fuel weight. The mission iteration is on fuel weight or energy. Flight conditions are specified for the sizing task, and for the flight performance analysis. For the sizing task, certain flight conditions are designated to be used for design gross weight calculations; for transmission sizing; for maximum takeoff weight calculations; and for anti-torque or auxiliary thrust rotor sizing. The flight condition parameters include gross weight and useful load. For flight conditions and mission takeoff, the gross weight can be maximized, such that the power required equals the power available. A flight state is defined for each mission segment and each flight condition. The aircraft performance can be analyzed for the specified state, or a maximum effort performance can be identified. The maximum effort is specified in terms of a quantity such as best endurance or best range, and a variable such as speed, rate of climb, or altitude.

Rotorcraft Input↗

NewSpace: The Emerging Commercial Space Industry

We are at a turning point in the history of space exploration and development, where new industries are being born to use space in non-traditional ways. Established state-run industrial space sector is no longer the only game in town; commercial space is becoming competitive. Many new entrepreneurial companies, such as SpaceX, Deep Space Industries, etc. are developing new markets, such as Orbital, Suborbital, and Deep Space. Together, government and private industry can facilitate the birth of this new industry. The U.S. national policy on commercial space is to develop a robust and competitive U.S. commercial space sector and to energize competitive domestic industries to participate in global markets. NASA can do this by purchasing and using commercial space capabilities and services; exploring the use of nontraditional arrangements for acquiring space capabilities and services; refraining from activities that preclude, discourage, or compete with commercial space activities; and pursuing opportunities to transfer some functions to the commercial space sector, where beneficial. Commercial space must be competitive, while the government has other priorities such as safety, jobs, etc.

emerging industry↗

Convective Influence and Transport Pathways Controlling the Tropical Distribution of Carbon Monoxide at 100 Hpa

Trajectory calculations with convective influence diagnosed from geostationary-satellite cloud measurements are used to evaluate the relative importance of different Tropical Tropopause Layer (TTL) transport pathways for establishing the distribution of carbon monoxide (CO) at 100 hPa as observed by the Microwave Limb Sounder (MLS) on board the Aura satellite. Carbon monoxide is a useful tracer for investigating TTL transport and convective influence because the CO lifetime is comparable to the time require for slow ascent through the TTL (a couple of months). Offline calculations of TTL radiative heating are used to determine the vertical motion field. The simple trajectory model does a reasonable job of reproducing the MLS CO distributions during Boreal wintertime and summertime. The broad maximum in CO concentration over the Pacific is primarily a result of the strong radiative heating (indicating upward vertical motion) associated with the abundant TTL cirrus in this region. Sensitivity tests indicate that the distinct CO maximum in the Asian monsoon anticyclone is strongly impacted by extreme convective systems with detrainment of polluted air above 360 K potential temperature. The relative importance of different CO source regions will also be discussed.

Tropical Tropopause Layer (TTL)↗

Separating the Influence of Environment from Stress Relaxation Effects on Dwell Fatigue Crack Growth

Seven different microstructural variations of LSHR were produced by controlling the cooling rate and the subsequent aging and thermal exposure heat treatments. Through cyclic fatigue crack growth testing performed both in air and vacuum, it was established that four out of the seven LSHR heat treatments evaluated, possessed similar intrinsic environmental resistance to cyclic crack growth. For these four heat treatments, it was further shown that the large differences in dwell crack growth behavior which still persisted, were related to their measured stress relaxation behavior. The apparent differences in their dwell crack growth resistance were attributed to the inability of the standard linear elastic fracture mechanics (LEFM) stress intensity parameter to account for visco-plastic behavior. Crack tip stress relaxation controls the magnitude of the remaining local tensile stresses which are directly related to the measured dwell crack growth rates. It was hypothesized that the environmentally weakened grain boundary crack tip regions fail during the dwells when their strength is exceeded by the remaining local crack tip tensile stresses. It was shown that the classical creep crack growth mechanisms such as grain boundary sliding did not contribute to crack growth, but the local visco-plastic behavior still plays a very significant role by determining the crack tip tensile stress field which controls the dwell crack growth behavior. To account for the influence of the visco-plastic behavior on the crack tip stress field, an empirical modification to the LEFM stress intensity parameter, Kmax, was developed by incorporating into the formulation the remaining stress level concept as measured by simple stress relaxation tests. The newly proposed parameter, Ksrf, did an excellent job in correlating the dwell crack growth rates for the four heat treatments which were shown to have similar intrinsic environmental cyclic fatigue crack growth resistance.

environmental damage↗

Spaceport Command and Control System Automation Testing

The goal of automated testing is to create and maintain a cohesive infrastructure of robust tests that could be run independently on a software package in its entirety. To that end, the Spaceport Command and Control System (SCCS) project at the National Aeronautics and Space Administration's (NASA) Kennedy Space Center (KSC) has brought in a large group of interns to work side-by-side with full time employees to do just this work. Thus, our job is to implement the tests that will put SCCS through its paces.

Plano, Tom↗

Work Term Assignment Spring 2017

My tour in the Engineering Robotics directorate exceeded my expectations. I learned lessons about Creo, manufacturing and assembly, collaboration, and troubleshooting. During my first tour, last spring, I used Creo on a smaller project, but had limited experience with it before starting in the Dynamic Systems Test branch this spring. I gained valuable experience learning assembly design, sheet metal design and designing with intent for manufacturing and assembly. These skills came from working both on the hatch and the floor. I also learned to understand the intent of other designers on models I worked with. While redesigning the floor, I was modifying an existing part and worked to understand what the previous designer had done to make it fit with the new model. Through working with the machine shop and in the mock-up, I learned much more about manufacturing and assembly. I used a Dremel, rivet gun, belt sander, and countersink for the first time. Through taking multiple safety training for different machine shops, I learned new machine shop safety skills specific to each one. This semester also gave me new collaborative opportunities. I collaborated with engineers within my branch as well as with Human Factors and the building 10 machine shop. This experience helped me learn how to design for functionality and assembly, not only for what would be easiest in my designs. In addition to these experiences, I learned many lessons in troubleshooting. I was the first person in my office to use a Windows 10 computer. This caused unexpected issues with NASA services and programs, such as the Digital Data Management Server (DDMS). Because of this, I gained experience finding solutions to lockout and freeze issues as well as Creo specific settings. These will be useful skills to have in the future and will be implemented in future rotations. This co-op tour has motivated me more to finish my degree and pursue my academic goals. I intend to take a machining Career Gateway Elective in the Fall to improve my skills in building as well as designing with manufacturing intent. I am also inspired to take more mechatronics CGE courses before I graduate to learn more about the crossover between mechanical and electrical engineering. This semester, I worked on multiple projects and had the opportunity to learn from engineers of different disciplines. I became proficient in Creo 2.0, a program I had not used significantly before. I finished modifying the hatch for 3D print and made sizeable modifications to the nose floor support design. I also gained hands-on experience that will be useful in my engineering career in the future. I would consider all of these major achievements from this spring semester. Lastly, I learned to ask more questions and to search for the right people to find answers which I know will be a valuable skill in the future. This summer, I will be completing my last rotation in the Flight Operations Directorate at Ellington Air Field. After this last tour, I will be returning to school for the Fall, Spring and Summer. I will graduate in August of 2018. I am looking forward to learning more about the different jobs available to engineers. This division works directly with many different types of aircrafts and I am excited to learn more about this focus of engineering. The Aircraft Operations Division values team work greatly and I intend to improve my interpersonal skills by working with them this summer.

Sico, Mallory↗

Public-Private Partnerships: NASA as Your Business Partner

Partnerships is an important part of doing business at NASA. NASA partners with external organizations to access capabilities under collaborative agreements; enters into agreements for partner access to NASA capabilities; expand overall landscape of space activity; and spurring innovation. The U.S. national policy on commercial space is to develop a robust and competitive U.S. commercial space sector and to energize competitive domestic industries to participate in global markets. Commercial space must be competitive, while the government has other priorities such as safety, jobs, etc. NASA partnerships consist of Reimbursable and Non-Reimbursable Space Act Agreements. Partnerships at Ames aligns with Ames' core competencies, and Partners often office in the NASA Research Park, which is an established regional innovation cluster that facilitates commercialization and services as a technology accelerator via onsite collaborations between NASA and its partners.

Ames↗