SEARCH · Search NASA

Results for “data lifecycle”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 181 records · Page 10

All sources NASA NTRS DOE OSTI

DOE OSTI2024

MLOps for Beam Controls

Machine learning operations (MLOps) is the standardization and streamlining of the ML development lifecycle to address the challenges associated with large-scale machine learning applications. The full MLOps pipeline consists of open-source tools: DataHub, MinIO and MLflow. It is being used for dataset management and model development to handle changing data dependencies, varying business needs, reproducibility, and diverse teams working with differing tools and skills. To demonstrate the completion of an MLOps pipeline for particle accelerator operations, we are deploying a simple script that computes settings for the Booster’s gradient magnet power supply. Once the demonstration is complete, we will develop and deploy ML-based optimization algorithms to improve Booster’s overall efficiency. This MLOps pipeline opens the gate to systematically develop and deploy ML applications for accelerator controls and diagnostics.

43 PARTICLE ACCELERATORS↗

NASA NTRS2011

Guidance, Navigation, and Control Program

The Rendezvous and Proximity Operations Program (RPOP) is real-time guidance, navigation, and control (GN&C) domain piloting-aid software that provides 3D Orbiter graphics and runs on the Space Shuttle's Criticality-3 Payload and General Support Computer (PGSC) in the crew cockpit. This software provides the crew with Situational Awareness during the rendezvous and proximity operations phases of flight. RPOP can be configured from flight to flight, accounting for mission-specific flight scenarios and target vehicles, via initialization load (I-load) data files. The software provides real-time, automated, closed-loop guidance recommendations and the capability to integrate the crew s manual backup techniques. The software can bring all relative navigation sensor data, including the Orbiter's GPC (general purpose computer) data, into one central application to provide comprehensive situational awareness of the rendezvous and proximity operations trajectory. RPOP also can separately maintain trajectory estimates (past, current, and predicted) based on certain data types and co-plot them, in order to show how the various navigation solutions compare. RPOP s best estimate of the relative trajectory is determined by a relative Kalman filter processing data provided by the sensor suite s most accurate sensor, the trajectory control sensor (TCS). Integrated with the Kalman filter is an algorithm that identifies the reflector that the TCS is tracking. Because RPOP runs on PC laptop computers, the development and certification lifecycles are more agile, flexible, and cheaper than those that govern the Orbiter FSW (flight software) that runs in the GPC. New releases of RPOP can be turned around on a 3- to 6-month template, from new Change Request (CR) to certification, depending on the complexity of the changes.

Hinkel, Heather↗

NASA NTRS2003

Software for Remote Monitoring of Space-Station Payloads

Telescience Resource Kit (TReK) is a suite of application programs that enable geographically dispersed users to monitor scientific payloads aboard the International Space Station (ISS). TReK provides local ground support services that can simultaneously receive, process, record, playback, and display data from multiple sources. TReK also provides interfaces to use the remote services provided by the Payload Operations Integration Center which manages all ISS payloads. An application programming interface (API) allows for payload users to gain access to all data processed by TReK and allows payload-specific tools and programs to be built or integrated with TReK. Used in conjunction with other ISS-provided tools, TReK provides the ability to integrate payloads with the operational ground system early in the lifecycle. This reduces the potential for operational problems and provides "cradle-to-grave" end-to-end operations. TReK contains user guides and self-paced tutorials along with training applications to allow the user to become familiar with the system.

Schneider, Michelle↗

NASA NTRS2019

Agile Approach to Assuring the Safety-Critical Embedded Software for NASA's Orion Spacecraft

