SEARCH · Engineering Papers

Results for “Planning software”

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 OSTI2017

Computerized System for Safety Verification of External Beam Radiation Therapy Planning

Purpose: To report an assessment of in-house software, Verifier, developed to improve efficacy and efficiency of the radiation therapy (RT) treatment planning process and quality control review (QCR). Methods and Materials: Radiation therapy plan parameters retrieved from our treatment planning database are used by automated tests to give 75 types of warnings, such as prescription and plan discrepancies. The software is continuously updated on the basis of new issues, ideas, and planning policies. Verifier was retrospectively assessed (2007-2015) by examining impact on treatment plan revisions, frequency of quality improvement incident reports of avoidable RT plan-related safety events, unaddressed issues, and staff efficiency. Results: Plan revisions for specific issues declined dramatically in response to implementation of corresponding Verifier tests. Between 2012 and 2015 our institution's total rate of plan revisions dropped from 18.0% to 11.2%. Between 2008 and 2015 specific tests were added to Verifier while the rate of corresponding avoidable safety events was reduced from 0.34% to 0.00% over the same period. Simulations suggest Verifier saves approximately 2 to 5 minutes per QCR. Conclusions: The decrease in quantifiable metrics of plan revisions and incident reports suggests automatic RT plan-checking software enhances patient safety and clinical efficiency. Although only modest time savings may be gained using Verifier for the QCR itself, the greater impact on efficiency is through avoiding late-stage plan modifications and improving documentation via automation. We encourage other institutions to consider working toward adding similar technologies to enhance their RT quality assurance programs.

62 RADIOLOGY AND NUCLEAR MEDICINE↗

NASA NTRS2020

Is Structured Agile an Oxymoron? Tales from Implementing and Executing Agile in a US Government Environment

To paraphrase a famous quote, "No plan survives contact with the reality." Software (SW) development is often a classic example of this: whatever the plan was for a particular development, it often does not survive contact with technical realities, budget realities, program realities and schedule realities. Traditionally, SW development has followed a waterfall methodology with requirements being rigorously specified before the design, which was completed before the coding and unit testing started, which were in turn finished before validation and verification started. This model of SW engineering derives much from the HW engineering of large systems, and has been the standard methodology used in US government software acquisitions and systems for decades, with highly variable results. US Government SW requirements are built around Waterfall concepts, which assume that the plan will survive contact with reality, or at least that modifications to the plan are relatively small, and relatively few.Because of the inefficiencies and difficulties inherent in Waterfall, the commercial SW world started using a different SW development methodology called Agile more than 20 years ago. Agile believes that a plan should evolve and learn rapidly in response to the realities encountered. At its core, there are a few key elements of Agile:- A small team of people which is highly flexible and adaptive. The team collaborates and interoperates through sophisticated development architectures and release environments- An iterative, incremental development and release approach which is based upon the concept that knowledge comes from experience within the team, and that the team makes decisions based upon what it knows- A team culture which prizes transparency, inspection and adaptation. These values are necessary so that the team experience and decision making is transparent and responsive to the realities encountered during development and testingSo, how to use Agile in a US Government environment? GMSEC (Goddard Mission Services Evolution Center) develops satellite ground system software for NASA and other US Government agencies. The SW developed by the team contains a large code base of many applications used within satellite mission operations centers. It spans the full gamut of SW development types: from SW which is in a classic maintenance and sustainment mode, to new developments with a fairly well understood scope and approach, to new developments whose scope and approach are quite unclear and which require significant research and prototyping. Team members move between all of these different types of SW development. Waterfall was inadequate to the programmatic and technical needs of the team, as well as the various types of SW development being done. The software plan was not surviving contact with the technical and programmatic realities experienced by the team. To address this, the team started a small pilot project in 2016 to test the use of Agile within a small subset of the team for a new web services application. In early 2018, the use of Agile was expanded to the whole team and all the software, but we had to fulfill the NASA SW development requirements. And we needed to do this while still remaining true to the key Agile elements of transparency, inspection and adaption. In order to do this, the team worked very closely with the Software Process Improvement (SPI) team at NASA Goddard, as well as NASA engineering manageme

Beech, Theresa W.↗

DOE OSTI2014

SU-E-J-89: Motion Effects On Organ Dose in Respiratory Gated Stereotactic Body Radiation Therapy

