Search NASA⌕ Search

SEARCH · Search NASA

Results for “software development kit (SDK)”

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.

6 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

Software for Automated Image-to-Image Co-registration

The project objectives are: a) Develop software to fine-tune image-to-image co-registration, presuming images are orthorectified prior to input; b) Create a reusable software development kit (SDK) to enable incorporation of these tools into other software; d) provide automated testing for quantitative analysis; and e) Develop software that applies multiple techniques to achieve subpixel precision in the co-registration of image pairs.

Benkelman, Cody A.↗
NASA NTRS2009

Proof of Concept Study of Trade Space Configuration Tool for Spacecraft Design

Spacecraft design is a very difficult and time consuming process because requirements and criteria are often changed or modified as the design is refined. Accounting for these adjustments in the design constraints plays a significant role in furthering the overall progress. There are numerous aspects and variables that hold significant influence on various characteristics of the design. This can be especially frustrating when attempting to conduct rapid trade space analysis on system configurations. Currently, the data and designs considered for trade space evaluations can only be displayed by using the traditional interfaces of Excel spreadsheets or CAD (Computer Aided Design) models. While helpful, these methods of analyzing the data from a systems engineering approach can be rather complicated and overwhelming. As a result, a proof of concept was conducted on a dynamic data visualization software called Thinkmap SDK (Software Developer Kit) to allow for better organization and understanding of the relationships between the various aspects that make up an entire design. The Orion Crew Module Aft Bay Subsystem was used as the test case for this study because the design and layout of many of the subsystem components will be significant in ensuring the overall center of gravity of the capsule is correct. A simplified model of this subsystem was created and programmed using Thinkmap SDK to create a preliminary prototype application of a Trade Space Configuration Tool. The completed application ensures that the core requirements for the Tool can be met. Further development is strongly suggested to produce a full prototype application to allow final evaluations and recommendations of the software capabilities.

Glidden, Geoffrey L.↗
NASA NTRS2016

NASA WorldWind: Open Source Visualization Technology for Earth Observation

NASA WorldWind: Open Source Visualization Technology for Earth Observation WorldWind, open source virtual globe technology for Java, iOS, Android and Web, is provided by NASA and is architected as API-centric modular componentry. This enable it to be continually optimized and feature-enriched in ways that allow applications based on this SDK (Software Development Kit) to benefit Earth Observation, especially Open Science, with minimal or no adjustment for the decade ahead. The next-generation National Airspace System (NAS) aviation management system for the U.S. Federal Aviation Administration, FAA, uses WorldWind, as do applications currently being developed by the European Space Agency, along with several other US and European government agencies and industry partners. This presentation will demonstrate several NASA open source use cases for WorldWind technology that include advances being made to optimize access to NetCDF and HDF data via WebWorldWind.NASA WorldWind: Multidimensional Geospatial Web Platform The ability to see spatial data in its native context is essential for that data to be appreciated whether by the scientific community, policy and decision-makers or the general public. Recently, the accessibility of spatial data has dramatically improved. Without the need to install an application, spatial data can now be experienced via any web browser, mobile devices included. For developers, by simply updating the app on your server, the latest version of your application is now immediately available to your entire usercommunity. Unlike other virtual globes such as Google Earth, NASA World Wind offers something very special, full control to customize the interface with any features or functionalities you might need. You decide how the data is accessed and experienced. This allows you to provide maximum value of the information to your user community. The web version of NASA WorldWind (WebWorldWind) has made it possible for a whole new suite of applications for managing and sharing spatial data. Apps built with this web version are ideal for immediate social media type activity and also facilitate delivery of sophisticated data exchange scenarios such as weather and climate research, disaster response, personal navigation, and industrial-strength tracking for transportation, supply chain, aviation and satellites. WebWorldWind is an application component, not an app in itself. It is written in JavaScript and provides the real world geographic context for spatial data and information visualization, using a rich set of shapes and graphic primitives. WebWorldWind also provides platform independence, while accommodating any number of data types. Web WorldWind runs on any platform via a browser, i.e., Internet Explorer, Firefox, Chrome and Safari. Features include, 3D virtual globe, 2D map with multiple projection choices (Mercator, Polar, UPS, Equirectangular), imagery and elevation import, extensible, data retrieval (via REST, WMS, WCS, WFS, Bing, User-Defined), decluttering, measurement, accurate line-ofsight, subsurface visualization, and more.

Open Source Mapping↗
NASA NTRS2021

Characterization Study of TestBed Infrastructure Performance in a Distributed Simulation Environment: Baseline Analysis

