Search NASA⌕ Search

SEARCH · Search NASA

Results for “team science”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 379 records · Page 21

Space-to-Ground Interactions While Conducting Scientific Fieldwork Under Mars Mission Constraints

The Biologic Analog Science Associated with Lava Terrains (BASALT) project is a 4-year program dedicated to iteratively designing, implementing, and evaluating concepts of operations (ConOps) and supporting capabilities to enable and enhance scientific exploration for future human Mars missions. BASALT incorporates three field deployments during which real (non-simulated) biological and geochemical field science is conducted at two high-fidelity Mars analog locations under simulated Mars mission conditions, including communication de-lays and data transmission limitations. BASALT’s primary science objective is to investigate how the redox conditions of altered basaltic environments affect the development of microbial communities in these Mars-relevant settings. Field sites include the active East Rift Zone on the Big Island of Hawaii, reminiscent of early Mars when basaltic volcanism and interaction with water were widespread, and the dormant eastern Snake River Plain in Idaho, similar to present-day Mars where basaltic volcanism is rare and most evidence for volcano-driven hydrothermal activity is relict. BASALT’s primary science operations objective is to investigate exploration ConOps and capabilities that facilitate scientific return during human-robotic exploration under Mars mission constraints. Each field deployment consists of ten extravehicular activities (EVAs) on the volcanic flows in which two extravehicular and two intravehicular (IV) crew-members conduct the science while communicating across time delay and under bandwidth constraints with an Earth-based Mission Support Center (MSC) comprised of expert scientists and operators. Communication latencies of 5 and 15-minute one-way light time and low (0.512 Mb/s uplink, 1.54 Mb/s down-link) and high (5.0 Mb/s uplink, 10.0 Mb/s downlink) bandwidth conditions are being evaluated. EVA crewmembers communicate with the MSC via voice and text messaging and provide scientific instrument data, still imagery, video streams, and GPS tracking information. The MSC reviews this data across delay and provides recommendations for presampling and sampling tasks. The scientists used dynamic leaderboards (priority rank-ing lists), to track and rank candidate samples relative to one another and against the science objectives for the current EVA and the overall mission. Updates to the dynamic leaderboards are relayed regularly to the IV crewmembers to provide scientific feedback from Earth and to help minimize crew idle time (time spent waiting for Earth input during which no productive tasks are performed). EVA timelines are strategically designed to enable continuous (delayed) feedback from an Earth-based science team while simultaneously minimizing crew idle time. Such timelines are operationally advantageous, reducing transport costs by eliminating the need for crews to return to the same locations on multiple EVAs while still providing opportunities for recommendations from science experts on Earth, and scientifically advantageous by minimizing the potential for cross-contamination across sites. This paper will highlight the space-to-ground interaction results from the three BASALT field deployments, including planned versus actual EVA time-line data, ground assimilation times (the amount of time available to the MSC to provide input to the crew), and idle time. Furthermore, we describe how these results vary under the different communication latency and bandwidth conditions. Together, these data will provide a basis for guiding and prioritizing capability development for future human exploration missions.

Beaton, Kara H.↗

Radio-science performance analysis software

The Radio Science Systems Group (RSSG) provides various support functions for several flight project radio-science teams. Among these support functions are uplink and sequence planning, real-time operations monitoring and support, data validation, archiving and distribution functions, and data processing and analysis. This article describes the support functions that encompass radio-science data performance analysis. The primary tool used by the RSSG to fulfill this support function is the STBLTY program set. STBLTY is used to reconstruct observable frequencies and calculate model frequencies, frequency residuals, frequency stability in terms of Allan deviation, reconstructed phase, frequency and phase power spectral density, and frequency drift rates. In the case of one-way data, using an ultrastable oscillator (USO) as a frequency reference, the program set computes the spacecraft transmitted frequency and maintains a database containing the in-flight history of the USO measurements. The program set also produces graphical displays. Some examples and discussions on operating the program set on Galileo and Ulysses data will be presented.

Morabito, D. D.↗

An Overview of the Mock LISA Data Challenges

The LISA International Science Team Working Group on Data Analysis (LIST-WG1B) is sponsoring several rounds of mock data challenges, with the purpose of fostering the development of LISA data-analysis capabilities, and of demonstrating technical readiness for the maximum science exploitation of the LISA data. The first round of challenge data sets were released at this Symposium. We describe the objectives, structure, and timeline of this program.

