Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “functional mockup interface”

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.

11 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

Asteroid Redirect Crewed Mission Space Suit and EVA System Maturation

The Asteroid Redirect Crewed Mission (ARCM) requires a Launch/Entry/Abort (LEA) suit capability and short duration Extra Vehicular Activity (EVA) capability from the Orion spacecraft. For this mission, the pressure garment that was selected, for both functions, is the Modified Advanced Crew Escape Suit (MACES) with EVA enhancements and the life support option that was selected is the Exploration Portable Life Support System (PLSS). The proposed architecture was found to meet the mission constraints, but much more work is required to determine the details of the required suit upgrades, the integration with the PLSS, and the rest of the tools and equipment required to accomplish the mission. This work has continued over the last year to better define the operations and hardware maturation of these systems. EVA simulations have been completed in the NBL and interfacing options have been prototyped and analyzed with testing planned for late 2014. For NBL EVA simulations, in 2013, components were procured to allow in-house build up for four new suits with mobility enhancements built into the arms. Boots outfitted with clips that fit into foot restraints have also been added to the suit and analyzed for possible loads. Major suit objectives accomplished this year in testing include: evaluation of mobility enhancements, ingress/egress of foot restraint, use of foot restraint for worksite stability, ingress/egress of Orion hatch with PLSS mockup, and testing with two crew members in the water at one time to evaluate the crew's ability to help one another. Major tool objectives accomplished this year include using various other methods for worksite stability, testing new methods for asteroid geologic sampling and improving the fidelity of the mockups and crew equipment. These tests were completed on a medium fidelity capsule mockup, asteroid vehicle mockup, and asteroid mockups that were more accurate for an asteroid type EVA than previous tests. Another focus was the design and fabrication of the interface between the MACES and the PLSS. The MACES was not designed to interface with a PLSS, hence an interface kit must accommodate the unique design qualities of the MACES and provide the necessary life support function connections to the PLSS. A prototype interface kit for MACES to PLSS has been designed and fabricated. Unmanned and manned testing of the interface will show the usability of the kit while wearing a MACES. The testing shows viability of the kit approach as well as the operations concept. The design will be vetted through suit and PLSS experts and, with the findings from the testing, the best path forward will be determined. As the Asteroid Redirect Mission matures, the suit/life support portion of the mission will mature along with it and EVA Tools & Equipment can be iterated to accommodate the overall mission objectives and compromises inherent in EVA Suit optimization. The goal of the EVA architecture for ARCM is to continue to build on the previously developed technologies and lessons learned, and accomplish the ARCM EVAs while providing a stepping stone to future missions and destinations.

Bowie, Jonathan T.↗
NASA NTRS2007

Integrating Human Factors into Crew Exploration Vehicle Design

With NASA's new Vision for Exploration to send humans beyond Earth orbit, it is critical to consider the human as a system that demands early and continuous user involvement, and an iterative prototype/test/redesign process. Addressing human-system interface issues early on can be very cost effective even cost reducing when performed early in the design and development cycle. To achieve this goal within Crew Exploration Vehicle (CEV) Project Office, human engineering (HE) team is formed. Key tasks are to apply HE requirements and guidelines to hardware/software, and provide HE design, analysis and evaluation of crew interfaces. Initial activities included many practice-orientated evaluations using low-fidelity CEV mock-ups. What follows is a description of such evaluations that focused on a HE requirement regarding Net Habitable Volume (NHV). NHV is defined as the total remaining pressurized volume available to on-orbit crew after accounting for the loss of volume due to deployed hardware and structural inefficiencies which decrease functional volume. The goal of the NHV evaluations was to develop requirements providing sufficient CEV NHV for crewmembers to live and perform tasks in support of mission goals. Efforts included development of a standard NHV calculation method using computer models and physical mockups, and crew/ stakeholder evaluations. Nine stakeholders and ten crewmembers participated in the unsuited evaluations. Six crewmembers also participated in a suited evaluation. The mock-up was outfitted with volumetric representation of sub-systems such as seats, and stowage bags. Thirteen scenarios were developed to represent mission/crew tasks and considered to be primary volume drivers (e.g., suit donning) for the CEV. Unsuited evaluations included a structured walkthrough of these tasks. Suited evaluations included timed donning of the existing launch and entry suit to simulate a contingency scenario followed by doffing/ stowing of the suits. All mockup evaluations were videotaped. Structured questionnaires were used to document user interface issues and volume impacts of layout configuration. Computer model and physical measures of the NHV agreed within 1 percent. This included measurement of the gross habitable volume, subtraction of intrusive volumes, and other non-habitable spaces. Calculation method developed was validated as a standard means of measuring NHV, and was recommended as a verification method for the NHV requirements. Evaluations confirmed that there was adequate volume for unsuited scenarios and suit donning/ doffing activity. Seats, suit design stowage and waste hygiene system noted to be critical volume drivers. The low-fidelity mock-up evaluations along with human modeling analysis generated discussions that will lead to high-level systems requirements and human-centered design decisions. This approach allowed HE requirements and operational concepts to evolve in parallel with engineering system concepts and design requirements. As the CEV design matures, these evaluations will continue and help with design decisions, and assessment, verification and validation of HE requirements.

