Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “software estimations”

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 433 records · Page 24

Moving Toward an Optimal and Automated Geospatial Network for CCUS Infrastructure

Modifications in the global climate are being driven by the anthropogenic release of greenhouse gases (GHG) including carbon dioxide (CO 2 ) (Middleton et al. 2014). CO 2 emissions have, for example, been directly linked to an increase in total global temperature (Seneviratne et al. 2016). Strategies that limit CO 2 emissions—like CO 2 capture, utilization, and storage (CCUS) technology—can greatly reduce emissions by capturing CO 2 before it is released to the atmosphere. However, to date CCUS technology has not been developed at a large commercial scale despite several promising high profile demonstration projects (Middleton et al. 2015). Current CCUS research has often focused on capturing CO 2 emissions from coal-fired power plants, but recent research at Los Alamos National Laboratory (LANL) suggests focusing CCUS CO 2 capture research upon industrial sources might better encourage CCUS deployment. To further promote industrial CCUS deployment, this project builds off current LANL research by continuing the development of a software tool called SimCCS, which estimates a regional system of transport to inject CO 2 into sedimentary basins. The goal of SimCCS, which was first developed by Middleton and Bielicki (2009), is to output an automated and optimal geospatial industrial CCUS pipeline that accounts for industrial source and sink locations by estimating a Delaunay triangle network which also minimizes topographic and social costs (Middleton and Bielicki 2009). Current development of SimCCS is focused on creating a new version that accounts for spatial arrangements that were not available in the previous version. This project specifically addresses the issue of non-unique Delaunay triangles by adding additional triangles to the network, which can affect how the CCUS network is calculated.

54 ENVIRONMENTAL SCIENCES↗

Fast BLT Code

This note discusses numerical algorithmic software design considerations and performance estimates for a fast BLT coupling code [1] written in c++. The aim of this code is to conduct faster parameter studies over line orientations. The original matlab code was written by Mike Rivera. Art Barnes ported this code to julia. I rewrote portions of the code for speed improvement, mainly to eliminate some redundant computation when calculating many line orientations. But this code is still far from optimal.

97 MATHEMATICS AND COMPUTING↗

Analysis of ISOCS Measurements to Establish Methodology Uncertainty

Qualification measurements were performed at the US Department of Energy’s (DOE’s) Oak Ridge National Laboratory (ORNL) on a variety of measurement standards. These measurements will be used to qualify the In-Situ Object Counting System (ISOCS) measurement method with a high-purity germanium (HPGe) detector for use at ORNL. Measured items include uranium isotopic standards, filter papers coated with uranium oxide (U 3 O 8 ), U 3 O 8 line sources, and a uranium tetrafluoride (UF 4 ) source. The 235 U mass was estimated using the ISOCS calibration software for each source and compared with the declared isotope mass value.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

Human Dosimetry and Preliminary Tumor Distribution of (superscript)18F-Fluoropaclitaxel in Healthy Volunteers and Newly Diagnosed Breast Cancer Patients Using PET/CT

