Search NASA⌕ Search

SEARCH · Search NASA

Results for “Laptop”

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 163 records · Page 9

Preliminary Radiation Testing of a State-of-the-Art Commercial 14nm CMOS Processor/System-on-a-Chip

Hardness assurance test results of Intel state-of-the-art 14nm “Broadwell” U-series processor / System-on-a-Chip (SoC) for total ionizing dose (TID) are presented, along with exploratory results from trials at a medical proton facility. Test method builds upon previous efforts [1] by utilizing commercial laptop motherboards and software stress applications as opposed to more traditional automated test equipment (ATE).

microprocessor↗

Analysis and Design of Crew Sleep Station for ISS

This paper details the analysis and design of the Temporary Sleep Station (TeSS) environmental control system for International Space Station (ISS). The TeSS will provide crewmembers with a private and personal space, to accommodate sleeping, donning and doffing of clothing, personal communication and performance of recreational activities. The need for privacy to accommodate these activities requires adequate ventilation inside the TeSS. This study considers whether temperature, carbon dioxide, and humidity within the TeSS remain within crew comfort and safety levels for various expected operating scenarios. Evaluation of these scenarios required the use and integration of various simulation codes. An approach was adapted for this study, whereby results from a particular code were integrated with other codes when necessary. Computational Fluid Dynamics (CFD) methods were used to evaluate the flow field inside the TeSS, from which local gradients for temperature, velocity, and species concentration such as CO (sub 2) could be determined. A model of the TeSS, containing a human, as well as equipment such as a laptop computer, was developed in FLUENT, a finite-volume code. Other factors, such as detailed analysis of the heat transfer through the structure, radiation, and air circulation from the TeSS to the US Laboratory Aisle, where the TeSS is housed, were considered in the model. A complementary model was developed in G189A, a code which has been used by NASA/JSC for environmental control systems analyses since the Apollo program. Boundary conditions were exchanged between the FLUENT and G189A TeSS models. G189A provides human respiration rates to the FLUENT model, while the FLUENT model provides local convective heat transfer coefficients to G189A model. An additional benefit from using an approach with both a systems simulation and CFD model, is the capability to verify the results of each model by comparison to the results of the other model. The G189A and FLUENT models were used to evaluate various ventilation designs for the TeSS over a range of operating conditions with varying crew metabolic load, equipment operating modes, ventilation flow rates, and with the TeSS doors open and closed. Results from the study were instrumental in the optimization of a design for the TeSS ventilation hardware. A special case was considered where failure of the TeSS ventilation system occurred. In this case, a study was conducted in order to determine the time required for the CO (sub 2) concentration inside the TeSS to increase to ISS limit values under transient conditions. A lumped-capacitance code, SINDA-FLUINT was used in this case to provide accurate predictions of the human reaction to the TeSS cabin conditions including core and skin temperatures and body heat storage. A simple two-dimensional CFD model of a crewmember inside the TeSS was developed in FLUENT in order to determine the volume envelope of the respired air from the human, which maintained a minimum velocity profile. This volume was then used in the SINDA-FLUINT model to facilitate the calculations of CO (sub 2) concentrations, dry bulb temperatures and humidity levels inside the TeSS.

Keener, John F.↗

Telescience Resource Kit (TReK)

