Results for “software ecosystem”

NASA NTRS2022

The DIARieS Ecosystem – A Software Ecosystem to Simplify Discovery, Implementation, Analysis, Reproducibility, and Sharing of Scientific Results and Environments in Heliophysics

The infrastructure of the Heliophysics discipline has promising components but with several missing gaps, drastically reducing research and development efficiency. Developing an online discovery and analysis software ecosystem will close several of these gaps. The five main focuses on this ecosystem should be Discovery, Implementation, Analysis, Reproducibility, and Sharing of results (DIARieS). In this paper, we give a detailed description of how the proposed software ecosystem should operate, and point out the large range of possible applications to benefit many disparate groups, such as researchers, operational staff, decision-makers, and educators. The infrastructure components and technological capabilities necessary for its completion are either currently available or in development, making such an ecosystem possible for the first time. One main focus of current infrastructure investments must be to adapt and connect these pieces together into a cohesive whole to increase our research and development efficiency.

infrastructure↗

NASA NTRSDate not supplied

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

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.

activity planning↗

NASA NTRSDate not supplied

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

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.

activity planning↗

NASA NTRS2022

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

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.

Kanefsky, Bob↗

NASA NTRS2026

Integrated Computational Materials Engineering (ICME) Capability Maturity Levels for Ecosystems Enabling Digital Transformation

Digital engineering (DE) and integrated computational materials engineering (ICME) are widely recognized as critical enablers of faster, more affordable, and more reliable aerospace systems. However, many organizations have struggled to realize the promised return on investment (ROI) from digital initiatives. A primary reason is the absence of a shared, decision-focused framework that distinguishes simple digitization of existing workflows from true digital transformation that fundamentally changes how engineering decisions are made. This paper introduces an ICME capability maturity framework that fills this gap. The framework defines six cumulative ICME capability maturity levels (CMLs), explicitly tied to decision authority, engineering integration, optimization, and uncertainty management across material, process, structure, and performance scales. It is designed to complement established readiness metrics such as technology readiness levels (TRLs), manufacturing readiness levels (MRLs), and integration readiness levels (IRLs), by addressing a missing dimension: the conditions required for model-informed decision authority across scales. A unifying figure and capability table illustrate the six-level ICME Capability Maturity Framework, showing how organizations progress from digitization—with limited or negative ROI—to true digital transformation, where ICME-enabled workflows deliver measurable improvements in decision quality, cycle time, risk reduction, and reuse. The framework is intended for both technical practitioners and executive leadership, providing a common language to assess current state, guide roadmaps, align software ecosystem investments, and set realistic expectations for digital transformation outcomes. A regulatory-relevant statement clarifying the relationship between ICME capability and existing certification frameworks is provided.

ICME↗

NASA NTRS2004

From Research to Operations: Integrating Components of an Advanced Diagnostic System with an Aspect-Oriented Framework

This paper presents some of the challenges associated with bringing software projects from the research world into an operationa1 environment. While the core functional components of research-oriented software applications can have great utility in an operational setting, these applications often lack aspects important in an operational environment such as logging and security. Furthermore, these stand-alone applications, sometimes developed in isolation from one another, can produce data products useful to other applications in a software ecosystem.

Fletcher, Daryl P.↗

NASA NTRSDate not supplied

Flight Test Evaluation of Automation-Induced Oscillations

Flight-test systems analysis techniques are applied to the case of aircraft automation-induced oscillations(AIO). Emerging technological advancements in flight control automation and artificial intelligence have created a need for evaluating the age-old aerial phenomenon of undesired aircraft oscillations. This paper is an overview on the study of AIO as interactions between human pilot, software engineer, and vehicle dynamics(e.g., latency) with the presence of winds aloft. Flight-test evaluation included a broad, non-comprehensive theory on cyclical and non-cyclical oscillations and a preliminary evaluation of the ecosystem from software engineer, airspace architect, and human test pilot.

David Zahn↗

NASA NTRSDate not supplied

Developing a Vision for Maturing the Heliophysics Infrastructure towards Open Science

In the dawn of open science and the upcoming requirements, we speak about the existing state of Heliophysics infrastructure and detail the evolution required to address capability or interconnection shortcomings. Such a daunting barrier calls for an analysis ecosystem with multi-faceted capability. We propose such an ecosystem, called DIARieS, to be built upon five conceptual pillars: Discovery, Implementation, Analysis, Reproducibility, and Sharing of results. The combination of these concepts in a single platform will enable users to more intuitively combine recent advances in technology to create ‘DIARieS’ of their workflows, which can be easily made open to others in the community. The DIARieS ecosystem will also increase our efficiency by streamlining our various workflow processes, including automatic incorporation of the impending requirements of open science. The various components of the ecosystem will simplify software installation and data implementation, including automatically generated citation lists based on the components included. Automatic containerization and version control of the ecosystem will make the custom workflows easily reproducible. Employing widget technology will ease the difficulty of producing publication and commercial quality visualizations and applying common analyses techniques. Incorporating multiple technologies will streamline the various sharing methods common in our work environments today. Overall, the totality of capabilities to be offered by this analysis ecosystem will drastically simplify the application of open science principles to our work in addition to improving our efficiency and ease of collaboration.