black holes↗

Discovering Physically Meaningful Structures from Climate Extreme Data

The original proposal described an interdisciplinary team spanning UC San Diego (lead), Columbia University, and UC Irvine, with Columbia investigators including Pierre Gentine, Elias Bareinboim, and Marcus van Lier-Walqui. The proposal further specified a leadership structure in which Columbia co-investigators contributed across the three aims, with Co-PI Gentine serving as a point of contact with science teams and with responsibilities distributed across aims.

42 ENGINEERING↗

Sample Identifiers and Metadata to Support Data Management and Reuse in Multidisciplinary Ecosystem Sciences

Physical samples are foundational entities for research across biological, Earth, and environmental sciences. Data generated from sample-based analyses are not only the basis of individual studies, but can also be integrated with other data to answer new and broader-scale questions. Ecosystem studies increasingly rely on multidisciplinary team-science to study climate and environmental changes. While there are widely adopted conventions within certain domains to describe sample data, these have gaps when applied in a multidisciplinary context. In this study, we reviewed existing practices for identifying, characterizing, and linking related environmental samples. We then tested practicalities of assigning persistent identifiers to samples, with standardized metadata, in a pilot field test involving eight United States Department of Energy projects. Participants collected a variety of sample types, with analyses conducted across multiple facilities. We address terminology gaps for multidisciplinary research and make recommendations for assigning identifiers and metadata that supports sample tracking, integration, and reuse. Furthermore, our goal is to provide a practical approach to sample management, geared towards ecosystem scientists who contribute and reuse sample data.

54 ENVIRONMENTAL SCIENCES↗

Maintaining the FGS3 optical field angle distortion calibration

To date four OFAD (Optical Field Angle Distortion) calibrations have been performed on FGS3 in M35 and analyzed by the Astrometry Science Team. Two have been performed since the last HST (Hubble Space Telescope) Calibration Workshop. The ongoing Long Term Stability Tests have also been analyzed and incorporated into the calibration. A lateral color calibration has been derived from calibration and science data. Descriptions of these tests and the results of our analysis of the resulting data are given. The astrometric science supported by these calibrations is briefly reviewed.

McArthur, B.↗

Project-domain Science Traceability and Alignment Framework (P-STAF): Analysis of a Payload Architecture

Large science-focused space missions often have multiple instruments working together to address broad science goals. Systems engineers on these types of projects must work with the project scientists to evaluate trades and make decisions that result in a system that efficiently serves the mission science goals. This collaboration is more effective if the systems engineers understand both the traceability from the L1 customer requirements to the selected instruments and the contributions of each instrument in the context of the whole payload suite. These relationships might be understood implicitly by the science team on a project, but there is value in formally codifying them so this understanding can be accessed and formally analyzed by a broader systems engineering effort. We first described a framework for this communication, called the Project-domain Science Traceability and Alignment Framework (P-STAF), in the IEEE 2017 paper “A Framework for Extending the Science Traceability Matrix: Application to the Planned Europa Mission.” This paper shows how that basic framework can be leveraged to not only formally capture these relationships between the instruments and the customer needs, but also how that information can be codified in an analyzable graph that can be queried to provide a better understanding of mission risks and scope. This work was drawn from the application of P-STAF to the Europa Clipper mission, but generic example networks are used to illustrate the power of this technique.

Reinholtz, Kirk↗

The Cassini Grand Finale Mission: Planning for a New Mission Environment

The Cassini F-Ring & Proximal Orbits (FRPO) is a new and unique mission; to ensure the highest priority science gets implemented, the POST (Proximal Orbit Science Team) was created to pre-allocate the time around periapse for all 22 proximal orbits. The F-ring orbits, and proximal time outside of POST, were handled similar to Cassini’s Solstice Mission using the Pre-Integrated Event (PIE) process. The new and unique properties of the spacecraft’s trajectory required much forethought to be flown safely while still planning for the most and best science return possible. Some ring-plane crossings (RPX) will be protected against dust impacts by turning the high gain antenna (HGA) to the dust RAM direction (HGA2RAM). If on the first proximal RPX higher than expected dust readings are seen then the Project Office may choose to require more (all) subsequent RPX to be HGA2RAM, implemented via a real-time command overlay for uplinked sequences. The pointing uncertainties will be larger than usual after the final targeted flyby; some of the process changes to address this include adding extra orbit trim maneuvers (OTMs) (fuel permitting) to resync to the reference trajectory and reduce pointing uncertainties; and movable blocks of commands to be used for some periapses where atmospheric drag may cause large timing shifts Changes made for FRPO to address perceptions that these sequences will be hard to implement include requiring early pointing designs (during integration) for certain types of observations, requiring teams to check early on that they can turn to and from their observation attitude, and that their attitude is safe, and adjusting the Implementation process to give more time for science observation designers. This paper will discuss these process changes and lessons learned so far.