Telescience Resource Kit (TReK) is one of the Huntsville Operations Support Center (HOSC) remote operations solutions. It can be used to monitor and control International Space Station (ISS) payloads from anywhere in the world. It is comprised of a suite of software applications and libraries that provide generic data system capabilities and access to HOSC services. The TReK Software has been operational since 2000. A new cross-platform version of TReK is under development. The new software is being released in phases during the 2014-2016 timeframe. The TReK Release 3.x series of software is the original TReK software that has been operational since 2000. This software runs on Windows. It contains capabilities to support traditional telemetry and commanding using CCSDS (Consultative Committee for Space Data Systems) packets. The TReK Release 4.x series of software is the new cross platform software. It runs on Windows and Linux. The new TReK software will support communication using standard IP protocols and traditional telemetry and commanding. All the software listed above is compatible and can be installed and run together on Windows. The new TReK software contains a suite of software that can be used by payload developers on the ground and onboard (TReK Toolkit). TReK Toolkit is a suite of lightweight libraries and utility applications for use onboard and on the ground. TReK Desktop is the full suite of TReK software -most useful on the ground. When TReK Desktop is released, the TReK installation program will provide the option to choose just the TReK Toolkit portion of the software or the full TReK Desktop suite. The ISS program is providing the TReK Toolkit software as a generic flight software capability offered as a standard service to payloads. TReK Software Verification was conducted during the April/May 2015 timeframe. Payload teams using the TReK software onboard can reference the TReK software verification. TReK will be demonstrated on-orbit running on an ISS provided T61p laptop. Target Timeframe: September 2015 -2016. The on-orbit demonstration will collect benchmark metrics, and will be used in the future to provide live demonstrations during ISS Payload Conferences. Benchmark metrics and demonstrations will address the protocols described in SSP 52050-0047 Ku Forward section 3.3.7. (Associated term: CCSDS File Delivery Protocol (CFDP)).

Lippincott, Jeff↗

DiskDetective.org: Finding Homes for Exoplanets Through Citizen Science

The Disk Detective project is scouring the data archive from the WISE all-sky survey to find new debris disks and protoplanetary disks-the dusty dens where exoplanets form and dwell. Volunteers on this citizen science website have already performed 1.6 million classifications, searching a catalog 8x the size of any published WISE survey. We follow up candidates using ground based telescopes in California, Arizona, Chile, Hawaii, and Argentina. We ultimately expect to increase the pool of known debris disks by approx. 400 and triple the solid angle in clusters of young stars examined with WISE, providing a unique new catalog of isolated disk stars, key planet-search targets, and candidate advanced extraterrestrial civilizations. Come to this talk to hear the news about our latest dusty discoveries and the trials and the ecstasy of launching a new citizen science project. Please bring your laptop or smartphone if you like!

debris disks↗

UAS-NAS Project Demo - Mini HITL Week 2 Stats

The UAS-NAS Project demo will showcase recent research efforts to ensure the interoperability between proposed UAS detect and avoid (DAA) human machine interface requirements (developed within RTCA SC-228) and existing collision avoidance displays. Attendees will be able to view the current state of the art of the DAA pilot traffic, alerting and guidance displays integrated with Traffic advisory and Collision Avoidance (TCAS) II in the UAS-NAS Project's research UAS ground control station (developed in partnership with the Air Force Research Laboratory). In addition, attendees will have the opportunity to interact with the research UAS ground control station and "fly" encounters, using the DAA and TCAS II displays to avoid simulated aircraft. The display of the advisories will be hosted on a laptop with an external 30" monitor, running the Vigilant Spirit system. DAA advisories will be generated by the JADEM software tool, connected to the system via the LVC Gateway. A repeater of the primary flight display will be shown on a 55" monitor mounted on a stand at the back of the booth to show the pilot interaction to the passersby.

UAS↗

Radiation Failures in Intel 14nm Microprocessors

In this study the 14 nm Intel Broadwell 5th generation core series 5005U-i3 and 5200U-i5 was mounted on Dell Inspiron laptops, MSI Cubi and Gigabyte Brix barebones and tested with Windows 8 and CentOS7 at idle. Heavy-ion-induced hard- and catastrophic failures do not appear to be related to the Intel 14nm Tri-Gate FinFET process. They originate from a small (9 m 140 m) area on the 32nm planar PCH die (not the CPU) as initially speculated. The hard failures seem to be due to a SEE but the exact physical mechanism has yet to be identified. Some possibilities include latch-ups, charge ion trapping or implantation, ion channels, or a combination of those (in biased conditions). The mechanism of the catastrophic failures seems related to the presence of electric power (1.05V core voltage). The 1064 nm laser mimics ionization radiation and induces soft- and hard failures as a direct result of electron-hole pair production, not heat. The 14nm FinFET processes continue to look promising for space radiation environments.

