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.
An Earth Science Collaboratory is: A rich data analysis environment with: (1) Access to a wide spectrum of Earth Science data, (3) A diverse set of science analysis services and tools, (4) A means to collaborate on data, tools and analysis, and (5)Supports sharing of data, tools, results and knowledge
The mission of the Planetary Data System is to facilitate achievement of NASA's planetary science goals by efficiently collecting, archiving, and making accessible digital data produced by or relevant to NASA's planetary missions, research programs, and data analysis programs. The vision is: (1) To gather and preserve the data obtained from exploration of the Solar System by the U.S. and other nations (2) To facilitate new and exciting discoveries by providing access to and ensuring usability of those data to the worldwide community (3) To inspire the public through availability and distribution of the body of knowledge reflected in the PDS data collection PDS is a federation of heterogeneous nodes including science and support nodes
A successful policy negotiation scheme for Policy-Based Management (PBM) has been implemented. Policy negotiation is the process of determining the "best" communication policy that all of the parties involved can agree on. Specifically, the problem is how to reconcile the various (and possibly conflicting) communication protocols used by different divisions. The solution must use protocols available to all parties involved, and should attempt to do so in the best way possible. Which protocols are commonly available, and what the definition of "best" is will be dependent on the parties involved and their individual communications priorities.
The paucity of existing employer-driven simulation education and the need for workers broadly trained in Modeling & Simulation (M&S) poses a critical need that the simulation community as a whole must address. This paper will describe how this need became an impetus for a new inter-university activity that allows students to learn about simulation by doing it. The event, called Smackdown, was demonstrated for the first time in April at the Spring Simulation Multi-conference. Smackdown is an adventure in international cooperation. Students and faculty took part from the US and Europe supported by IEEE/SISO standards, industry software and National Aeronautics and Space Administration (NASA) content of are supply mission to the Moon. The developers see Smackdown providing all participants with a memorable, interactive, problem-solving experience, which can contribute, importantly to the workforce of the future. This is part of the larger need to increase undergraduate education in simulation and could be a prime candidate for senior design projects.
Future missions requiring robust internetworking services may use Delay-Disruption-Tolerant Networking (DTN) technology. CNES, NASA, and other international space agencies are committed to using CCSDS standards in their space and ground mission communications systems. The experiment described in this presentation will evaluate operations concepts, system performance, and advance technology readiness for the use of DTN protocols in conjunction with CCSDS ground systems, CCSDS data links, and CCSDS file transfer applications
The Advanced Multi-Mission Operations System (AMMOS) provides a common Mission Operation System (MOS) infrastructure to NASA deep space missions. The evolution of AMMOS has been driven by two factors: increasingly challenging requirements from space missions, and the emergence of new IT technology. The work described in this paper focuses on three key tasks related to IT technology requirements: first, to eliminate duplicate functionality; second, to promote the use of loosely coupled application programming interfaces, text based file interfaces, web-based frameworks and integrated Graphical User Interfaces (GUI) to connect users, data, and core functionality; and third, to build, develop, and deploy AMMOS services that are reusable, agile, adaptive to project MOS configurations, and responsive to industrially endorsed information technology standards.
No abstract available
The current relay orbiter infrastructure at Mars, in support of the user assets presently at Mars and those scheduled for the 2008 to 2015 time frame, only have a need to store-and-forward the returned data collected by an asset to Earth as a single non-prioritized data file. In the forward direction, the relay orbiters are only required to relay the forward link data, i.e., command sequences, software and configuration information assembled on the ground, to the Asset. There are currently no requirements for status/control messages or files to be sent in the return direction from an Asset to an application located on the Relay, nor are there requirements in the forward direction to send status/control messages or files originating on a Relay to an Asset. In addition there are currently no networking requirements at Mars where data originally sent by an Asset is to be delivered to another user asset. However, we foresee the day when standard services for 1) on-board file prioritization of user asset data by a Relay, 2) control/status message transfer between assets and a Relay, and 3) networking between assets i.e., Asset to Asset message/file transfer via a Relay will be required. Each of these services will require the Relay to be capable of understanding the data type and routing needs of the user asset data and be capable of processing it for these purposes. This paper will focus on the innovative enhancements required to the existing communications infrastructure at Mars to enable these future services.
Describe how the CCSDS recommendations have been implemented in existing infrastructure and current ongoing Mars missions. Identify what should be included in future infrastructure elements, and possible upgrades to current ground and space infrastructure, for conducting cross support for future Mars missions.
No abstract available
Realization of the expected proliferation of Unmanned Aircraft System (UAS) operations in the National Airspace System (NAS) depends on the development and validation of standards for UAS Detect and Avoid (DAA) Systems. The RTCA Special Committee 228 is charged with leading the development of draft Minimum Operational Performance Standards (MOPS) for UAS DAA Systems. NASA, as a participating member of RTCA SC-228 is committed to supporting the development and validation of draft requirements for DAA alerting and guidance systems. This presentation contains the results of two combinatorial encounter analysis studies using NASA's SAA Control fast-time simulation capability for this purpose. In these studies, encounters between two aircraft were simulated one at a time for the full factorial combination of encounter geometries (e.g., encounter angle, CPA offset) and aircraft performance (e.g., ownership and intruder ground speeds and vertical rates). The first study analyzes the relationships (e.g., timeline) between the different alerting-safety regions in the SC-228 MOPS (in order of increasing severity): 1) DAA warning alert, 2) well clear recovery (WCR) guidance, 3) DAA-Collision Avoidance (CA), and 4) TCAS RA. This study will focus primarily on encounter situations in which TCAS RA occurs prior to any of the other alerting-safety boundaries. In particular, this study will investigate whether using vertical distance or vertical distance at closest point of approach (i.e., vertical miss distance or VMD) is more appropriate for the definition of the DAA-CA region. In addition, cases where transitions between different regions skip an intermediate region will be analyzed. The second study in this presentation explores a proposal to use an altitude rate error threshold to determine if vertical maneuvers are acceptable for DAA WCR guidance against non-cooperative intruders. This study incorporates the radar from the Honeywell sensor model and examines a series of pairwise encounters between a non-cooperative intruder and a UAS ownship, with different combinations of intruder states and ownship performance levels. The study uses SAA Control as a simulation platform and pilot model, and Omnibands to provide DWC recovery guidance. Two simulation sets, one that allows vertical DWC recovery guidance and one that does not, are compared to determine if encounters with altitude rate errors above 250 feet-per-minute are more likely to have more severe losses of well clear, as determined by the Loss of Well-Clear Severity metric.
For over two decades, researchers, space users, Global Navigation Satellite System (GNSS) service providers, and international policy makers have been working diligently to expand the space-borne use of the Global Positioning System (GPS) and, most recently, to employ the full complement of GNSS constellations to increase spacecraft navigation performance. Space-borne Positioning, Navigation, and Timing (PNT) applications employing GNSS are now ubiquitous in Low Earth Orbit (LEO). GNSS use in space is quickly expanding into the Space Service Volume (SSV), the signal environment in the volume surrounding the Earth that enables real-time PNT measurements from GNSS systems at altitudes of 3000 km and above. To support the current missions and planned future missions within the SSV, initiatives are being conducted in the United States and internationally to ensure that GNSS signals are available, robust, and yield precise navigation performance. These initiatives include the Interagency Forum for Operational Requirements (IFOR) effort in the United States, to support GPS SSV signal robustness through future design changes, and the United Nations-sponsored International Committee on GNSS (ICG), to coordinate SSV development across all international GNSS constellations and regional augmentations. The results of these efforts have already proven fruitful, enabling new missions through radically improved navigation and timing performance, ensuring quick recovery from trajectory maneuvers, improving space vehicle autonomy and making GNSS signals more resilient from potential disruptions. Missions in the SSV are operational now and have demonstrated outstanding PNT performance characteristics; much better than what was envisioned less than a decade ago. The recent launch of the first in a series of US weather satellites will employ the use of GNSS in the SSV to substantially improve weather prediction and public-safety situational awareness of fast moving events, including hurricanes, flash floods, severe storms, tornados and wildfires. Thus, the benefits of the GNSS expansion and use into the SSV are tremendous, resulting in orders of magnitude return in investment to national governments and extraordinary societal benefits, including lives saved and critical infrastructure and property protected. However, this outstanding success is tempered by dual challenges: that for GPS, the current SSV specifications do not adequately protect SSV future use; and that for GNSS, the capabilities that are currently available are not protected in the future by specifications.
For over two decades, researchers, space users, Global Navigation Satellite System (GNSS) service providers, and international policy makers have been working diligently to expand the space-borne use of the Global Positioning System (GPS) and, most recently, to employ the full complement of GNSS constellations to increase spacecraft navigation performance. Space-borne Positioning, Navigation, and Timing (PNT) applications employing GNSS are now ubiquitous in Low Earth Orbit (LEO). GNSS use in space is quickly expanding into the Space Service Volume (SSV), the signal environment in the volume surrounding the Earth that enables real-time PNT measurements from GNSS systems at altitudes of 3000 km and above. To support the current missions and planned future missions within the SSV, initiatives are being conducted in the United States and internationally to ensure that GNSS signals are available, robust, and yield precise navigation performance. These initiatives include the Interagency Forum for Operational Requirements (IFOR) effort in the United States, to support GPS SSV signal robustness through future design changes, and the United Nations-sponsored International Committee on GNSS (ICG), to coordinate SSV development across all international GNSS constellations and regional augmentations. The results of these efforts have already proven fruitful, enabling new missions through radically improved navigation and timing performance, ensuring quick recovery from trajectory maneuvers, improving space vehicle autonomy and making GNSS signals more resilient from potential disruptions. Missions in the SSV are operational now and have demonstrated outstanding PNT performance characteristics; much better than what was envisioned less than a decade ago. The recent launch of the first in a series of US weather satellites will employ the use of GNSS in the SSV to substantially improve weather prediction and public-safety situational awareness of fast moving events, including hurricanes, flash floods, severe storms, tornados and wildfires. Thus, the benefits of the GNSS expansion and use into the SSV are tremendous, resulting in orders of magnitude return in investment to national governments and extraordinary societal benefits, including lives saved and critical infrastructure and property protected. However, this outstanding success is tempered by dual challenges: that for GPS, the current SSV specifications do not adequately protect SSV future use; and that for GNSS, the capabilities that are currently available are not protected in the future by specifications.
No abstract available
In order to demonstrate NASMAT’s multiscale operability, a series of illustrative examples will be presented that focus on the application of NASMAT to practical problems. First, the multiscale integration and data recursion is demonstrated by performing a multiscale analysis using only built-in micromechanics methods. NASMAT’s integration is then highlighted by running a multiscale analysis where an external finite element software calls NASMAT. In this case, at each integration point within the finite element model, a local NASMAT analysis is performed to account for failure behavior at the constituent scale. In a similar example, an external program is called from within NASMAT. This case would be relevant for a user wanting to implement an outside micromechanics technique. A combination of these examples is then presented to further illustrate the code’s flexibility when interfacing with outside codes in a multiscale framework. For all examples, data is presented using a custom-developed visualization tool. Additional potential use cases are also addressed. Finally, the plan for upcoming features and added capabilities is discussed.
Explore the source record for details and available documents.
Explore the source record for details and available documents.