Engineering Papers⌕ Search

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.

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

At least 361 records · Page 20
All sourcesNASA NTRSDOE OSTI
DOE OSTI2016

TU-FG-201-07: Development of SRS Conical Collimator Collision Prediction Software for Radiation Treatment Safety

Purpose: Stereotactic radiosurgery (SRS) treatments using conical collimators can potentially result in gantry collision with treatment table due to limited collision-clear spaces. An in-house software was developed to help the SRS treatment planner mitigate potential SRS conical collimator (Varian Medical System, Palo Alto, CA) collisions with the treatment table. This software was designed to remove treatment re-planning secondary to unexpected collisions. Methods: A BrainLAB SRS ICT Frameless Extension used for SRS treatments in our clinic was mathematically modelled using surface points registered to the 3D co-ordinate space of the couch extension. The surface points are transformed based on the treatment isocenter point and potential collisions are determined in 3D space for couch and gantry angle combinations. The distance between the SRS conical collimators and LINAC isocenter is known. The collision detection model was programmed in MATLAB (Mathwork, Natick, MA) to display graphical plots of the calculations, and the plotted data is used to avoid the gantry and couch angle combinations that would likely result in a collision. We have utilized the cone collision tool for 23 SRS cone treatment plans (8 retrospective and 15 prospective for 10 patients). Results: Twenty one plans strongly agreed with the software tool prediction for collision. However, in two plans, a collision was observed with a 0.5 cm margin when the software predicted no collision. Therefore, additional margins were added to the clearance criteria in the program to achieve a lower risk of actual collisions. Conclusion: Our in-house developed collision check software successfully avoided SRS cone re-planning by 91.3% due to a reduction in cone collisions with the treatment table. Future developments to our software will include a CT image data set based collision prediction model as well as a beam angle optimization tool to avoid normal critical tissues as well as previously treated lesions.

60 APPLIED LIFE SCIENCES↗
NASA NTRS2008

Constellation Training Facility Support

The National Aeronautics and Space Administration is developing the next set of vehicles that will take men back to the moon under the Constellation Program. The Constellation Training Facility (CxTF) is a project in development that will be used to train astronauts, instructors, and flight controllers on the operation of Constellation Program vehicles. It will also be used for procedure verification and validation of flight software and console tools. The CxTF will have simulations for the Crew Exploration Vehicle (CEV), Crew Module (CM), CEV Service Module (SM), Launch Abort System (LAS), Spacecraft Adapter (SA), Crew Launch Vehicle (CLV), Pressurized Cargo Variant CM, Pressurized Cargo Variant SM, Cargo Launch Vehicle, Earth Departure Stage (EDS), and the Lunar Surface Access Module (LSAM). The Facility will consist of part-task and full-task trainers, each with a specific set of mission training capabilities. Part task trainers will be used for focused training on a single vehicle system or set of related systems. Full task trainers will be used for training on complete vehicles and all of its subsystems. Support was provided in both software development and project planning areas of the CxTF project. Simulation software was developed for the hydraulic system of the Thrust Vector Control (TVC) of the ARES I launch vehicle. The TVC system is in charge of the actuation of the nozzle gimbals for navigation control of the upper stage of the ARES I rocket. Also, software was developed using C standards to send and receive data to and from hand controllers to be used in CxTF cockpit simulations. The hand controllers provided movement in all six rotational and translational axes. Under Project Planning & Control, support was provided to the development and maintenance of integrated schedules for both the Constellation Training Facility and Missions Operations Facilities Division. These schedules maintain communication between projects in different levels. The CxTF support provided is one that requires continuous maintenance since the project is still on initial development phases.

Flores, Jose M.↗
DOE OSTI2014

SU-E-T-194: From Dicom-RT to Radiobiological Dose Metrics in 5 Minutes

Purpose: To develop a flexible and standalone framework for batch calculation of radiobiological dose metrics from Dicom-RT. Methods: Software has been developed which allows (1) The calculation of DVH data from DICOM dose and structure files (DVHgenerator), (2) Calculation of a wide range of radiobiological metrics from this data (CompPlanGui). Both these tools are run via graphical user interface (GUI), making them fast and simple. Part 1 is a new tool which has not previously been published, whilst part 2 is a GUI overlay for the previously published software ‘Comp-Plan’ (Holloway et. al., Medical Dosimetry, 2012), previously reliant on command line interface. The time taken for an experienced user to evaluate a test case of 6 plans with and without CompPlanGUI was quantified. Results: The DVH-generator has been found to be faster, more robust and require far less physical memory then using alternative software solutions for the same purpose. The Comp Plan GUI significantly reduces the amount of time required to set up a base directory, eliminates code crashes arising from typographical errors, and renders the code far more accessible to non-expert users. It took an experienced user of the code around 3 minutes to set up a base directory of 6 plans compared around 8 minutes without, indicating that using CompPlanGUI reduced setup time by over 50%. Conclusion: A standalone GUI based framework has developed which allows for the batch calculation of radiobiological dose metrics directly from Dicom-RT files. As with the original code, this work will be made freely available on request, as well as via matlab file exchange.