Human-rated missions like those in NASA's Orion Program continue to grow in complexity. The role of software in achieving ambitious mission objectives has expanded dramatically in the last few decades. Assuring the safety and performance of the embedded flight software is quickly growing beyond the reach of traditional methods and resource levels. The methods used to build these software-dominant systems evolve in an on-going attempt to keep pace with the scope of our ambitions. Agile software development is now commonplace. The long timelines and large batches of work associated with traditional methods are being replaced by rapid delivery of small increments _ as system capabilities are realized in waves. Assurance of these critical software capabilities must therefore conquer an ever-expanding frontier of challenges, and do so with an approach matched to the evolving development methods. This paper recounts the journey of the Orion Independent Verification and Validation (IV&V) team as we addressed this dynamic environment. Widening our aperture to encompass a dramatically larger mission scope, while adjusting our cadence to synchronize with the rapid pace of agile software development, a new approach to IV&V is emerging. This approach is characterized by a sharper focus on mission capabilities, matched with a method to dynamically _follow the risk' as the IV&V team delivers more compelling assurance data in waves. Traditional methods prevalent in IV&V tend to scope the work using artifacts of the development process as they evolve from preliminary to final versions, and the pace of delivery was synchronized with the development timelines prevalent in the waterfall lifecycle. That more static approach is out of phase with the demands of the new environment. Scoping work according to the critical capabilities of the system (rather than artifacts of development) and synchronizing with the rapid pace of agile development, we are moving toward more effective parity with the demands of the environment. We explain the concrete steps we took, the principles that motivated our choices, and the results we have achieved to date.

Capability based assurance↗

DOE OSTI2024

Characterizing Wet Season Precipitation in the Central Amazon Using a Mesoscale Convective System Tracking Algorithm

To comprehensively characterize convective precipitation in the central Amazon region, we utilize the Python FLEXible object TRacKeR (PyFLEXTRKR) to track mesoscale convective systems (MCSs) observed through satellite measurements and simulated by the Weather Research and Forecasting model at a convection-permitting resolution. This study spans a 2-month period during the wet seasons of 2014 and 2015. We observe a strong correlation between the MCS track density and accumulated precipitation in the Amazon basin. Key factors contributing to precipitation, such as MCS properties (number, size, rainfall intensity, and movement), are thoroughly examined. Our analysis reveals that while the overall model produces fewer MCSs with smaller mean sizes compared to observations, it tends to overpredict total precipitation due to excessive rainfall intensity for heavy rainfall events (≥10 mm hr –1 ). These biases in simulated MCS properties could vary with the constraints on the convective background environment. Moreover, while the wet bias from heavy (convective) rainfall outweighs the dry bias in light (stratiform) rainfall, the latter can be crucial, particularly when MCS cloud cover is significantly underestimated. A case study for 1 April 2014 highlights the influence of environmental conditions on the MCS lifecycle and identifies an unrealistic model representation in both stratiform and convective precipitation features.

54 ENVIRONMENTAL SCIENCES↗

NASA NTRS2007

Observations on Cost Modeling and Performance Measurement of Long Term Archives

This paper describes a prototype suite of Excel-based tools that could be used for estimating lifecycle costs for newly planned or modified long-term archival facilities. These tools may also prove valuable for monitoring the long-term performance of such facilities once operational. Cost estimation is by analogy, using statistical curve-fitting techniques across a database of comparable data activities. The database currently includes 29 operational data centers ranging from small (2 FTEs) to large (66 FTEs), and is readily expandable to include additional activities specifically involving data preservation and added value. Each comparable data center is described in terms of its staffing, throughput workload, archival and distribution requirements, levels of user service, overall complexity, degree of automation, and other data, comprising 94 distinct descriptors in all. The descriptors were developed by normalizing heterogeneous data from the various centers and mapping them into an Excel framework consistent with the OAIS reference model. A user-friendly tool is provided for generating input to and updating the comparables database. This tool can also be used to benchmark the performance (in terms of cost versus throughput) of an operational data center, and to update the staffing, cost and workload data on a periodic basis. The comparables database could thus provide a history of staffing and throughput over time, as a means of performance monitoring and providing feedback for continuous improvement. Ancillary tools are also provided for performing "what-if' cost exercises for planning purposes, and for graphical display of data and results. We provide a high-level description of the tools; present our experiences and observations on gathering the information and maintaining the database; and discuss how this tool set might be applied to long term archives.