{sup 18}F-fluoropaclitaxel is a radiolabeled form of paclitaxel, a widely used chemotherapy agent. Preclinical data suggest that {sup 18}F-fluoropaclitaxel may be a reasonable surrogate for measuring the uptake of paclitaxel. As a substrate of P-glycoprotein, a drug efflux pump associated with multidrug resistance, {sup 18}F-fluoropaclitaxel may also be useful in identifying multidrug resistance and predicting tumor response for drugs other than paclitaxel. After informed consent was obtained, 3 healthy volunteers and 3 patients with untreated breast cancer (neoadjuvant chemotherapy candidates, tumor size > 2 cm) received an intravenous infusion of {sup 18}F-fluoropaclitaxel and then underwent PET/CT. Healthy volunteers underwent serial whole-body imaging over an approximately 3-h interval, and organ {sup 18}F residence times were determined from the time-activity curves uncorrected for decay to determine dosimetry. Radiation dose estimates were calculated using OLINDA/EXM software. For breast cancer patients, dynamic imaging of the primary tumor was performed for 60 min, followed by static whole-body scans at 1 and 2 h after injection. Dosimetry calculations showed that the gallbladder received the highest dose (229.50 {mu}Gy/MBq [0.849 rad/mCi]), followed by the small and large intestines (161.26 {mu}Gy/MBq [0.597 rad/mCi] and 184.59 {mu}Gy/MBq [0.683 rad/mCi]). The resultant effective dose was 28.79 {mu}Gy/MBq (0.107 rem/mCi). At approximately 1 h after injection, an average of 42% of the decay-corrected activity was in the gastrointestinal system, with a mean of 0.01% in the tumor. All 3 breast cancer patients showed retention of {sup 18}F-fluoropaclitaxel and ultimately demonstrated a complete pathologic response (no invasive cancer in the breast or axillary nodes) to chemotherapy that included a taxane (either paclitaxel or docetaxel) at surgical resection. The tumor-to-background ratio increased with time to a maximum of 7.7 at 20 min. This study demonstrates the feasibility of using {sup 18}F-fluoropaclitaxel PET/CT tumor imaging and provides radiation dosimetry measurements in humans. Although further study is needed, it is hoped that the measured intratumoral {sup 18}F-fluoropaclitaxel distribution can serve as a surrogate for paclitaxel, and potentially other chemotherapeutic agent retention, in solid tumors.

18F-Fluoropaclitaxel (FPAC)↗

Level B/C software ground navigation program. Delta-T processor

The Delta-T Processor (DTP) computes the instantaneous downtrack error in a specified orbiter onboard navigation state vector recovered via downlink telemetry. The downtrack error, expressed in units of time, is computed based on current incoming Earth based range and Doppler navigation tracking data and the ground selected onboard navigation state vector. The computed time difference when used to modify the timetag of the vector used for onboard navigation reduces the instantaneous downtrack error in this vector to within the threshold of the DTP, the input data, and the onboard software. This threshold is currently estimated to be approximately 2 to 4 nautical miles. The DTP is not restricted to using only onboard vectors. Any vector, either input via the manual entry device or accessible via the vector administration table, may be used. The DTP does not require that both data types be available.

Source record↗

An experimental evaluation of software redundancy as a strategy for improving reliability

The strategy of using multiple versions of independently developed software as a means to tolerate residual software design faults is suggested by the success of hardware redundancy for tolerating hardware failures. Although, as generally accepted, the independence of hardware failures resulting from physical wearout can lead to substantial increases in reliability for redundant hardware structures, a similar conclusion is not immediate for software. The degree to which design faults are manifested as independent failures determines the effectiveness of redundancy as a method for improving software reliability. Interest in multi-version software centers on whether it provides an adequate measure of increased reliability to warrant its use in critical applications. The effectiveness of multi-version software is studied by comparing estimates of the failure probabilities of these systems with the failure probabilities of single versions. The estimates are obtained under a model of dependent failures and compared with estimates obtained when failures are assumed to be independent. The experimental results are based on twenty versions of an aerospace application developed and certified by sixty programmers from four universities. Descriptions of the application, development and certification processes, and operational evaluation are given together with an analysis of the twenty versions.

Eckhardt, Dave E., Jr.↗

Advanced transport operating system software upgrade: Flight management/flight controls software description

The Flight Management/Flight Controls (FM/FC) software for the Norden 2 (PDP-11/70M) computer installed on the NASA 737 aircraft is described. The software computes the navigation position estimates, guidance commands, those commands to be issued to the control surfaces to direct the aircraft in flight based on the modes selected on the Advanced Guidance Control System (AGSC) mode panel, and the flight path selected via the Navigation Control/Display Unit (NCDU).

Clinedinst, Winston C.↗

Power system state estimation for a spacecraft power system