Infrastructure↗

NASA NTRSDate not supplied

Developing a Vision for Maturing the Heliophysics Infrastructure towards Open Science: The DIARieS Analysis Ecosystem

In the dawn of open science and the upcoming requirements, we speak about the existing state of Heliophysics infrastructure and detail the evolution required to address capability or interconnection shortcomings. Such a daunting barrier calls for an analysis ecosystem with multi-faceted capability. We propose such an ecosystem, called DIARieS, to be built upon five conceptual pillars: Discovery, Implementation, Analysis, Reproducibility, and Sharing of results. The combination of these concepts in a single platform will enable users to more intuitively combine recent advances in technology to create ‘DIARieS’ of their workflows, which can be easily made open to others in the community. The DIARieS ecosystem will also increase our efficiency by streamlining our various workflow processes, including automatic incorporation of the impending requirements of open science. The various components of the ecosystem will simplify software installation and data implementation, including automatically generated citation lists based on the components included. Automatic containerization and version control of the ecosystem will make the custom workflows easily reproducible. Employing widget technology will ease the difficulty of producing publication and commercial quality visualizations and applying common analyses techniques. Incorporating multiple technologies will streamline the various sharing methods common in our work environments today. Overall, the totality of capabilities to be offered by this analysis ecosystem will drastically simplify the application of open science principles to our work in addition to improving our efficiency and ease of collaboration. This talk summarizes a vision of the proposed ecosystem, which is described in more detail in Ringuette et al. (2022: https://doi.org/10.1016/j.asr.2022.05.012).

infrastructure↗

NASA NTRS2023

The SunPy Project: An Interoperable Ecosystem for Solar Data Analysis

The SunPy Project is a community of scientists and software developers creating an ecosystem of Python packages for solar physics. The project includes the sunpy core package as well as a set of affiliated packages. The sunpy core package provides general purpose tools to access data from different providers, read image and time series data, and transform between commonly used coordinate systems. Affiliated packages perform more specialized tasks that do not fall within the more general scope of the sunpy core package. In this article, we give a high-level overview of the SunPy Project, how it is broader than the sunpy core package, and how the project curates and fosters the affiliated package system. We demonstrate how components of the SunPy ecosystem, including sunpy and several affiliated packages, work together to enable multi-instrument data analysis workflows. We also describe members of the SunPy Project and how the project interacts with the wider solar physics and scientific Python communities. Finally, we discuss the future direction and priorities of the SunPy Project.

Solar physics↗

NASA NTRSDate not supplied

Evaluating SAR Radiometric Terrain Correction products: Optimal products for applied users

Operational applications for Synthetic Aperture Radar (SAR) are under development around the world, driven by the free-and-open access of SAR C-band observations that Sentinel-1 of Copernicus has been providing since 2014. Groups like SERVIR, a joint initiative between NASA and USAID, are at the forefront of remote sensing applied uses, and have made many significant contributions to lower the barrier to access, process, and apply SAR for ecosystem services. A takeaway from the SERVIR experience in using SAR is the need to use the appropriate SAR polarimetric product. Radiometric Terrain Correction (RTC) is a key entry-level product for multiple applications that range from ecosystems to hazards. Many software packages exist to create RTC products from SLC or GRD-type Level-1 SAR data, some of which were released only recently, e.g. Interferometric SAR Computing Environment (ISCE) added an RTC module in April 2020. In addition, new versions of open source softwares are expected to address known issues from previous versions, such as Sentinel-1 Toolbox from the European Space Agency (SNAP-7). Despite the growing availability of RTC software solutions, little work has been done to identify differences between RTC products from different softwares. And to address the question, which open-source software produces the most accurate RTC product? This work evaluates Sentinel-1 RTC products created with three different softwares and approaches, including SNAP-7, ISCE-2, and a pseudo RTC product derived from GEE. The GAMMA-derived RTC product, a known optimal RTC and implemented by Alaska Satellite Facility (ASF), is used as a reference. Time series stacks over ten different sites representing varied terrain and ecosystems are evaluated. Products are evaluated for geolocation quality, absolute radiometric calibration, and for the fidelity of the radiometric terrain flattening. The results provide direct guidance and recommendations about the quality of the RTC products obtained from open source methods. This understanding is key to develop operational applications that rely on SAR Sentinel-1 data that need affordable and scalable solutions.

Africa Flores-Anderson↗

NASA NTRSDate not supplied

Extravehicular Activity Mission System Software (EMSS) - Enabling Human Planetary Exploration Data Within The Broader Planetary Data Ecosystem

The planetary science community is once again on the verge of generating, capturing and analyzing human planetary exploration data, this time via the Artemis program. Artemis missions will involve robotic missions in addition to human extravehicular activity (EVA) where crew will be generating scientific data [1]. Present-day robotic mission data expectations for data archiving involves ingesting data into the Planetary Data System (PDS), but how might PDS be leveraged/adapted/ready (or not) for human spaceflight mission data, particularly EVA data that includes non-scientific data that provides important context to the scientific data gathered on the lunar surface? This question has broader implications than what this abstract can answer, but we wanted to pose the question to 1) get conversations started and 2) highlight how operations software data handling could play a role in overall data curation.