Fontaine, Kathy↗

NASA NTRS2018

Investigation of Bolt Preload Relaxation for JWST Thermal Heat Strap Assembly Joints with Aluminum-1100 and Indium Gaskets

Accurately predicting fastener preload relaxation in the James Webb Space Telescope (JWST) heat strap assemblies is essential to insure adequate thermal performance during its mission lifecycle. The mechanisms for preload relaxation in the strap joints include Al-1100 material creep, indium gasket flow-out, and embedment of the joint faying surfaces. This report documents the results from a bolted joint relaxation test, including analysis and curve fitting of the test data for predicting preloads five years after initial torque application. The report also includes the derivation of a preload uncertainty factor enveloping both torque/preload application scatter and expected preload relaxation at the end of mission life.

Joint↗

NASA NTRS2018

Investigation of Bolt Preload Relaxation for JWST Thermal Heat Strap Assembly Joints with Aluminum-1100 and Indium Gaskets

Preload↗

NASA NTRS2008

James Webb Space Telescope - Applying Lessons Learned to I&T

The James Webb Space Telescope (JWST) is part of a new generation of spacecraft acquiring large data volumes from remote regions in space. To support a mission such as the JWST, it is imperative that lessons learned from the development of previous missions such as the Hubble Space Telescope and the Earth Observing System mission set be applied throughout the development and operational lifecycles. One example of a key lesson that should be applied is that core components, such as the command and telemetry system and the project database, should be developed early, used throughout development and testing, and evolved into the operational system. The purpose of applying lessons learned is to reap benefits in programmatic or technical parameters such as risk reduction, end product quality, cost efficiency, and schedule optimization. In the cited example, the early development and use of the operational command and telemetry system as well as the establishment of the intended operational database will allow these components to be used by the developers of various spacecraft components such that development, testing, and operations will all use the same core components. This will reduce risk through the elimination of transitions between development and operational components and improve end product quality by extending the verification of those components through continual use. This paper will discuss key lessons learned that have been or are being applied to the JWST Ground Segment integration and test program.

Johns, Alan↗

NASA NTRS2019

A Validation Study of the Performance Prediction Methodology of the Early Warning Metrics

Complex projects frequently experience delays and develop backlogs of their project control milestones during the acquisition and development lifecycles. In response, the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) formed an independent group of Subject Matter Experts (SMEs) to monitor the execution performance of GSFC Flight projects and instruments that are under development. The SME team’s objective is to generate data driven performance-based indicators that quantify the degree to which projects are meeting their respective schedule and budget commitments. One of these performance-based indicators, the Early Warning Metrics, provides performance forecasts and insight to project performance relative to historical successful projects. Herein this paper describes the purpose and utility of the Early Warning Metrics. Additionally, the initial prediction method used in the creation of the metrics is described along with its validity and the validity of comparable prediction methods.

Holloman, Sherrica↗

NASA NTRS2015

[Redesign of the Spacesuit Long Life Battery and the Personal Life Support System Battery]

This fall I was working on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the department. The purpose of this document is to create a standard process and ensure that the data in the same way no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own all while taking notes on the procedure. These notes were used to write the final work instruction that will become is the department standard. My second project continued the work of the summer co-op before me. I was testing aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks were designed by the summer intern but there was not much time for testing before he left. We ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (energy systems test area) and are providing very promising results that safe, high performing (greater than 180 Wh/kg) designs are possible. My main project was a redesign of the LLB battery. Another summer intern did some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the current design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density and the rest of the design was up to me. First, I created new heat sink banks in Creo using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve greater than 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options of cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan is to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Some of my side projects included working on the CAD data for the PLSS with EC and attending the NASA Aerospace Battery Workshop in Huntsville. I was also a member of the Tours and Lectures Committee for the USRA and Pathways interns. I coordinated Apollo Evening and was on the committee for touring KSC and seeing an Atlas 5 launch. I really enjoyed my time at JSC and I would like to continue working for NASA or another aerospace company in the future. I have worked other internships prior to this, but I think the heavy research and development focus is the best fit for me. I originally thought I would need to go to grad school to work in an environment like this, but I now see it is possible with a bachelor’s degree and hard work. I would like to go into the workforce and maybe continue my education with night classes.

