Search NASA⌕ Search

SEARCH · Search NASA

Results for “collaborative interfaces.”

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 415 records · Page 23
All sourcesNASA NTRSDOE OSTI
NASA NTRS2000

Internet Technologies for Space-based Communications: State of the Art and Challenges

The Internet is rapidly changing the ways we communicate information around the globe today. The desire to provide Internet-based services to anyone, anywhere, anytime has brought satellite communications to the forefront to become an integral part of the Internet. In spite of the distances involved, satellite links are proving to be capable of providing Internet services based on Internet protocol (TCP/IP) stack. This development has led to the question particularly at NASA; can satellites and other space platforms become an Internet-node in space? This will allow the direct transfer of information directly from space to the users on Earth and even be able to control the spacecraft and its instruments. NASA even wants to extend the near earth space Internet to deep space applications where scientists and the public here on Earth may view space exploration in real time via the Internet. NASA's future solar system exploration will involve intensive in situ investigations of planets, moons, asteroids, and comets. While past missions typically involved a single fly-by or orbiting science spacecraft, future missions will begin to use fleets of small, highly intelligent robotic vehicles to carry out collaborative investigations. The resulting multi-spacecraft topologies will effectively create a wide area network spanning the solar system. However, this will require significant development in Internet technologies for space use. This paper provides the status'of the Internet for near earth applications and the potential extension of the Internet for use in deep space planetary exploration. The paper will discuss the overall challenges of implementing the space Internet and how the space Internet will integrate into the complex terrestrial systems those forms the Internet of today in a hybrid set of networks. Internet. We envision extending to the deep space environment such Internet concepts as a well-designed layered architecture. This effort will require an ability to develop and infuse new physical layer technology to increase network bandwidth at very low-bit error rates. In addition, we identify network technologies such as routers and switches needed to maintain standard application layer interfaces, while providing low-cost, efficient, modular networking solutions. We will describe the overall architectural approach to extending the concept of the Internet to space and highlight the important technological challenges and initiatives that will make it a reality.

Bhasin, K.↗
NASA NTRSDate not supplied

The Wizard Staff: A Mobile Tool Supporting Human Exploration on The Lunar Surface

The Wizard Staff is a rechargeable, battery powered mobile tool with multiple uses for lunar surface exploration. It supports human activity as a surface survey tool, provides external illumination to enhance safety, delivers networking, communications, and navigation features to remote sites, and assists crew rescue with an emergency beacon and rigid splint structure. As a survey tool, it assists crewed geologic field site exploration with external lights, cameras, and LiDAR to illuminate, map, and record the sample collection process. As a relay station, it provides a surface intranet communications and navigation node for extended exploration far from the lander or habitation module. A separately developed Search-and-Rescue (SAR) handheld device can broadcast a signal to the Gandalf Staff containing crew position and biometric data. The staff then formats the message and sends it orbiting satellite(s) for emergency response via the LunaNET on a dedicated frequency similar to terrestrial applications using an Emergency Position-Indicating Radiobeacon (EPIRB). The staff is designed with an upper and lower segment. Components in the upper segment are the LiDAR, external lighting arrays, cameras, communications equipment, intelligence devices, and user interface for crew operations. The lower segment is a set of FeLiPO4 battery cells packed into the 2” diameter carbon fiber tube. When the battery pack is discharged, a spring connector (designed for the dusty lunar environment) easily disconnects the two segments for replacement with another fully charged battery pack. The lower segment can be used for Incapacitated Crew Rescue (ICR) as a rigid splint. As a stand-alone science platform, the Wizard Staff provides infrastructure for instruments and sensors to record the lunar environment over long periods of time. After a crew installs the components on the lunar surface, the platform delivers data to the lunar lander or base station for analysis. The stand-alone mode requires an auxiliary power source (e.g. solar array) and energy storage system (e.g. battery), so it could also be used as an electrical recharging station. A working prototype of Wizard Staff has been developed with collaboration between NASA (JSC, MSFC, and GSFC), Texas Space Technology Applications and Research (T STAR), and Texas A&M University (TAMU) using $300k of innovation funding in FY’21 and FY’22. The functional staff weights 36# on Earth (6# on the Moon), stands 2.1m tall and delivers external lighting with an array of 40 LED bulbs generating 1460 Lux at 2m range (near field), or 2 Lux at 50m (far field).

Gandalf Staff↗
NASA NTRS2013

Space Station Integrated Kinetic Launcher for Orbital Payload Systems (SSIKLOPS) - Cyclops

