Search NASA⌕ Search

SEARCH · Search NASA

Results for “Internship”

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 379 records · Page 21

ExMC Technology Watch

The Technology Watch (Tech Watch) project is directed by the NASA Human Research Program's (HRP) Exploration Medical Capability (ExMC) element, and primarily focuses on ExMC technology gaps. The project coordinates the efforts of multiple NASA centers, including the Johnson Space Center (JSC), Glenn Research Center (GRC), Ames Research Center (ARC), and the Langley Research Center (LaRC). The objective of Tech Watch is to identify emerging, high-impact technologies that augment current NASA HRP technology development efforts. Identifying such technologies accelerates the development of medical care and research capabilities for the mitigation of potential health issues encountered during human space exploration missions. The aim of this process is to leverage technologies developed by academia, industry and other government agencies and to identify the effective utilization of NASA resources to maximize the HRP return on investment. The establishment of collaborations with these entities is beneficial to technology development, assessment and/or insertion, and advance NASA's goal to provide a safe and healthy environment for human exploration. In fiscal year 2013, the Tech Watch project maintained student project activity aimed at specific ExMC gaps, completed the gap report review cycle for all gaps through a maturated gap report review process, and revised the ExMC Tech Watch Sharepoint site for enhanced data content and organization. Through site visits, internships and promotions via aerospace journals, several student projects were initiated and completed this past year. Upon project completion, the students presented their results via telecom or WebEx to the ExMC Element as a whole. The upcoming year will continue to forge strategic alliances and student projects in the interest of technology and knowledge gap closure. Through the population of Sharepoint with technologies assessed by the gap owners, the database expansion will develop a more comprehensive technology set for each gap. By placing such data in Sharepoint, the gap report updates in fiscal year 2014 are anticipated to be streamlined since the evaluated technologies will be readily available to the gap owners in a sortable archive, and may be simply exported into the final gap report presentation

Exploration Medical Capability↗

Altitude-Limiting Airbrake System for Small to Medium Scale Rockets

The goal of the overall internship opportunity this semester was to learn and practice the elements of engineering design through direct exposure to real engineering problems. The primary exposure was to design and manufacture an airbrake device for use with small-medium scale rocket applications. The idea was to take the presented concept of a solution and transform said concept into a reliable fully-functioning and reusable mechanism. The mechanism was to be designed as an insurance feature so that the overall altitude of a rocket with relatively undetermined engine capabilities does not unexpectedly exceed the imposed 10,000 foot ceiling, per range requirements. The airbrake concept was introduced to the Prototype Development Lab as a rotation-driven four tiered offset track pin mechanism, i.e. the airbrake was deployed by rotating a central shaft attached directly to the bottom plate. The individual airbrake fins were subsequently deployed using multiple plates with tracks of offset curvature. The fins were created with guide pins to follow the tracks in each of the offset plates, thus allowing the simultaneous rotational deployment of all fins by only rotating one plate. The concept of this solution was great; though it did not function in application. The rotating plates alone brought up problems like the entire back half of the rocket rotating according to the motion of the aforementioned base plate. Subsequently, the solution currently under development became a static linear actuator-driven spring-loaded fin release system. This solution is almost instantaneously triggered electronically when the avionics detect that the rocket has reached the calculated altitude of deceleration. This altitude will allow enough time remaining to the overall ceiling to adequately decelerate the rocket prior to reaching the ceiling.

Rocket University↗

The Vacuum-Compacted Regolith Gripping Mechanism and Unmanned Flights via Quad-Rotors

