SEARCH · Search NASA

Results for “script”

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 379 records · Page 21

All sources NASA NTRS DOE OSTI

DOE OSTI2016

SU-G-TeP4-08: Automating the Verification of Patient Treatment Parameters

Purpose: To automate the daily verification of each patient’s treatment by utilizing the trajectory log files (TLs) written by the Varian TrueBeam linear accelerator while reducing the number of false positives including jaw and gantry positioning errors, that are displayed in the Treatment History tab of Varian’s Chart QA module. Methods: Small deviations in treatment parameters are difficult to detect in weekly chart checks, but may be significant in reducing delivery errors, and would be critical if detected daily. Software was developed in house to read TLs. Multiple functions were implemented within the software that allow it to operate via a GUI to analyze TLs, or as a script to run on a regular basis. In order to determine tolerance levels for the scripted analysis, 15,241 TLs from seven TrueBeams were analyzed. The maximum error of each axis for each TL was written to a CSV file and statistically analyzed to determine the tolerance for each axis accessible in the TLs to flag for manual review. The software/scripts developed were tested by varying the tolerance values to ensure veracity. After tolerances were determined, multiple weeks of manual chart checks were performed simultaneously with the automated analysis to ensure validity. Results: The tolerance values for the major axis were determined to be, 0.025 degrees for the collimator, 1.0 degree for the gantry, 0.002cm for the y-jaws, 0.01cm for the x-jaws, and 0.5MU for the MU. The automated verification of treatment parameters has been in clinical use for 4 months. During that time, no errors in machine delivery of the patient treatments were found. Conclusion: The process detailed here is a viable and effective alternative to manually checking treatment parameters during weekly chart checks.

60 APPLIED LIFE SCIENCES↗

DOE OSTI2016

Sci-Fri PM: Radiation Therapy, Planning, Imaging, and Special Techniques - 08: Retrospective Dose Accumulation Workflow in Head and Neck Cancer Patients Using RayStation 4.5.2

Purpose: We have developed a semi-automated dose accumulation workflow for Head and Neck Cancer (HNC) patients to evaluate volumetric and dosimetric changes that take place during radiotherapy. This work will be used to assess how dosimetric changes affect both toxicity and disease control, hence inform the feasibility and design of a prospective HNC adaptive trial. Methods: RayStation 4.5.2 features deformable image registration (DIR), where structures already defined on the planning CT image set can be deformably mapped onto cone-beam computed tomography (CBCT) images, accounting for daily treatment set-up shifts and changes in patient anatomy. The daily delivered dose can be calculated on each CBCT and mapped back to the planning CT to allow dose accumulation. The process is partially automated using Python scripts developed in collaboration with RaySearch. Results: To date we have performed dose accumulation on 18 HNC patients treated at our institution during 2013–2015 under REB approval. Our semi-automated process establishes clinical feasibility. Generally, dose accumulation for the entire treatment course of one case takes 60–120 minutes: importing all CBCTs requires 20–30 minutes as each patient has 30 to 40 treated fractions; image registration and dose accumulation require 60–90 minutes. This is in contrast to the process without automated scripts where dose accumulation alone would take 3–5 hours. Conclusions: We have developed a reliable workflow for retrospective dose tracking in HNC using RayStation. The process has been validated for HNC patients treated on both Elekta and Varian linacs with CBCTs acquired on XVI and OBI platforms respectively.

60 APPLIED LIFE SCIENCES↗

DOE OSTI2019

Parsl: Pervasive Parallel Programming in Python