Scharf, Stephanie↗

NASA NTRSDate not supplied

Enhancing Dataset Discovery and Usage Tracking in Earth Sciences: Integrating Knowledge Graphs and Large Language Models

NASA's Data Active Archive Centers (DAACs) have played a crucial role in supporting a wide range of applied research in Earth and Environmental sciences. To date, over 20,000 publications have been collected, citing more than 3,000 NASA Earth science datasets. We present an innovative approach that links datasets and collected publications through a knowledge graph (KG). This KG enables the tracking of dataset citations throughout the dataset's lifecycle, revealing patterns of dataset usage across various applied research areas. We fine-tuned the pre-trained NASA IMPACT INDUS-Base Retriever Large Language Model (LLM) using a set of labeled publication abstracts. Our results indicate that 87% of the publications were classified into one of twenty applied research areas, while the remaining 13% were categorized into non-applied research areas. The classified publications linked to datasets are used to discover datasets by users interested in specific applied research and by dataset providers to determine dataset usage for applications.

open-source↗

NASA NTRS2017

Synergies Between the Kepler, K2 and TESS Missions with the PLATO Mission (Revised)

Two transit survey missions will have been flown by NASA prior to the launch of ESA's PLATO Mission in 2026, laying the groundwork for exoplanet discovery via the transit method. The Kepler Mission, which launched in 2009, collected data on its 100+ square degree field of view for four years before failure of a reaction wheel ended its primary mission. The results from Kepler include 2300+ confirmed or validated exoplanets, 2200+ planetary candidates, 2100+ eclipsing binaries. Kepler also revolutionized the field of asteroseismology by measuring the pressure mode oscillations of over 15000 solar-like stars spanning the lifecycle of such stars from hydrogen-burning dwarfs to helium-burning red giants. The re-purposed Kepler Mission, dubbed K2, continues to observe fields of view in and near the ecliptic plane for 80 days each, significantly broadening the scope of the astrophysical investigations as well as discovering an additional 156 exoplanets to date. The TESS mission will launch in 2017 to conduct an all-sky survey for small exoplanets orbiting stars 10X closer and 100X brighter than Kepler exoplanet host stars, allowing for far greater follow-up and characterization of their masses as well as their sizes for at least 50 small planets. Future assets such as James Webb Space Telescope, and ground-based assets such as ESOs Very Large Telescope (VLT) array, the Exremely Large Telescope (ELT), and the Thirty Meter Telescope (TMT) will be able to characterize the atmospheric composition and properties of these small planets. TESS will observe each 24 X 96 field of view for 30 days and thereby cover first the southern and then the northern hemisphere over 13 pointings during each year of the primary mission. The pole-most camera will observe the James Webb continuous viewing zone for one year in each hemisphere, permitting much longer period planets to be detected in this region. The PLATO mission will seek to detect habitable Earth-like planets with an instrument composed of 26 small telescopes in several 2232 square deg FOVs with a range of observation durations over a mission lifetime of up to eight years. This paper summarizes the findings of the KeplerK2 missions, previews the likely results from the TESS mission, and explores the lessons learned and to be learned from these prior missions that can be incorporated into the observation and data reduction strategy for the PLATO Mission so as to maximize the science return.

exoplanet detection↗

NASA NTRSDate not supplied

End-User Assessment of the NASA SPoRT Lightning AI Product