Ray, Trina↗

Open Source Principles Utilized by the CERES Edition 5 Level-3 Framework

The Clouds and the Earth’s Radiant Energy System (CERES) Science Team integrates and fuses observations from six CERES instruments aboard the Terra, Aqua, S-NPP, and NOAA-20 missions with data from twenty-five geostationary imagers, in creating a nearly 25-year, ongoing record of the Earth’s radiation budget. In preparation for the next version of CERES data products, the team has been exploring software development methods leveraging open-source principles and software to streamline data product configuration and algorithm implementation. This effort will provide robust software for production while maintaining greater flexibility for the algorithm developers to explore new science.

T. Nelson Hillyer↗

Open Source Principles Utilized by the CERES Edition 5 Level-3 Framework

The Clouds and the Earth’s Radiant Energy System (CERES) Science Team integrates and fuses observations from six CERES instruments aboard the Terra, Aqua, S-NPP, and NOAA-20 missions with data from twenty-five geostationary imagers, in creating a nearly 25-year, ongoing record of the Earth’s radiation budget. In preparation for the next version of CERES data products, the team has been exploring software development methods leveraging open-source principles and software to streamline data product configuration and algorithm implementation. This effort will provide robust software for production while maintaining greater flexibility for the algorithm developers to explore new science.

Thomas N Hillyer↗

Shadow of the Future: Developing Trust and Software within the Exascale Computing Project

Collaboration and team science are emerging areas of interest in software production. Historically, multi-institutional research collaborations are difficult to initiate and maintain, negatively impacting communication, negotiation, and dialogue between industry, government, and academic researchers. The Exascale Computing Project (ECP), a massive, multi-team, high-stakes initiative, facilitated broader research collaboration under a shared funding structure and extended timeline to support scientific discovery. Here, we conducted interviews with ECP teams, representing a variety of domain specialties, research institutions, and programming backgrounds. Using thematic analysis, we assessed how ECP’s structure created an environment of increased trust among projects and how software shared between teams facilitated sustained collaboration. We found that the expectation of future collaboration, i.e., the shadow of the future, greatly enhanced trust among teams and the quality of scientific software produced. Based on our findings within ECP projects, we connect to the existing literature on trust in software engineering and share recommendations for sustainable multi-institutional collaboration and shared best software practices.

Exascale computing project↗

From Prime to Extended Mission: Evolution of the MER Tactical Uplink Process

To support a 90-day surface mission for two robotic rovers, the Mars Exploration Rover mission designed and implemented an intensive tactical operations process, enabling daily commanding of each rover. Using a combination of new processes, custom software tools, a Mars-time staffing schedule, and seven-day-a-week operations, the MER team was able to compress the traditional weeks-long command-turnaround for a deep space robotic mission to about 18 hours. However, the pace of this process was never intended to be continued indefinitely. Even before the end of the three-month prime mission, MER operations began evolving towards greater sustainability. A combination of continued software tool development, increasing team experience, and availability of reusable sequences first reduced the mean process duration to approximately 11 hours. The number of workshifts required to perform the process dropped, and the team returned to a modified 'Earth-time' schedule. Additional process and tool adaptation eventually provided the option of planning multiple Martian days of activity within a single workshift, making 5-day-a-week operations possible. The vast majority of the science team returned to their home institutions, continuing to participate fully in the tactical operations process remotely. MER has continued to operate for over two Earth-years as many of its key personnel have moved on to other projects, the operations team and budget have shrunk, and the rovers have begun to exhibit symptoms of aging.

mission operations↗

From Prime to Extended Mission: Evolution of the MER Tactical Uplink Process