Purpose: Existing reports on gated radiation therapy focus mainly on optimizing dose delivery to the target structure. This work investigates the motion effects on radiation dose delivered to organs at risk (OAR) in respiratory gated stereotactic body radiation therapy (SBRT). A new algorithmic tool of dose analysis is developed to evaluate the optimality of gating phase for dose sparing on OARs while ensuring adequate target coverage. Methods: Eight patients with pancreatic cancer were treated on a phase I prospective study employing 4DCT-based SBRT. For each patient, 4DCT scans are acquired and sorted into 10 respiratory phases (inhale-exhale- inhale). Treatment planning is performed on the average CT image. The average CT is spatially registered to other phases. The resultant displacement field is then applied on the plan dose map to estimate the actual dose map for each phase. Dose values of each voxel are fitted to a sinusoidal function. Fitting parameters of dose variation, mean delivered dose and optimal gating phase for each voxel over respiration cycle are mapped on the dose volume. Results: The sinusoidal function accurately models the dose change during respiratory motion (mean fitting error 4.6%). In the eight patients, mean dose variation is 3.3 Gy on OARs with maximum of 13.7 Gy. Two patients have about 100cm{sup 3} volumes covered by more than 5 Gy deviation. The mean delivered dose maps are similar to plan dose with slight deformation. The optimal gating phase highly varies across the patient, with phase 5 or 6 on about 60% of the volume, and phase 0 on most of the rest. Conclusion: A new algorithmic tool is developed to conveniently quantify dose deviation on OARs from plan dose during the respiratory cycle. The proposed software facilitates the treatment planning process by providing the optimal respiratory gating phase for dose sparing on each OAR.

60 APPLIED LIFE SCIENCES↗

NASA NTRS1990

JPL's Real-Time Weather Processor project (RWP) metrics and observations at system completion

As an integral part of the overall upgraded National Airspace System (NAS), the objective of the Real-Time Weather Processor (RWP) project is to improve the quality of weather information and the timeliness of its dissemination to system users. To accomplish this, an RWP will be installed in each of the Center Weather Service Units (CWSUs), located in 21 of the 23 Air Route Traffic Control Centers (ARTCCs). The RWP System is a prototype system. It is planned that the software will be GFE and that production hardware will be acquired via industry competitive procurement. The ARTCC is a facility established to provide air traffic control service to aircraft operating on Instrument Flight Rules (IFR) flight plans within controlled airspace, principally during the en route phase of the flight. Covered here are requirement metrics, Software Problem Failure Reports (SPFRs), and Ada portability metrics and observations.

Loesh, Robert E.↗

DOE OSTI2018

Combining Simulation and Emulation Systems for Smart Grid Planning and Evaluation

Software-defined networking (SDN) enables efficient network management. As the technology matures, utilities are looking to integrate those benefits to their operations technology (OT) networks. To help the community to better understand and evaluate the effects of such integration, we develop DSSnet, a testing platform that combines a power distribution system simulator and an SDN-based network emulator for smart grid planning and evaluation. DSSnet relies on a container-based virtual time system to achieve efficient synchronization between the simulation and emulation systems. To enhance the system scalability and usability, we extend DSSnet to support a distributed controller environment. To enhance system fidelity, we extend the virtual time system to support kernel-based switches. In conclusion, we also evaluate the system performance of DSSnet and demonstrate the usability of DSSnet with a resilient demand response application case study.

24 POWER TRANSMISSION AND DISTRIBUTION↗

DOE OSTI2018

CWA 15793 2011 Planning and Implementation Tool

This software, built on an open source platform called Electron (runs on Chromium and Node.js), is designed to assist organizations in the implementation of a biorisk management system consistent with the requirements of the international, publicly available guidance document CEN Workshop Agreement 15793:2011 (CWA 15793). The software includes tools for conducting organizational gap analysis against CWA 15793 requirements, planning tools to support the implementation of CWA 15793 requirements, and performance monitoring support. The gap analysis questions are based on the text of CWA 15793, and its associated guidance document, CEN Workshop Agreement 16393:2012. The authors have secured permission from the publisher of CWA 15793, the European Committee for Standardization (CEN), to use language from the document in the software, with the understanding that the software will be made available freely, without charge.

Gross, Alan↗