An application of the maximum likelihood state estimator to a space-based power system is presented. The state estimator uses current and voltage measurements to generate estimates of node voltages for an electrical power distribution system for the Space Shuttle. Preliminary results on the effect of noisy measurements on estimated parameters are reported. The software used in generating these results is part of an overall package being developed at Louisiana Tech University. Intended applications of this package include the analysis of power systems and real-time parallel processing on the Space Shuttle.

Berry, F. C.↗

An experimental evaluation of software redundancy as a strategy for improving reliability

The strategy of using multiple versions of independently developed software as a means to tolerate residual software design faults is suggested by the success of hardware redundancy for tolerating hardware failires. Although, as generally accepted, the independence of hardware failures resulting from physical wearout can lead to substantial increases in reliability for redundant hardware structures, a similar conclusion is not immediate for software. The degree to which design faults are manifested as independent failures determines the effectiveness of redundancy as a method for improving software reliability. Interest in multi-version software centers on whether it provides an adequate measure of increased reliability to warrant its use in critical applications. The effectiveness of multi-version software is studied by comparing estimates of the failure probabilities of these systems with the failure probabilities of single versions. The estimates are obtained under a model of dependent failures and compared with the estimates obtained when failures are assumed to be independent. The experimental results are based on twenty versions of an aerospace application developed and certified by sixty programmers from four universities. Descriptions of the application, development and certifications processes, and operational evaluation are given together with an analysis of the twenty versions.

Eckhardt, Dave E.↗

DORIS Satellite Phase Center Determination and Consequences on the Derived Scale of the Terrestrial Reference Frame

This slide presentation reports on the analysis of several years of Delft Object-oriented Radar Interferometric Software (Doris) data undertaken to estimate daily determination of satellite antenna phase center corrections. This was done on a satellite by satellite basis. For each DORIS satellite, we considered long-term time series of such individual estimations, looking for possible biases, discontinuities, trends or annual signals. The analysis compared DORIS to GPS estimates for common satellites (Jason and TOPEX/Poseidon).

terrestrial reference frame scale↗

NASA Tech Briefs, October 2007

Topics covered include; Wirelessly Interrogated Position or Displacement Sensors; Ka-Band Radar Terminal Descent Sensor; Metal/Metal Oxide Differential Electrode pH Sensors; Improved Sensing Coils for SQUIDs; Inductive Linear-Position Sensor/Limit-Sensor Units; Hilbert-Curve Fractal Antenna With Radiation- Pattern Diversity; Single-Camera Panoramic-Imaging Systems; Interface Electronic Circuitry for an Electronic Tongue; Inexpensive Clock for Displaying Planetary or Sidereal Time; Efficient Switching Arrangement for (N + 1)/N Redundancy; Lightweight Reflectarray Antenna for 7.115 and 32 GHz; Opto-Electronic Oscillator Using Suppressed Phase Modulation; Alternative Controller for a Fiber-Optic Switch; Strong, Lightweight, Porous Materials; Nanowicks; Lightweight Thermal Protection System for Atmospheric Entry; Rapid and Quiet Drill; Hydrogen Peroxide Concentrator; MMIC Amplifiers for 90 to 130 GHz; Robot Would Climb Steep Terrain; Measuring Dynamic Transfer Functions of Cavitating Pumps; Advanced Resistive Exercise Device; Rapid Engineering of Three-Dimensional, Multicellular Tissues With Polymeric Scaffolds; Resonant Tunneling Spin Pump; Enhancing Spin Filters by Use of Bulk Inversion Asymmetry; Optical Magnetometer Incorporating Photonic Crystals; WGM-Resonator/Tapered-Waveguide White-Light Sensor Optics; Raman-Suppressing Coupling for Optical Parametric Oscillator; CO2-Reduction Primary Cell for Use on Venus; Cold Atom Source Containing Multiple Magneto- Optical Traps; POD Model Reconstruction for Gray-Box Fault Detection; System for Estimating Horizontal Velocity During Descent; Software Framework for Peer Data-Management Services; Autogen Version 2.0; Tracking-Data-Conversion Tool; NASA Enterprise Visual Analysis; Advanced Reference Counting Pointers for Better Performance; C Namelist Facility; and Efficient Mosaicking of Spitzer Space Telescope Images.