The NASA Short-term Prediction Research and Transition (SPoRT) Center has begun to develop products to address operational challenges and enhance safety during the lifecycle of lightning activity, and conduct evaluations in concentrated R2O/O2R efforts. The product evaluated for this study is Lightning Artificial Intelligence (A.I.), which predicts the probability of lightning out to 15 minutes in advance and spatially maps it using filled color contours. Lightning A.I. uses reflectivity, differential reflectivity, and correlation coefficient data from a subset of radars within the NEXRAD network to generate lightning probabilities at approximately 2 km resolution. The domains, spanning 145 x 145 km are centered over NASA-affiliated centers across the CONUS and use radar data which are closest in proximity. Lightning A.I. was developed with intended use by emergency managers at NASA centers. However, National Weather Service (NWS) offices are also often tasked with monitoring and forecasting the threat for lightning within their County Warning Areas for various impact-based decision support services. These forecasts are typically provided for aviation operations and large-scale, outdoor events, which may have varying safety requirements for decision-making based on lightning proximity and recency. The NASA SPoRT center conducted an assessment of the operational uses of Lightning A.I by various collaborative NWS Offices from late July into early September. This assessment included feedback from participants on both the product itself as well as its accessibility within the new, interactive NASA SPoRT Lightning Viewer. This presentation will include background information about Lightning A.I. and highlight results from this assessment. The feedback from the assessment will be used to inform research on any necessary modifications to this and future lightning products to assist end users.

Kelley Murphy↗

DOE OSTI2026

Robotics for HVAC applications: A critical review and future perspectives

Recent advances in artificial intelligence (AI), enhanced computational capabilities, and innovations in sensors and hardware have driven the increasing development and application of robots in heating, ventilation, and air conditioning (HVAC) systems. We selected and reviewed 101 studies published between 2005 and 2025, sourced from IEEE Xplore, Scopus, Web of Science, and the ACM Digital Library. To analyze these works, we developed a five-dimensional analytical framework (morphology, sensing, navigation, task execution, and system integration), inspired by the Springer Handbook of Robotics and tailored specifically for robotic applications in HVAC. Based on the reviewed studies, six distinct tasks spanning the entire HVAC lifecycle have been identified. Among the six tasks, inspection and maintenance dominate (59 %), followed by indoor monitoring and auditing (21 %), whereas leakage detection, comfort support, and installation/retrofit remain less explored. To address the identified gaps, this review proposes future research directions including investigating robot-aware HVAC design principles, developing multimodal HVAC sensing and data fusion techniques, enhancing robot training and hardware capabilities, and expanding robotic applications beyond Maintenance and Operations (M&O). The findings from this review inform future robotics research for HVAC applications and ultimately enhance system affordability, energy efficiency, resilience or reliability, and occupant environmental comfort. Moreover, it seeks to inspire researchers to explore the intersections of robotics, computer science, building science, and HVAC engineering fostering advancements in this multidisciplinary field.

AI↗

NASA NTRS1991

Ada and the rapid development lifecycle

JPL is under contract, through NASA, with the US Army to develop a state-of-the-art Command Center System for the US European Command (USEUCOM). The Command Center System will receive, process, and integrate force status information from various sources and provide this integrated information to staff officers and decision makers in a format designed to enhance user comprehension and utility. The system is based on distributed workstation class microcomputers, VAX- and SUN-based data servers, and interfaces to existing military mainframe systems and communication networks. JPL is developing the Command Center System utilizing an incremental delivery methodology called the Rapid Development Methodology with adherence to government and industry standards including the UNIX operating system, X Windows, OSF/Motif, and the Ada programming language. Through a combination of software engineering techniques specific to the Ada programming language and the Rapid Development Approach, JPL was able to deliver capability to the military user incrementally, with comparable quality and improved economies of projects developed under more traditional software intensive system implementation methodologies.

Deforrest, Lloyd↗

NASA NTRS2010

Modeling the Frozen-In Anticyclone in the 2005 Arctic Summer Stratosphere