NASA NTRS1990

Resource Allocation Planning Helper (RALPH): Lessons learned

The current task of Resource Allocation Process includes the planning and apportionment of JPL's Ground Data System composed of the Deep Space Network and Mission Control and Computing Center facilities. The addition of the data driven, rule based planning system, RALPH, has expanded the planning horizon from 8 weeks to 10 years and has resulted in large labor savings. Use of the system has also resulted in important improvements in science return through enhanced resource utilization. In addition, RALPH has been instrumental in supporting rapid turn around for an increased volume of special what if studies. The status of RALPH is briefly reviewed and important lessons learned from the creation of an highly functional design team are focused on through an evolutionary design and implementation period in which an AI shell was selected, prototyped, and ultimately abandoned, and through the fundamental changes to the very process that spawned the tool kit. Principal topics include proper integration of software tools within the planning environment, transition from prototype to delivered to delivered software, changes in the planning methodology as a result of evolving software capabilities and creation of the ability to develop and process generic requirements to allow planning flexibility.

Durham, Ralph↗

NASA NTRS1980

Software cost/resource modeling

The Putnam method for planning the time/work effort component of software development is evaluated. This software costing model, based on Norden-Rayleigh product life cycle concepts, was applied to four development projects. The time/effort tradeoff leading to savings attainable when development time on a project is extended by a few months is demonstrated. The software equation which relates the principal parameters of development time, total effort, system size, and the development environment is presented.

Golden, J. R.↗

DOE OSTI2015

SU-E-T-308: Dosimetric Comparison of SBRT VMAT Treatment Plans Generated for 6 MV, 6 MV FFF, and 10 MV FFF Photon Beams

Purpose: To assess differences in treatment plan quality between VMAT stereotactic body plans generated using the 6 MV, 6 MV FFF, and 10 MV FFF modalities available in our clinic. Plans for lung, spine, and other sites were compared to see if there is any advantage of one modality over the other. Methods: Treatment plans done for actual SBRT patients were selected. Groups of ten lung plans, five spine plans, and five plans from other sites were selected. New treatment plans were generated for each plan using the Varian Eclipse AAA algorithm. The constraints were kept the same as used in the actual plans, but the same version of software was used to generate plans for the three modalities. In addition, because there are natural variations in plans re-done with the same dose constraints, one of the lung plans was repeated ten times to assess those differences. Volumes of the 100%, 90%, 50%, 20% and 10% isodose surfaces were compared. Maximum dose two centimeters from the PTV were compared, as well as the volume of the 105% isodose surface outside of the PTV. In addition, the 20 Gray lung volume was compared for the lung plans. The values of these parameters were divided by the values for the 6 MV plans for comparison. Average and standard deviations were obtained for quantities in each group. The Student t test was done to determine if differences were seen at the 95% confidence level. Results: Comparison of the treatment plans showed no significant differences when assessing these volumes and doses. There were not any trends seen when comparing modalities as a function of PTV volume either. Conclusion: There is no obvious dosimetric advantage in selection of one modality over another for these types of SBRT plans.

60 APPLIED LIFE SCIENCES↗

NASA NTRS2019

Overview of the PLEXIL Plan Execution Technology and its Applications in Autonomous Piloting Projects at NASA

Automated planning is a key Artificial Intelligence technology enabling Unmanned Aerial Systems (UAS) and the eminent reality of Urban Air Mobility (UAM). It produces plans, which formalize procedures often performed by humans. Plans differ from other kinds of computer programs in their ability to react and interact with a dynamically changing environment. Aviation plans must encode the procedural knowledge, reasoning capability, and capacity for multi-tasking held by competent human pilots. Correct execution of these plans (performed by software called an executive) in the dynamic airspace environment is vital to the success of each automated flight, and the safety of the vehicle and all things in its path. In the early 2000s NASA developed a plan representation language and executive called PLEXIL (Plan Execution Interchange Language) that has successfully been applied in several NASA aviation and UAS projects. Autonomy Operating System (AOS), Cockpit Hierarchical Automated Planning and Execution (CHAP-E), and ICAROUS are all projects that have used PLEXIL to help encode and automatically execute flight procedures, some normally performed by human pilots. AOS also automates a subset of pilot/Air Traffic Control communication towards enabling UAS entry into the National Airspace. PLEXIL has been open-source software since 2008 and has seen usage in a wide range of prototypical autonomy applications in academia, government, and industry. In this presentation, we describe PLEXIL and highlight its significant accomplishments in the aviation domain.