Microprocessors↗

Conducting Research on the International Space Station using the EXPRESS Rack Facilities

Eight "Expedite the Processing of Experiments to Space Station" (EXPRESS) Rack facilities are located within the International Space Station (ISS) laboratories to provide standard resources and interfaces for the simultaneous and independent operation of multiple experiments within each rack. Each EXPRESS Rack provides eight Middeck Locker Equivalent locations and two drawer locations for powered experiment equipment, also referred to as sub-rack payloads. Payload developers may provide their own structure to occupy the equivalent volume of one, two, or four lockers as a single unit. Resources provided for each location include power (28 Vdc, 0-500 W), command and data handling (Ethernet, RS-422, 5 Vdc discrete, +/- 5 Vdc analog), video (NTSC/RS 170A), and air cooling (0-200 W). Each rack also provides water cooling for two locations (500W ea.), one vacuum exhaust interface, and one gaseous nitrogen interface. Standard interfacing cables and hoses are provided on-orbit. One laptop computer is provided with each rack to control the rack and to accommodate payload application software. Four of the racks are equipped with the Active Rack Isolation System to reduce vibration between the ISS and the rack. EXPRESS Racks are operated by the Payload Operations Integration Center at Marshall Space Flight Center and the sub-rack experiments are operated remotely by the investigating organization. Payload Integration Managers serve as a focal to assist organizations developing payloads for an EXPRESS Rack. NASA provides EXPRESS Rack simulator software for payload developers to checkout payload command and data handling at the development site before integrating the payload with the EXPRESS Functional Checkout Unit for an end-to-end test before flight. EXPRESS Racks began supporting investigations onboard ISS on April 24, 2001 and will continue through the life of the ISS.

Thompson, Sean W.↗

AIAA Aviation UAS DAA Demonstration-Mini HITL Week 2 Stats

The UAS-NAS Project demo will showcase recent research efforts to ensure the interoperability between proposed UAS detect and avoid (DAA) human machine interface requirements (developed within RTCA SC-228) and existing collision avoidance displays. Attendees will be able to view the current state of the art of the DAA pilot traffic, alerting and guidance displays integrated with Traffic advisory and Collision Avoidance (TCAS) II in the UAS-NAS Project's research UAS ground control station (developed in partnership with the Air Force Research Laboratory). In addition, attendees will have the opportunity to interact with the research UAS ground control station and "fly" encounters, using the DAA and TCAS II displays to avoid simulated aircraft. The display of the advisories will be hosted on a laptop with an external 30" monitor, running the Vigilant Spririt system. DAA advisories will be generated by the JADEM software tool, connected to the system via the LVC Gateway. A repeater of the primary flight display will be shown on a 55" tv/monitor mounted on a stand at the back of the booth to show the pilot interaction to the passersby.

UAS↗

Medical Data Architecture Project Capabilities and Design

Mission constraints will challenge the delivery of medical care on a long-term, deep space exploration mission. This type of mission will be restricted in the availability of medical knowledge, skills, procedures and resources to prevent, diagnose, and treat in-flight medical events. Challenges to providing medical care are anticipated, including resource and resupply constraints, delayed communications and no ability for medical evacuation. The Medical Data Architecture (MDA) project will enable medical care capability in this constrained environment. The first version of the system, called "Test Bed 1," includes capabilities for automated data collection, data storage and data retrieval to provide information to the Crew Medical Officer (CMO). Test Bed 1 seeks to establish a data architecture foundation and develop a scalable data management system through modular design and standardized interfaces. In addition, it will demonstrate to stakeholders the potential for an improved, automated, flow of data to and from the medical system over the current methods employed on the International Space Station (ISS). It integrates a set of external devices, software and processes, and a Subjective, Objective, Assessment, and Plan (SOAP) note commonly used by clinicians. Medical data like electrocardiogram plots, heart rate, skin temperature, respiration rate, medications taken, and more are collected from devices and stored in the Electronic Medical Records (EMR) system, and reported to crew and clinician. Devices integrated include the Astroskin biosensor vest and IMED CARDIAX electrocardiogram (ECG) device with INEED MD ECG Glove, and the NASA-developed Medical Dose Tracker application. The system is designed to be operated as a standalone system, and can be deployed in a variety of environments, from a laptop to a data center. The system is primarily composed of open-source software tools, and is designed to be modular, so new capabilities can be added. The software components and integration methods will be discussed.