During the course of the Kennedy Space Center Summer Internship, two main experiments were performed: The Vacuum-Compacted Regolith Gripping Mechanism and Unmanned Flights via Quad-copters. The objectives of the Vacuum-Compacted Regolith Gripping Mechanism, often abbreviated as the Granular Gripper, are to exhibit Space Technology, such as a soft robotic hand, lift different apparatuses used to excavate regolith, and conserve energy while executing its intended task. The project is being conducted to test how much weight the Granular Gripper can hold. With the use of an Animatronic Robotic Hand, Arduino Uno, and other components, the system was calibrated before actually conducting the intended weight test. The maximum weight each finger could hold with the servos running, in the order of pinky, ring, middle, and index fingers, are as follows: 1.340N, 1.456 N, 0.9579 N, and 1.358 N. Using the small vacuum pump system, the maximum weight each finger could hold, in the same order, was: 4.076 N, 6.159 N, 5.454 N, and 4.052 N. The maximum torques on each of the fingers when the servos were running, in the same respective order, was: 0.0777 Nm, 0.0533 Nm, 0.0648 Nm, and 0.0532 Nm. The maximum torques on the individual fingers, when the small vacuum pump was in effect, in the same order as above, was: 0.2318 Nm, 0.3032 Nm, 0.2741 Nm, and 0.1618 Nm. In testing all the fingers with the servos running, the total weight was 5.112 N and the maximum torque on the all the fingers was 0.2515 Nm. However, when the small vacuum pump system was used, the total weight was 19.741 N and the maximum torque on the all the fingers was 0.9713 Nm. The conclusion that was drawn stated that using the small vacuum pump system proved nearly 4 times more effective when testing how much weigh the hand could hold. The resistance provided by the compacted sand in the glove allowed more weight to be held by the hand and glove. Also, when the servos turned off and the hand still retaining its position, energy is being saved because the vacuum created the same resistance the running servos did without using power. The Unmanned Flights via Quad-rotors are built because multi-rotor dynamics are an important starting point and fair analog for space craft control systems and they make good terrestrial development platforms for various aspects of control for space crafts. The project is being conducted to see what the thrust response is going to be when a pulse width modulation command is sent to the control system since the quad-rotors are PWM controlled. A simulation environment in constructed so that one can quickly iterate and test different designs such as control systems, PID control vs. LDR control, and state estimation. Using two DIY Quad Kits, APM 2.6, testing apparatus (called a data acquisition system) to test the quad-rotors, and a simulation program such as Simulink, two quad-rotors are built and controlled via a simulation program, which is designed to be as realistic as possible and not idealistic. Due to the quad-rotors not being completely built nor ready for testing, there are no results or conclusions to report.

Granular Gripper↗

Advanced Space Surface Systems Operations

The importance of advanced surface systems is becoming increasingly relevant in the modern age of space technology. Specifically, projects pursued by the Granular Mechanics and Regolith Operations (GMRO) Lab are unparalleled in the field of planetary resourcefulness. This internship opportunity involved projects that support properly utilizing natural resources from other celestial bodies. Beginning with the tele-robotic workstation, mechanical upgrades were necessary to consider for specific portions of the workstation consoles and successfully designed in concept. This would provide more means for innovation and creativity concerning advanced robotic operations. Project RASSOR is a regolith excavator robot whose primary objective is to mine, store, and dump regolith efficiently on other planetary surfaces. Mechanical adjustments were made to improve this robot's functionality, although there were some minor system changes left to perform before the opportunity ended. On the topic of excavator robots, the notes taken by the GMRO staff during the 2013 and 2014 Robotic Mining Competitions were effectively organized and analyzed for logistical purposes. Lessons learned from these annual competitions at Kennedy Space Center are greatly influential to the GMRO engineers and roboticists. Another project that GMRO staff support is Project Morpheus. Support for this project included successfully producing mathematical models of the eroded landing pad surface for the vertical testbed vehicle to predict a timeline for pad reparation. And finally, the last project this opportunity made contribution to was Project Neo, a project exterior to GMRO Lab projects, which focuses on rocket propulsion systems. Additions were successfully installed to the support structure of an original vertical testbed rocket engine, thus making progress towards futuristic test firings in which data will be analyzed by students affiliated with Rocket University. Each project will be explained in further detail, as well as the full scope of the contributions made during this opportunity.

Robotics↗

Recommendation of a More Effective Alternative to the NASA Launch Services Program Mission Integration Reporting System (MIRS) and Implementation of Updates to the Mission Plan

Over the course of my internship in the Flight Projects Office of NASA's Launch Services Program (LSP), I worked on two major projects, both of which dealt with updating current systems to make them more accurate and to allow them to operate more efficiently. The first project dealt with the Mission Integration Reporting System (MIRS), a web-accessible database application used to manage and provide mission status reporting for the LSP portfolio of awarded missions. MIRS had not gone through any major updates since its implementation in 2005, and it was my job to formulate a recommendation for the improvement of the system. The second project I worked on dealt with the Mission Plan, a document that contains an overview of the general life cycle that is followed by every LSP mission. My job on this project was to update the information currently in the mission plan and to add certain features in order to increase the accuracy and thoroughness of the document. The outcomes of these projects have implications in the orderly and efficient operation of the Flight Projects Office, and the process of Mission Management in the Launch Services Program as a whole.

recommendation↗

Developing Avionics Hardware and Software for Rocket Engine Testing