Immediately following the breakup of the 2005 Arctic spring stratospheric vortex, a tropical air mass, characterized by low potential vorticity (PV) and high nitrous oxide (N2O), was advected poleward and became trapped in the easterly summer polar vortex. This feature, known as a "Frozen-In Anticyclone (FrIAC)", was observed in Earth Observing System (EOS) Aura Microwave Limb Sounder (MLS) data to span the potential temperature range from approximately 580 to 1100 K (approximately 25 to 40 km altitude) and to persist from late March to late August 2005. This study compares MLS N2O observations with simulations from the Global Modeling Initiative (GMI) chemistry and transport model, the GEOS-5/MERRA Replay model, and the VanLeer Icosahedral Triangular Advection isentropic transport model to elucidate the processes involved in the lifecycle of the FrIAC which is here divided into three distinct phases. During the "spin-up phase" (March to early April), strong poleward flow resulted in a tight isolated anticyclonic vortex at approximately 70-90 deg N, marked with elevated N2O. GMI, Replay, and VITA all reliably simulted the spin-up of the FrIAC, although the GMI and Replay peak N2O values were too low. The FrIAC became trapped in the developing summer easterly flow and circulated around the polar region during the "anticyclonic phase" (early April to the end of May). During this phase, the FrIAC crossed directly over the pole between the 7th and 14th of April. The VITA and Replay simulations transported the N2O anomaly intact during this crossing, in agreement with MLS, but unrealistic dispersion of the anomaly occurred in the GMI simulation due to excessive numerical mixing of the polar cap. The vortex associated with the FrIAC was apparently resistant to the weak vertical hear during the anticyclonic phase, and it thereby protected the embedded N20 anomaly from stretching. The vortex decayed in late May due to diabatic processes, leaving the N2O anomaly exposed to horizontal and vertical wind shears during the "shearing phase" (June to August). The observed lifetime of the FrIAC during this phase is consistent with time-scales calculated from the ambient horizontal and vertical wind shear. Replay maintained the horizontal structure of the N2O anomaly similar to NILS well into August. The VITA simulation also captured the horizontal structure of the FrIAC during this phase, but VITA eventually developed fine-scale N2O structure not observed in MLS data.

Allen, D. R.↗

NASA NTRS2014

Usability/Sentiment for the Enterprise and ENTERPRISE

The purpose of the Sentiment of Search Study for NASA Johnson Space Center (JSC) is to gain insight into the intranet search environment. With an initial usability survey, the authors were able to determine a usability score based on the Systems Usability Scale (SUS). Created in 1986, the freely available, well cited, SUS is commonly used to determine user perceptions of a system (in this case the intranet search environment). As with any improvement initiative, one must first examine and document the current reality of the situation. In this scenario, a method was needed to determine the usability of a search interface in addition to the user's perception on how well the search system was providing results. The use of the SUS provided a mechanism to quickly ascertain information in both areas, by adding one additional open-ended question at the end. The first ten questions allowed us to examine the usability of the system, while the last questions informed us on how the users rated the performance of the search results. The final analysis provides us with a better understanding of the current situation and areas to focus on for improvement. The power of search applications to enhance knowledge transfer is indisputable. The performance impact for any user unable to find needed information undermines project lifecycle, resource and scheduling requirements. Ever-increasing complexity of content and the user interface make usability considerations for the intranet, especially for search, a necessity instead of a 'nice-to-have'. Despite these arguments, intranet usability is largely disregarded due to lack of attention beyond the functionality of the infrastructure (White, 2013). The data collected from users of the JSC search system revealed their overall sentiment by means of the widely-known System Usability Scale. Results of the scores suggest 75%, +/-0.04, of the population rank the search system below average. In terms of a grading scaled, this equated to D or lower. It is obvious JSC users are not satisfied with the current situation, however they are eager to provide information and assistance in improving the search system. A majority of the respondents provided feedback on the issues most troubling them. This information will be used to enrich the next phase, root cause analysis and solution creation.

Meza, David↗