To support a 90-day surface mission for two robotic rovers, the Mars Exploration Rover mission designed and implemented an intensive tactical operations process, enabling daily commanding of each rover. Using a combination of new processes, custom software tools, a Mars-time staffing schedule, and seven-day-a-week operations, the MER team was able to compress the traditional weeks-long command-turnaround for a deep space robotic mission to about 18 hours. However, there was never an intention of maintaining the pace of this process indefinitely. Even before the end of the three-month prime mission, MER operations began evolving towards greater sustainability. A combination of continued software tool development, increasing team experience, and availability of reusable sequences first reduced the mean process duration to approximately 11 hours. The number of workshifts required to perform the process dropped, and the team returned to a modified 'Earth-time' schedule. Additional process and tool adaptation eventually provided the option of planning multiple Martian days of activity within a single workshift, making 5- day-a-week operations possible. The vast majority of the science team returned to their home institutions, continuing to participate fully in the tactical operations process remotely. MER has continued to operate for over two Earth-years as many of its key personnel have moved on to other projects, the operations team and budget have shrunk, and the rovers have begun to exhibit symptoms of aging.

Mars exploration↗

Digital Lunar Exploration Sites (DLES)

After an almost 50-year absence, NASA along with a group of international and commercial partners will return humans to the surface of the Moon as part of the Artemis program. As with the preceding Apollo program, modeling and simulation (M&S) will be an enabling technology for achieving the Artemis mission objectives. Fortunately, M&S has advanced considerably in the past half century, permitting much more detailed and encompassing integrated representations of the Artemis systems. One modeling area of critical importance to simulating the Artemis elements and mission activities is the accurate and efficient modeling of the operational lunar environment. This is particularly challenging since the Artemis program is considering exploration sites in the area of the Lunar South Pole (LSP), far away from any previous surface exploration sites. Fortunately, we now have considerably more and better data from recent lunar sensing missions. A planetary science team and a human exploration simulation team at NASA’s Johnson Space Center are developing a suite of products called the Digital Lunar Exploration Sites (DLES). DLES is intended to provide some of the necessary lunar environmental data products. This paper describes the fundamental need for DLES, the science data sets that are going into DLES, some of the processes used to integrate this data into DLES products, the basic products that constitute DLES, and some examples of DLES in use.

DLES↗

Digital Lunar Exploration Sites (DLES)

After an almost 50-year absence, NASA along with a group of international and commercial partners will return humans to the surface of the Moon as part of the Artemis program. As with the preceding Apollo program, modeling and simulation (M&S) will be an enabling technology for achieving the Artemis mission objectives. Fortunately, M&S has advanced considerably in the past half century, permitting much more detailed and encompassing integrated representations of the Artemis systems. One modeling area of critical importance to simulating the Artemis elements and mission activities is the accurate and efficient modeling of the operational lunar environment. This is particularly challenging since the Artemis program is considering exploration sites in the area of the Lunar South Pole (LSP), far away from any previous surface exploration sites. Fortunately, we now have considerably more and better data from recent lunar sensing missions. A planetary science team and a human exploration simulation team at NASA’s Johnson Space Center are developing a suite of products called the Digital Lunar Exploration Sites (DLES). DLES is intended to provide some of the necessary lunar environmental data products. This paper describes the fundamental need for DLES, the science data sets that are going into DLES, some of the processes used to integrate this data into DLES products, the basic products that constitute DLES, and some examples of DLES in use.

DLES↗

Artificial Intelligence (AI) Methods for Augmenting the IMPACT Tool Evidence Library