M J Miller↗

NASA NTRS2016

ROS Hexapod

As an intern project for NASA Johnson Space Center (JSC), my job was to familiarize myself and operate a Robotics Operating System (ROS). The project outcome converted existing software assets into ROS using nodes, enabling a robotic Hexapod to communicate to be functional and controlled by an existing PlayStation 3 (PS3) controller. Existing control algorithms and current libraries have no ROS capabilities within the Hexapod C++ source code when the internship started, but that has changed throughout my internship. Conversion of C++ codes to ROS enabled existing code to be compatible with ROS, and is now controlled using an existing PS3 controller. Furthermore, my job description was to design ROS messages and script programs that enabled assets to participate in the ROS ecosystem by subscribing and publishing messages. Software programming source code is written in directories using C++. Testing of software assets included compiling code within the Linux environment using a terminal. The terminal ran the code from a directory. Several problems occurred while compiling code and the code would not compile. So modifying code to where C++ can read the source code were made. Once the code was compiled and ran, the code was uploaded to Hexapod and then controlled by a PS3 controller. The project outcome has the Hexapod fully functional and compatible with ROS and operates using the PlayStation 3 controller. In addition, an open source software (IDE) Arduino board will be integrated into the ecosystem with designing circuitry on a breadboard to add additional behavior with push buttons, potentiometers and other simple elements in the electrical circuitry. Other projects with the Arduino will be a GPS module, digital clock that will run off 22 satellites to show accurate real time using a GPS signal and an internal patch antenna to communicate with satellites. In addition, this internship experience has led me to pursue myself to learn coding more efficiently and effectively to write, subscribe and publish my own source code in different programming languages. With some familiarity with software programming, it will enhance my skills in the electrical engineering field. In contrast, my experience here at JSC with the Simulation and Graphics Branch (ER7) has led me to take my coding skill to be more proficient to increase my knowledge in software programming, and also enhancing my skills in ROS. This knowledge will be taken back to my university to implement coding in a school project that will use source coding and ROS to work on the PR2 robot which is controlled by ROS software. My skills learned here will be used to integrate messages to subscribe and publish ROS messages to a PR2 robot. The PR2 robot will be controlled by an existing PS3 controller by changing C++ coding to subscribe and publish messages to ROS. Overall the skills that were obtained here will not be lost, but increased.

Davis, Kirsch↗

NASA NTRS2016

ROS Hexapod

As an intern project for NASA Johnson Space Center (JSC), my job was to familiarize myself and operate a Robotics Operating System (ROS). The project outcome will convert existing software assets into ROS using nodes, enabling a robotic Hexapod to communicate and to be functional and controlled by an existing PlayStation 3 (PS3) controller. Existing control algorithms and current libraries have no ROS capabilities within the Hexapod C++ source code. Conversion of C++ codes to ROS will enable existing code to be compatible with ROS, and will be controlled using existing PS3 controller. Furthermore, my job description is to design ROS messages and script programs which will enable assets to participate in the ROS ecosystem. In addition, an open source software (IDE) Arduino board will be integrated in the ecosystem with designing circuitry on a breadboard to add additional behavior with push buttons, potentiometers and other simple elements in the electrical circuitry. Other projects with the Arduino will be a GPS module digital clock that will run off 22 satellites to show accurate real time using a GPS signal and internal patch antenna to communicate with satellites.

Davis, Kirsch↗

NASA NTRS2019

The Arctic-Boreal vulnerability experiment model benchmarking system