Dalal, Michael↗

NASA NTRS2005

NASA Tech Briefs, September 2005

Topivs include: Diamond-Coated Carbon Nanotubes for Efficient Field Emission; Improved Anode Coatings for Direct Methanol Fuel Cells; Advanced Ablative Insulators and Methods of Making Them; PETIs as High-Temperature Resin-Transfer-Molding Materials; Stable Polyimides for Terrestrial and Space Uses; Low-Density, Aerogel-Filled Thermal-Insulation Tiles; High-Performance Polymers Having Low Melt Viscosities; Nonflammable, Hydrophobic Aerogel Composites for Insulation; Front-Side Microstrip Line Feeding a Raised Antenna Patch; Medium-Frequency Pseudonoise Georadar; Facilitating Navigation Through Large Archives; Program for Weibull Analysis of Fatigue Data; Comprehensive Micromechanics-Analysis Code - Version 4.0; Component-Based Visualization System; Software for Engineering Simulations of a Spacecraft; LabVIEW Interface for PCI-SpaceWire Interface Card; Path Following with Slip Compensation for a Mars Rover; International Space Station Electric Power System Performance Code-SPACE; Software for Automation of Real-Time Agents, Version 2; Software for Optimizing Plans Involving Interdependent Goals; Computing Gravitational Fields of Finite-Sized Bodies; Custom Sky-Image Mosaics from NASA's Information Power Grid; ANTLR Tree Grammar Generator and Extensions; Generic Kalman Filter Software; Alignment Stage for a Cryogenic Dilatometer; Rugged Iris Mechanism; Treatments To Produce Stabilized Aluminum Mirrors for Cryogenic Uses; Making AlNx Tunnel Barriers Using a Low-Energy Nitrogen-Ion Beam; Making Wide-IF SIS Mixers with Suspended Metal-Beam Leads; Sol-Gel Glass Holographic Light-Shaping Diffusers; Automated Counting of Particles To Quantify Cleanliness; Phase Correction for GPS Antenna with Nonunique Phase Center; Compact Infrasonic Windscreen; Broadband External-Cavity Diode Laser; High-Efficiency Solar Cells Using Photonic-Bandgap Materials; Generating Solid Models from Topographical Data; Computationally Lightweight Air-Traffic-Control Simulation; Spool Valve for Switching Air Flows Between Two Beds; Partial Model of Insulator/ Insulator Contact Charging; Asymmetric Electrostatic Radiation Shielding for Spacecraft; and Reusable Hybrid Propellant Modules for Outer-Space Transport.

Source record↗

NASA NTRS2004

Software for Analyzing Laminar-to-Turbulent Flow Transitions

Software assurance is the planned and systematic set of activities that ensures that software processes and products conform to requirements, standards, and procedures. Examples of such activities are the following: code inspections, unit tests, design reviews, performance analyses, construction of traceability matrices, etc. In practice, software development projects have only limited resources (e.g., schedule, budget, and availability of personnel) to cover the entire development effort, of which assurance is but a part. Projects must therefore select judiciously from among the possible assurance activities. At its heart, this can be viewed as an optimization problem; namely, to determine the allocation of limited resources (time, money, and personnel) to minimize risk or, alternatively, to minimize the resources needed to reduce risk to an acceptable level. The end result of the work reported here is a means to optimize quality-assurance processes used in developing software. This is achieved by combining two prior programs in an innovative manner

Chang, Chau-Lyan↗

NASA NTRS2004

Software for Optimizing Quality Assurance of Other Software

Feather, Martin↗

DOE OSTI2016

SU-F-T-25: Design and Implementation of a Multi-Purpose Applicator for Pelvic Brachytherapy Applications