Data architecture↗

Using Docker Containers to Extend Reproducibility Architecture for the NASA Earth Exchange (NEX)

NASA Earth Exchange (NEX) is a data, supercomputing and knowledge collaboratory that houses NASA satellite, climate and ancillary data where a focused community can come together to address large-scale challenges in Earth sciences. As NEX has been growing into a petabyte-size platform for analysis, experiments and data production, it has been increasingly important to enable users to easily retrace their steps, identify what datasets were produced by which process chains, and give them ability to readily reproduce their results. This can be a tedious and difficult task even for a small project, but is almost impossible on large processing pipelines. We have developed an initial reproducibility and knowledge capture solution for the NEX, however, if users want to move the code to another system, whether it is their home institution cluster, laptop or the cloud, they have to find, build and install all the required dependencies that would run their code. This can be a very tedious and tricky process and is a big impediment to moving code to data and reproducibility outside the original system. The NEX team has tried to assist users who wanted to move their code into OpenNEX on Amazon cloud by creating custom virtual machines with all the software and dependencies installed, but this, while solving some of the issues, creates a new bottleneck that requires the NEX team to be involved with any new request, updates to virtual machines and general maintenance support. In this presentation, we will describe a solution that integrates NEX and Docker to bridge the gap in code-to-data migration. The core of the solution is saemi-automatic conversion of science codes, tools and services that are already tracked and described in the NEX provenance system, to Docker - an open-source Linux container software. Docker is available on most computer platforms, easy to install and capable of seamlessly creating and/or executing any application packaged in the appropriate format. We believe this is an important step towards seamless process deployment in heterogeneous environments that will enhance community access to NASA data and tools in a scalable way, promote software reuse, and improve reproducibility of scientific results.

earth exchange↗

Medical Data Architecture Capabilities and Design

Mission constraints will challenge the delivery of medical care on a long-term, deep space explorationmission. This type of mission will be restricted in the availability of medical knowledge, skills, procedures and resourcesto prevent, diagnose, and treat in-flight medical events. Challenges to providing medical care are anticipated, includingresource and resupply constraints, delayed communications and no ability for medical evacuation. The Medical DataArchitecture (MDA) project will enable medical care capability in this constrained environment.The first version of thesystem, called Test Bed 1, includes capabilities for automated data collection, data storage and data retrieval to provideinformation to the Crew Medical Officer (CMO). Test Bed 1 seeks to establish a data architecture foundation and developa scalable data management system through modular design and standardized interfaces. In addition, it will demonstrateto stakeholders the potential for an improved, automated, flow of data to and from the medical system over the currentmethods employed on the International Space Station (ISS). It integrates a set of external devices, software andprocesses, and a Subjective, Objective, Assessment, and Plan (SOAP) note commonly used by clinicians. Medical datalike electrocardiogram plots, heart rate, skin temperature, respiration rate, medications taken, and more are collectedfrom devices and stored in the Electronic Medical Records (EMR) system, and reported to crew and clinician. Devicesintegrated include the Astroskin biosensor vest and IMED CARDIAX electrocardiogram (ECG) device with INEED MDECG Glove, and the NASA-developed Medical Dose Tracker application.The system is designed to be operated as astandalone system, and can be deployed in a variety of environments, from a laptop to a data center. The system isprimarily composed of open-source software tools, and is designed to be modular, so new capabilities can be added. Thesoftware components and integration methods will be discussed.

Exploration medical system↗

