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.
This presentation supports a Collaborative Discussion regarding industry's utilization of other NASA or external design standards and feedback and recommendations to support the possibility of an EVA suit standard.
NASA is conducting research under the UAS Integration in the NAS Project to develop standards that will enable mid-size and large unmanned aircraft to fly unrestricted in the National Airspace System. As these efforts move into its second phase, NASA is planning a series of flight tests and demonstrations, integrating industry partners' technologies. These events will not only provide valuable data to inform the RTCA Special Committee 228 DAA and C2 MOPS, but also provide an opportunity for the UAS community to test their technologies in a realistic environment. An overview of NASA UAS-NAS research will be presented touching on human systems integration, modeling and simulation and guidance and control. Plans for Flight Test 6 and Systems Integration Operationalization (SIO) will also be presented. The purpose of this meeting is to share with Kitty Hawk, at a high level, UAS-NAS research and discuss potential future collaboration between NASA and Kitty Hawk.
The Ascent Abort-2 Crew Module and Separation Ring (CSR) were developed internally to NASA, led by the JSC EA Integrated Product Team. The CSR IPT leveraged Sharepoint as an Integrated Data environment to link systems engineering and project management data element, enabling collaborative development and engagement from across the project (NASA-wide). This presentation describes the mission, the development approach, and the benefits of this approach. flight operations
NASA’s Earth Observing System Data and Information System (EOSDIS) open source Cumulus software is designed as a common set of code and services that can be used to create a pipeline to deliver and manage earth science data in the cloud. Cumulus strives to create an ecosystem on the foundation of open source that unites those with shared problems and goals by encouraging users to contribute solutions back to the platform. Large parts of ingesting and managing data are common and much of what is created can be used by others. Our goal is to maximize collaboration and code reuse while allowing users to design a custom solution that meets their needs without having to take on extraneous functionality. In this talk we will describe how the Cumulus ecosystem works beyond just open source software. We will review the technology, the successes and challenges, and the evolution and future of Cumulus as an ecosystem.
Evolving Project Integration, Innovation, and Collaboration (EPIIC) is a vision defined to transform the way projects manage information to support real-time decisions, capture best practices and lessons learned, perform assessments, and manage risk across a portfolio of projects. The foundational project management needs for data and information will be revolutionized through innovations on how we manage and access that data, implement configuration control, and certify compliance. The embedded intelligence of new interactive data interfaces integrate technical and programmatic data such that near real time analytics can be accomplished to more efficiently and accurately complete systems engineering and project management tasks. The system-wide data analytics that are integrated into customized data interfaces allows the growing team of engineers and managers required to develop and implement major NASA missions the ability to access authoritative source(s) of system information while greatly reducing the labor required to complete system assessments. This would allow, for example, much of what is accomplished in a scheduled design review to take place as needed, between any team members, at any time. An intelligent data interface that rigorously integrates systems engineering and project management information in near real time can provide substantially greater insight for systems engineers, project managers, and the large diverse teams required to complete a complex project. System engineers, programmatic personnel (those who focus on cost, schedule, and risk), the technical engineering disciplines, and project management can realize immediate benefit from the shared vision described herein. Implementation of the vision also enables significant improvements in the performance of the engineered system being developed.
The Atmospheric Science Data Center (ASDC), Goddard Earth Sciences Data and Information Systems Center (GES DISC), Socioeconomic Data and Applications Center (SEDAC), Oak Ridge National Laboratory (ORNL), Land Processes DAAC, Alaska Satellite Facility (ASF), as well as NASA Global Imagery Browse Service (GIBS), Earth Science Data Systems (ESDS) Geographic Information Systems Team (EGIST), Earthdata Content Delivery Team, ArcGIS Online Governance Team, and the Systematic Data Transformation ACCESS team have come together to establish the ArcGIS DAAC Collaboration. This coalition of participants will demonstrate their use of the ArcGIS Enterprise to support Earth science research, applied science, and outreach using Earth Observing System Data and Information System (EOSDIS) data. This includes the use of web services to fuse data products across space and time through services (e.g. ArcGIS Image Services, Open Geospatial Consortium (OGC) Web Coverage Service (WCS), and OGC Web Mapping Services (WMS)) for analysis in Jupyter notebooks, desktop tools, and web based applications.
TRACLabs’ PRIDE software was the first collaborative and highly-customizable tool designed to allow astronauts to document and mark progress on procedures in real-time, display system data, and issue commands—all from a single application. The versatility of the software caught the eye of a major oil field service company, who bought licenses and support from TRACLabs for $3.3M
In this presentation, current approaches to enable multiple-operator, multiple vehicle (M:N) operations are reviewed together with recent collaborative efforts between NASA and Uber. Topics include a review of human-automation teaming (HAT) concepts, including plays and working agreements, and a particular task-allocation method called Automation Level-based Task Allocation (ALTA). Following introductory material on HAT, an overview of a recent (July 2020) cognitive walkthrough study of M:N operations in the context of a food delivery via small-Unmanned Aircraft Systems application is provided. Initial results from this cognitive walkthrough detailing operator feedback on displays, operator and supervisor roles and responsibilities, and the overall concept of operation are reviewed. The presentation concludes with a description of a future, human-in-the-loop simulation experiment of M:N operations in a high-fidelity environment, which will examine the effects of high workload and assistive automation/tools on operator performance.
NASA’s Safe and Precise Landing Integrated Capabilities Evolution (SPLICE) project is developing sensor, algorithm, and compute technologies for precision landing and hazard avoidance. These technologies are being tested as an integrated Precision Landing and Hazard Avoidance (PL&HA) system on Blue Origin’s New Shephard suborbital vehicle. A key goal for the computing element of this technology development is to characterize the performance of the SPLICE software workloads on the project’s Descent and Landing Computer (DLC). The DLC is a multi-core processor designed as a surrogate for NASA’s High-Performance Space Computer (HPSC). Measurements of the SPLICE workload performance on the DLC provides NASA insight on how PL&HA capabilities will perform on the HPSC, and guidance on how the SPLICE algorithms can be implemented to best utilize the DLC platform. This insight can also be used to derive requirements to guide trade studies on candidate computing architectures, for use on platforms like Blue Moon. NASA and Blue Origin are collaborating under an agreement to pursue this mutual benefit. Performance metrics collected are based on measurement of common compute resources such as percentage used of memory bandwidth, I/O utilization, interrupt latency, and kernel vs. user space code residency. Where possible existing performance counters and metrics that are part of the operating system kernel are used. As the design has a significant FPGA component, performance counters are identified and instantiated in the fabric to measure DMA performance and interface metrics. Collection of metrics is performed on the DLC with a representative workload that simulates a full landing cycle of the Blue Origin New Shepard vehicle. Consideration is given to the other compute implementations and whether they can run SPLICE algorithms at the same rate and with the same latency as the DLC. One option being considered is the use of a RISC-V soft core instantiated in a radiation resilient FPGA fabric such as the Xilinx KU60. Select algorithms from the SPLICE code will be run for comparison with the DLC. This paper describes how the DLC is instrumented to collect performance measurements of the SPLICE workloads, preliminary results from these measurements, and their implications on SPLICE algorithm implementation. The results of experimentation to derive candidate requirements for architecture trades on a PL&HA computing system are also presented.
The Genesis Solar Wind Sample Return was flown with the goal of creating a baseline of elemental and isotopic solar photospheric composition from solar matter (not rocks!) for use in cosmochemical modeling. No uses for the samples outside of Cosmochemistry were advertised, and for good reason. In these days of limited funding, there is an overwhelming tendency to look inward instead of recognizing that the best outcomes of science tend to be interdisciplinary. So, below, we suggest two radical acts of collaboration that we believe will accelerate the advancement of science.
An advanced integrated environment is being developed at JPL that links collaborators who wish to perform interactive design analyses and/or mission simulations.
This paper examines unique operations considerations that drove the design of the Reference Activity Plan, the composition and proposed implementation of the RAP, and how the use of a single authoritative activity plan allows collaborative, flexible planning during uplink plan development.
The amount of autonomy in software engineering tools is increasing as developers build increasingly complex systems. Research in other domains shows that too much or too little trust in autonomous tools can have negative consequences, but we are not aware of any study that has investigated trust in autonomous tools in the highly interactive context of a software engineering workplace. We present the results of a ten week ethnographic case study of engineers collaborating with autonomous tools to write flight software at a large national space exploration organization to support high stakes missions. We find that trust in an autonomous software engineering tool in this setting was influenced by four main factors: the tool’s transparency, social context, an organization’s associated processes, and its usability. We outline theoretical implications for future research into trust in autonomous software engineering tools, and practical implications for tool designers and organizations conducting high stakes work with autonomous tools.
Resources for academia collaborating with NASA subject matter experts
Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.
Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.
A reliable method for pose estimation of an unknown and uncooperative space target using monocular vision remains an open problem. Vision-based pose determination can be challenging in case of unfavorable illumination, time-varying conditions due to rotational motion and relative orbit, and scale ambiguity resolution. To address these challenges, we propose a novel collaborative pose determination algorithm called Multi- Spacecraft Simultaneous Estimation of Pose and Shape algorithm or M-SEPS.Within M-SEPS, a team of chaser spacecraft, each equipped with a monocular camera, exchange information over a local network to jointly estimate the relative kinematic state of the target and its sparse shape landmarks. In this approach, each spacecraft processes its own images and observes particular target landmarks in parallel and in a distributed fashion. Then, the local network is exploited by the spacecraft to share their consensus proposals and aggregate them to achieve the joint estimate. We validate our algorithm using simulations of relative orbits and observations, captured by each chaser spacecraft. To the best of the authors’ knowledge, this is the first cooperative, vision-based algorithm for estimating the pose and shape of a space object for an arbitrary number of spacecraft.
Contamination containment gloveboxes are sealed containers where operators outside the glovebox can safely manipulate hazardous or contamination-sensitive materials inside the glovebox through glove ports on the container. Containment gloveboxes are used in the space industry to study sample materials returned from space such as lunar, asteroid, and comet materials, to manufacture sensitive instruments and space ight hardware, and to perform contamination-sensitive experiments. A hands-on activity has been developed by contamination control engineer and STEM education experts as part of the Virginia Earth System Science Scholars (VESSS) summer academy program to teach high school students about gloveboxes and about problem solving in a collaborative environment. In this activity, student teams are given a list of common household materials (e.g. plastic bags, plastic straws, aluminum foil, tape, disposable gloves, etc.) for building their own glovebox. Students work together to sketch and design their glovebox before being provided a kit of materials, which they must purchase along with any extra materials with a mock team budget. They are given 30 minutes to build their glovebox, however, they do not know what will be placed inside the glovebox or what operations they will need to perform within the glovebox. At the end of the build time, teams are given a small, sealed paper envelope which they place in the glovebox. Each team selects a team member to be designated as the operator, and the operator places their hands in the gloves of the glovebox. The operator uses their gloves to open the envelope in the glovebox, and they discover they have 20 minutes to assemble a jigsaw puzzle. However, the puzzle is \contaminated" with talcum powder. After the 20 minute time period, teams are judged on how well they completed and cleaned the contaminated puzzle. In a post-activity debrief, teams discuss lessons learned such as how the actual built box di ered from the sketched design, the challenge of managing a budget for materials, how the team dealt with surprises, and if their glovebox allowed enough room for the operator to perform the task. This activity has been part of the VESSS summer academy since 2016, and teaches students teamwork, creativity, hands-on experimentation, communication, and reasoning skills. In a demonstration at IAC, a volunteer from the audience will be chosen to assemble a glovebox during the presentation using the same kit of materials and will demonstrate handling puzzle pieces in the completed glovebox.