07 ISOTOPE AND RADIATION SOURCES↗
NASA NTRS2017

Playbook Data Analysis Tool: Collecting Interaction Data from Extremely Remote Users

Typically, user tests for software tools are conducted in person. At NASA, the users may be located at the bottom of the ocean in a pressurized habitat, above the atmosphere in the International Space Station, or in an isolated capsule on a simulated asteroid mission. The Playbook Data Analysis Tool (P-DAT) is a human-computer interaction (HCI) evaluation tool that the NASA Ames HCI Group has developed to record user interactions with Playbook, the group's existing planning-and-execution software application. Once the remotely collected user interaction data makes its way back to Earth, researchers can use P-DAT for in-depth analysis. Since a critical component of the Playbook project is to understand how to develop more intuitive software tools for astronauts to plan in space, P-DAT helps guide us in the development of additional easy-to-use features for Playbook, informing the design of future crew autonomy tools.P-DAT has demonstrated the capability of discreetly capturing usability data in amanner that is transparent to Playbook’s end-users. In our experience, P-DAT data hasalready shown its utility, revealing potential usability patterns, helping diagnose softwarebugs, and identifying metrics and events that are pertinent to Playbook usage aswell as spaceflight operations. As we continue to develop this analysis tool, P-DATmay yet provide a method for long-duration, unobtrusive human performance collectionand evaluation for mission controllers back on Earth and researchers investigatingthe effects and mitigations related to future human spaceflight performance.

in-flight monitoring↗
DOE OSTI2014

SU-E-T-01: 2-D Characterization of DLG Among All MLC Leaf Pairs

Purpose: The aim of this study is to evaluate the variation of dosimetric leaf-gap (DLG) along the travel path of each MLC leaf pair. This study evaluates whether the spatial variations in DLG could cause dose differences between TPS-calculated and measured dose. Methods: The 6MV DLG values were measured for all leaf pairs in the direction of leaf motion using a 2-D diode array and 0.6cc ion chamber. These measurements were performed on two Varian Linacs, employing the Millennium 120-leaf MLC and a 2-D-DLG variation map was created via in-house software. Several test plans were created with sweeping MLC fields using constant gaps from 2mm to 10mm and corrected for 2-D variation utilizing in-house software. Measurements were performed utilizing the MapCHECK at 5.0cm depth for plans with and without the 2-D DLG correction and compared to the TPS calculated dose via gamma analysis (3%/3mm). Results: The measured DLGs for the middle 40 MLC leaf pairs (0.5cm width) were very similar along the central superior-inferior axis, with maximum variation of 0.2mm. The outer 20 MLC leaf pairs (1.0cm width) have DLG values from 0.32mm (mean) to 0.65mm (maximum) lower than the central leaf-pair, depending on off-axis distance. Gamma pass rates for the 2mm, 4mm, and 6mm sweep plans increased by 23.2%, 28.7%, and 26.0% respectively using the 2-D-DLG correction. The most improved dose points occur in areas modulated by the 1.0cm leaf-pairs. The gamma pass rate for the 10mm sweep plan increased by only 7.7%, indicating that the 2D variation becomes less significant for dynamic plans with larger MLC gaps. Conclusion: Fluences residing significantly off-axis with narrow sweeping gaps may exhibit significant variations from planned dose due to large differences between the true DLG exhibited by the 1.0cm leaf-pairs versus the constant DLG value utilized by the TPS for dose calculation.

60 APPLIED LIFE SCIENCES↗
DOE OSTI2014

SU-E-T-212: Influence of the Modulation Index On Daily Quality Assurance in Rapid Arc Treatments