Whitmore, Mihriban↗
NASA NTRS2018

Development of an Inflatable Airlock for a Deep Space Gateway

Inflatable structures technology utilizes high-strength fabric materials and internal pressure to create a stiffened pressure vessel that can replace traditional metallic primary structure in a habitable spacecraft. The flexibility of fabric structures allows them to be compactly stowed for launch and expanded in space, providing significant launch volume savings. The unique construction and design flexibility of these structures can be customized for a variety of uses in space including landing bags, decelerators, long duration in-space and planetary surface habitats, and even airlocks. An airlock is often a required component of a crewed spacecraft to allow for maintenance and human exploration outside of the vehicle. Airlock designs in use today rely on complex hatches and seals connected by metallic walls. Recent developments towards the design of an inflatable airlock structure show feasibility and a significant launch volume savings over a traditional metallic design. This paper will provide a high-level summary of these projects and the current state-of-the-art in inflatable airlock development with additional references and detail about previous and on-going research, providing guidance for the design of a softgoods airlock system. The use of inflatables in space has been in development since the 1960’s for both habitats and airlocks. The first ever EVA was conducted by the USSR in 1965 using an inflatable airlock known as the Volga. This airlock was attached to the Voskhod 2 spacecraft and turned the vehicle into a dual chamber airlock. The airlock was successfully deployed, used and jettisoned after Alexey Leonov’s historic spacewalk. Additional work on human-rated inflatable structures was not continued until the late 1990’s when NASA-JSC led an effort to demonstrate these structures as feasible long-term pressurized elements with the TransHab project. The technology developed and pioneered during this project led to multiple patents and proven feasibility that inflatables could be used for large habitable structures. Following TransHab, Bigelow Aerospace continued the development of inflatable structures with technical support from NASA. This partnership eventually led to the successful flight certification, launch, attachment and deployment of the Bigelow Expandable Activities Module (BEAM) on the ISS in 2016. Inflatable and expandable airlock structures have undergone various detailed feasibility studies and testing for over 15 years, most notably with the Advanced Inflatable Airlock (AIA), Dual-Chamber Hybrid Inflatable Suitlock (DCIS), Minimalistic Advanced Soft Hatch (MASH), and Lightweight External Inflatable Airlock (LEIA). During this time, full-scale articles have been built and pressure-tested, and mock-ups and demonstrators have been constructed and evaluated. During the 2001-2003 timeframe, the AIA concept was matured through requirements development, conceptual design, subscale and full-scale engineering breadboards subjecting various test articles to deployment and pressure testing up to four times operating pressure. These tests proved the feasibility of successful deployment and structural integrity of an inflatable crewlock. Additional testing was performed in the ensuing years, as funding permitted, to further refine additional structural and deployment concepts and to understand the EVA crewmember interfaces, hatches and EVA support equipment interfaces that would be required for a fully functioning airlock. This work resulted in a refinement of the structural requirements and an accounting of the systems needed in an inflatable airlock. In 2014, the MASH project developed an ultra-lightweight airlock concept with a fabric hatch that utilized a unique pressure vessel shape to minimize structural loads around a linear seal. The concept uses an automated zipper-like seal that allows for crew egress/ingress. Most of the development work on the project thus far has focused on the design, analysis and testing of the primary structure and the zipper-like seal system is in the preliminary stages of development with a successful proof-of-concept test. As part of the 2017 LEIA effort, studies were conducted on EVA crewmember interfaces on the inside of an inflatable airlock. These efforts included the design of an internal secondary structure and placement of handholds and foot restraints to enable hatch opening, closing and translation through the airlock. Structural design, analysis and testing was completed on several secondary structure candidates. Crew interface testing was also completed using an inflatable crewlock mockup and the JSC Active Response Gravity Offload System (ARGOS) to simulate the movement of an EVA crewmember through an inflatable crewlock in microgravity. The results of these tests helped demonstrate the feasibility of utilizing an inflatable structure as an airlock and informed the required volume, hatch size, and configuration and location of translation aids for crewmembers in a microgravity crewlock. The ISS Quest airlock uses a dual-chamber design with isolated compartments known as the equipment-lock and the crewlock. The equipment-lock houses the Servicing, Performance and Checkout Equipment (SPCE) items (suit batteries, consumables, etc.) while the crewlock has limited internal hardware and is the nominally depressurized compartment during US EVAs. While inflatable dual chamber airlocks have been studied, the current state of the art emphasizes an inflatable crewlock-type structure attached to a rigid equipment-lock type or habitat structure. Since a large portion of the hardware in the equipment-lock are rigid components and connectors that are installed on the ground - and an inflatable structure does not achieve full structural capabilities until pressurized in space - a depressurized fabric structure cannot provide the capabilities of a full equipment-lock. The use of an inflatable as a crewlock, however, provides all the required capabilities for EVA operations in a small launch package that offers significant volume savings over a metallic crewlock. The functions of a traditional equipment lock, including the SPCE, could be provided by a spacecraft’s habitat module or node and not necessarily in a separate equipment lock. An inflatable crewlock would be attached to the vehicle and launched in a packed and compressed state, saving volume under the launch shroud and mass for the overall airlock element compared to a rigid crewlock. Work is currently underway to continue development of an inflatable airlock with a variety of focus areas including the consideration of crew-induced loads and interfaces, the design and development of an internal sub-structure to provide translation aids and restraints, the thermal considerations of a fabric shell depressurized during an EVA, the micrometeorite environment in deep space, and the packaging and deployment of an inflatable airlock.