UAV Inspection of Electrical Transmission Infrastructure with Path Conformance Autonomy and Lidar-Based Geofences NASA Report on UTM Reference Mission Flights at Southern Company Flights November 2016

Flights at low altitudes in close proximity to electrical transmission infrastructure present serious navigational challenges: GPS and radio communication quality is variable and yet tight position control is needed to measure defects while avoiding collisions with ground structures. To advance unmanned aerial vehicle (UAV) navigation technology while accomplishing a task with economic and societal benefit, a high voltage electrical infrastructure inspection reference mission was designed. An integrated air-ground platform was developed for this mission and tested in two days of experimental flights to determine whether navigational augmentation was needed to successfully conduct a controlled inspection experiment. The airborne component of the platform was a multirotor UAV built from commercial off-the-shelf hardware and software, and the ground component was a commercial laptop running open source software. A compact ultraviolet sensor mounted on the UAV can locate 'hot spots' (potential failure points in the electric grid), so long as the UAV flight path adequately samples the airspace near the power grid structures. To improve navigation, the platform was supplemented with two navigation technologies: lidar-to-polyhedron preflight processing for obstacle demarcation and inspection distance planning, and trajectory management software to enforce inspection standoff distance. Both navigation technologies were essential to obtaining useful results from the hot spot sensor in this obstacle-rich, low-altitude airspace. Because the electrical grid extends into crowded airspaces, the UAV position was tracked with NASA unmanned aerial system traffic management (UTM) technology. The following results were obtained: (1) Inspection of high-voltage electrical transmission infrastructure to locate 'hot spots' of ultraviolet emission requires navigation methods that are not broadly available and are not needed at higher altitude flights above ground structures. (2) The sensing capability of a novel airborne UV detector was verified with a standard ground-based instrument. Flights with this sensor showed that UAV measurement operations and recording methods are viable. With improved sensor range, UAVs equipped with compact UV sensors could serve as the detection elements in a self-diagnosing power grid. (3) Simplification of rich lidar maps to polyhedral obstacle maps reduces data volume by orders of magnitude, so that computation with the resultant maps in real time is possible. This enables real-time obstacle avoidance autonomy. Stable navigation may be feasible in the GPS-deprived environment near transmission lines by a UAV that senses ground structures and compares them to these simplified maps. (4) A new, formally verified path conformance software system that runs onboard a UAV was demonstrated in flight for the first time. It successfully maneuvered the aircraft after a sudden lateral perturbation that models a gust of wind, and processed lidar-derived polyhedral obstacle maps in real time. (5) Tracking of the UAV in the national airspace using the NASA UTM technology was a key safety component of this reference mission, since the flights were conducted beneath the landing approach to a heavily used runway. Comparison to autopilot tracking showed that UTM tracking accurately records the UAV position throughout the flight path.

Moore, Andrew J.↗

Reusing JPSS Ground System Components to Process Aura Ozone Monitoring Instrument Science Products

New Earth observation instruments are planned to enable advancements in Earth science research over the next decade. Diversity of Earth observing instruments and their observing platforms will continue to increase as new instrument technologies emerge and are deployed as part of National programs such as Joint Polar Satellite System (JPSS), Geostationary Operational Environmental Satellite system (GOES), Landsat as well as the potential for many CubeSat and aircraft missions. The practical use and value of these observational data often extends well beyond their original purpose. The practicing community needs intuitive and standardized tools to enable quick unfettered development of tailored products for specific applications and decision support systems. However, the associated data processing system can take years to develop and requires inherent knowledge and the ability to integrate increasingly diverse data types from multiple sources. This paper describes the adaptation of a large-scale data processing system built for supporting JPSS algorithm calibration and validation (CalVal) node to a simplified science data system for rapid application. The new configurable data system reuses scalable JAVA technologies built for the JPSS Government Resource for Algorithm Verification, Independent Test, and Evaluation (GRAVITE) system to run within a laptop environment and support product generation and data processing of AURA Ozone Monitoring Instrument (OMI) science products. Of particular interest are the root requirements necessary for integrating experimental algorithms and Hierarchical Data Format (HDF) data access libraries into a science data production system. This study demonstrates the ability to reuse existing Ground System technologies to support future missions with minimal changes.