My summer was spent working as an intern at Kennedy Space Center in the Propulsion Avionics Branch of the NASA Engineering Directorate Avionics Division. The work that I was involved with was part of Rocket University's Project Neo, a small scale liquid rocket engine test bed. I began by learning about the layout of Neo in order to more fully understand what was required of me. I then developed software in LabView to gather and scale data from two flowmeters and integrated that code into the main control software. Next, I developed more LabView code to control an igniter circuit and integrated that into the main software, as well. Throughout the internship, I performed work that mechanics and technicians would do in order to maintain and assemble the engine.

liquid rocket↗

Remote Software Application and Display Development

The era of the shuttle program has come to an end, but only to give rise to newer and more exciting projects. Now is the time of the Orion spacecraft, a work of art designed to exceed all previous endeavors of man. NASA is exiting the time of exploration and is entering a new period, a period of pioneering. With this new mission, many of NASAs organizations must undergo a great deal of change and development to support the Orion missions. The Spaceport Command and Control System (SCCS) is the new system that will provide NASA the ability to launch rockets into orbit and thus control Orion and other spacecraft as the goal of populating Mars becomes ever increasingly tangible. Since the previous control system, Launch Processing System (LPS), was primarily designed to launch the shuttles, SCCS was needed as Kennedy Space Center (KSC) reorganized to a multiuser spaceport for commercial flights, providing a more versatile control over rockets. Within SCCS, is the Launch Control System (LCS), which is the remote software behind the command and monitoring of flight and ground system hardware. This internship at KSC has involved two main components in LCS, including Remote Software Application and Display development. The display environment provides a graphical user interface for an operator to view and see if any cautions are raised, while the remote applications are the backbone that communicate with hardware, and then relay the data back to the displays. These elements go hand in hand as they provide monitoring and control over hardware and software alike from the safety of the Launch Control Center. The remote software applications are written in Application Control Language (ACL), which must undergo unit testing to ensure data integrity. This paper describes both the implementation and writing of unit tests in ACL code for remote software applications, as well as the building of remote displays to be used in the Launch Control Center (LCC).

ACL↗

Orion Crew Module / Service Module Structural Weight and Center of Gravity Simulator and Vehicle Motion Simulator Hoist Structure for Orion Service Module Umbilical Testing

An Orion Crew Module Service Module Structural Weight and Center of Gravity Simulator and a Vehicle Motion Simulator Hoist Structure for Orion Service Module Umbilical Testing were designed during a summer 2014 internship in Kennedy Space Centers Structures and Mechanisms Design Branch. The simulator is a structure that supports ballast, which will be integrated into an existing Orion mock-up to simulate the mass properties of the Exploration Mission-1 flight vehicle in both fueled and unfueled states. The simulator mimics these configurations through the use of approximately 40,000 lbf of steel and water ballast, and a steel support structure. Draining four water tanks, which house the water ballast, transitions the simulator from the fueled to unfueled mass properties. The Ground Systems Development and Operations organization will utilize the simulator to verify and validate equipment used to maneuver and transport the Orion spacecraft in its fueled and unfueled configurations. The second design comprises a cantilevered tripod hoist structure that provides the capability to position a large Orion Service Module Umbilical in proximity to the Vehicle Motion Simulator. The Ground Systems Development and Operations organization will utilize the Vehicle Motion Simulator, with the hoist structure attached, to test the Orion Service Module Umbilical for proper operation prior to installation on the Mobile Launcher. Overall, these two designs provide NASA engineers viable concepts worthy of fabricating and placing into service to prepare for the launch of Orion in 2017.

VMS↗

Support of LAVA Integration and Testing

The Lunar Advanced Volatile Analysis (LAVA) subsystem is a part of the Regolith and Environment Science & Oxygen and Lunar Volatile Analysis (RESOLVE) Payload that will fly to the lunar pole on the Resource Prospector Mission (RPM) in 2019. The purpose of the mission is to characterize the water on the surface and subsurface of the moon in various locations in order to map the distribution. This characterization of water will help to understand how feasible water is as a resource that can be used for drinking water, breathable air, and propellants in future missions. This paper describes the key support activities performed during a 10 week internship; specifically, troubleshooting the Near Infrared Spectrometer for the Surge Tank (NIRST) instrument count loss, contributing to a clamp to be used in the installation of Resistive Temperature Detectors (RTDs) to tubing, performing a failure analysis of the LAVA Fluid Subsystem (FSS), and finalizing trade studies for release.