Source record↗

Autonomous Aerobraking: A Design, Development, and Feasibility Study

Aerobraking has been used four times to decrease the apoapsis of a spacecraft in a captured orbit around a planetary body with a significant atmosphere utilizing atmospheric drag to decelerate the spacecraft. While aerobraking requires minimum fuel, the long time required for aerobraking requires both a large operations staff, and large Deep Space Network resources. A study to automate aerobraking has been sponsored by the NASA Engineering and Safety Center to determine initial feasibility of equipping a spacecraft with the onboard capability for autonomous aerobraking, thus saving millions of dollars incurred by a large aerobraking operations workforce and continuous DSN coverage. This paper describes the need for autonomous aerobraking, the development of the Autonomous Aerobraking Development Software that includes an ephemeris estimator, an atmospheric density estimator, and maneuver calculation, and the plan forward for continuation of this study.

Prince, Jill L. H.↗

Implementation and Simulation Results using Autonomous Aerobraking Development Software

An Autonomous Aerobraking software system is currently under development with support from the NASA Engineering and Safety Center (NESC) that would move typically ground-based operations functions to onboard an aerobraking spacecraft, reducing mission risk and mission cost. The suite of software that will enable autonomous aerobraking is the Autonomous Aerobraking Development Software (AADS) and consists of an ephemeris model, onboard atmosphere estimator, temperature and loads prediction, and a maneuver calculation. The software calculates the maneuver time, magnitude and direction commands to maintain the spacecraft periapsis parameters within design structural load and/or thermal constraints. The AADS is currently tested in simulations at Mars, with plans to also evaluate feasibility and performance at Venus and Titan.

Maddock, Robert W.↗

Software Fault Tolerance: A Tutorial

Because of our present inability to produce error-free software, software fault tolerance is and will continue to be an important consideration in software systems. The root cause of software design errors is the complexity of the systems. Compounding the problems in building correct software is the difficulty in assessing the correctness of software for highly complex systems. After a brief overview of the software development processes, we note how hard-to-detect design faults are likely to be introduced during development and how software faults tend to be state-dependent and activated by particular input sequences. Although component reliability is an important quality measure for system level analysis, software reliability is hard to characterize and the use of post-verification reliability estimates remains a controversial issue. For some applications software safety is more important than reliability, and fault tolerance techniques used in those applications are aimed at preventing catastrophes. Single version software fault tolerance techniques discussed include system structuring and closure, atomic actions, inline fault detection, exception handling, and others. Multiversion techniques are based on the assumption that software built differently should fail differently and thus, if one of the redundant versions fails, it is expected that at least one of the other versions will provide an acceptable output. Recovery blocks, N-version programming, and other multiversion techniques are reviewed.

Torres-Pomales, Wilfredo↗

Object-oriented productivity metrics

Software productivity metrics are useful for sizing and costing proposed software and for measuring development productivity. Estimating and measuring source lines of code (SLOC) has proven to be a bad idea because it encourages writing more lines of code and using lower level languages. Function Point Analysis is an improved software metric system, but it is not compatible with newer rapid prototyping and object-oriented approaches to software development. A process is presented here for counting object-oriented effort points, based on a preliminary object-oriented analysis. It is proposed that this approach is compatible with object-oriented analysis, design, programming, and rapid prototyping. Statistics gathered on actual projects are presented to validate the approach.

Connell, John L.↗

Analysis and Recommendation of Tritium Gas Continuous Air Monitor Alarm Setpoints for the RPL Stack Exhaust