Deep Space Exploration↗
NASA NTRS1983

Crew systems and flight station concepts for a 1995 transport aircraft

Aircraft functional systems and crew systems were defined for a 1995 transport aircraft through a process of mission analysis, preliminary design, and evaluation in a soft mockup. This resulted in a revolutionary pilot's desk flight station design featuring an all-electric aircraft, fly-by-wire/light flight and thrust control systems, large electronic color head-down displays, head-up displays, touch panel controls for aircraft functional systems, voice command and response systems, and air traffic control systems projected for the 1990s. The conceptual aircraft, for which crew systems were designed, is a generic twin-engine wide-body, low-wing transport, capable of worldwide operation. The flight control system consists of conventional surfaces (some employed in unique ways) and new surfaces not used on current transports. The design will be incorporated into flight simulation facilities at NASA-Langley, NASA-Ames, and the Lockheed-Georgia Company. When interfaced with advanced air traffic control system models, the facilities will provide full-mission capability for researching issues affecting transport aircraft flight stations and crews of the 1990s.

Sexton, G. A.↗
NASA NTRS2010

Ares I-X: First Step in a New Era of Exploration

Since 2005, NASA's Constellation Program has been designing, building, and testing the next generation of launch and space vehicles to carry humans beyond low-Earth orbit (LEO). On October 28, 2009, the Ares Projects successfully launched the first suborbital development flight test of the Ares I crew launch vehicle, Ares I-X, from Kennedy Space Center (KSC). Although the final Constellation Program architecture is under review, data and lessons obtained from Ares I-X can be applied to any launch vehicle. This presentation will discuss the mission background and future impacts of the flight. Ares I is designed to carry up to four astronauts to the International Space Station (ISS). It also can be used with the Ares V cargo launch vehicle for a variety of missions beyond LEO. The Ares I-X development flight test was conceived in 2006 to acquire early engineering, operations, and environment data during liftoff, ascent, and first stage recovery. Engineers are using the test flight data to improve the Ares I design before its critical design review the final review before manufacturing of the flight vehicle begins. The Ares I-X flight test vehicle incorporated a mix of flight and mockup hardware, reflecting a similar length and mass to the operational vehicle. It was powered by a four-segment SRB from the Space Shuttle inventory, and was modified to include a fifth, spacer segment that made the booster approximately the same size as the five-segment SRB. The Ares I-X flight closely approximated flight conditions the Ares I will experience through Mach 4.5, performing a first stage separation at an altitude of 125,000 feet and reaching a maximum dynamic pressure ("Max Q") of approximately 850 pounds per square foot. The Ares I-X Mission Management Office (MMO) was organized functionally to address all the major test elements, including: first stage, avionics, and roll control (Marshall Space Flight Center); upper stage simulator (Glenn Research Center); crew module/launch abort system simulator (Langley Research Center); and ground systems and operations (KSC). Interfaces between vehicle elements and vehicle-ground elements, as well as environment analyses were performed by a systems engineering and integration team at Langley. Experience and lessons learned from these integrated product teams area are already being integrated into the Ares Projects to support the next generation of exploration launch vehicles.