Development of the Evidence Library for use with the IMPACT probability risk assessment tool took several years and involved a staggering amount of effort from a multi-disciplinary team. A very significant amount of the labor effort to collect, assess and finalize the Clinical Finding Form (CliFF) for each of the 119 medical conditions was provided by physician subject matter experts from the Exploration Medical Capability (ExMC) Element Clinical and Science Team. Many AI tools such as ChatGPT are excellent at summarizing large amounts of information and the current project was initiated to determine how such tools might streamline laborious processes, e.g., review and summarization of many scientific research publications, to execute key steps more efficiently in the process of developing CliFFs. The process for collecting the evidence which is found in the CliFFs is well documented in the Evidence Library Methods document (ELM; HRP-48036*). Using ELM and the CliFF development instructions as a guideline, a team of developers is leveraging Microsoft Azure AI tools and services along with open-source frameworks, to construct an AI-assisted automated pipeline. This pipeline is designed to search, retrieve, and process the necessary data sources, and ultimately help generate the final version of a CliFF. Currently, the large language model evaluates the relevance of each source material to spaceflights, either as direct evidence or as an analog. Additionally, the model assists in extracting keywords and generating brief summaries to enhance augmented retrieval and search processes in later stages of CliFF development. Once the data is ready, the model can perform semantic search and retrieval, generating and extracting valuable information for the CliFF. For instance, it can handle epidemiological statistical data, such as incidence rates and the likelihood of best or worst-case scenarios. The steps that required reading and summarizing articles were viewed as providing the greatest return on investment since large language models are very efficient and accurate in summarizing large amounts of text. Since labor effort to complete the original CliFF was not recorded with sufficient granularity, comparisons with an AI tool-generated CliFF will provide merely an approximation of time saved. Upon completion of the process, the CliFF for the medical condition “appendicitis” generated with the support of AI-based methods will serve as a proof-of-concept and will be compared to the original appendicitis CliFF to determine if use of the tools resulted in content and conclusory similarity. Based upon the results from face validation of the two CliFFs, modifications to the process will be made if necessary and additional condition CliFFs will be evaluated. Ultimately, CliFFs for the entire set of medical conditions will be created with the assistance of AI tools. Depending on the cost savings realized, CliFFs for additional medical conditions can be created to expand the Evidence Library. Future direction includes specifying the characteristics of the reviewer (prompting the AI tools to generate output assuming the reviewer is a sub-specialist physician, or nurse or EMT/medic) to determine if the effects on AI-generated output are different based on knowledge, skills and abilities. *Exploration Medical Capability Evidence Library Methods, HRP-48036 Rev A, July 2022.

Ali Al↗

Cassini distributed instrument operations – what we’ve learned since Saturn orbit insertion

The Cassini mission to Saturn is complex with 12 science teams conducting distributed operations across the United States and Europe. Each Team includes scientists from around the world who actively participate in operations, including observation design, instrument commanding, downlink processing, and archiving. This represents a change in how JPL complex deep-space missions have been operated. Since Saturn Orbit Insertion (SOI), the Cassini Project has spent 17 months conducting science operations and has gained realworld experience that has tested the assumptions and rationale for this approach. We have learned that many of the expected benefits have been realized, but there were numerous unexpected challenges as well. This paper will discuss the lessons learned from the Cassini Tour experience to date. It will revisit the assumptions and rationale behind the distributed instrument operations design and will describe the results, good and bad, of implementing this method of operations. We will describe how Instrument Teams are structured, their roles and responsibilities, what challenges they faced going into orbital operations (the “tour”) and what creative solutions were proposed when funding limitations and schedule milestones prevented optimum solutions. We will also discuss the problems that have been encountered both on the ground and with the instruments, how these problems and anomalies were overcome, and what was learned along the way about the characteristics of distributed instrument operations.

Woncik, Pam↗

Cassini Distributed Instrument Operations: What We've Learned Since Saturn Orbit Insertion

The Cassini mission to Saturn is complex with 12 science teams conducting distributed operations across the United States and Europe. Each Team includes scientists from around the world who actively participate in operations, including observation design, instrument commanding, downlink processing, and archiving. This represents a change in how JPL complex deep-space missions have been operated. Since Saturn Orbit Insertion (SOI), the Cassini Project has spent 17 months conducting science operations and has gained real-world experience that has tested the assumptions and rationale for this approach. We have learned that many of the expected benefits have been realized, but there were numerous unexpected challenges as well. This paper will discuss the lessons learned from the Cassini Tour experience to date. It will revisit the assumptions and rationale behind the distributed instrument operations design and will describe the results, good and bad, of implementing this method of operations. We will describe how Instrument Teams are structured, their roles and responsibilities, what challenges they faced going into orbital operations (the 'tour') and what creative solutions were proposed when funding limitations and schedule milestones prevented optimum solutions. We will also discuss the problems that have been encountered both on the ground and with the instruments, how these problems and anomalies were overcome, and what was learned along the way about the characteristics of distributed instrument operations.

Cassini↗