Purpose: At our Institute some measured parameters for daily quality assurance (DQA) of dynamic arc therapy plans showed an unexpected behavior, therefore an investigation of the influence of the magnitude of modulation was conducted. Methods: In our clinical practice all DQAs of dynamic arc therapy plans are measured and analyzed prior to treatments using commercial software. For this study these plans were additionally exported to our in-house software written in MATLAB.The developed software extracted the leaf position, gantry angle, cumulative meterset weight of each control point (CP) and the total number of Monitor Units (MU) of each arc. Based on this information we calculated the leaf travel distance, irradiated segment area, number of MUs and dose rate for each CP. These data allowed us to calculate the modulation indexes (MI) of the plans, applying five different definitions of MI. The results were then correlated to the results of our DQA measurements.To validate the software, additional plans of known MIs were created and analyzed. For confirmation, the calculated parameters were compared to the segmented treatment table (STT) coming from the treatment planning system. Results: All calculated CP-parameters matched the STT by 99% or better. For linac 1, the comparison of the MI evaluation and the DQA results showed a slight tendency: 91.3% failed DQA plans had a MI lower than the average value. For this definition we consider that the lower the MI the higher the modulation. The results of the linac 2 present no significant relevance due to the low sample sizes for each DQA software. Conclusion: Available data and given definitions of the modulation index do not bring conclusive results; one cannot find a clear and distinct correlation with the failure of the DQA. The ongoing analysis with an increased sample size might lead to another conclusion.

07 ISOTOPE AND RADIATION SOURCES↗
NASA NTRS1993

Network upgrades

The NASA Scientific and Technical Information (STI) Project modernization plan covers both software and hardware upgrades. On the hardware side, replacing terminals with PC's will enhance office automation functions, provide mainframe and computer network systems access, and facilitate client/server functions. The modernization plan upgrades will involve commercial off-the-shelf software, user interface and client development tools, and the redesign and integration of application systems and software.

Ridgeway, Roland↗
DOE OSTI2016

Power & Water Facility and Infrastructure Planning: CRADA Final Report

Los Alamos National Laboratory (LANL) has developed software and expertise for planning power grids and for examining the human resource issues for a nuclear power program. These programs, and other LANL software innovations, can offer an efficient manner in which to assist the power and water generation industries in both developed and undeveloped countries.

24 POWER TRANSMISSION AND DISTRIBUTION↗
DOE OSTI2023

MARVEL 90% Final Design Report

This document provides documentation of the Microreactor Applications Research Validation and Evaluation Project’s (MARVEL) 90% Final Design, as required by U.S. Department of Energy (DOE) Standard-1189, “Integration of Safety into the Design Process." Per DOE-STD-1189-2016, the 90% Final Design documentation focuses on design completion, at a level capable of supporting procurement, construction, testing, and operation. At this phase, the design organization finalizes the hazards and accident analyses, Fire Hazard Analysis (FHA), security vulnerability assessments, and other supporting analyses for design completion. The objective of this report is to provide a high-level summary of the design thus far and provide references including, but not limited to, the following design deliverables: • Complete final drawings, specifications and commercial grade dedications that may be released for bid and/or construction. • Clearly defined testing plans for the safety and functionality of all subsystems. • Quality Assurance Program for Design, Testing and Procurement. • Software Quality Assurance Plan. • Code of Record (COR), applicable design requirements including codes and standards. • Final design that meets all the requirements stipulated in the COR. • Final design review, consisting of final validation of comment resolution from previous reviews, and a review of any additional developments since the last review. • Updated Safety Design Strategy. • Hazard Analysis. • Fire Hazard Analysis. • Accident analysis. • Security vulnerability assessment. • Current and detailed cost estimate. • Current construction schedule, and • Risk & Opportunities Assessment.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
NASA NTRS1996

Software Program: Software Management Guidebook

The purpose of this NASA Software Management Guidebook is twofold. First, this document defines the core products and activities required of NASA software projects. It defines life-cycle models and activity-related methods but acknowledges that no single life-cycle model is appropriate for all NASA software projects. It also acknowledges that the appropriate method for accomplishing a required activity depends on characteristics of the software project. Second, this guidebook provides specific guidance to software project managers and team leaders in selecting appropriate life cycles and methods to develop a tailored plan for a software engineering project.

Source record↗
NASA NTRS1992

Coordinating space telescope operations in an integrated planning and scheduling architecture

