Search NASASearch

SEARCH · Search NASA

Results for “VS Code”

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 19 records

An Open-source Llm Enhanced-tool Specialized In Helping Moose Related Problems And Tasks

MOOSEenger is an open-source, terminal-first chat application for the MOOSE ecosystem that couples specialized parsing of MOOSE documentation and “.i” input files with retrieval-augmented generation to deliver grounded answers about multiphysics modeling and workflows. It includes dedicated readers for MOOSE-style HTML and a pyhit-based parser that uses the MOOSE syntax tree to preserve block structure and attach retrieval metadata. A data-ingestion pipeline performs semantic chunking into atomic facts and stores them hierarchically in a local Chroma vector database that maintains parent–child relationships across documents; the system can ingest directories, individual files, and single-page web content, and it provides CRUD operations (insert, update, delete) to manage the corpus. At query time, relevant chunks are embedded, retrieved, and fused into the model context, with interactive features such as token streaming, persistent chat history, and dynamic RAG (retrieval triggered by user input or intermediate model output). Deployment is flexible: MOOSEenger runs with local Ollama models or remote Hugging Face/OpenAI backends—typically coordinating generation, lightweight tagging/summarization, and embeddings across three models—and it also supports a server mode and integration with the VS Code Continue interface.

Li, Mengnan [Idaho National Laboratory (INL), Idah

Using containers to speed up development, to run integration tests and to teach about distributed systems

GlideinWMS is a workload manager provisioning resources for many experiments including CMS and DUNE. The software is distributed both as native packages and specialized production containers. Following an approach used in other communities like web development we built our workspaces, system-like containers to ease development and testing. Developers can change the source tree or check out a different branch and quickly reconfigure the services to see the effect of their changes. In this paper, we’ll talk about what differentiates workspaces from other containers. We’ll describe our base system composed of three containers. A one-node cluster including a compute element and a batch system. A GlideinWMS Factory controlling pilot jobs. And a scheduler and Frontend, to submit jobs and provision resources. Additional containers can be used for optional components. This system can easily run on a laptop and we’ll share our evaluation of different container runtimes, with an eye for ease of use and performance. Finally, we’ll talk about our experience as developers and with students. The GlideinWMS workspaces are easily integrated with IDEs like VS Code, simplifying debugging and allowing development and testing of the system also when offline. They simplified the training and onboarding of new team members and Summer interns. And they were useful in workshops where students could have first-hand experience with the mechanisms and components that, in production, run millions of jobs.

Mambelli, Marco

Using Containers to Speed Up Development, to Run Integration Tests and to Teach About Distributed Systems

GlideinWMS is a workload manager provisioning resources for many experiments, including CMS and DUNE. The software is distributed both as native packages and specialized production containers. Following an approach used in other communities like web development, we built our workspaces, system-like containers to ease development and testing. Developers can change the source tree or check out a different branch and quickly reconfigure the services to see the effect of their changes. In this paper, we will talk about what differentiates workspaces from other containers. We will describe our base system, composed of three containers: a one-node cluster including a compute element and a batch system, a GlideinWMS Factory controlling pilot jobs, and a scheduler and Frontend to submit jobs and provision resources. Additional containers can be used for optional components. This system can easily run on a laptop, and we will share our evaluation of different container runtimes, with an eye for ease of use and performance. Finally, we will talk about our experience as developers and with students. The GlideinWMS workspaces are easily integrated with IDEs like VS Code, simplifying debugging and allowing development and testing of the system even when offline. They simplified the training and onboarding of new team members and summer interns. And they were useful in workshops where students could have first-hand experience with the mechanisms and components that, in production, run millions of jobs.

Mambelli, Marco [Fermilab] (ORCID:0000000294892681

Model data for a watershed-scale study in the Portage River Basin (OH) examining the effects of subsurface drainage on the hydrologic response of an agricultural watershed.

This study builds on Rathore et al. (2024, WRR) and investigates the role of artificial tile-drainage on various aspects of watershed hydrological response, with a particular focus on peakflow. The model-data for the original modeling-focused paper (Rathore et al., 2024, WRR) is archived at Rathore et al. (2024, ESS-DIVE). Hence, this model-data archive provides scripts that are specific to this study that includes model updates, processing and analysis scripts. For details and models files of original model, readers are referred to Rathore et al. (2024, ESS-DIVE). The key difference between the model configuration in this study and Rathore et al. (2024, WRR) is that the tile drains are applied to the entire domain, to study the impact of tile-drains on different aspects of hydrological response. Additional scenario considering intensified precipitation after a dry period was also simulated. The Watershed Workflow package is implemented in Python3. The Jupyter notebooks can be executed through multiple open-source tools, for example, Anaconda Jupyter Lab, VS Studio Code, etc. Other data files include CSV and HDF5 files, which can be read through Python scripts.

54 ENVIRONMENTAL SCIENCES

MSAT voice modulation considerations

The challenge for Mobile satellite (MSAT) voice services is to provide near toll quality voice to the user, while minimizing the power and bandwidth resources of the satellite. The options for MSAT voice can be put into one of two groups: Analog and Digital. Analog, nominally narrowband single sideband techniques, have a shown robustness to the fading and shadowing environment. Digital techniques, a combination of low rate vocoders and bandwidth efficient modems, show the promise of enhanced fidelity, as well as easier networking to the emerging digital world. The problems and tradeoffs to designers are many, especially in the digital case. Processor speed vs. cost and MET power requirements, channel coding, bandwidth efficiency vs. power efficiency etc. While the list looks daunting, in fact an acceptable solution is well within the technology. The objectives are reviewed that the MSAT voice service must meet, along with the options that are seen for the future.

Bossler, Dan

Total-dose radiation effects data for semiconductor devices, volume 3

Volume 3 of this three-volume set provides a detailed analysis of the data in Volumes 1 and 2, most of which was generated for the Galileo Orbiter Program in support of NASA space programs. Volume 1 includes total ionizing dose radiation test data on diodes, bipolar transistors, field effect transistors, and miscellaneous discrete solid-state devices. Volume 2 includes similar data on integrated circuits and a few large-scale integrated circuits. The data of Volumes 1 and 2 are combined in graphic format in Volume 3 to provide a comparison of radiation sensitivities of devices of a given type and different manufacturer, a comparison of multiple tests for a single data code, a comparison of multiple tests for a single lot, and a comparison of radiation sensitivities vs time (date codes). All data were generated using a steady-state 2.5-MeV electron source (Dynamitron) or a Cobalt-60 gamma ray source. The data that compose Volume 3 represent 26 different device types, 224 tests, and a total of 1040 devices. A comparison of the effects of steady-state electrons and Cobat-60 gamma rays is also presented.

Price, W. E.

Elasto-Plastic Analysis of Tee Joints Using HOT-SMAC

The Higher Order Theory - Structural/Micro Analysis Code (HOT-SMAC) software package is applied to analyze the linearly elastic and elasto-plastic response of adhesively bonded tee joints. Joints of this type are finding an increasing number of applications with the increased use of composite materials within advanced aerospace vehicles, and improved tools for the design and analysis of these joints are needed. The linearly elastic results of the code are validated vs. finite element analysis results from the literature under different loading and boundary conditions, and new results are generated to investigate the inelastic behavior of the tee joint. The comparison with the finite element results indicates that HOT-SMAC is an efficient and accurate alternative to the finite element method and has a great deal of potential as an analysis tool for a wide range of bonded joints.

Arnold, Steve M.

NASA and Blue Origin Collaborative Assessment of Precision Landing Algorithms and Computing

NASA’s Safe and Precise Landing Integrated Capabilities Evolution (SPLICE) project is developing sensor, algorithm, and compute technologies for precision landing and hazard avoidance. These technologies are being tested as an integrated Precision Landing and Hazard Avoidance (PL&HA) system on Blue Origin’s New Shephard suborbital vehicle. A key goal for the computing element of this technology development is to characterize the performance of the SPLICE software workloads on the project’s Descent and Landing Computer (DLC). The DLC is a multi-core processor designed as a surrogate for NASA’s High-Performance Space Computer (HPSC). Measurements of the SPLICE workload performance on the DLC provides NASA insight on how PL&HA capabilities will perform on the HPSC, and guidance on how the SPLICE algorithms can be implemented to best utilize the DLC platform. This insight can also be used to derive requirements to guide trade studies on candidate computing architectures, for use on platforms like Blue Moon. NASA and Blue Origin are collaborating under an agreement to pursue this mutual benefit. Performance metrics collected are based on measurement of common compute resources such as percentage used of memory bandwidth, I/O utilization, interrupt latency, and kernel vs. user space code residency. Where possible existing performance counters and metrics that are part of the operating system kernel are used. As the design has a significant FPGA component, performance counters are identified and instantiated in the fabric to measure DMA performance and interface metrics. Collection of metrics is performed on the DLC with a representative workload that simulates a full landing cycle of the Blue Origin New Shepard vehicle. Consideration is given to the other compute implementations and whether they can run SPLICE algorithms at the same rate and with the same latency as the DLC. One option being considered is the use of a RISC-V soft core instantiated in a radiation resilient FPGA fabric such as the Xilinx KU60. Select algorithms from the SPLICE code will be run for comparison with the DLC. This paper describes how the DLC is instrumented to collect performance measurements of the SPLICE workloads, preliminary results from these measurements, and their implications on SPLICE algorithm implementation. The results of experimentation to derive candidate requirements for architecture trades on a PL&HA computing system are also presented.

computer performance

Impact of Electric Vehicle Charging Station Reliability, Resilience, and Location on Electric Vehicle Adoption

While the majority of electric vehicle (EV) charging events in the United States occur at home, issues with public charging stations are consistently found to be a top reason that potential EV buyers do not purchase an EV, demonstrating that both EVSE reliability and availability impacts EV adoption. This report explores multiple parameters that impact EVSE reliability and deployment, which in turn impact EV sales. These include extreme weather, codes and standards, region (urban vs. rural), and grid network type. Grid reliability was not found to impact EV adoption. The relationships between EV station reliability, station resilience, grid resilience, and EV adoption are largely outside the scope of the National Renewable Energy Laboratory's (NREL's) Automotive Deployment Options Projection Tool (ADOPT) and other vehicle adoption models, so the methodology of this report is varied. Section 2 sets the baseline for infrastructure reliability, user satisfaction, and maintenance practices. Section 3 explores the ways that electric vehicle supply equipment (EVSE) reliability impacts the relationship between EVSE and EV adoption. Section 4 shows how geographical categories such as urban, rural, large grid, off-grid, or microgrid can be helpful in EVSE deployment strategies, as well as how the relationship between EVSE and EV adoption differs among these categories. Section 5 investigates the impacts of grid reliability and infrastructure resilience on EV adoption. Finally, Section 6 reverses the perspective to examine the impact that EVs and EVSE have on grid resilience and reliability. As recent funding initiatives result in an expansion of public chargers across the United States, as well as an increase in the uptime of existing chargers, EV adoption will likely grow.

33 ADVANCED PROPULSION SYSTEMS

Contamination Analysis Tools

This talk presents 3 different tools developed recently for contamination analysis:HTML QCM analyzer: runs in a web browser, and allows for data analysis of QCM log filesJava RGA extractor: can load in multiple SRS.ana files and extract pressure vs. time dataC++ Contamination Simulation code: 3D particle tracing code for modeling transport of dust particulates and molecules. Uses residence time to determine if molecules stick. Particulates can be sampled from IEST-STD-1246 and be accelerated by aerodynamic forces.

A performance comparison between block interleaved and helically interleaved concatenated coding systems

The performance (bit-error rate vs. signal-to-noise ratio) of two different interleaving systems, block interleaving and the newer helical interleaving are compared. Both systems are studied with and without error forecasting. Without error forecasting, the two systems have identical performance. When error forecasting is used with shallow interleaving, helical interleaving gains, but less than 0.05 dB, over block interleaving. For higher interleaving depth, the systems have almost indistinguishable performance.

Cheung, K.-M.

Formally specifying the logic of an automatic guidance controller

The following topics are covered in viewgraph form: (1) the Penelope Project; (2) the logic of an experimental automatic guidance control system for a 737; (3) Larch/Ada specification; (4) some failures of informal description; (5) description of mode changes caused by switches; (6) intuitive description of window status (chosen vs. current); (7) design of the code; (8) and specifying the code.

Guaspari, David

Historical Aerospace Software Errors Categorized to Influence Fault Tolerance

- Motivation - Very little literature exists characterizing software errors in real-time avionic systems - How, where, and why is software most likely to fail? - Purpose - Raise awareness of how software fails through historical study - Recommend improvements to software fault tolerant design based on historical study - Outline - Discuss Software Failures - Common Cause, Failure Classes, Mitigation strategies - Review NASA requirements for Software Fault Tolerance - Review Historical Software Failures - Analyze failures and provide statistics - Erroneous vs. fail-Silent - Reboot recoverability likelihood - Code Location - Missing or unknown code?

Flilght

Predictive outlook for experiments resolving prompt vs local redeposition of high- Z materials in tokamaks

High-Z plasma facing components redeposit within the sheath through a combination of two distinct mechanisms: prompt (or geometric-driven) and local (or sheath-driven) redeposition. Experimental efforts are needed to determine the leading-order parameters influencing prompt-vs-local trade-off, which sets the fraction of material entering the scrape-off layer. In preparation for such experiments, leading-order parameters are isolated within the PYEAD-RustBCA-GITR coupled net erosion code using Sobol’ sensitivity analysis. Then, experiments resolving prompt-vs-local trade-off under variation of these leading-order parameters are proposed using an isotopic coupon design with multifaceted diagnostic coverage. The measurability of these experiments is evaluated using synthetic diagnostics.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY

Reducing the Cost of Fatigue Crack Growth Testing for Storage Vessel Steels in Hydrogen Gas

Hydrogen storage pressure vessels are designed against fatigue crack growth, and the ASME Boiler and Pressure Vessel Code requires the fatigue crack growth rate (da/dN) vs. stress-intensity factor range (ΔK) relationship of the construction steel to be measured directly in hydrogen gas. These measurements are notoriously slow and expensive: the cyclic loading frequencies prescribed by standards (often 0.1 Hz) are two or more orders of magnitude below those for conventional fatigue testing, individual tests run for days to weeks, and the high-pressure test-chamber set-up imposes a significant per-specimen labor cost. Due to these time and cost constraints, near-threshold data—the regime most valuable for extending design fatigue life—are rarely generated for ferritic storage vessel steels in hydrogen gas.

08 HYDROGEN

Sensitivity study of the monogroove with screen heat pipe design

The present sensitivity study of design variable effects on the performance of a monogroove-with-screen heat pipe obtains performance curves for maximum heat-transfer rates vs. operating temperatures by means of a computer code; performance projections for both 1-g and zero-g conditions are obtainable. The variables in question were liquid and vapor channel design, wall groove design, and the number of feed lines in the evaporator and condenser. The effect on performance of three different working fluids, namely ammonia, methanol, and water, were also determined. Greatest sensitivity was to changes in liquid and vapor channel diameters.

Evans, Austin L.