Science Data Systems↗

Overview of the Life Sciences Glovebox (LSG) Facility

The Life Sciences Glovebox (LSG) is a rack-level payload facility designed to house biological investigations in a "workbench" type environment aboard the International Space Station (ISS). The facility is scheduled to be launched in September 2018 and will be installed in the Japanese Experiment Module (JEM) of the ISS. LSG is comprised of an extendable work volume, an airlock, an avionics package, a laptop, and supporting structure. The 450L work volume provides two levels of containment for investigations via the physical barrier of its structure and an internal, filtered airflow that results in a negative pressure relative to ISS cabin pressure. The facility provides many other resources for investigation use including 28 VDC power, 120 VAC power, heat rejection, data connections, and video. Portions of the interior surfaces of the work volume are ferrous, allowing investigations and supporting hardware to be magnetically affixed to these surfaces. A UV decontamination system and a variety of ancillary hardware are available for investigations to use while occupying LSG. An engineering unit on the ground is used for payload development and integrated verification testing. Once the facility is installed and commissioned, it will be managed by the same team that manages the Microgravity Science Glovebox (MSG), another rack-level payload facility that has been operating aboard the ISS since 2002. Experienced Investigation Payload Integration Managers (IPIMs), who also support MSG payloads, will be available to assist payload developers through the integration process. This presentation will provide an overview of the LSG facility and the planned investigation flow for the near future.

Jordan, Lee↗

Demonstrating Autonomous Mission Operations Onboard the International Space Station

The NASA Autonomous Mission Operations (AMO) project conducted an experiment to turn over operation and management of selected International Space Station (ISS) sys- tems to the on-board crew. ISS crews managed two different spacecraft systems: the Total Organic Carbon Analyzer (TOCA), a water quality analyzer, and Station Support Com- puters (SSC) laptops, which are non-critical crew computer systems. These systems were selected because they are representative of systems a future crew may need to operate au- tonomously during a deep space mission. The crew autonomously operated these systems, taking on mission operations functions traditionally performed by support teams on the ground, using new software tools that provide decision support algorithms for planning, monitoring and fault management, hardware schematics, system briefs, and data displays that are normally unavailable to the crew. The experiment lasted seven months, during which ISS crews managed TOCA and SSCs on 22 occasions. The AMO software processed data from TOCA and SSCs continuously during this seven month period. The combined performance of the software and crew achieved a 88 success rate on managing TOCA activity, the system for which ground-truth was available.

Autonomous Mission Operations↗

Wearable Biosensor Monitor to Support Autonomous Crew Health and Readiness to Perform

For future human exploration missions, NASA needs a health monitoring system composed of hardware that is compact, fully interoperable with an integrated data management system, and requires minimal consumables. Such a system will be achieved through the integration of small, easy to use biomedical sensors that will have the ability to measure, store and transmit physiological parameters during operational and ambulatory activity. Since 2012, the Canadian Space Agency (CSA) has been active in funding the development of wearable biomonitoring sensors. The Astroskin is the first prototype and consists of a shirt-based garment and headband with embedded sensors, and associated software and technology that measure vital signs, sleep quality and activity level of the wearer. NASA and CSA have been collaborating since 2014 to test and validate this system in a lab environment at Ames Research Center and more recently in the Human Exploration Research Analog (HERA) located at Johnson Spaceflight Center. Specific objectives of the HERA study were: 1) to assess the performance of the Astroskin biosensor system for long-term health monitoring (24-hours) capabilities and during exercise as a measure of crew fitness; 2) to obtain crew feedback on comfort and usability of the Astroskin system; 3) to demonstrate performance of Bluetooth communication during real-time transmission and for verification of data in this environment; and 4) to obtain baseline data for further development of algorithms and tools that facilitate decision support for diagnosing and monitoring of a sick or injured crewmember. HERA Campaign 3 included four missions (each 30-days in duration) with four crewmembers assigned to each mission. A total of 9 men and 7 women participated in the Astroskin evaluation that included continuous physiological monitoring (24-hours) on mission days MD-11, MD1 (high workload), MD15 (low workload), MD19, MD29, and MD+7. Mission days 19 and 29 also included 30 minutes of sub-maximal exercise on a cycle ergometer. Following each 24-hour monitoring session crew physiological data were downloaded to laptops and each crewmember completed a 28 question survey on their experiences with the Astroskin hardware and software. This presentation will focus on lessons learned from the HERA missions. Specifically it will address Astroskin system performance in terms of data loss and data quality (no comparison to lab standard devices), wireless communication with the onboard mobile device, crew usability and comfort, and future development of a next generation biomonitoring system.