NASA's Arctic-Boreal Vulnerability Experiment (ABoVE) integrates field and airborne data into modeling and synthesis activities for understanding Arctic and Boreal ecosystem dynamics. The ABoVE Benchmarking System (ABS) is an operational software package to evaluate terrestrial biosphere models against key indicators of Arctic and Boreal ecosystem dynamics, i.e.: carbon biogeochemistry, vegetation, permafrost, hydrology, and disturbance. The ABS utilizes satellite remote sensing data, airborne data, and field data from ABoVE as well as collaborating research networks in the region, e.g.: the Permafrost Carbon Network, the International Soil Carbon Network, the Northern Circumpolar Soil Carbon Database, AmeriFlux sites, the Moderate Resolution Imaging Spectroradiometer, the Orbiting Carbon Observatory 2, and the Soil Moisture Active Passive mission. The ABS is designed to be interactive for researchers interested in having their models accurately represent observations of key Arctic indicators: a user submits model results to the system, the system evaluates the model results against a set of Arctic-Boreal benchmarks outlined in the ABoVE Concise Experiment Plan, and the user then receives a quantitative scoring of model strengths and deficiencies through a web interface. This interactivity allows model developers to iteratively improve their model for the Arctic-Boreal Region by evaluating results from successive model versions. We show here, for illustration, the improvement of the Lund–Potsdam–Jena-Wald Schnee und Landschaft (LPJwsl) version model through the ABoVE ABS as a new permafrost module is coupled to the existing model framework. The ABS will continue to incorporate new benchmarks that address indicators of Arctic-Boreal ecosystem dynamics as they become available.

ABoVE↗

NASA NTRS2019

The Cumulus Ecosystem: Open Source and Beyond to Foster Collaboration

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.

Cumulus↗

NASA NTRSDate not supplied

Monitoring and Assessing Heat Vulnerability to Identify Locations for Heat Mitigation Efforts in Sarasota, Florida

Located in the coastal subtropical region, Florida’s Sarasota County receives plenty of sunlight for more than half of the year. However, the ongoing rise in summer temperatures attributed to climate change poses an increasing vulnerability to extreme heat for the residents. Moreover, the area's high relative humidity exacerbates the discomfort of high temperatures, thereby intensifying the severity of heat events and elevating the risks of heat-related illnesses. Our collaborations with Sarasota County Sustainability underscore shared concerns about the impact of urban heat island (UHI) on the community. We utilized Earth observation data from NASA Landsat 8 and Landsat 9’s Thermal Infrared Sensors (TIRS) and the International Space Station’s Ecosystem Spaceborne Thermal Radiometer Experiment on Space Station (ECOSTRESS) to model UHI effects within the county during the summer from 2019 to 2023. By implementing the open-source Integrated Valuation of Ecosystem Services and Tradeoffs (InVEST) Urban Cooling software model, ArcGIS ModelBuilder, and principal component analysis, we identified the land surface temperature variance within the county and areas that are least capable of mitigating the effects of UHI. In addition, we use socioeconomic and demographic data as indicators to quantify vulnerability at the census tract level. The results revealed that heat intensity varies significantly across Sarasota County, with the highest temperatures being in the more developed western part of the region. We pinpointed that at least three vulnerable communities reside in high-heat regions: North Sarasota, Venice, and North Port. These areas demonstrate a confluence between socioeconomic sensitivity and environmental hazard, indicating a high priority in future heat mitigation efforts.

Theresia Phoa↗

NASA NTRSDate not supplied

Microbial Communities in Microgravity: Simulation in Lab and on the Computer

Microorganisms grow differently in spaceflight than they do on Earth. While much remains unexplained about how microgravity affects microbial growth, one dominant hypothesis is that the lack of density-driven convection in the liquid growth environment makes mixing diffusion-limited, and therefore slower. This is supported by evidence that individual microbial strains experience starvation and acid stress in microgravity. However, if it is true, then microgravity would also have measurable effects on microbes in mixed communities, because many interspecies interactions involve the exchange of soluble metabolites through the medium (cross-feeding). Specifically, cooperative cross-feeding communities would grow more slowly in microgravity, and cooperation would be less stable on evolutionary timescales. Here we describe our efforts to test this hypothesis by simulating microgravity in silico and in the lab, using a model system of Eschericia coli and Salmonella enterica that grow only when they can exchange methionine and acetate. We created CAMDLES (CFD-DEM Artificial Microgravity Developments for Living Ecosystem Simulation) as an extension of CFDEM®coupling software, to carry out computational modeling of biological flows, growth, and mass transfer in microgravity and also in laboratory artificial microgravity devices (rotating wall vessels, RWV). Using CAMDLES, we found distinct differences in growth rates between RWV and true microgravity, and we were able to identify several features, such as spatial distribution, biofilm formation, and product yield parameters, that influence the degree to which RWV growth recapitulates microgravity growth. In addition, we report on the development of a laboratory system for monitoring growth rates and species ratios of the community in RWVs, using fluorescent strains. Pairing CAMDLES with the laboratory model system allows us to generate quantitative predictions about the effects of spaceflight on organisms that will be essential to sustaining human space exploration in the long term.

microbiology↗