Purpose: The current generation of inflatable multichannel brachytherapy applicators, such as the Varian Capri, have limited implementation to only vaginal and rectal cancers. While there are similar designs utilizing rigid, non-inflatable applicators, these alternatives could cause increased dose to surrounding tissue due to air gaps. Modification of the Capri could allow for easier treatment planning by reducing the number of channels and increased versatility by modifying the applicator to include an attachable single tandem for cervical or multiple tandems for endometrial applications. Methods: A Varian Capri applicator was simulated in water to replicate a patient. Multiple plans were optimized to deliver a prescribed dose of 100 cGy at 5mm away from the exterior of the applicator using six to thirteen existing channels. The current model was expanded upon to include a detachable tandem or multiple tandoms to increase its functionality to both cervical and endometrial cancers. Models were constructed in both threedimensional rendering software and Monte Carlo to allow prototyping and simulations. Results: Treatment plans utilizing six to thirteen channels produced limited dosimetric differences between channel arrangements, with a seven channel plan very closely approximating the thirteen channels. It was concluded that only seven channels would be necessary in future simulations to give an accurate representation of the applicator. Tandem attachments were prototyped for the applicator to demonstrate the ease of which they could be included. Future simulation in treatment planning software and Monte Carlo results will be presented to further define the ideal applicator geometry Conclusion: The current Capri applicator design could be easily modified to increase applicability to include cervical and endometrial treatments in addition to vaginal and rectal cancers. This new design helps in a more versatile single use applicator that can easily be inserted and to further reduce dose to critical structures during brachytherapy treatments.

60 APPLIED LIFE SCIENCES↗

NASA NTRS2000

Putting ROSE to Work: A Proposed Application of a Request-Oriented Scheduling Engine for Space Station Operations

Scheduling engines are found at the core of software systems that plan and schedule activities and resources. A Request-Oriented Scheduling Engine (ROSE) is one that processes a single request (adding a task to a timeline) and then waits for another request. For the International Space Station, a robust ROSE-based system would support multiple, simultaneous users, each formulating requests (defining scheduling requirements), submitting these requests via the internet to a single scheduling engine operating on a single timeline, and immediately viewing the resulting timeline. ROSE is significantly different from the engine currently used to schedule Space Station operations. The current engine supports essentially one person at a time, with a pre-defined set of requirements from many payloads, working in either a "batch" scheduling mode or an interactive/manual scheduling mode. A planning and scheduling process that takes advantage of the features of ROSE could produce greater customer satisfaction at reduced cost and reduced flow time. This paper describes a possible ROSE-based scheduling process and identifies the additional software component required to support it. Resulting changes to the management and control of the process are also discussed.

Jaap, John↗

NASA NTRS1995

Automated Planning Of Spacecraft Telecommunications

Computer program known as SWIfT (Software for What-If Telecommunications) is user-friendly, modular, portable, window-based software tool. Accelerates and automates planning of antenna usage for spacecraft telecommunication systems and enables predictions of performances of such systems.

Veregge, John R.↗

DOE OSTI2020

Lightweight Software Quality Practice PSIP: Productivity Sustainability Improvement Planning.

Abstract not provided.

Raybourn, Elaine M.↗

DOE OSTI2017

The WTP Immobilized LAW Formulation Algorithm: Recent Efforts Toward Software Development - 17342

The immobilized low-activity waste (ILAW) product from WTP must meet certain requirements and processing constraints. The strategy for controlling ILAW product composition uses the ILAW formulation algorithm. This algorithm is approved by the DOE Office of River Protection (ORP) for use in calculating melter feed recipes that will produce acceptable ILAW product during Low-Activity Waste (LAW) Facility commissioning. The calculations performed by the algorithm have been demonstrated using a sophisticated spreadsheet, but this spreadsheet is not expected to support continuous operation. Efforts are underway to develop software that will support glass formulation during operation. Recent work toward software development includes an examination of assumptions made in the algorithm about expected LAW Facility operation, and spreadsheet calculations to formulate glass for potential LAW compositions under the direct feed LAW (DFLAW) strategy that ORP has adopted. The documentation of the ILAW algorithm is the planned basis for software development. However, some assumptions made in the current algorithm's mass balance logic do not match the matured design and expected operation of the LAW Facility. A self-assessment effort evaluated the validity of these assumptions by reviewing design documents, in order to identify opportunities to align the algorithm's mass balance logic with the matured design and ensure that the developed software supports continuous LAW Facility operation. Several improvement opportunities were identified and are discussed. The results of ILAW algorithm calculations to formulate glass for eighteen challenging LAW compositions indicate that the current WTP baseline LAW glass models are sufficiently robust to accommodate DFLAW. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