Search NASA⌕ Search

SEARCH · Search NASA

Results for “interoperability”

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 181 records · Page 10

Governing Data Findability, Accessibility, Interoperability and Reusability (FAIR) Compliance

The most recent data strategy documents at both the federal and NASA levels stipulate that systems should strive for the data they manage to be Findable, Accessible, Interoperable, and Reusable (FAIR). The NASA Life Sciences Portal (NLSP) has already begun leading efforts in this area for HRP, initiating efforts to comply with the FAIR principles. The broad interpretation of the FAIR principles has led to a plethora of tools that use a splay of metrics specifically but variably developed to judge how compliant data and systems are with the principles. A recent review [3] identified and studied 1,180 metrics across 20 publicly available tools for checking FAIR compliance of data and systems. Because of their very recent development, many organizations and data systems managers and developers have not yet had adequate time or resources to understand these FAIR compliance tools and metrics, their variations in design, accuracy or ease of application to their specific data sets and systems. Thus, it would be best for larger organizations like NASA to approach formulating a strategy for governance of FAIR compliance that can be flexibly applied and is adaptable to an evolving awareness knowledge of FAIR compliance methods and tools. In September 2024, the NASA Science Mission Directorate(SMD) organized a workshop on NASA science data repositories, including the topics of implementing FAIR and governing FAIR compliance across SMD. The initial part of these FAIR discussions focused on developing consensus around required science metadata fields. This is challenging given the diverse nature of NASA’s scientific data portfolio, the variety of metadata models and vocabularies used, and variable level of resources available to curate these data. Later discussion focused on three possible approaches to governing FAIR compliance: distributed, in which various programs, projects or systems define their own methods for assessing FAIR compliance, reporting results up appropriate management lines; centralized, in which higher-level organization(s) specify compliance tools or methods for the various data systems; and multi-level, in which a group comprised of individuals with expertise from multiple levels with organizations is formed to provide guidance and/or specifications for governing FAIR compliance. We report on the recommendations this session yielded, and how these might be shaped specifically to help implement and govern the compliance with FAIR of Human Research Program data and systems.

governance↗

CCAMP: OpenMP and OpenACC Interoperable Framework

Heterogeneous systems have become a staple of the HPC environment. Several directive-based solutions, such as OpenMP and OpenACC, have been developed to alleviate the challenges of programming heterogeneous systems, and these standards strive to provide a single portable programming solution across heterogeneous environments. However, in many ways this goal has yet to be realized due to device-specific implementations and different levels of language support across compilers. In this framework we aim to analyze and address the different levels of optimization and compatibility between OpenACC and OpenMP programs and device compilers. We introduce the CCAMP framework, built on the OpenARC compiler, which implements language translation between OpenACC and OpenMP, with the goal of exploiting the maturity of different device-specific compilers to maximize performance for a given architecture. We show that CCAMP allows us to generate code for a specific device-compiler combination given a device-agnostic OpenMP or OpenACC program, allowing compilation and execution of programs with specific directives on otherwise incompatible devices. CCAMP also provides a starting point for a more advanced interoperable framework that can effectively provide directive translation and device, compiler, and application specific optimizations.

Lambert, Jacob↗

Application of DLT cybersecurity stack to TES applications for a scalable, cybersecure, and interoperable future

Transactive Energy Systems (TES) are expected to improve upon existing grid operations and capabilities by enabling the integration of traditional grid resources with distributed energy resources (DER). Distributed Ledger Technology or DLT (e.g., blockchain) presents itself as a viable instrument to support decentralized, autonomous, and tamper-evident applications, which can be leveraged within TES's ecosystem. DLTs can provide pertinent security controls including access controls, data immutability, and traceability in addition to other well-known advantages such as decentralization and scalability. This work demonstrates the DLT Cybersecurity stack and its applicability to TES-based use-cases/applications. The seven-layer DLT cybersecurity stack is a DLT-agnostic framework that can quickly be used to classify and group the individual needs of an application into the different processing and cybersecurity layers offered by a DLT using a common taxonomy and an architectural mapping framework. This enables application engineers to demystify and strengthen the overall security aspects of their systems while maintaining an open perspective towards features and drawbacks that may hinder their performance in real-world scenarios. The paper leverages the work performed by the IEEE P2418.5 - Blockchain for Energy Standards working group.

Blockchain, blockchain interoperability, Cybersecu↗

Computing Sparse Tensor Decompositions via Chapel and C++/MPI Interoperability without Intermediate I/O