Access to space for satellites in the 50-100 kg class is a challenge for the small satellite community. Rideshare opportunities are limited and costly, and the small sat must adhere to the primary payloads schedule and launch needs. Launching as an auxiliary payload on an Expendable Launch Vehicle presents many technical, environmental, and logistical challenges to the small satellite community. To assist the community in mitigating these challenges and in order to provide the community with greater access to space for 50-100 kg satellites, the NASA International Space Station (ISS) and Engineering communities in collaboration with the Department of Defense (DOD) Space Test Program (STP) is developing a dedicated 50-100 kg class ISS small satellite deployment system. The system, known as Cyclops, will utilize NASA's ISS resupply vehicles to launch small sats to the ISS in a controlled pressurized environment in soft stow bags. The satellites will then be processed through the ISS pressurized environment by the astronaut crew allowing satellite system diagnostics prior to orbit insertion. Orbit insertion is achieved through use of the Japan Aerospace Exploration Agency's Experiment Module Robotic Airlock (JEM Airlock) and one of the ISS Robotic Arms. Cyclops' initial satellite deployment demonstration of DOD STP's SpinSat and UT/TAMU's Lonestar satellites will be toward the end of 2013 or beginning of 2014. Cyclops will be housed on-board the ISS and used throughout its lifetime. The anatomy of Cyclops, its concept of operations for satellite deployment, and its satellite interfaces and requirements will be addressed further in this paper.

Smith, James P.↗
NASA NTRSDate not supplied

Developing Concepts of Operations Using Multi-Step Tool Techniques With Large Language Models

The National Aeronautics and Space Administration (NASA) Air Mobility Pathfinders (AMP) project is developing and evaluating concepts of operations (ConOps) for safe, secure, and scalable Urban Air Mobility (UAM) operations. The AMP project’s Operational Concepts, Architecture, and Requirements Integration (OCARI) Team is using a Model Based System Engineering (MBSE) approach for integration, interoperability, and traceability of Advanced Air Mobility (AAM) ecosystems centered around urban air taxi services. The team’s goal is to define structures and behaviors needed for system feasibility, readiness, and interoperability, establish a UAM knowledge base, and trace and validate assumptions and requirements relevant to AAM. NASA Langley Research Center (LaRC) is spearheading an innovative digital engineering approach to integrate, communicate, and facilitate the research of multi-modal transportation systems. The Knowledge-based Digital Platform (KbDP) is a concept being developed that ties the workflows of Project Managers (PM), Principal Investigators (PI), and System Engineers together across organizational boundaries. It does so through the management of an information database defined by mathematical, data science, and system engineering principles. Machine Learning (ML) algorithms play a key role in this concept by extracting meaningful knowledge from relational and graph databases, document repositories, and system artifacts, which the human user leverages to greatly improve the efficiency and effectiveness of their research. Recent advancements in the field of Large Language Models (LLMs), specifically models trained for tool use, such as Command-R , now allow for the reliable implementation of single-step and multi-step tool-centric systems. These techniques provide the LLM with a set of tools, in our case Python functions, that can be called on to answer a much wider range of questions compared to LLMs implemented using a traditional single-source or Retrieval Augmented Generation (RAG) approach. Through this method, the LLM can pull information from multiple data sources, such as relational or graph databases, document repositories, application programming interfaces (APIs), and SysML artifacts depending on the user’s question. The LLM can also output the information in a variety of different formats, using output generation tools, such as CSV, UML, or SysML artifacts. Additionally, tools can be assigned roles and can work together to provide answers to queries in an “agent” like approach, similar to that implemented by Microsoft’s AutoGen framework where different agents can converse with each other to accomplish tasks. Previously, our team developed a chatbot system with “agent like” functionality in the form of different “modes” the user could select from a user interface (UI), this architecture can be seen on the left in figure 1. Three different modes were implemented, the first mode allowed the LLM to utilize the structures and algorithms within a graph database to trace UAM requirements. The second mode gave the LLM access to a vector search capable of providing relevant information from thousands of document pages related to UAM ConOps and requirements. The third mode served as a general assistant where users could enter open-ended questions and custom prompts to utilize the LLM for different use-cases. This system improved the process surrounding generating and analyzing information related to UAM requirements, however, the implementation provided a clunky user experience. Users were required to know what mode to select within the UI in advance before entering their question to the selected tool. Moreover, the different tools were isolated from each other, they lacked bidirectional links that would allow for tools to collaborate to generate better responses. Our team is working on a new architecture, seen on the right in the below figure, with the goal to address many of the UX shortcomings of our original system while improving the accuracy and depth of responses from the LLM. This new system will automatically select the appropriate tool to use based off the user’s question. Each tool will be capable of calling on any of the other tools available to the LLM, resulting in a collaborative pipeline where tools can pass data between other tools until enough data is received to generate an answer to the user’s question. Using a locally deployed, open-source, LLM, the NASA OCARI team, in collaboration with Collins Aerospace, will implement a prototype application that will bridge knowledge across multiple sources to assist System Engineers (SEs) with requirements discovery and tracing, research question and use case identification, and assumption validation. Such a system will also allow SEs to more easily, and intuitively, explore the AAM ecosystem, ultimately improving the efficiency and effectiveness of the SE's research and decision-making processes surrounding ConOps development and validation. In this session, our team will provide a video demonstration of our new prototype architecture in action. We will also present an overview of our prototype system architecture and talk about its advantages over traditional LLM deployments along with how those advantages can provide additional value to the field of System Engineering.

systems engineering↗
NASA NTRS2000

A Collaborative Analysis Tool for Integrated Hypersonic Aerodynamics, Thermal Protection Systems, and RBCC Engine Performance for Single Stage to Orbit Vehicles