crew fitness↗

Designing the User Experience for Earth Observation Data Services in the Cloud

NASA's Earth Observation (EO) inventory is projected to grow by an order of magnitude over the next 5-6 years. The current mode for working with EO data of downloading the data to a local machine (laptop, desktop or server) will be difficult to sustain for these upcoming volumes. Therefore, NASA is in the process of developing a capability to host large volume data in commercial cloud, with an eye toward encouraging data analysis in the cloud. However, in order for the user community to take advantage of this new mode of data interaction, the user experience must be redesigned. Cloud-hosted data brings new challenges, such as managing the costs of data egress and working with data in Web Object Storage instead of a Posix filesystem. However, it also brings new opportunities. Scaling data transformation processes may permit more synchronous data services with near-immediate response vs. cumbersome ordering systems with latencies of hours or days. Data co-location in the cloud can facilitate data integration and fusion. Highly scalable filesystems and databases in the cloud support data reorganization to facilitate analysis at scale. In the course of NASA's reimagining of the User Experience for EO data usage relies on end user input gathered through surveys, workshops and meetings (such as this). At the same time, we have embarked on a course of pedagogy and capacity building to help the user community evolve to cloud-based analysis.

Lynnes, Christopher↗

Software Tool for Tracking & Mapping the NASA Orion AA-2 Test Flight Ejectable Data Recorders in Real Time

On 2 July 2019, the NASA Ascent Abort 2 flight took place off the Florida coast to test the emergency systems to separate the Orion Crew Module (CM) from the future Space Launch System rocket in the event of a malfunction. During this high-altitude test, instrumentation data was recorded on twelve customized buoyant Ejectable Data Recorders (EDRs) and subsequently jettisoned from the CM in mid-air. Upon release, the EDRs activated their GPS-Iridium beacon systems and began transmitting Short Burst Data (SBD) messages via the Iridium satellite network to relay their individual location and system health information. To locate, track and retrieve each EDR from the ocean surface in real-time, multiple open-source programming tools (Python and Linux shells) were developed for parsing the incoming Iridium binary SBD messages. For this, a Linux laptop was used to receive the Iridium-generated emails containing the SBD messages and autonomously execute the parsing tools. The received SBD data contained location, timestamp and health status information that was translated, saved, and subsequently used for simultaneously generating a continuously updated color-coded tabular display summary and unique KML files used with Google Earth to track their locations. Once their locations were known, dedicated recovery vessels retrieved all EDRs from the ocean. An additional tool was also developed in order to generate 5- and 10-minute geolocation predictions for each EDR by deriving the displacement distance, elapsed time, displacement heading and velocity based on the latest known information available. The recovery vessels were also tracked with the use of a separate commercial GPS beacon system. After jettison, 67% of the EDRs transmitted valid data by the time they were retrieved from the ocean. However, the real-time information presented by the plotting tool allowed for the ready depiction of EDR dispersal patterns and reference drift trajectories, which contributed to the recovery of all twelve EDRs and the AA-2 flight data. Lastly, the available data showed that the distance between the software’s reported drift/predicted locations and the recovery locations did not exceed 38 meters, therefore demonstrating the advantages of this software tool for supporting real-time tracking and recovery efforts of beacon devices.

Moxey, Lucas↗