The Radiochemical Processing Laboratory (RPL) tritium continuous air monitor (CAM) is used for near real-time detection of tritium gas (i.e., elemental tritium [HT] and tritiated water vapor [HTO]) in the stack exhaust. The CAM interfaces with software developed by the Pacific Northwest National Laboratory (PNNL)—called the “PNNL OS3700 Tritium Monitoring Software”—that provides near real-time estimates of tritium gas air concentrations and integrated daily activities that are calculated from measured CAM counts. The OS3700 software implements alarm setpoints to alert the facility of larger tritium gas releases that if allowed to persist, could begin to challenge permitted emission and established dose constraints. This report performs a detailed review of historical and current tritium alarm setpoints used at RPL, including discussion of the technical basis used in their development, analysis of alarm frequencies using measured historical data, and performs a detailed dose assessment using more realistic release scenarios and meteorology. Based on the results, the tritium air concentration and integrated daily tritium activity alarm setpoints will remain 2.0 × 10 -5 µCi/ml and 25 Ci/day, respectively. These setpoints achieve the right operational balance in identifying larger releases from planned tritium work at RPL, without being overly conservative so as to cause nuisance alarming. Furthermore, implied doses associated with these setpoints are well below defined and regulatory limits.

325RPL↗

An Innovative Approach to Modeling VIPER Rover Software Life Cycle Cost

NASA’s “Volatiles Investigating Polar Exploration Rover” (VIPER) will be the first robotic mission to prospect for water ice near the south pole of the Moon in late 2023 on a 100-Earth-day mission. The information that the VIPER rover provides will help improve understanding of the composition, distribution, and accessibility of Lunar polar volatiles and will help determine how the Moon’s resources can support future human space exploration. VIPER, however, represents a radical departure from the way that NASA has traditionally developed planetary robotic missions. A key consequence of these differences is that estimating the cost of VIPER’s rover software is challenging and complex.For example, VIPER is being developed using management procedures typically applied to NASA research and technology projects, rather than space flight programs. In addition, key portions of the rover’s software are being designed as ground software to run on mission control computers (rather than on-board the rover as flight software as with prior planetary missions) taking advantage of continuous, interactive data communications between the Moon and Earth and higher performance computing available on the ground. Moreover, the rover’s software is being engineered using Agile software development practices and incorporates a significant amount of open-source, rather than following traditional (spiral, waterfall, etc.) development methods and in-house code. In this paper, we present an innovative process to estimate the life cycle cost of VIPER’s rover software. We first describe how we modeled the architecture and code counts for three software elements: Rover Flight Software (RFSW), Rover Ground Software (RGSW), and Rover Simulation Software (RSIM). We then discuss key challenges and unique aspects of our approach, such as the lack of Lunar rover analogies, the need to integrate and test large open source software, and the strategies developed to account for use of non-space flight management practices and the impact of the COVID-19 pandemic. We conclude with a summary of our results, including cumulative distribution, nearest neighbors and cluster analysis, as well as heuristics used to confirm the reasonableness of the cost estimate.

Utz, Hans↗

Monitoring and Evaluation of Smolt Migration in the Columbia Basin : Volume XVIII: Survival and Transportation Effects of Migrating Snake River Wild Chinook Salmon and Steelhead: Historical Estimates From 1996-2004 and Comparison to Hatchery Results. Draft.