Trade Study↗

IT Security Support for the Spaceport Command Control System Development

My job title is IT Security support for the Spaceport Command & Control System Development. As a cyber‐security analyst it is my job to ensure NASA's information stays safe from cyber threats, such as, viruses, malware and denial-of-service attacks by establishing and enforcing system access controls. Security is very important in the world of technology and it is used everywhere from personal computers to giant networks ran by Government agencies worldwide. Without constant monitoring analysis, businesses, public organizations and government agencies are vulnerable to potential harmful infiltration of their computer information system. It is my responsibility to ensure authorized access by examining improper access, reporting violations, revoke access, monitor information request by new programming and recommend improvements. My department oversees the Launch Control System and networks. An audit will be conducted for the LCS based on compliance with the Federal Information Security Management Act (FISMA) and The National Institute of Standards and Technology (NIST). I recently finished analyzing the SANS top 20 critical controls to give cost effective recommendations on various software and hardware products for compliance. Upon my completion of this internship, I will have successfully completed my duties as well as gain knowledge that will be helpful to my career in the future as a Cyber Security Analyst.

IT Security↗

Software Development for Remote Control and Firing Room Displays

The Launch Control System (LCS) developed at NASA's Kennedy Space Center (KSC) will be used to launch future spacecraft. Two of the many components of this system are the Application Control Language (ACL) and remote displays. ACL is a high level domain specific language that is used to write remote control applications for LCS. Remote displays are graphical user interfaces (GUIs) developed to display vehicle and Ground Support Equipment (GSE) data, they also provide the ability to send commands to control GSE and the vehicle. The remote displays and the control applications have many facets and this internship experience dealt with several of them.

LCS↗

Development and Testing of Functionally Operative and Visually Appealing Remote Firing Room Displays and Applications

This internship provided an opportunity for an intern to work with NASA's Ground Support Equipment (GSE) for the Spaceport Command and Control System (SCCS) at Kennedy Space Center as a remote display developer, under NASA technical mentor Kurt Leucht. The main focus was on creating remote displays and applications for the hypergolic and high pressure helium subsystem team to help control the filling of the respective tanks. As a remote display and application developer for the GSE hypergolic and high pressure helium subsystem team the intern was responsible for creating and testing graphical remote displays and applications to be used in the Launch Control Center (LCC) on the Firing Room's computers. To become more familiar with the subsystem, the individual attended multiple project meetings and acquired their specific requirements regarding what needed to be included in the software. After receiving the requirements for the displays, the next step was to create displays that had both visual appeal and logical order using the Display Editor, on the Virtual Machine (VM). In doing so, all Compact Unique Identifiers (CUI), which are associated with specific components within the subsystem, were need to be included in each respective display for the system to run properly. Then, once the display was created it was to be tested to ensure that the display runs as intended by using the Test Driver, also found on the VM. This Test Driver is a specific application that checks to make sure all the CUIs in the display are running properly and returning the correct form of information. After creating and locally testing the display it needed to go through further testing and evaluation before deemed suitable for actual use. For the remote applications the intern was responsible for creating a project that focused on channelizing each component included in each display. The core of the application code was created by setting up spreadsheets and having an auto test generator, generate the complete code structure. This application code was then loaded and ran on a testing environment set to ensure the code runs as anticipated. By the end of the semester-long experience at NASA's Kennedy Space Center, the individual should have gained great knowledge and experience in various areas of both display and application development and testing. They were able to demonstrate this new knowledge obtained by creating multiple successful remote displays that will one day be used by the hypergolic and high pressure helium subsystem team in the LCC's firing rooms to service the new Orion spacecraft. The completed display channelization application will be used to receive verification from NASA quality engineers.

Display Devices↗

Firing Room Remote Application Software Development

The Engineering and Technology Directorate (NE) at National Aeronautics and Space Administration (NASA) Kennedy Space Center (KSC) is designing a new command and control system for the checkout and launch of Space Launch System (SLS) and future rockets. The purposes of the semester long internship as a remote application software developer include the design, development, integration, and verification of the software and hardware in the firing rooms, in particular with the Mobile Launcher (ML) Launch Accessories subsystem. In addition, a Conversion Fusion project was created to show specific approved checkout and launch engineering data for public-friendly display purposes.

Pathways↗

Pathway Intern Showcase

This presentation outlines assignments or projects performed during pathway internship.

Pathways↗

High Temperature Ultrasonic Transducers : Material Selection and Testing