High-level programming languages such as Python are increasingly used to provide intuitive interfaces to libraries written in lower-level languages and for assembling applications from various components. This migration towards orchestration rather than implementation, coupled with the growing need for parallel computing (e.g., due to big data and the end of Moore's law), necessitates rethinking how parallelism is expressed in programs. Here, we present Parsl, a parallel scripting library that augments Python with simple, scalable, and flexible constructs for encoding parallelism. These constructs allow Parsl to construct a dynamic dependency graph of components that it can then execute efficiently on one or many processors. Parsl is designed for scalability, with an extensible set of executors tailored to different use cases, such as low-latency, high-throughput, or extreme-scale execution. We show, via experiments on the Blue Waters supercomputer, that Parsl executors can allow Python scripts to execute components with as little as 5 ms of overhead, scale to more than 250000 workers across more than 8000 nodes, and process upward of 1200 tasks per second. Other Parsl features simplify the construction and execution of composite programs by supporting elastic provisioning and scaling of infrastructure, fault-tolerant execution, and integrated wide-area data management. We show that these capabilities satisfy the needs of many-task, interactive, online, and machine learning applications in fields such as biology, cosmology, and materials science.

parallel programming↗

DOE OSTI2016

dfnWorks, Version 1.0

DFNWorks is a suite of software for generating and solving flow and transport physics on a Discrete Fracture Network (DFN). The suite is composed of three components: DFNGen: Stochastic fracture generation, mesh generation, model setup; DFNFlow: Flow solution using PFLOTRAN or FEHM control volume formulation solver; DFNTrans: Particle tracking transport; DFNGen Algorithm Description: This is a workflow that uses Mathematica software, Python scripts written by the authors and the LaGriT software to generate; DFNFlow; The solution of flow in porous media is accomplished by coupling DFNGen output with the existing software packages FEHM and PFLOTRAN. The DFNWorks workflow involves modules and scripts that translate DFNGen output to formats compatible with FEHM and PFLOTRAN input. FEHM LA-CC-2012-083 PFLOTRAN LA-CC-09-047 LaGriT LA-CC-07-38 DFNTrans Stand alone particle tracking algorithm that takes FEHM/PFLOTRAN flow solution as output and computes velocity field and advects particles.

Makedonska, Nataliia↗

DOE OSTI2017

dfnWorks, Version 2.0

DFNWorks is a suite of software for generating and solving flow and transport physics on a Discrete Fracture Network (DFN). The suite is composed of three components: DFNGen: Stochastic fracture generation, mesh generation, model setup; DFNFlow: Flow solution using PFLOTRAN or FEHM control volume formulation solver; DFNTrans: Particle tracking transport; DFNGen Algorithm Description: This is a workflow that uses C++ software version for fracture generation, Python scripts written by the authors and the LaGriT software to generate computational mesh. DFNFlow The solution of flow in porous media is accomplished by coupling DFNGen output with the existing software packages FEHM and PFLOTRAN. The DFNWorks workflow involves modules and scripts that translate DFNGen output to formats compatible with FEHM and PFLOTRAN input. FEHM LA-CC-2012-083 PFLOTRAN LA-CC-09-047 LaGriT LA-CC-07-38 DFNTrans Stand-alone particle tracking algorithm that takes FEHM/PFLOTRAN flow solution as output and computes velocity field and advects particles.

Makedonska, Nataliia↗

DOE OSTI2017

Transactive Energy Simulation Platform

Transactive Energy Simulation Platform (TESP) combines existing domain simulators in the electric power grid, buildings, and communication systems, with new transactive agents, growth models and evaluation scripts. The existing domain simulators include GridLAB-D for the distribution grid and single-family residential buildings, MATPOWER for transmission and bulk generation, EnergyPlus for large buildings and ns-3 for communication systems. More are planned for subsequent versions of TESP. The new elements are: TEAgents - simulate market participants and transactive systems for market clearing. Some of this functionality was extracted from GridLAB-D and implemented in Python for customization by PNNL and others. Growth Model - a means for simulating system changes over a multiyear period, including both normal load growth and specific investment decisions. Customizable in Python code. Evaluation Script - a means of evaluating different transactive systems through customizable post-processing in Python code. TESP will run on Linux, Windows and Mac OS X.

McDermott, Tom↗

DOE OSTI2017

Soil Carbon Data: long tail recovery

The software is intended to be part of an open source effort regarding soils data. The software provides customized data ingestion scripts for soil carbon related data sets and scripts for output databases that conform to common templates.

Source record↗

DOE OSTI2017

Synthetic Transaction Test Generator for Websites

Python script for querying a list of web sites and their details from Splunk and dynamically creating tests for monitoring uptime. The data generated from this script is then sent back to Splunk for creating reports and alerts.

Brown, Justin↗

DOE OSTI2018

GHOST (Grid Hardware Open Source Testbed) [SWR-18-32]

The software was developed for the purpose of Microgrid Controller Procurement where multiple Microgrid Controller vendors were competing to prove the best performance. Each microgrid controller was connected to Real-Time Simulator (Opal-RT) where the Real-Time model of microgrid was simulated. Microgrid controllers were able to control most of the assets in the model. To be able to fairly compare controller's performance each controller was evaluated using exactly the same model, with the same initial conditions and exactly the same test sequence. The microgrid evaluation test sequence lasted 100 minutes and consist of various grid disturbances to which a microgrid controller must respond. The microgrid and power system will experience multiple types of disturbances while performing dispatch functions. Many functions are tested in grid-connected and islanded modes such as unexpended failures of generators, energy storage trip events, and large load fluctuations. The test sequence focuses on fault scenarios that cause the highest short-circuit fault current contribution; force a swing bus or generator capable of being a swing bus offline; cause the most reconfigurations; and cause conflicting objectives for the microgrid controller. During the test sequence execution multiple datapoints are being recorded and stored. During data postprocessing key performance parameters are extracted allowing quantitative comparison of performance on multiple aspects including: resiliency, fuel utilization, grid interconnection, ancillary services and power quality and eventually after summing all key performance parameters by comparing the overall result. To be able to perform such testing multiple tools had to be developed included in this repository including: - Real time model of microgrid (Urban-Banshee, Remote-smaller model) - Test sequence configuration tools - Test execution real-time scripts - Post processing scripts - Human Machine Interface software

Koralewicz, Przemyslaw↗

DOE OSTI2018

High Performance Computing Cluster Engineering Academy

Collection of tools and code for evaluation testing of HPC orchestration solutions by HPCCEA summer students. These scripts and configuration files were written by HPCCEA summer students as part of their summer internship where they explore alternative solutions to our current HPC cluster management software. These scripts/configuration files range from using configuration management tools (Puppet, Chef, Ansible, Fabric, etc.) to scripting languages (Phython, BASH, Perl, etc.). Each year, new students will be added to the project and expand on previous years work.

Bennett, ThomasG↗

DOE OSTI2020

STAR

Structured Threat Automated Response (STAR) is a script that creates a python run-time for automated response action included in the Structure Threat Information Expression (STIX) Course of Action object. This script can parse a valid STIX json file and execute the included Course of Action.

McClurg, BryceL↗

DOE OSTI2018

MCR Container Tools

MathWorks' MATLAB is widely used in academia and industry for prototyping, data analysis, data processing, etc. Many users compile their programs using the MATLAB Compiler to run on workstations/computing clusters via the free MATLAB Compiler Runtime (MCR). The MCR facilitates the execution of code calling Application Programming Interfaces (API) functions from both base MATLAB and MATLAB toolboxes. In a Linux environment, a sizable number of third-party runtime dependencies (i.e. shared libraries) are necessary. Unfortunately, to the MTLAB community's knowledge, these dependencies are not documented, leaving system administrators and/or end-users to find/install the necessary libraries either as runtime errors resulting from them missing or by inspecting the header information of Executable and Linkable Format (ELF) libraries of the MCR to determine which ones are missing from the system. To address various shortcomings, Docker Images based on Community Enterprise Operating System (CentOS) 7, a derivative of Redhat Enterprise Linux (RHEL) 7, containing recent (2015-2017) MCR releases and their dependencies were created. These images, along with a provided sample Docker Compose YAML Script, can be used to create a simulated computing cluster where MATLAB Compiler created binaries can be executed using a sample Slurm Workload Manager script.

Haas, NicholasQ↗

DOE OSTI2020

Lithium-Ion Battery Vent Gas Tools

The spreadsheets and Python scripts are used to determine vent gas hazard metrics (i.e. flammability limits, flame speed, etc.). These scripts and spreadsheets use open source literature to determine these hazard metrics. SAND2020-12540 O Sandia National Laboratories is a multimission laboratory managed and operated by National Technology & Engineering Solutions of Sandia, LLC, a wholly owned subsidiary of Honeywell International Inc., for the U.S. Department of Energy's National Nuclear Security Administration under contract DE-NA0003525.

Baird, Austin↗

DOE OSTI2019

Bead-Tracking Toolbox for MATLAB

A collection of MATLAB scripts forming a toolbox for video (frame by frame) detection and tracking of beads imaged with fluorescence microscope for estimating bead flow and location tracks. Scripts accept tiff image stacks of video frames and provide bead locations and tracked positions over frames in stack. Various utility functions are also provided to assist in data I/O. A custom solution for specific data source - specifically, the software works well for noisy/out of focus florescence microscopy images.

Rose, DerekC.↗

DOE OSTI2022

AutoBEM-DynamicArchetypes

Automatic Building Energy Modeling (AutoBEM, https://bit.ly/AutoBEM) has been used to create an OpenStudio and EnergyPlus building energy model of 122.9 million U.S. buildings (https://bit.ly/ModelAmerica). Simulating and analyzing a model of every building for large areas (e.g. cities) is often not feasible. This dynamic archetyping capability uses a representative building and calculates a floor-space multiplier that allows millions of buildings to be represented by less than 100 buildings. This script (WRF_Archetypes_Parallel.py) calculates these building archetypes for each of the grid cells from a Weather Research and Forecasting (WRF) model in a parallel fashion. The script works by looping through each of the grid cells in the shapefile in parallel, spatially joining the building metadata table to each grid cell, aggregating relevant archetypes and calculating necessary statistics related to area and number of buildings in each cell. The output is a table (.csv) in which each row is an archetype building with properties about that building as well as statistics that relate that building to the total cell (such as an area multiplier). The following inputs are required: WRF zone shapefile (.shp) (wrf-grids-origin_Vegas_Select_100.geojson) The projection of the shapefile ("EPSG:XXXX") Input table containing building metadata for area corresponding to shapefile (.csv) (https://zenodo.org/record/4552901#.YZQEotDMJPY - ClarkCounty2.csv) The number of cores that will be parallelized (integer) The output file name for the archetype table (.csv) Sample command line inputs: python3 ~/WRF_Archetypes_Parallel.py -i ~/wrf-grids-origin_Vegas_Select_100.geojson -c ~/ClarkCounty2.csv -o ~/OutputArchetypes.csv -j 72 -e EPSG:4326 Using Geopandas Version 0.9.0

Bass, Brett (0000000240988434)↗

DOE OSTI2021

HyPerPy (Hydrogen Extraction and Parabolic Trough Plant Performance Models using Python) [SWR-21-53]

The HyPerPy package consists of three scripts: 1) Model for Hydrogen Tracking in Parabolic Trough Power Plants, 2) Model for Receiver Performance, and 3) Model for Hydrogen Extraction Process. The power plant model (1) tracks hydrogen generation and transport within the circulating heat transfer fluid (HTF) of the power plant. This script is a transient, initial value simulation, in which the hydrogen concentration in the circulating HTF is 0 moles per cubic meter everywhere at time 0 seconds. Hydrogen concentration is calculated at discrete locations within the circulating HTF with 4-second time resolution. During each time step, the change in hydrogen concentration due to hydrogen generation and permeation is calculated for each location according to the local HTF temperature, vessel or piping properties, hydrogen concentration and partial pressure. This model predicts hourly hydrogen concentrations for typical operating days in the spring, summer, fall, and winter seasons. Data is used to create hourly mappings of hydrogen concentrations for a typical operating year. The receiver model (2) uses a 1-hour time step to estimate getter loading and annulus pressure. For each time step, the model uses HTF and ambient temperature data to estimate absorber tube, bellows, and getter temperatures for the time step. In addition, the model uses hourly HTF hydrogen concentrations that are generated by the power plant model (1), and annulus hydrogen pressure from the previous time step. With these data, the model calculates the moles of hydrogen permeating across the absorber tube and bellows during the time step. The net change in moles hydrogen is added or subtracted from the getter loading for the previous time step, and the hydrogen pressure is re-calculated based on getter loading and temperature. The model uses this algorithm to simulate hydrogen permeation and loading 24 hours per day, 365 days per year using seasonal temperature data. The model repeats these calculations for 25 years to create a mapping of receiver getter loading and annulus hydrogen pressure for four seasons of each year. The model for hydrogen extraction (3) estimates hydrogen extraction rates for a specific separation module configuration. The rate depends primarily on membrane area, vacuum pump performance, headspace gas flowrate to the membrane, and headspace gas hydrogen partial pressure. This model has two versions. The steady-state version predicts hydrogen extraction rates when the module is operating in separation mode. The dynamic version predicts hydrogen transfer through the membrane when the module is operating in sensor mode. The steady-state version is used with the plant model (1) to predict hydrogen partial pressures in the power plant when the extraction process is operating.