Davis, Stephan R.↗
NASA NTRS2014

Use MACES IVA Suit for EVA Mobility Evaluations

The use of an Intra-Vehicular Activity (IVA) suit for a spacewalk or Extra-Vehicular Activity (EVA) was evaluated for mobility and usability in the Neutral Buoyancy Lab (NBL) environment. The Space Shuttle Advanced Crew Escape Suit (ACES) has been modified (MACES) to integrate with the Orion spacecraft. The first several missions of the Orion MPCV spacecraft will not have mass available to carry an EVA specific suit so any EVA required will have to be performed by the MACES. Since the MACES was not designed with EVA in mind, it was unknown what mobility the suit would be able to provide for an EVA or if a person could perform useful tasks for an extended time inside the pressurized suit. The suit was evaluated in multiple NBL runs by a variety of subjects including crewmembers with significant EVA experience. Various functional mobility tasks performed included: translation, body positioning, carrying tools, body stabilization, equipment handling, and use of tools. Hardware configurations included with and without TMG, suit with IVA gloves and suit with EVA gloves. Most tasks were completed on ISS mockups with existing EVA tools. Some limited tasks were completed with prototype tools on a simulated rocky surface. Major findings include: demonstration of the ability to weigh-out the suit, understanding the need to have subjects perform multiple runs prior to getting feedback, determination of critical sizing factors, and need for adjustment of suit work envelop. The early testing has demonstrated the feasibility of EVA's limited duration and limited scope. Further testing is required with more flight like tasking and constraints to validate these early results. If the suit is used for EVA, it will require mission specific modifications for umbilical management or PLSS integration, safety tether attachment, and tool interfaces. These evaluations are continuing through calendar year 2014.

Watson, Richard D.↗
NASA NTRS2001

Modeling and simulation for space medicine operations: preliminary requirements considered

The NASA Space Medicine program is now developing plans for more extensive use of high-fidelity medical simulation systems. The use of simulation is seen as means to more effectively use the limited time available for astronaut medical training. Training systems should be adaptable for use in a variety of training environments, including classrooms or laboratories, space vehicle mockups, analog environments, and in microgravity. Modeling and simulation can also provide the space medicine development program a mechanism for evaluation of other medical technologies under operationally realistic conditions. Systems and procedures need preflight verification with ground-based testing. Traditionally, component testing has been accomplished, but practical means for "human in the loop" verification of patient care systems have been lacking. Medical modeling and simulation technology offer potential means to accomplish such validation work. Initial considerations in the development of functional requirements and design standards for simulation systems for space medicine are discussed.