Presented is a computer-based tool that connects several disciplines that are needed in the complex and integrated design of high performance reusable single stage to orbit (SSTO) vehicles. Every system is linked to every other system, as is the case of SSTO vehicles with air breathing propulsion, which is currently being studied by NASA. An RBCC propulsion system integrates airbreathing and rocket propulsion into a single engine assembly enclosed within a cowl or duct. A typical RBCC propulsion system operates as a ducted rocket up to approximately Mach 3. Then there is a transition to a ramjet mode for supersonic-to-hypersonic acceleration. Around Mach 8 the engine transitions to a scramjet mode. During the ramjet and scramjet modes, the integral rockets operate as fuel injectors. Around Mach 10-12 (the actual value depends on vehicle and mission requirements), the inlet is physically closed and the engine transitions to an integral rocket mode for orbit insertion. A common feature of RBCC propelled vehicles is the high degree of integration between the propulsion system and airframe. At high speeds the vehicle forebody is fundamentally part of the engine inlet, providing a compression surface for air flowing into the engine. The compressed air is mixed with fuel and burned. The combusted mixture must be expanded to an area larger than the incoming stream to provide thrust. Since a conventional nozzle would be too large, the entire lower after body of the vehicle is used as an expansion surface. Because of the high external temperatures seen during atmospheric flight, the design of an airbreathing SSTO vehicle requires delicate tradeoffs between engine design, vehicle shape, and thermal protection system (TPS) sizing in order to produce an optimum system in terms of weight (and cost) and maximum performance. To adequately determine the performance of the engine/vehicle, the Hypersonic Flight Inlet Model (HYFIM) module was designed to interface with the RBCC engine model. HYFIM performs the aerodynamic analysis of forebodies and inlet characteristics of RBCC powered SSTO launch vehicles. HYFIM is applicable to the analysis of the ramjet/scramjet engine operations modes (Mach 3-12), and provides estimates of parameters such as air capture area, shock-on-lip Mach number, design Mach number, compression ratio, etc., based on a basic geometry routine for modeling axisymmetric cones, 2-D wedge geometries. HYFIM also estimates the variation of shock layer properties normal to the forebody surface. The thermal protection system (TPS) is directly linked to determination of the vehicle moldline and the shaping of the trajectory. Thermal protection systems to maintain the structural integrity of the vehicle must be able to mitigate the heat transfer to the structure and be lightweight. Herein lies the interdependency, in that as the vehicle's speed increases, the TPS requirements are increased. And as TPS masses increase the effect on the propulsion system and all other systems is compounded. The need to analyze vehicle forebody and engine inlet is critical to be able to design the RBCC vehicle. To adequately determine insulation masses for an RBCC vehicle, the hypersonic aerodynamic environment and aeroheating loads must be calculated and the TPS thicknesses must be calculated for the entire vehicle. To accomplish this an ascent or reentry trajectory is obtained using the computer code Program to Optimize Simulated Trajectories (POST). The trajectory is then used to calculate the convective heat rates on several locations on the vehicles using the Miniature Version of the JA70 Aerodynamic Heating Computer Program (MINIVER). Once the heat rates are defined for each body point on the vehicle, then insulation thicknesses that are required to maintain the vehicle within structural limits are calculated using Systems Improved Numerical Differencing Analyzer (SINDA) models. If the TPS masses are too heavy for the performance of the vehicle the process may be repeated altering the trajectory or some other input to reduce the TPS mass. E-PSURBCC is an "engine performance" model and requires the specification of inlet air static temperature and pressure as well as Mach number (which it pulls from the HYFIM and POST trajectory files), and calculates the corresponding stagnation properties. The engine air flow path geometry includes inlet, a constant area section where the rocket is positioned, a subsonic diffuser, a constant area afterburner, and either a converging nozzle or a converging-diverging nozzle. The current capabilities of E-PSURBCC ejector and ramjet mode treatment indicated that various complex flow phenomena including multiple choking and internal shocks can occur for combinations of geometry/flow conditions. For a given input deck defining geometry/flow conditions, the program first goes through a series of checks to establish whether the input parameters are sound in terms of a solution path. If the vehicle/engine performance fails mission goals, the engineer is able to collaboratively alter the vehicle moldline to change aerodynamics, or trajectory, or some other input to achieve orbit. The problem described is an example of the need for collaborative design and analysis. RECIPE is a cross-platform application capable of hosting a number of engineers and designers across the Internet for distributed and collaborative engineering environments. Such integrated system design environments allow for collaborative team design analysis for performing individual or reduced team studies. To facilitate the larger number of potential runs that may need to be made, RECIPE connects the computer codes that calculate the trajectory data, aerodynamic data based on vehicle geometry, heat rate data, TPS masses, and vehicle and engine performance, so that the output from each tool is easily transferred to the model input files that need it.

Stanley, Thomas Troy↗
NASA NTRS2017

Creative Analytics of Mission Ops Event Messages