We extend an existing approach for efficient use of shared mapped memory across Chapel and C++ for graph data stored as 1-D arrays to sparse tensor data stored using a combination of 2-D and 1-D arrays. We describe the specific extensions that provide use of shared mapped memory tensor data for a particular C++ tensor decomposition tool called GentenMPI. We then demonstrate our approach on several real-world datasets, providing timing results that illustrate minimal overhead incurred using this approach. Finally, we extend our work to improve memory usage and provide convenient random access to sparse shared mapped memory tensor elements in Chapel, while still being capable of leveraging high performance implementations of tensor algorithms in C++.

97 MATHEMATICS AND COMPUTING↗

Legacy Devices and Interoperability: Developing a Scientific Strategy for Inclusion and Representation of Older Devices

Legacy devices across grid, transportation, and building systems present complex modernization challenges that extend far beyond simple equipment obsolescence. Pulling from presentations and break-out group discussions from this workshop on legacy devices across all three sectors, this report examines the interconnected factors driving replacement decisions, documents successful modernization initiatives from recent years, and provides strategic guidance for coordinating infrastructure transformation across these critical sectors.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Interoperable Solution for Test Execution in Various I&T Environments

When there is spacecraft collaboration between several industry partners, there is an inherent difference in integration and test (I&T) methodologies, which creates a challenge for verifying flight systems during the development phase. To converge the differing I&T methodologies, considerations were required for multiple project areas such as Flight System Testbed (FST), Assembly, Test, and Launch Operations (ATLO), and Spacecraft Simulator environments. This paper details the challenges and approaches of the JPL's effort in engineering a solution to testing the flight system with the Mission Operations Ground System while maintaining the comparability with testing methods of the industry partners.

integration↗

Interoperability in the Labyrinth

During the upcoming Summer 2016 meeting of the ESIP Federation (July 19-22), OpenDAP will hold a Developers and Users Workshop. While a broad set of topics will be covered, a key focus is capitalizing on recent EOSDIS-sponsored advances in Hyrax, OPeNDAPs own software for server-side realization of the DAP2 and DAP4 protocols. These Hyrax advances are as important to data users as to data providers, and the workshop will include hands-on experiences of value to both.

ESIP↗

SC-228 Inclusion of DAA Warning Alert for TCAS Interoperability

This white paper summarizes NASA research results that have informed Special Committee 228 (SC-228) discussions and decisions regarding the inclusion of a warning-level alert within the detect and avoid (DAA) alerting structure for unmanned aircraft systems (UAS). For UAS, the removal of the pilot from onboard the aircraft has eliminated the ability of the ground-based pilot in command (PIC) to use out-the-window visual information to make judgments about a potential threat of a loss of well clear with another aircraft. As a result, the DAA traffic display will be the primary source of information that the PIC can use to execute the three primary well clear functions: 1) detect a potential loss of well clear, 2) determine a resolution maneuver, and 3) upload that maneuver to the aircraft via the ground control station (GCS). In addition, pilots are required to coordinate with air traffic control (ATC) prior to maneuvering off of their approved flight plan. In determining an appropriate resolution maneuver to avoid a loss of well clear, the PIC must decide both when and how to maneuver, and both the timeliness and the accuracy (i.e., correctness) of the maneuver are critical to reducing the likelihood and/or severity of a loss of well clear. Alerting information is one of three critical components of the DAA display, along with traffic information elements (e.g., relative heading, speed and altitude) and maneuver guidance. Alerting information and maneuver guidance, in particular, have been found to have a significant impact, both statistically and practically, on pilots' ability to avoid and minimize the severity of losses of well clear While all three display components are key to pilots performing the traffic avoidance task of remaining well clear, in general, alerting information provides crucial information about when a resolution maneuver is required while maneuver guidance assists the pilot in determining how best to maneuver. A fundamental task of the DAA alerting system is to provide critical timing information to the pilot about the potential for a loss of well clear with another aircraft. This is done by employing both temporal and spatial thresholds that indicate to the pilot the likelihood and imminence of a loss of well clear. The design of the DAA alerting thresholds is a balancing act between eliciting the desired pilot response in real loss of well clear threat events and reducing excessive, unnecessary, and/or uncoordinated UAS maneuvering within the air traffic environment; larger thresholds, both spatially and temporally, may increase the likelihood of a pilot avoiding a loss of well clear, but it can also increase the frequency of maneuvering - especially in cases where a maneuver is not actually needed to maintain well clear. A series of human in the loop (HITL) simulations have been conducted as part of NASA's Unmanned Aircraft Systems (UAS) Integration in the National Airspace System (NAS) project. The purpose of these HITLs has been to provide empirical results in order to inform development of the minimum human-machine interface requirements for the DAA system. This white paper will present those results which provide evidence of a human performance benefit (in terms of response times and ability to remain well clear of other aircraft) of the DAA warning alert both with and without a collision avoidance system on board the aircraft.

TCAS interoperability↗