The task of my two-months internship was to test different materials to be used to build an high temperature transducer, to develop some prototypes and to test their performance, to assess the reliability of commercial product rated for such a temperature, as well as to collaborate in developing the signal processing code to measure the condensed water levels.

health monitoring steam pipes↗

Improving Spacecraft Data Visualization Using Splunk

EPOXI, like all spacecraft missions, receives large volumes of telemetry data from its spacecraft, DIF. It is extremely important for this data to be updated quickly and presented in a readable manner so that the flight team can monitor the status of the spacecraft. Existing DMD pages for monitoring spacecraft telemetry, while functional, are limited and do not take advantage of modern search technology. For instance, they only display current data points from instruments on the spacecraft and have limited graphing capabilities, making it difficult to see historical data. The DMD pages have fixed refresh rates so the team must often wait several minutes to see the most recent data, even after it is received on the ground. The pages are also rigid and require an investment of time and money to update. To more easily organize and visualize spacecraft telemetry, the EPOXI team has begun experimenting with Splunk, a commercially-available data mining system. Splunk can take data received from the spacecraft's different data channels, often in different formats, and index all the data into a common format. Splunk allows flight team members to search through the different data formats from a single interface and to filter results by time range and data field to make finding specific spacecraft events quick and easy. Furthermore, Splunk provides functions to create custom interfaces which help team members visualize the data in charts and graphs to show how the health of the spacecraft has changed over time.One of the goals of my internship with my mentor, Victor Hwang, was to develop new Splunk interfaces to replace the DMD pages and give the spacecraft team access to historical data and visualizations that were previously unavailable. The specific requirements of these pages are discussed in the next section.

spacecraft missions↗

Mobile and Web Game Development: Using Videogames as an Educational and Outreach Tool

Few tools reach out to capture the imagination and interests of children like video games do. As such, the development of educational applications that foster young minds' interest in science and technology become of the utmost importance. To this end, I spent my summer internship developing outreach and educational applications in conjunction with JPL's Space Place team. This small, but dedicated, team of people manages three NASA websites that focus on presenting science and technology information in such a manner that young children can understand it and develop an interest in the subjects. Besides the websites, with their plethora of educational content presented through hands-on activities, games and informative articles, the team also creates and coordinates the distribution of printed material to museums, astronomy clubs and a huge network of educators.

NASA's Space Place↗

Towards Reliable Evaluation of Anomaly-Based Intrusion Detection Performance

This report describes the results of research into the effects of environment-induced noise on the evaluation process for anomaly detectors in the cyber security domain. This research was conducted during a 10-week summer internship program from the 19th of August, 2012 to the 23rd of August, 2012 at the Jet Propulsion Laboratory in Pasadena, California. The research performed lies within the larger context of the Los Angeles Department of Water and Power (LADWP) Smart Grid cyber security project, a Department of Energy (DoE) funded effort involving the Jet Propulsion Laboratory, California Institute of Technology and the University of Southern California/ Information Sciences Institute. The results of the present effort constitute an important contribution towards building more rigorous evaluation paradigms for anomaly-based intrusion detectors in complex cyber physical systems such as the Smart Grid. Anomaly detection is a key strategy for cyber intrusion detection and operates by identifying deviations from profiles of nominal behavior and are thus conceptually appealing for detecting "novel" attacks. Evaluating the performance of such a detector requires assessing: (a) how well it captures the model of nominal behavior, and (b) how well it detects attacks (deviations from normality). Current evaluation methods produce results that give insufficient insight into the operation of a detector, inevitably resulting in a significantly poor characterization of a detectors performance. In this work, we first describe a preliminary taxonomy of key evaluation constructs that are necessary for establishing rigor in the evaluation regime of an anomaly detector. We then focus on clarifying the impact of the operational environment on the manifestation of attacks in monitored data. We show how dynamic and evolving environments can introduce high variability into the data stream perturbing detector performance. Prior research has focused on understanding the impact of this variability in training data for anomaly detectors, but has ignored variability in the attack signal that will necessarily affect the evaluation results for such detectors. We posit that current evaluation strategies implicitly assume that attacks always manifest in a stable manner; we show that this assumption is wrong. We describe a simple experiment to demonstrate the effects of environmental noise on the manifestation of attacks in data and introduce the notion of attack manifestation stability. Finally, we argue that conclusions about detector performance will be unreliable and incomplete if the stability of attack manifestation is not accounted for in the evaluation strategy.

cyber defense↗