Glatzmaier, Gregory↗

DOE OSTI2022

CMEC Module Manager

The CMEC module manager package is designed install and update CMEC modules (https://cmec.llnl.gov/). CMEC modules are independent climate model analysis packages. Individual scripts are provided in the module manager that outline the installation process for each module in a robust way, and a wrapper python script is provided that lets users install a chosen CMEC package with a single command.

Ordonez, AnaC↗

DOE OSTI2022

labquake_future_prediction

The labquake_future_prediction code is a collection of python modules and scripts that serves as supporting information for the article “Predicting future laboratory fault friction through deep learning” for publication in the journal of “Geophysical Research Letters”. It is designed to predict laboratory fault slips in the immediate future by scanning continuous acoustic emission (AE) waveforms recorded in laboratory biaxial shear experiments. The predictions are made with a deep learning model based on convolutional encoder-decoder (CED) models and the Transformer model primarily developed for Natural Language Processing (NLP). The deep learning model is trained with the tensorflow package using publicly available laboratory data sets in standard binary file format in numpy. The utility functions for reading data files, configuring model hyperparameters, constructing the CED and Transformer models, training and testing of the models are defined in python module files. The workflow of training the models for labquake future predictions and the multiple GPU’s rapid model hyperparameter optimization as described in the journal article, are demonstrated in accompanying python script files and Jupyter notebooks.

Wang, Kun↗