Historically, tremendous effort has been put into processing and displaying mission health and safety telemetry data; and relatively little attention has been paid to extracting information from missions time-tagged event log messages. Todays missions may log tens of thousands of messages per day and the numbers are expected to dramatically increase as satellite fleets and constellations are launched, as security monitoring continues to evolve, and as the overall complexity of ground system operations increases. The logs may contain information about orbital events, scheduled and actual observations, device status and anomalies, when operators were logged on, when commands were resent, when there were data drop outs or system failures, and much much more. When dealing with distributed space missions or operational fleets, it becomes even more important to systematically analyze this data. Several advanced information systems technologies make it appropriate to now develop analytic capabilities which can increase mission situational awareness, reduce mission risk, enable better event-driven automation and cross-mission collaborations, and lead to improved operations strategies: Industry Standard for Log Messages. The Object Management Group (OMG) Space Domain Task Force (SDTF) standards organization is in the process of creating a formal standard for industry for event log messages. The format is based on work at NASA GSFC. Open System Architectures. The DoD, NASA, and others are moving towards common open system architectures for mission ground data systems based on work at NASA GSFC with the full support of the commercial product industry and major integration contractors. Text Analytics. A specific area of data analytics which applies statistical, linguistic, and structural techniques to extract and classify information from textual sources. This presentation describes work now underway at NASA to increase situational awareness through the collection of non-telemetry mission operations information into a common log format and then providing display and analytics tools to provide in-depth assessment of the log contents. The work includes: Common interface formats for acquiring time-tagged text messages Conversion of common files for schedules, orbital events, and stored commands to the common log format Innovative displays to depict thousands of messages on a single display Structured English text queries against the log message data store, extensible to a more mature natural language query capability Goal of speech-to-text and text-to-speech additions to create a personal mission operations assistant to aid on-console operations. A wide variety of planned uses identified by the mission operations teams will be discussed.

events↗
NASA NTRS2024

Exploring Earth's Interface with Space: The Scientific Case for a Satellite Mission to the Lower Thermosphere-Ionosphere Transition Region

The ESA-NASA Lower Thermosphere-Ionosphere Science (ENLoTIS) Working Group was formed in May 2022 to cooperatively explore future lower thermosphere-ionosphere (LTI) satellite mission concepts, targeting very low altitudes (100-200 km) with in situ sampling of relevant geophysical parameters associated with the neutral atmosphere, the ionosphere’s plasma, electromagnetic fields, and energetic particles, which, together with modeling, would enable significant advancements in the understanding of neutral-ion interactions and other related science and space weather topics in this critical region of Geospace. The LTI region has been identified as one of considerable interest to both NASA and ESA. Most recently, the Daedalus mission study was carried out under the remit of ESA’s Earth Observation Programmes (EOP) Directorate competitive Earth Explorer 10 pre-feasibility (Phase 0) activities. Furthermore, many NASA studies have also focused on the LTI region, including both directed missions with dipping spacecraft, such as the initial TIMED dual-satellites and the GEC constellation, as well as numerous highly-rated Explorer proposals targeting the LTI. Although the Daedalus mission was not selected, the ESA Advisory Committee on Earth Observation (ACEO) ranked it highly on scientific grounds and encouraged further study activities to mature the concept, exploring potential international collaboration. Subsequent bilateral discussions with NASA’s Science Mission Directorate (SMD) noted that such a concept was in alignment with the 2020 SMD science plan – Science 2020-2024: A Vision for Scientific Excellence – along with other complimentary activities within the NASA Heliophysics Division. Building on NASA’s and ESA’s long history of very successful collaborations, this mutual interest in LTI science led to the establishment of a new inter-agency and cross-discipline science connection, linking the ESA EOP Climate Action, Sustainability and Science Department and the NASA Heliophysics Division. Initial exploratory discussions led to the formation of the ENLoTIS Working Group, which was directed to explore the science case behind a potential joint LTI mission. Members of the ENLoTIS Working Group are listed below, consisting of 7 scientists from ESA Member and Cooperating States and 7 scientists from the United States. The working group held 3 “in person” meetings over the course of 18 months, interspersed with regular virtual meetings on a more frequent basis. This report constitutes their chief findings and recommendations.

thermosphere↗
NASA NTRS1990

An expert system to advise astronauts during experiments: The protocol manager module

Perhaps the scarcest resource for manned flight experiments - on Spacelab or on the Space Station Freedom - will continue to be crew time. To maximize the efficiency of the crew and to make use of their abilities to work as scientist collaborators as well as equipment operators, normally requires more training in a wide variety of disciplines than is practical. The successful application of on-board expert systems, as envisioned by the Principal Investigator in a Box program, should alleviate the training bottleneck and provide the astronaut with the guidance and coaching needed to permit him or her to operate an experiment according to the desires and knowledge of the PI, despite changes in conditions. The Protocol Manager module of the system is discussed. The Protocol Manager receives experiment data that has been summarized and categorized by the other modules. The Protocol Manager acts on the data in real-time, by employing expert system techniques. Its recommendations are based on heuristics provided by the Principal Investigator in charge of the experiment. This prototype was developed on a Macintosh II by employing CLIPS, a forward-chaining rule-based system, and HyperCard as an object-oriented user interface builder.