Non-programmatic↗
NASA NTRS2016

Usable Translational Hand Controllers for NASA's Habitability Design Center

This summer I was given the opportunity to work at the Habitability Design Center (HDC). NASA Johnson Space Center's HDC is currently developing Cislunar and Mars spacecraft mockups. I contributed to this effort by designing from scratch low cost, functional translational hand controllers (THCs) that will be used in spacecraft mission simulation in low to medium fidelity exploration spacecraft mockups. This project fell under the category of mechatronics, a combination of mechanical, electrical, and computer engineering. Being an aerospace engineering student, I was out of my comfort zone. And that was a wonderful thing. The autonomy that my mentor, Dr. Robert Howard, allowed me gave me the opportunity to learn by trying, failing, and trying again. This project was not only a professional success for me, but a significant learning experience. I appreciated the freedom that I had to take the time to learn new things for myself rather than blindly follow instructions. I was the sole person working on this project, and was required to work independently to solve the many hardware and software challenges that the project entailed. I researched THCs that have been used on the ISS, the Space Shuttle, and the Orion MPVC and based my design off of these. I worked through many redesigns before finding an optimal configuration of the necessary mechanisms and electrical components for the THC. Once I had a functional hardware design, I dove into the challenge of getting an Arduino Uno, an extremely low cost and easily programmable microcontroller, to behave as a human interface device. The THCs I built needed to be able to integrate to a mission simulation designed by NASA's Graphics and Visualization Lab. This proved to be the most challenging aspect of the project. To accomplish this I learned how to change the firmware of the USB serial converter microcontroller. The process was very complicated as it involved multiple software programs and manual flashing of pins on the Arduino itself. When I successfully achieved the goal I wrote an instructions manual for the process so that the HDC will be able to do this easily in the future for any human interface device they may want to create. I also created a detailed CAD model of my THC design with construction instructions. My THC utilizes three ultrasonic sensors, one for each axis of motion. I wrote a code that stimulates these sensors continuously and feeds back values from each axis ranging from -%100 to %100 of the min/max position in relation to the neutral position of each axis. This was the data that the Graphics and Visualization Lab required to interface with their simulation. I truly enjoyed working in the HDC surrounded by passionate, proactive, and brilliantly creative people. I felt valued and respected as a part of their team. I was given the time and support of my mentor whenever I asked for it. Beyond my positive project experience, I was fortunate enough to be able to take advantage of many of the extra activities that JSC has to offer. I took Russian Phase One during my lunch break every day and can now read Russian and accomplish basic verbal communication. I was heavily involved with the co-tern music video, which led to numerous incredible experiences and friendships. I saw every facility, attended every lecture, and met everyone that I could. I had coffee with Lauri Hansen. I played on an intern volleyball team at the Gilruth. I traveled to Michoud, Stennis, NOLA, and Big Bend National Park. I had the time of my life and I fell in love with JSC. In the next month I will return to Maryland and start my senior year of my undergraduate degree. As I work through it I will remember that all of the studying I do, all of the concentration I give, and all of the sacrifices that I make for school are so that I can work at a place like JSC where I am proud and excited to go into work every day. This internship was an invaluable experience for me, both professionally and personally.

Westbrook, Kimberly↗
NASA NTRS2010

Suggestions for Layout and Functional Behavior of Software-Based Voice Switch Keysets