The Heuristic Scheduling Testbed System (HSTS), a software architecture for integrated planning and scheduling, is discussed. The architecture has been applied to the problem of generating observation schedules for the Hubble Space Telescope. This problem is representative of the class of problems that can be addressed: their complexity lies in the interaction of resource allocation and auxiliary task expansion. The architecture deals with this interaction by viewing planning and scheduling as two complementary aspects of the more general process of constructing behaviors of a dynamical system. The principal components of the software architecture are described, indicating how to model the structure and dynamics of a system, how to represent schedules at multiple levels of abstraction in the temporal database, and how the problem solving machinery operates. A scheduler for the detailed management of Hubble Space Telescope operations that has been developed within HSTS is described. Experimental performance results are given that indicate the utility and practicality of the approach.

Muscettola, Nicola↗
NASA NTRS2003

Abstract-Reasoning Software for Coordinating Multiple Agents

A computer program for scheduling the activities of multiple agents that share limited resources has been incorporated into the Automated Scheduling and Planning Environment (ASPEN) software system, aspects of which have been reported in several previous NASA Tech Briefs articles. In the original intended application, the agents would be multiple spacecraft and/or robotic vehicles engaged in scientific exploration of distant planets. The program could also be used on Earth in such diverse settings as production lines and military maneuvers. This program includes a planning/scheduling subprogram of the iterative repair type that reasons about the activities of multiple agents at abstract levels in order to greatly improve the scheduling of their use of shared resources. The program summarizes the information about the constraints on, and resource requirements of, abstract activities on the basis of the constraints and requirements that pertain to their potential refinements (decomposition into less-abstract and ultimately to primitive activities). The advantage of reasoning about summary information is that time needed to find consistent schedules is exponentially smaller than the time that would be needed for reasoning about the same tasks at the primitive level.

Clement, Bradley↗
DOE OSTI2024

Integrated solution techniques for security constrained unit commitment problem

Apparatus and methods are disclosed for solving Mixed Integer Programming (MIP) problems, such as Security Constrained Unit Commitment (SCUC) problems used by power grid authorities to perform day-ahead market clearing. In certain examples, a plurality of threads of a software tool implementing a concurrent optimizer can be executed concurrently and sequentially to generate new solutions to a SCUC problem for an upcoming planning horizon. Data can be shared among the concurrently executing threads, such as intermediate/incumbent solutions and hints regarding the fixing of variables and constraints to reduce the size of the SCUC problem. In some examples, the threads are seeded with historical solutions from prior planning horizons. The software tool can select a best solution from the solutions generated by the threads, and determine dispatch instructions for a device coupled to the power grid for the upcoming planning horizon based at least in part on the selected solution.

Pan, Feng↗
NASA NTRS2005

Robotic and Human-Tended Collaborative Drilling Automation for Subsurface Exploration

Future in-situ lunar/martian resource utilization and characterization, as well as the scientific search for life on Mars, will require access to the subsurface and hence drilling. Drilling on Earth is hard - an art form more than an engineering discipline. Human operators listen and feel drill string vibrations coming from kilometers underground. Abundant mass and energy make it possible for terrestrial drilling to employ brute-force approaches to failure recovery and system performance issues. Space drilling will require intelligent and autonomous systems for robotic exploration and to support human exploration. Eventual in-situ resource utilization will require deep drilling with probable human-tended operation of large-bore drills, but initial lunar subsurface exploration and near-term ISRU will be accomplished with lightweight, rover-deployable or standalone drills capable of penetrating a few tens of meters in depth. These lightweight exploration drills have a direct counterpart in terrestrial prospecting and ore-body location, and will be designed to operate either human-tended or automated. NASA and industry now are acquiring experience in developing and building low-mass automated planetary prototype drills to design and build a pre-flight lunar prototype targeted for 2011-12 flight opportunities. A successful system will include development of drilling hardware, and automated control software to operate it safely and effectively. This includes control of the drilling hardware, state estimation of both the hardware and the lithography being drilled and state of the hole, and potentially planning and scheduling software suitable for uncertain situations such as drilling. Given that Humans on the Moon or Mars are unlikely to be able to spend protracted EVA periods at a drill site, both human-tended and robotic access to planetary subsurfaces will require some degree of standalone, autonomous drilling capability. Human-robotic coordination will be important, either between a robotic drill and humans on Earth, or a human-tended drill and its visiting crew. The Mars Analog Rio Tinto Experiment (MARTE) is a current project that studies and simulates the remote science operations between an automated drill in Spain and a distant, distributed human science team. The Drilling Automation for Mars Exploration (DAME) project, by contrast: is developing and testing standalone automation at a lunar/martian impact crater analog site in Arctic Canada. The drill hardware in both projects is a hardened, evolved version of the Advanced Deep Drill (ADD) developed by Honeybee Robotics for the Mars Subsurface Program. The current ADD is capable of 20m, and the DAME project is developing diagnostic and executive software for hands-off surface operations of the evolved version of this drill. The current drill automation architecture being developed by NASA and tested in 2004-06 at analog sites in the Arctic and Spain will add downhole diagnosis of different strata, bit wear detection, and dynamic replanning capabilities when unexpected failures or drilling conditions are discovered in conjunction with simulated mission operations and remote science planning. The most important determinant of future 1unar and martian drilling automation and staffing requirements will be the actual performance of automated prototype drilling hardware systems in field trials in simulated mission operations. It is difficult to accurately predict the level of automation and human interaction that will be needed for a lunar-deployed drill without first having extensive experience with the robotic control of prototype drill systems under realistic analog field conditions. Drill-specific failure modes and software design flaws will become most apparent at this stage. DAME will develop and test drill automation software and hardware under stressful operating conditions during several planned field campaigns. Initial results from summer 2004 tests show seven identifi distinct failure modes of the drill: cuttings-removal issues with low-power drilling into permafrost, and successful steps at executive control and initial automation.