Haymann-Haber, Guido↗
NASA NTRS2014

Large Plant Growth Chambers: Flying Soon on a Space Station near You!

The International Space Station (ISS) now has platforms for conducting research on horticultural plant species, and those capabilities continue to grow. The Veggie vegetable production system will be deployed to the ISS in Spring of 2014 to act as an applied research platform with goals of studying food production in space, providing the crew with a source of fresh food, allowing behavioral health and plant microbiology experimentation, and being a source of recreation and enjoyment for the crew. Veggie was conceived, designed, and constructed by Orbital Technologies Corporation (ORBITEC, Madison, WI). Veggie is the largest plant growth chamber that NASA has flown to date, and is capable of growing a wide array of horticultural crops. It was designed for low energy usage, low launch mass and stowage volume, and minimal crew time requirements. The Veggie flight hardware consists of a light cap containing red (630 nanometers), blue, (455 nanometers) and green (530 nanometers) light emitting diodes. Interfacing with the light cap is an extendable bellows baseplate secured to the light cap via magnetic closures and stabilized with extensible flexible arms. The baseplate contains vents allowing air from the ISS cabin to be pulled through the plant growth area by a fan in the light cap. The baseplate holds a Veggie root mat reservoir that will supply water to plant pillows attached via elastic cords. Plant pillows are packages of growth media and seeds that will be sent to ISS dry and installed and hydrated on orbit. Pillows can be constructed in various sizes for different plant types. Watering will be via passive wicking from the root mat to the pillows. Science procedures will include photography or videography, plant thinning, pollination, harvesting, microbial sampling, water sampling, etcetera. Veggie is one of the ISS flight options currently available for research investigations on plants. The Plant Habitat (PH) is being designed and constructed through a NASA-ORBITEC collaboration, and is scheduled to fly on ISS around 2016. This large plant chamber will control light quality, level, and timing, temperature, CO2, relative humidity, and irrigation, while scrubbing ethylene. Additional monitoring capabilities include leaf temperature sensing and root zone moisture and oxygen sensing. The PH light cap will have red (630 nanometers), blue (450 nanometers), green (525 nanometers), far red (730 nanometers) and broad spectrum white light emitting diodes. There will be several internal cameras to monitor and record plant growth and operations.

Space Biology↗
NASA NTRS2011

Airborne Observation of the Hayabusa Sample Return Capsule Re-Entry

The Japan Aerospace Exploration Agency (JAXA) recently completed their Hayabusa asteroid exploration mission. Launched in 2003, Hayabusa made contact with, and retrieved a sample from, the near-Earth asteroid Itokawa in 2005. The sample return capsule (SRC) re-entered over the Woomera Test Range (WTR) in southern Australia on June 13, 2010, at approximately 11:21 pm local time (09:51 UTC). The SRC re-entry velocity was 12.2 km/s, making it the second-fastest Earth return velocity behind NASA s Stardust sample return capsule re-entry in 2006. From a space technology development perspective, Hayabusa s re-entry functioned as a rare flight experiment of an entry vehicle and its thermal protection system. In collaboration with the SETI Institute, NASA deployed its DC-8 airborne laboratory and a team of international researchers to Australia to observe the re-entry of the SRC. The use of an airborne platform enables observation above most clouds and weather and greatly diminishes atmospheric absorption of the optical signals. The DC-8 s flight path was engineered and flown to provide a view of the spacecraft that bracketed the heat pulse to the capsule. A suite of imaging instruments on board the DC-8 successfully recorded the luminous portion of the re-entry event. For approximately 70 seconds, the spectroscopic and radiometric instruments acquired images and spectra of the capsule, its wake, and destructive re-entry of the spacecraft bus. Figure 1 shows a perspective view of the WTR, the SRC re-entry trajectory, and the flight path of the DC-8. The SRC was jettisoned from the spacecraft bus approximately 3 hours prior to entry interface. Due to thruster failures on the spacecraft, it could not be diverted from the entry path and followed the trajectory of the SRC, where it burned up in the atmosphere between approximately 100 and 50 km altitude. Fortuitously, the separation distance between the spacecraft and SRC was sufficient to clearly resolve the SRC from the debris field of the burning spacecraft. Figure 2 shows a frame from a high-definition television camera on board the aircraft and denotes the locations of the SRC and spacecraft bus debris.

Grinstead, Jay H.↗
NASA NTRSDate not supplied

A Multi-Year Effort to Forward the Validation of Solar Energetic Particle Prediction Models