Marshall Space Flight Center (MSFC) provides communication services for a number of real time environments, including Space Shuttle Propulsion support and International Space Station (ISS) payload operations. In such settings, control team members speak with each other via multiple voice circuits or loops. Each loop has a particular purpose and constituency, and users are assigned listen and/or talk capabilities for a given loop based on their role in fulfilling the purpose. A voice switch is a given facility's hardware and software that supports such communication, and may be interconnected with other facilities switches to create a large network that, from an end user perspective, acts like a single system. Since users typically monitor and/or respond to several voice loops concurrently for hours on end and real time operations can be very dynamic and intense, it s vital that a control panel or keyset for interfacing with the voice switch be a servant that reduces stress, not a master that adds it. Implementing the visual interface on a computer screen provides tremendous flexibility and configurability, but there s a very real risk of overcomplication. (Remember how office automation made life easier, which led to a deluge of documents that made life harder?) This paper a) discusses some basic human factors considerations related to keysets implemented as application software windows, b) suggests what to standardize at the facility level and what to leave to the user's preference, and c) provides screen shot mockups for a robust but reasonably simple user experience. Concepts apply to keyset needs in almost any type of operations control or support center.

Scott, David W.↗
NASA NTRS2017

CisLunar Habitat Internal Architecture Design Criteria

BACKGROUND: In preparation for human exploration to Mars, there is a need to define the development and test program that will validate deep space operations and systems. In that context, a Proving Grounds CisLunar habitat spacecraft is being defined as the next step towards this goal. This spacecraft will operate differently from the ISS or other spacecraft in human history. The performance envelope of this spacecraft (mass, volume, power, specifications, etc.) is being defined by the Future Capabilities Study Team. This team has recognized the need for a human-centered approach for the internal architecture of this spacecraft and has commissioned a CisLunar Phase-1 Habitat Internal Architecture Study Team to develop a NASA reference configuration, providing the Agency with a "smart buyer" approach for future acquisition. THE CISLUNAR HABITAT INTERNAL ARCHITECTURE STUDY: Overall, the CisLunar Habitat Internal Architecture study will address the most significant questions and risks in the current CisLunar architecture, habitation, and operations concept development. This effort is achieved through definition of design criteria, evaluation criteria and process, design of the CisLunar Habitat Phase-1 internal architecture, and the development and fabrication of internal architecture concepts combined with rigorous and methodical Human-in-the-Loop (HITL) evaluations and testing of the conceptual innovations in a controlled test environment. The vision of the CisLunar Habitat Internal Architecture Study is to design, build, and test a CisLunar Phase-1 Habitat Internal Architecture that will be used for habitation (e.g. habitability and human factors) evaluations. The evaluations will mature CisLunar habitat evaluation tools, guidelines, and standards, and will interface with other projects such as the Advanced Exploration Systems (AES) Program integrated Power, Avionics, Software (iPAS), and Logistics for integrated human-in-the-loop testing. The mission of the CisLunar Habitat Internal Architecture Study is to become a forcing function to establish a common understanding of CisLunar Phase-1 Habitation Internal Architecture design criteria, processes, and tools. The scope of the CisLunar Habitat Internal Architecture study is to design, develop, demonstrate, and evaluate a Phase-1 CisLunar Habitat common module internal architecture based on design criteria agreed to by NASA, the International Partners, and Commercial Exploration teams. This task is to define the CisLunar Phase-1 Internal Architecture Government Reference Design, assist NASA in becoming a "smart buyer" for Phase-1 Habitat Concepts, and ultimately to derive standards and requirements from the Internal Architecture Design Process. The first step was to define a Habitat Internal Architecture Design Criteria and create a structured philosophy to be used by design teams as a filter by which critical aspects of consideration would be identified for the purpose of organizing and utilizing interior spaces. With design criteria in place, the team will develop a series of iterative internal architecture concept designs which will be assessed by means of an evaluation criteria and process. These assessments will successively drive and refine the design, leading to the combination and down-selection of design concepts. A single refined reference design configuration will be developed into in a medium-to-high fidelity mockup. A multi-day human-in-the-loop mission test will fully evaluate the reference design and validate its configuration. Lessons learned from the design and evaluation will enable the team to identify appropriate standards for Phase-1 CisLunar Habitat Internal Architecture and will enable NASA to develop derived requirements in support of maturing CisLunar Habitation capabilities. This paper will describe the criteria definition process, workshop event, and resulting CisLunar Phase-1 Habitat Internal Architecture Design Criteria.

Jones, R.↗
NASA NTRS2016

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↗