Characterization of the performance of Air Traffic Management Exploration (ATM-X) TestBed integration environment has been investigated and documented for one system configuration for progressively increasing traffic. Several statistical parameters were used to assess the performance of the TestBed distributed system such as mean, standard deviation, skewness, and kurtosis of latency, and update rate for aircraft state messages that are transmitted through the simulated system under investigation. It is necessary to assess the performance characteristics of distributed systems in terms of the indicated statistical parameters mentioned above. It is critical to verify the system performance with respect to a researcher’s required system performance. Computer host specifications are documented in terms of Central Processing Unit (CPU) clock speed and core count. Transmission Control Protocol/ Internet Protocol (TCP/IP) message protocol was used for data transmission. The system network topology also contributes to the latency and update rate variations from the one imposed by the data source. The motivation for selecting the TestBed infrastructure as the focus of this study can be attributed to the number of services and capabilities it provides that help simplify the process of preparing and conducting a simulation. These capabilities include an easy to use GUI for simulation configuration, access to TestBed library by the end-user of other simulation software components, a modular adapter paradigm that allows simple connectivity of external software to TestBed, connectivity with other simulation laboratories, and a Software Development Kit (SDK) for quicker development. Two types of traffic generators, Air Traffic Generator (ATG) and Multi Aircraft Control System (MACS) were used to generate messages that were injected into the TestBed distributed environment. Eight different air traffic scenarios with progressively increasing loads were generated for each air traffic simulator. The corresponding air traffic loads between the two simulators had an identical number of aircraft per scenario, but different flight plans. It was observed that the performance of MACS degraded for air traffic scenarios containing more than 200 aircraft (37.5 KB/s nominal throughput). However, ATG performed adequately under all tested air traffic loads up to 1200 aircraft (225. KB/s nominal throughput). The tests show that MACS exhibits better latency performance with smaller aircraft loads when compared to ATG. The tests also show that the TestBed infrastructure successfully transmits 1200 aircraft without significant degradation of its performance. From the latency trends for both MACS and ATG, it is clear that as aircraft load increases, the latency in the system increases as well as its standard deviation. Likewise, the trends for the update data rate for both MACS and ATG show that as the aircraft load increases, so does the standard deviation and mean of the update rates which can be attributed to the performance of MACS and ATG applications. The analysis of the results of this study have proven that the overall system performance is dependent on the individual performance of each system component that is connected to TestBed, which subsequently propagates into the system. All TestBed characterization tests were conducted in SimLabs at NASA Ames Research Center in November 2019. This study addresses the need for a baseline TestBed characterization, and the results will serve as a reference for more complex simulation systems.

Air Traffic Management simulations↗
NASA NTRS2010

Math Description Engine Software Development Kit

The Math Description Engine Software Development Kit (MDE SDK) can be used by software developers to make computer-rendered graphs more accessible to blind and visually-impaired users. The MDE SDK generates alternative graph descriptions in two forms: textual descriptions and non-verbal sound renderings, or sonification. It also enables display of an animated trace of a graph sonification on a visual graph component, with color and line-thickness options for users having low vision or color-related impairments. A set of accessible graphical user interface widgets is provided for operation by end users and for control of accessible graph displays. Version 1.0 of the MDE SDK generates text descriptions for 2D graphs commonly seen in math and science curriculum (and practice). The mathematically rich text descriptions can also serve as a virtual math and science assistant for blind and sighted users, making graphs more accessible for everyone. The MDE SDK has a simple application programming interface (API) that makes it easy for programmers and Web-site developers to make graphs accessible with just a few lines of code. The source code is written in Java for cross-platform compatibility and to take advantage of Java s built-in support for building accessible software application interfaces. Compiled-library and NASA Open Source versions are available with API documentation and Programmer s Guide at http:/ / prim e.jsc.n asa. gov.

Shelton, Robert O.↗
NASA NTRS2007

JMS Proxy and C/C++ Client SDK

JMS Proxy and C/C++ Client SDK (JMS signifies "Java messaging service" and "SDK" signifies "software development kit") is a software package for developing interfaces that enable legacy programs (here denoted "clients") written in the C and C++ languages to communicate with each other via a JMS broker. This package consists of two main components: the JMS proxy server component and the client C library SDK component. The JMS proxy server component implements a native Java process that receives and responds to requests from clients. This component can run on any computer that supports Java and a JMS client. The client C library SDK component is used to develop a JMS client program running in each affected C or C++ environment, without need for running a Java virtual machine in the affected computer. A C client program developed by use of this SDK has most of the quality-of-service characteristics of standard Java-based client programs, including the following: Durable subscriptions; Asynchronous message receipt; Such standard JMS message qualities as "TimeToLive," "Message Properties," and "DeliveryMode" (as the quoted terms are defined in previously published JMS documentation); and Automatic reconnection of a JMS proxy to a restarted JMS broker.

Wolgast, Paul↗