To enable a consistent and quantitative understanding of solar energetic particle (SEP) model performance, a generalized, automated validation infrastructure, called SPHINX, is being developed by the NASA Space Radiation Analysis Group (SRAG) in close collaboration with the NASA Community Coordinated Modeling Center (CCMC), NASA Moon to Mars Space Weather Analysis Office (M2M), NOAA Space Weather Prediction Center (SWPC), and the Royal Belgian Institute for Space Aeronomy (BIRA-IASB). SPHINX is being developed to evaluate the SEP Scoreboards (https://ccmc.gsfc.nasa.gov/scoreboards/sep/), which are being used by SRAG to support space radiation operations for Mission Control. SPHINX is also being developed through a series of community challenges, which have defined a list of challenge events and a prescribed set of rules of participation. The participation of the research community has enabled the generalization of the infrastructure to validate all the types of outputs being produced by SEP models and fully exercised the framework. The most recent challenge includes 30 SEP events and 33 non-event (quiet) periods and was supported by two dedicated SEPVAL working meetings, one in the US and one in Europe (https://ccmc.gsfc.nasa.gov/community-workshops/ccmc-sepval-2023/). Here, we describe SPHINX and its interactive user interface, SPHINX-VIVID, which will eventually be made available for public use. We present selected results, outcomes, and lessons learned from the SEPVAL working meetings and validation results of the SEP Scoreboards from 2019 to present. These efforts aim to define a set of community standards for SEP model validation and describe the current state-of-the-art of SEP model performance.

Kathryn Whitman↗
NASA NTRS2005

A Reliable Service-Oriented Architecture for NASA's Mars Exploration Rover Mission

The Collaborative Information Portal (CIP) was enterprise software developed jointly by the NASA Ames Research Center and the Jet Propulsion Laboratory (JPL) for NASA's highly successful Mars Exploration Rover (MER) mission. Both MER and CIP have performed far beyond their original expectations. Mission managers and engineers ran CIP inside the mission control room at JPL, and the scientists ran CIP in their laboratories, homes, and offices. All the users connected securely over the Internet. Since the mission ran on Mars time, CIP displayed the current time in various Mars and Earth time zones, and it presented staffing and event schedules with Martian time scales. Users could send and receive broadcast messages, and they could view and download data and image files generated by the rovers' instruments. CIP had a three-tiered, service-oriented architecture (SOA) based on industry standards, including J2EE and web services, and it integrated commercial off-the-shelf software. A user's interactions with the graphical interface of the CIP client application generated web services requests to the CIP middleware. The middleware accessed the back-end data repositories if necessary and returned results for these requests. The client application could make multiple service requests for a single user action and then present a composition of the results. This happened transparently, and many users did not even realize that they were connecting to a server. CIP performed well and was extremely reliable; it attained better than 99% uptime during the course of the mission. In this paper, we present overviews of the MER mission and of CIP. We show how CIP helped to fulfill some of the mission needs and how people used it. We discuss the criteria for choosing its architecture, and we describe how the developers made the software so reliable. CIP's reliability did not come about by chance, but was the result of several key design decisions. We conclude with some of the important lessons we learned form developing, deploying, and supporting the software.

Mak, Ronald↗
NASA NTRS2012

Retrieving Atmospheric Temperature and Moisture Profiles from NPP CRIS/ATMS Sensors Using Crimss EDR Algorithm

The Joint Polar Satellite System (JPSS) is a U.S. National Oceanic and Atmospheric Administration (NOAA) mission in collaboration with the U.S. National Aeronautical Space Administration (NASA) and international partners. The NPP Cross-track Infrared Microwave Sounding Suite (CrIMSS) consists of the infrared (IR) Crosstrack Infrared Sounder (CrIS) and the microwave (MW) Advanced Technology Microwave Sounder (ATMS). The CrIS instrument is hyperspectral interferometer, which measures high spectral and spatial resolution upwelling infrared radiances. The ATMS is a 22-channel radiometer similar to Advanced Microwave Sounding Units (AMSU) A and B. It measures top of atmosphere MW upwelling radiation and provides capability of sounding below clouds. The CrIMSS Environmental Data Record (EDR) algorithm provides three EDRs, namely the atmospheric vertical temperature, moisture and pressure profiles (AVTP, AVMP and AVPP, respectively), with the lower tropospheric AVTP and the AVMP being JPSS Key Performance Parameters (KPPs). The operational CrIMSS EDR an algorithm was originally designed to run on large IBM computers with dedicated data management subsystem (DMS). We have ported the operational code to simple Linux systems by replacing DMS with appropriate interfaces. We also changed the interface of the operational code so that we can read data from both the CrIMSS science code and the operational code and be able to compare lookup tables, parameter files, and output results. The detail of the CrIMSS EDR algorithm is described in reference [1]. We will present results of testing the CrIMSS EDR operational algorithm using proxy data generated from the Infrared Atmospheric Sounding Interferometer (IASI) satellite data and from the NPP CrIS/ATMS data.

Liu, X.↗
DOE OSTI2024

Generating An Advanced Cross-section Library For HTGR Pebble Bed Depletion Calculations Using Reduced-Order Model Generation Techniques

For code development, Advanced Reactor Technologies - Gas Cooled Reactors Program (ART-GCR) rely on a collaboration with the Nuclear Energy Advanced Modeling and Simulation (NEAMS) program, but the cross sections generation and the methodology definition is part of this program area goals. Based on previous studies in FY23, the size of microscopic cross section libraries increases rapidly with the number of tabulations, requiring significant amount of memory and drastically slowing down the Griffin calculations when evaluating cross sections via the multivariate linear interpolation approach. Rising to these challenges, this work investigates constructing Reduced-order Models (ROMs) for the multi-group microscopic cross sections to accelerate the cross section evaluation in Griffin. A database of multigroup cross sections is first collected considering all possible parameters that a designer could change for optimization. Down-selection of the ROM techniques afterward shows Deep Neural Network (DNN) as the best candidate when jointly consider memory efficiency, predictive accuracy, computational cost, scalability, flexibility and ease of implementation of the algorithms in comparison to the multidimensional interpolation. This work develops a specific interface that enables the cross section predictions using pre-trained DNN models into Griffin leveraging the existing ROM capabilities. DNNs have been trained for all isotopes for use in Griffin. Preliminary Griffin testing shows that DNNs exhibit exceptional predictive accuracy and the use of DNNs provides orders of magnitude improvement in memory efficiency compared to conventional interpolation techniques. With such ROM techniques, it holds great promise to further increase the fidelity of the Pebble Bed Reactor (PBR) simulation by increasing the number of tabulations/state variables during cross section evaluation, while maintaining the computational cost affordable in Griffin.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRS2002

Repair and Utilization of the Kratos XSAM 800 X-Ray Photoelectron Spectrometer (XPS)

The objectives for this summer faculty fellowship were first to repair the Kratos XSAM 800 X-ray Photoelectron Spectrometer (XPS) and then to utilize the instrument to participate in ongoing research projects at KSC and in the researcher's own laboratory at UCF. The first 6 weeks were used in repairing the instrument. Working both alone and with the Kratos service engineer, a number of hardware problems, largely associated with the sample stage control system, were corrected. Defective parts were identified and fixed in the computer driver boards, the stage power supply, and the driver interface. The power supply was completely replaced. After four weeks of work, the instrument was functional. This occurred on a Wednesday. The following Friday the instrument had to be completely shut down because the power to the O & C Building was to be turned off. The instrument was properly secured. On Monday, the instrument was powered up and the original problems returned. After another 2 weeks of work, a software problem was identified. This problem caused the computer to use a defective port for the sample stage control. It was circumvented by rewriting the startup routine. The final 3 weeks of the fellowship were spent using the XPS to analyze samples being studied in the Langley materials project (Martha Williams) and a catalyst project (Dr. Orlando Melendez). During this time, several sample analysis requests from other groups at KSC also came in and those samples were run as well. The summer faculty fellowship also allowed many contacts to be made. After meeting with the sensors group, two projects were identified for collaboration and white papers are being prepared. One project aims to develop small, very sensitive hydrogen detectors and the other to develop a broad area, easily monitored, zero power consumption hydrogen detector. In addition to the work mentioned above, the XPS was utilized in a study underway in Dr. Hampton's laboratory at UCF.

Hampton, Michael D.↗
NASA NTRS1993

Visualization techniques to aid in the analysis of multi-spectral astrophysical data sets

The goal of this project was to support the scientific analysis of multi-spectral astrophysical data by means of scientific visualization. Scientific visualization offers its greatest value if it is not used as a method separate or alternative to other data analysis methods but rather in addition to these methods. Together with quantitative analysis of data, such as offered by statistical analysis, image or signal processing, visualization attempts to explore all information inherent in astrophysical data in the most effective way. Data visualization is one aspect of data analysis. Our taxonomy as developed in Section 2 includes identification and access to existing information, preprocessing and quantitative analysis of data, visual representation and the user interface as major components to the software environment of astrophysical data analysis. In pursuing our goal to provide methods and tools for scientific visualization of multi-spectral astrophysical data, we therefore looked at scientific data analysis as one whole process, adding visualization tools to an already existing environment and integrating the various components that define a scientific data analysis environment. As long as the software development process of each component is separate from all other components, users of data analysis software are constantly interrupted in their scientific work in order to convert from one data format to another, or to move from one storage medium to another, or to switch from one user interface to another. We also took an in-depth look at scientific visualization and its underlying concepts, current visualization systems, their contributions, and their shortcomings. The role of data visualization is to stimulate mental processes different from quantitative data analysis, such as the perception of spatial relationships or the discovery of patterns or anomalies while browsing through large data sets. Visualization often leads to an intuitive understanding of the meaning of data values and their relationships by sacrificing accuracy in interpreting the data values. In order to be accurate in the interpretation, data values need to be measured, computed on, and compared to theoretical or empirical models (quantitative analysis). If visualization software hampers quantitative analysis (which happens with some commercial visualization products), its use is greatly diminished for astrophysical data analysis. The software system STAR (Scientific Toolkit for Astrophysical Research) was developed as a prototype during the course of the project to better understand the pragmatic concerns raised in the project. STAR led to a better understanding on the importance of collaboration between astrophysicists and computer scientists.

Brugel, Edward W.↗
NASA NTRS1993

Visualization techniques to aid in the analysis of multispectral astrophysical data sets

The goal of this project was to support the scientific analysis of multi-spectral astrophysical data by means of scientific visualization. Scientific visualization offers its greatest value if it is not used as a method separate or alternative to other data analysis methods but rather in addition to these methods. Together with quantitative analysis of data, such as offered by statistical analysis, image or signal processing, visualization attempts to explore all information inherent in astrophysical data in the most effective way. Data visualization is one aspect of data analysis. Our taxonomy as developed in Section 2 includes identification and access to existing information, preprocessing and quantitative analysis of data, visual representation and the user interface as major components to the software environment of astrophysical data analysis. In pursuing our goal to provide methods and tools for scientific visualization of multi-spectral astrophysical data, we therefore looked at scientific data analysis as one whole process, adding visualization tools to an already existing environment and integrating the various components that define a scientific data analysis environment. As long as the software development process of each component is separate from all other components, users of data analysis software are constantly interrupted in their scientific work in order to convert from one data format to another, or to move from one storage medium to another, or to switch from one user interface to another. We also took an in-depth look at scientific visualization and its underlying concepts, current visualization systems, their contributions and their shortcomings. The role of data visualization is to stimulate mental processes different from quantitative data analysis, such as the perception of spatial relationships or the discovery of patterns or anomalies while browsing through large data sets. Visualization often leads to an intuitive understanding of the meaning of data values and their relationships by sacrificing accuracy in interpreting the data values. In order to be accurate in the interpretation, data values need to be measured, computed on, and compared to theoretical or empirical models (quantitative analysis). If visualization software hampers quantitative analysis (which happens with some commercial visualization products), its use is greatly diminished for astrophysical data analysis. The software system STAR (Scientific Toolkit for Astrophysical Research) was developed as a prototype during the course of the project to better understand the pragmatic concerns raised in the project. STAR led to a better understanding on the importance of collaboration between astrophysicists and computer scientists. Twenty-one examples of the use of visualization for astrophysical data are included with this report. Sixteen publications related to efforts performed during or initiated through work on this project are listed at the end of this report.

Brugel, E. W.↗
NASA NTRS2012

The Namibia Early Flood Warning System, A CEOS Pilot Project

Over the past year few years, an international collaboration has developed a pilot project under the auspices of Committee on Earth Observation Satellite (CEOS) Disasters team. The overall team consists of civilian satellite agencies. For this pilot effort, the development team consists of NASA, Canadian Space Agency, Univ. of Maryland, Univ. of Colorado, Univ. of Oklahoma, Ukraine Space Research Institute and Joint Research Center(JRC) for European Commission. This development team collaborates with regional , national and international agencies to deliver end-to-end disaster coverage. In particular, the team in collaborating on this effort with the Namibia Department of Hydrology to begin in Namibia . However, the ultimate goal is to expand the functionality to provide early warning over the South Africa region. The initial collaboration was initiated by United Nations Office of Outer Space Affairs and CEOS Working Group for Information Systems and Services (WGISS). The initial driver was to demonstrate international interoperability using various space agency sensors and models along with regional in-situ ground sensors. In 2010, the team created a preliminary semi-manual system to demonstrate moving and combining key data streams and delivering the data to the Namibia Department of Hydrology during their flood season which typically is January through April. In this pilot, a variety of moderate resolution and high resolution satellite flood imagery was rapidly delivered and used in conjunction with flood predictive models in Namibia. This was collected in conjunction with ground measurements and was used to examine how to create a customized flood early warning system. During the first year, the team made use of SensorWeb technology to gather various sensor data which was used to monitor flood waves traveling down basins originating in Angola, but eventually flooding villages in Namibia. The team made use of standardized interfaces such as those articulated under the Open Cloud Consortium (OGC) Sensor Web Enablement (SWE) set of web services was good [1][2]. However, it was discovered that in order to make a system like this functional, there were many performance issues. Data sets were large and located in a variety of location behind firewalls and had to be accessed across open networks, so security was an issue. Furthermore, the network access acted as bottleneck to transfer map products to where they are needed. Finally, during disasters, many users and computer processes act in parallel and thus it was very easy to overload the single string of computers stitched together in a virtual system that was initially developed. To address some of these performance issues, the team partnered with the Open Cloud Consortium (OCC) who supplied a Computation Cloud located at the University of Illinois at Chicago and some manpower to administer this Cloud. The Flood SensorWeb [3] system was interfaced to the Cloud to provide a high performance user interface and product development engine. Figure 1 shows the functional diagram of the Flood SensorWeb. Figure 2 shows some of the functionality of the Computation Cloud that was integrated. A significant portion of the original system was ported to the Cloud and during the past year, technical issues were resolved which included web access to the Cloud, security over the open Internet, beginning experiments on how to handle surge capacity by using the virtual machines in the cloud in parallel, using tiling techniques to render large data sets as layers on map, interfaces to allow user to customize the data processing/product chain and other performance enhancing techniques. The conclusion reached from the effort and this presentation is that defining the interoperability standards in a small fraction of the work. For example, once open web service standards were defined, many users could not make use of the standards due to security restrictions. Furthermore, once an interoperable sysm is functional, then a surge of users can render a system unusable, especially in the disaster domain.

Mandl, Daniel↗