The combined juvenile and adult detection histories of PIT-tagged wild salmonids migrating through the Federal Columbia River Power System (FCRPS) were analyzed using the ROSTER (River-Ocean Survival and Transportation Effects Routine) statistical release-recapture model. This model, implemented by software Program ROSTER, was used to estimate survival on large temporal and spatial scales for PIT-tagged wild spring and summer Chinook salmon and steelhead released in the Snake River Basin upstream of Lower Granite Dam from 1996 to 2004. In addition, annual results from wild salmonids were compared with results from hatchery salmonids, which were presented in a previous report in this series (Buchanan, R. A., Skalski, J. R., Lady, J. L., Westhagen, P., Griswold, J., and Smith, S. 2007, 'Survival and Transportation Effects for Migrating Snake River Hatchery Chinook Salmon and Steelhead: Historical Estimates from 1996-2003', Technical report, Bonneville Power Administration, Project 1991-051-00). These results are reported here. Annual estimates of the smolt-to-adult return ratio (SAR), juvenile inriver survival from Lower Granite to Bonneville, the ocean return probability from Bonneville to Bonneville, and adult upriver survival from Bonneville to Lower Granite are reported. Annual estimates of transport-inriver (T/I) ratios and differential post-Bonneville mortality (D) are reported on a dam-specific basis for release years with sufficient numbers of wild PIT-tagged smolts transported. Transportation effects are estimated only for dams where at least 1,000 tagged wild smolts were transported from a given upstream release group. Because few wild Chinook salmon and steelhead tagged upstream of Lower Granite Dam were transported before the 2003 release year, T/I and D were estimated only for the 2003 and 2004 release years. Performance measures include age-1-ocean adult returns for steelhead, but not for Chinook salmon. Spring and summer Chinook salmon release groups were pooled across the entire Snake River Basin upstream of Lower Granite Dam for this report. Annual estimates of SAR from Lower Granite back to Lower Granite averaged 0.92% with an estimated standard error (dSE) of 0.25% for wild spring and summer Chinook salmon for tagged groups released from 1996 through 2004, omitting age-1-ocean (jack) returns. Only for the 1999 and 2000 release years did the wild Chinook SAR approach the target value of 2%, identified by the NPCC as the minimum SAR necessary for recovery. Annual estimates of SAR for wild steelhead from the Snake River Basin averaged 0.63% (dSE = 0.15%), including age-1-ocean returns, for release years 1996 through 2004. For release years when the ocean return probability from Bonneville back to Bonneville could be estimated (i.e., 1999 through 2004), it was estimated that on average approximately 83% of the total integrated mortality for nontransported, tagged wild spring and summer Chinook, and 78% for steelhead (omitting the 2001 release year), occurred during the ocean life stage (i.e., from Bonneville to Bonneville). This suggests that additional monitoring and research efforts should include the ocean and estuary environment. Annual estimates of the dam-specific T/I for Lower Granite Dam were available for the 2003 and 2004 release years for both wild Chinook salmon and wild steelhead. The estimated T/I for Lower Granite was significantly > 1.0 for Chinook in 2004 (P < 0.0001) and for steelhead in both 2003 (P < 0.0001) and 2004 (P < 0.0001), indicating that for these release years, wild fish transported at Lower Granite returned there in higher proportions than fish that were returned to the river at Lower Granite, or that passed Lower Granite without detection as juveniles. Annual estimates of the dam-specific T/I for Little Goose Dam were available for wild Chinook salmon for both 2003 and 2004. The estimated T/I for Little Goose was significantly > 1.0 for wild Chinook in 2004 (P = 0.0024), but not in 2003 (P = 0.1554). Differential post-Bonneville mortality (D) is the ratio of post-Bonneville survival to Lower Granite Dam of transported fish to that of nontransported ('inriver') fish. Estimates of D were available for transportation from Lower Granite and Little Goose dams in 2003 and 2004 for wild Chinook, and from Lower Granite Dam in 2003 and 2004 for wild steelhead. Point estimates ranged from 0.74 (dSE = 0.29) for transportation of wild Chinook salmon from Lower Granite Dam in 2003 to 1.91 (dSE = 0.61) for transportation of wild steelhead from Lower Granite Dam in 2003. Small transport groups resulted in high uncertainty on the point estimates, and only for 2003 steelhead transported from Lower Granite Dam did transported fish have significantly greater post-Bonneville survival than nontransported fish (P = 0.0213).

13 HYDRO ENERGY↗