SEARCH · Search NASA
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.
Objectives of this project was to: Gather senior design project ideas and internship opportunities: Relative to space explorationnd In support of the ESMD Space Grant Student Project Support NASAs Educational Framework Outcome 1: Contribute to the development of the STEM workforce
My project at Kennedy Space Center (KSC) during the spring 2013 Project Management and Systems Engineering Internship was to functionalJy test and deploy the SharePoint Extranet system and ensure successful completion of the project's various lifecycle milestones as described by NASA Procedural Requirement (NPR) 7 120.7. I worked alongside NASA Project Managers, Systems Integration Engineers, and Information Technology (IT) Professionals to pilot this collaboration capability between NASA and its External Partners. The use of identity federation allows NASA to leverage externally-issued credentials of other federal agencies and private aerospace and defense companies, versus the traditional process of granting and maintaining full NASA identities for these individuals. This is the first system of its kind at NASA and it will serve as a pilot for the Federal Government. Recognizing the novelty of this service, NASA's initial approach for deployment included a pilot period where nearby employees of Patrick Air Force Base would assist in testing and deployment. By utilizing a credential registration process, Air Force users mapped their Air Force-issued Common Access Cards (CAC) to a NASA identity for access to the External SharePoint. Once the Air Force stands up an Active Directory Federation Services (ADFS) instance within their Data Center and establishes a direct trust with NASA, true identity federation can be established. The next partner NASA is targeting for collaboration is Lockheed Martin (LMCO), since they collaborate frequently for the ORION Program. Through the use of Exostar as an identity hub, LMCO employees will be able to access NASA data on a need to know basis, with NASA ultimately managing access. In a time when every dollar and resource is being scrutinized, this capability is an exciting new way for NASA to continue its collaboration efforts in a cost and resource effective manner.
As an intern at Kennedy Space Center (KSC), I was involved in research for the Fluids and Propulsion Division of the NASA Engineering (NE) Directorate. I was immersed in the Integrated Ground Operations Demonstration Units (IGODU) project for the majority of my time at KSC, primarily with the Ground Operations Demonstration Unit Liquid Oxygen (GODU L02) branch of IGODU. This project was established to develop advancements in cryogenic systems as a part of KSC's Advanced Exploration Systems (AES) program. The vision of AES is to develop new approaches for human exploration, and operations in and beyond low Earth orbit. Advanced cryogenic systems are crucial to minimize the consumable losses of cryogenic propellants, develop higher performance launch vehicles, and decrease operations cost for future launch programs. During my internship, I conducted a flange torque tracking study that established a baseline configuration for the flanges in the Simulated Propellant Loading System (SPLS) at the KSC Cryogenics Test Laboratory (CTL) - the testing environment for GODU L02.
The purpose of this study was to ascertain the colleges and universities from which engineering interns were chosen for the Langley Aerospace Research Student Scholars (LARSS) internship program over a six year period. While the initial question was where the interns were from, information was also obtained on these colleges and universities' rankings with respect to female faculty in tenure/tenure-track positions as well as research expenditures according to the American Society for Engineering Education's (ASEE) 2012 Annual Report. The majority of interns were selected from 14 institutions. Eight of the institutions for female interns and 7 for male interns were also cited as having the largest percentages/numbers of female faculty according to ASEE data. In 10 of the 14 institutions for male interns and 9 of 14 for female interns, the institutions were cited as having some of the highest research expenditures. Last, data from ASEE's report on bachelor degrees awarded in 2011 was assessed with respect to the 21 institutions listed as having higher numbers of women in tenure/tenure-track positions. The majority of these institutions represented larger engineering programs with a sizeable number of engineering faculty. These 21institutions accounted for 24.4% of the total engineering bachelor degrees awarded in 2011, with 27.4% of all female and 23.8% of all male graduates in the U.S.
Participants in this study were student interns and mentors taking part in the 2012, 10- week Langley Aerospace Research Student Scholars (LARSS) summer internship program in Hampton, Virginia. The study examined mentors and student interns' ratings of their preparedness in basic knowledge and skills. The study focused on three primary areas: 1) overall evaluation of knowledge and skills by mentors and interns; 2) male and female interns' perceptions of their own skills in these key areas; and 3) mentors' perceptions of their student interns' knowledge and skills in the same areas by gender. Overall mentors were more positive about their interns' improvement in 12 of 17 areas assessed than were the student interns. There were no significant gender differences in how mentors rated their male and female interns' abilities in these workforce skills, but there were four key areas where female interns rated their own abilities lower than did their male peers: analytical thinking, computational skills, computer skills and technical skills. Implications of these findings are discussed.
During my internship at NASA, I was a model developer for Ground Support Equipment (GSE). The purpose of a model developer is to develop and unit test model component libraries (fluid, electrical, gas, etc.). The models are designed to simulate software for GSE (Ground Special Power, Crew Access Arm, Cryo, Fire and Leak Detection System, Environmental Control System (ECS), etc. ~.) before they are implemented into hardware. These models support verifying local control and remote software for End-Item Software Under Test (SUT). The model simulates the physical behavior (function, state, limits and 110) of each end-item and it's dependencies as defined in the Subsystem Interface Table, Software Requirements & Design Specification (SRDS), Ground Integrated Schematic (GIS), and System Mechanical Schematic.(SMS). The software of each specific model component is simulated through MATLAB's Simulink program. The intensiv~ model development life cycle is a.s follows: Identify source documents; identify model scope; update schedule; preliminary design review; develop model requirements; update model.. scope; update schedule; detailed design review; create/modify library component; implement library components reference; implement subsystem components; develop a test script; run the test script; develop users guide; send model out for peer review; the model is sent out for verific~tionlvalidation; if there is empirical data, a validation data package is generated; if there is not empirical data, a verification package is generated; the test results are then reviewed; and finally, the user. requests accreditation, and a statement of accreditation is prepared. Once each component model is reviewed and approved, they are intertwined together into one integrated model. This integrated model is then tested itself, through a test script and autotest, so that it can be concluded that all models work conjointly, for a single purpose. The component I was assigned, specifically, was a fluid component, a discrete pressure switch. The switch takes a fluid pressure input, and if the pressure is greater than a designated cutoff pressure, the switch would stop fluid flow.
This paper will focus the on research and testing done on penetrating a network for security purposes. This research will provide the IT security office new methods of attacks across and against a company's network as well as introduce them to new platforms and software that can be used to better assist with protecting against such attacks. Throughout this paper testing and research has been done on two different Linux based operating systems, for attacking and compromising a Windows based host computer. Backtrack 5 and BlackBuntu (Linux based penetration testing operating systems) are two different "attacker'' computers that will attempt to plant viruses and or NASA USRP - Internship Final Report exploits on a host Windows 7 operating system, as well as try to retrieve information from the host. On each Linux OS (Backtrack 5 and BlackBuntu) there is penetration testing software which provides the necessary tools to create exploits that can compromise a windows system as well as other operating systems. This paper will focus on two main methods of deploying exploits 1 onto a host computer in order to retrieve information from a compromised system. One method of deployment for an exploit that was tested is known as a "social engineering" exploit. This type of method requires interaction from unsuspecting user. With this user interaction, a deployed exploit may allow a malicious user to gain access to the unsuspecting user's computer as well as the network that such computer is connected to. Due to more advance security setting and antivirus protection and detection, this method is easily identified and defended against. The second method of exploit deployment is the method mainly focused upon within this paper. This method required extensive research on the best way to compromise a security enabled protected network. Once a network has been compromised, then any and all devices connected to such network has the potential to be compromised as well. With a compromised network, computers and devices can be penetrated through deployed exploits. This paper will illustrate the research done to test ability to penetrate a network without user interaction, in order to retrieve personal information from a targeted host.
When I began my internship with the Granular Mechanics and Regolith Operations laboratory (GMRO), also known as Swamp Works, I was given the unique opportunity to shadow many teams working on various projects, and decide what projects I wanted to take part in. Before I go into details of my experiences at Swamp Works, I would like to take a moment to explain what I discovered Swamp Works to be. Swamp Works is a family of hardworking, dedicated, and driven people from various backgrounds and skill sets. These people all work to advance technologies and make science fiction science fact through means of rapid prototyping. They support and encourage failure as an option when learning new things, as long as lesson learned from said failure. In fact, their motto states "Fail, Fast, Forward." What this means is, not if but when one fails he or she must do so quickly and spring forward from the failure so that his or her progress is not delayed. With this acceptance, it provided me the confidence to dive into a multitude of projects working in various fields and with a wide range of skill sets. The first project I joined was Badger. My motivation for taking on this project was the opportunity I would have to obtain valuable experience working with 3D modeling and 3D printing technologies. Badger was a digging apparatus to be used in a highly dusty environment in a material known as Regolith. Regolith is a scientific term for the dirt or top soil found on planetary bodies. Regolith contains a large quantity of sediments less than lOppm and as a result poses a challenge of keeping it out of any cracks and crevices. Furthermore, regolith can create high levels of electrostatic energy, which can prove damaging to sensitive electrical hardware. With these characteristics in mind, I decided to take on the task of designing and manufacturing a dust proof cover for the sensitive electrical hardware. When I began this project, I did not have the slightest idea as to how to use 3D modeling software or a means of manufacturing a viable product. As I went along with variants of the design, I became very proficient with a 3D modeling program known as CREO 2.0. Upon completion of my 3D design, I then had the task of manufacturing and having, in my hands, a usable model. To do this I had to work with additive printing technologies also known as 3D printing. Through my experiences working with Badger, I realized that 3D modeling is the focal point in much of engineering. With this in mind, I have embraced this fact and decided to further my experience with this software so that I may become a more valuable asset to any firm later in my career. Mid-way through work with Badger, I picked up another project in which I found much interest. I ha~ the opportunity to work side by side with a materials and composites guru in manufacturing carbon composite coupons (test strips) for performing stress, strain, and sheer analysis on. Being from a surfing, kiteboarding, and other water sport background I have always been interested in board design. With this in mind, it is no wonder why I found interest in such a project. I had the opportunity to refine Mold preparatory, composite layup, and composite curing techniques. Following manufacturing of these composite strips, I then performed various stress tests and logged my results. With these results, future teams could create lighter, stronger, and more cost effective composite structures for use in varieties of applications. After my experiences with materials and composites testing, I have obtained crucial appreciation for detailed documentation and analysis that material sciences involve. However, as interesting as composite materials testing has been, I do not feel this is where my future career lies. Another, more on the side, project I have been involved in is building a 626 cubic foot regolith containment chamber for doing full scale testing of robotic systems. This chamber is built of high strength aluminum scaffold materials, 80/20, and massive panels of Lexan. Once the chamber is completed, it is be filled with 120 tons of regolith and dubbed the largest regolith test chamber in the world. Through my experiences with building "Big Bin" as we called it, I discovered my demand for engaging and hands on activities. Through all of my incredible experiences working with the Swamp Works at Kennedy Space Center; I have obtained crucial knowledge, insights, and experiences that have fuelled, shaped, and will continue to drive me toward my ultimate goal of obtaining not only a degree in Engineering, but obtaining a job that I can call a career. I want to give much thanks to all of those who mentored me along my journey, and to all who made this opportunity a reality.
This internship focused primarily upon software unit testing of Ground Cooling System (GCS) components, one of the three types of tests (unit, integrated, and COTS/regression) utilized in software verification. Unit tests are used to test the software of necessary components before it is implemented into the hardware. A unit test determines that the control data, usage procedures, and operating procedures of a particular component are tested to determine if the program is fit for use. Three different files are used to make and complete an efficient unit test. These files include the following: Model Test file (.mdl), Simulink SystemTest (.test), and autotest (.m). The Model Test file includes the component that is being tested with the appropriate Discrete Physical Interface (DPI) for testing. The Simulink SystemTest is a program used to test all of the requirements of the component. The autotest tests that the component passes Model Advisor and System Testing, and puts the results into proper files. Once unit testing is completed on the GCS components they can then be implemented into the GCS Schematic and the software of the GCS model as a whole can be tested using integrated testing. Unit testing is a critical part of software verification; it allows for the testing of more basic components before a model of higher fidelity is tested, making the process of testing flow in an orderly manner.
My internship consisted of two major projects for the Launch Control System.The purpose of the first project was to implement the Application Control Language (ACL) to Activate Data Acquisition (ADA) and to Inhibit Data Acquisition (IDA) the Kennedy Ground Control Sub-Systems (KGCS) Gateway, to update existing Pad-B End Item Control (EIC) Display to program the ADA and IDA buttons with new ACL, and to test and release the ACL Display.The second project consisted of unit testing all of the Application Services Framework (ASF) by March 21st. The XmlFileReader was unit tested and reached 100 coverage. The XmlFileReader class is used to grab information from XML files and use them to initialize elements in the other framework elements by using the Xerces C++ XML Parser; which is open source commercial off the shelf software. The ScriptThread was also tested. ScriptThread manages the creation and activation of script threads. A large amount of the time was used in initializing the environment and learning how to set up unit tests and getting familiar with the specific segments of the project that were assigned to us.
This internship provides the opportunity to support the creation and use of Firing Room Displays and Firing Room Applications that use an abstraction layer called the Application Control Language (ACL). Required training included video watching, reading assignments, face-to-face instruction and job shadowing other Firing Room software developers as they completed their daily duties. During the training period various computer and access rights needed for creating the applications were obtained. The specific ground subsystems supported are the Cryogenics Subsystems, Liquid Hydrogen (LH2) and Liquid Oxygen (LO2). The cryogenics team is given the task of finding the best way to handle these very volatile liquids that are used to fuel the Space Launch System (SLS) and the Orion flight vehicles safely.
The major problem addressed throughout the term was the need to update the group's current website, as it was outdated and required streamlining and modernization. The old Gateway to Astronaut Photography of the Earth website had multiple components, many of which involved searches through expansive databases. The amount of work required to update the website was large and due to a desired release date, assistance was needed to help build new pages and to transfer old information. Additionally, one of the tools listed on the website called Image Detective had been underutilized in the past. It was important to address why the public was not using the tool and how it could potentially become more of a resource for the team. In order to help with updating the website, it was necessary to first learn HTML. After assisting with small edits, I began creating new pages. I utilized the "view page source" and "developer" tools in the internet browser to observe how other websites created their features and to test changes without editing the code. I then edited the code to create an interactive feature on the new page. For the Image Detective Page I began an evaluation of the current page. I also asked my fellow interns and friends at my University to offer their input. I took all of the opinions into account and wrote up a document regarding my recommendations. The recommendations will be considered as I help to improve the Image Detective page for the updated website. In addition to the website, other projects included the need for additional, and updated image collections, along with various project requests. The image collections have been used by educators in the classroom and the impact crater collection was highly requested. The glaciers collection focused mostly on South American glaciers and needed to include more of the earth's many glaciers. The collections had not been updated or created due to the fact that related imagery had not been catalogued. The process of cataloging involves identifying the center point location of the image and feature identification. Other project needs included collecting night images of India in for publishing. Again, many of the images were not catalogued and the database was lacking in night time imagery for that region. The last project was to calculate the size of mega fans in South Africa. Calculating the fan sizes involved several steps. To expedite the study, calculations needed to be made after the base maps had been created. Using data files that included an outline of the mega fans on a topographic map, I opened the file in Photoshop, determined the number of pixels within the outlined area, created a one degree squared box, determined the pixels within the box, converted the pixels within the box to kilometers, and then calculated the fan size using this information. Overall, the internship has been a learning experience for me. I have learned how to use new programs and I developed new skills. These These skills can help me as I enter into the next phase of my career. Learning Photoshop and HTML in addition to coding in Dreamweaver are highly sought after skills that are used in a variety of fields. Additionally, the exposure to different aspects of the team and working with different people helped me to gain a broader set of skills and allowed me to work with people with different experiences. The various projects I have worked on this summer have directly benefitted the team whether it was completing projects they did not have the time to do, or by helping the team reach deadlines sooner. The new website will be the best place to see all of my work as it will include the newly designed pages and will feature my updates to collections.
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 mentor Kurt Leucht. The main focus was on creating remote displays for the hypergolic and high pressure helium subsystem team to help control the filling of the respective tanks. As a remote display developer for the GSE hypergolic and high pressure helium subsystem team the intern was responsible for creating and testing graphical remote displays to be used in the Launch Control Center (LCC) on the Firing Room's computer monitors. 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 remote displays. After receiving the requirements, the next step was to create a display 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, will need to be included in each respective display for the system to run properly. Then, once the display was created it needed 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 will need to go through further testing and evaluation before deemed suitable for actual use. 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 display 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 one of the LCC's firing rooms to fill the new Orion spacecraft.
The Technology Watch (Tech Watch) project is directed by the NASA Human Research Programs (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 NASAs 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.
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
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.
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.
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.