Glass, Brian↗
NASA NTRS1991

Using C to build a satellite scheduling expert system: Examples from the Explorer platform planning system

Recently, many expert systems were developed in a LISP environment and then ported to the real world C environment before the final system is delivered. This situation may require that the entire system be completely rewritten in C and may actually result in a system which is put together as quickly as possible with little regard for maintainability and further evolution. With the introduction of high performance UNIX and X-windows based workstations, a great deal of the advantages of developing a first system in the LISP environment have become questionable. A C-based AI development effort is described which is based on a software tools approach with emphasis on reusability and maintainability of code. The discussion starts with simple examples of how list processing can easily be implemented in C and then proceeds to the implementations of frames and objects which use dynamic memory allocation. The implementation of procedures which use depth first search, constraint propagation, context switching and a blackboard-like simulation environment are described. Techniques for managing the complexity of C-based AI software are noted, especially the object-oriented techniques of data encapsulation and incremental development. Finally, all these concepts are put together by describing the components of planning software called the Planning And Resource Reasoning (PARR) shell. This shell was successfully utilized for scheduling services of the Tracking and Data Relay Satellite System for the Earth Radiation Budget Satellite since May 1987 and will be used for operations scheduling of the Explorer Platform in November 1991.

Mclean, David R.↗
NASA NTRS1987

Expert system verification concerns in an operations environment

The Space Shuttle community is currently developing a number of knowledge-based tools, primarily expert systems, to support Space Shuttle operations. It is proposed that anticipating and responding to the requirements of the operations environment will contribute to a rapid and smooth transition of expert systems from development to operations, and that the requirements for verification are critical to this transition. The paper identifies the requirements of expert systems to be used for flight planning and support and compares them to those of existing procedural software used for flight planning and support. It then explores software engineering concepts and methodology that can be used to satisfy these requirements, to aid the transition from development to operations and to support the operations environment during the lifetime of expert systems. Many of these are similar to those used for procedural hardware.

Goodwin, Mary Ann↗
NASA NTRS1989

Shuttle relative navigation of a tethered satellite mission with current on board software

A Shuttle mission planned in 1991 will test the feasibility of tethers in space. This mission, a joint effort between Italy and the United States, will connect a satellite (built by the Italians) to the Shuttle with a 20 km long tether. This mission poses unique navigation problems. The flight software on the Shuttle was never designed to account for the low level acceleration that is generated by the gravity gradient. IMUs on the Shuttle was never designed to account for the low level acceleration that is generated by the gravity gradient. Inertial Maneuvering Units on the shuttle will sense the acceleration of the tether but it turns out that incorporating the continuous accelerometer noise also generates large error growth. Relative navigation is another important issue since the majority of the mission will be conducted while the satellite is out of the visual range of the crew. Some kind of feedback on the motion of the satellite will be desirable. Feedback of the satellite motion can be generated by using the rendezvous radar. To process the radar measurements, the flight software uses a 13 state Kalman Filter, but unfortunately with the filter currently tuned as it is, valid measurements tend to be ignored. This is due to the constraint of the tether on the satellite, which is an unmodeled force. Analysis shows that with proper tuning, relative navigation is possible.

Lee, Kevin A.↗
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↗