Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “reasoning about programs”

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

Squash-Box Feasibility Driven Differential Dynamic Programming

Recently, Differential Dynamic Programming (DDP) and other similar algorithms have become the solvers of choice when performing non-linear Model Predictive Control (nMPC) with modern robotic devices. The reason is that they have a lower computational cost per iteration when compared with off-the-shelf Non-Linear Programming (NLP) solvers, which enables its online operation. However, they cannot handle constraints, and are known to have poor convergence capabilities. In this paper, we propose a method to solve the optimal control problem with control bounds through a squashing function (i.e., a sigmoid, which is bounded by construction). It has been shown that a naive use of squashing functions damage the convergence rate. To tackle this, we first propose to add a quadratic barrier that avoids the difficulty of the plateau produced by the sigmoid. Second, we add an outer loop that adapts both the sigmoid and the barrier; it makes the optimal control problem with the squashing function converge to the original control-bounded problem. To validate our method, we present simulation results for different types of platforms including a multi-rotor, a biped, a quadruped and a humanoid robot.

Navarro, Angel Santamaria↗

A memory efficient user interface for CLIPS micro-computer applications

The goal of the Integrated Southern Pine Beetle Expert System (ISPBEX) is to provide expert level knowledge concerning treatment advice that is convenient and easy to use for Forest Service personnel. ISPBEX was developed in CLIPS and delivered on an IBM PC AT class micro-computer, operating with an MS/DOS operating system. This restricted the size of the run time system to 640K. In order to provide a robust expert system, with on-line explanation, help, and alternative actions menus, as well as features that allow the user to back up or execute 'what if' scenarios, a memory efficient menuing system was developed to interface with the CLIPS programs. By robust, we mean an expert system that (1) is user friendly, (2) provides reasonable solutions for a wide variety of domain specific problems, (3) explains why some solutions were suggested but others were not, and (4) provides technical information relating to the problem solution. Several advantages were gained by using this type of user interface (UI). First, by storing the menus on the hard disk (instead of main memory) during program execution, a more robust system could be implemented. Second, since the menus were built rapidly, development time was reduced. Third, the user may try a new scenario by backing up to any of the input screens and revising segments of the original input without having to retype all the information. And fourth, asserting facts from the menus provided for a dynamic and flexible fact base. This UI technology has been applied successfully in expert systems applications in forest management, agriculture, and manufacturing. This paper discusses the architecture of the UI system, human factors considerations, and the menu syntax design.

Sterle, Mark E.↗

Electronics for a focal plane crystal spectrometer

The HEAO-B program forced the usual constraints upon the spacecraft experiment electronics: high reliability, low power consumption, and tight packaging at reasonable cost. The programmable high voltage power supplies were unique in both application and simplicity of manufacture. The hybridized measurement chain is a modification of that used on the SAS-C program; the charge amplifier design in particular shows definite improvement in performance over previous work.

Goeke, R. F.↗

Evidence Report: Risk of Hypobaric Hypoxia from the Exploration Atmosphere

Extravehicular activity (EVA) is at the core of a manned space exploration program. Some elements of exploration may be safely and effectively performed by robots, but certain critical elements will require the trained, assertive, and reasoning mind of a human crewmember. To effectively use these skills, NASA needs a safe, effective, and efficient EVA component integrated into the human exploration program. The EVA preparation time should be minimized and the suit pressure should be low to accommodate EVA tasks without causing undue fatigue, physical discomfort, or suit-related trauma. Commissioned in 2005, the Exploration Atmospheres Working Group (EAWG) had the primary goal of recommending to NASA an internal environment that allowed efficient and repetitive EVAs for missions that were to be enabled by the former Constellation Program. At the conclusion of the EAWG meeting, the 8.0 psia and 32% oxygen (O2) environment were recommended for EVA-intensive phases of missions. After re-evaluation in 2012, the 8/32 environment was altered to 8.2 psia and 34% O2 to reduce the hypoxic stress to a crewmember. These two small changes increase alveolar O2 pressure by 11 mmHg, which is expected to significantly benefit crewmembers. The 8.2/34 environment (inspired O2 pressure = 128 mmHg) is also physiologically equivalent to the staged decompression atmosphere of 10.2 psia / 26.5% O2 (inspired O2 pressure = 127 mmHg) used on 34 different shuttle missions for approximately a week each flight. As a result of selecting this internal environment, NASA gains the capability for efficient EVA with low risk of decompression sickness (DCS), but not without incurring the additional negative stimulus of hypobaric hypoxia to the already physiologically challenging spaceflight environment. This report provides a review of the human health and performance risks associated with the use of the 8.2 psia / 34% O2 environment during spaceflight. Of most concern are the potential effects on the central nervous system (CNS), including increased intracranial pressure, visual impairment, sensorimotor dysfunction, and oxidative damage. Other areas of focus include validation of the DCS mitigation strategy, incidence and treatment of transient acute mountain sickness (AMS), development of new exercise countermeasure protocols, effective food preparation at 8.2 psia, assurance of quality sleep, and prevention of suit-induced injury. Although missions proposing to use an 8.2/34 environment are still years away, it is recommended that these studies begin early enough to ensure that the correct decisions pertaining to vehicle design, mission operational concepts, and human health countermeasures are appropriately informed.

Norcross, Jason R.↗

Precision inclusive Higgs physics at e+e- colliders with tracking detectors and without calorimetry

A primary goal of a future e + e - collider program will be the precision measurement of Higgs boson properties. For practical reasons it is of interest to determine the minimal set of detector specifications required to reach this and other scientific goals. Here we investigate the precision obtainable for the e + e - Zh μ + μ - X inclusive cross section and the Higgs boson mass using the di-muon recoil method, considering a detector that has only an inner tracking system within a solenoidal magnetic field, surrounded by many nuclear interaction lengths of absorbing material, and an outer muon identification system. We find that the sensitivity achievable in these measurements with such a tracking detector is only marginally reduced compared to that expected for a general purpose detector with additional electromagnetic and hadronic calorimeter systems. The difference results mainly from multi-photon backgrounds that are not as easily rejected with tracking detectors. We also comment on the prospects for an analogous measurement of the e + e - → Zh → e + e - X inclusive cross section. Finally, we study searches for light scalars utilizing the di-muon recoil method, estimating the projected reach with a tracking or general purpose detector.

71 CLASSICAL AND QUANTUM MECHANICS, GENERAL PHYSIC↗

Studying Nuclear Astrophysics at NIF

The National Ignition Facility's primary goal is to generate fusion energy. But the starlike conditions that it creates will also enable NIF scientists to study astrophysically important nuclear reactions. When scientists at the stadium-sized National Ignition Facility attempt to initiate fusion next year, 192 powerful lasers will direct 1.2 MJ of light energy toward a two-mm-diameter pellet of deuterium ({sup 2}H, or D) and tritium ({sup 3}H, or T). Some of that material will be gaseous, but most will be in a frozen shell. The idea is to initiate 'inertial confinement fusion', in which the two hydrogen isotopes fuse to produce helium-4, a neutron, and 17.6 MeV of energy. The light energy will be delivered to the inside walls of a hohlraum, a heavy-metal, centimeter-sized cylinder that houses the pellet. The container's heated walls will produce x rays that impinge on the pellet and ablate its outer surface. The exiting particles push inward on the pellet and compresses the DT fuel. Ultimately a hot spot develops at the pellet's center, where fusion produces {sup 4}He nuclei that have sufficient energy to propagate outward, trigger successive reactions, and finally react the frozen shell. Ignition should last several tens of picoseconds and generate more than 10 MJ of energy and roughly 10{sup 19} neutrons. The temperature will exceed 10{sup 8} K and fuel will be compressed to a density of several hundred g/cm{sup 3}, both considerably greater than at the center of the Sun. The figure shows a cutaway view of NIF. The extreme conditions that will be produced there simulate those in nuclear weapons and inside stars. For that reason, the facility is an important part of the US stockpile stewardship program, designed to assess the nation's aging nuclear stockpile without doing nuclear tests. In this Quick Study we consider a third application of NIF - using the extraordinary conditions it will produce to perform experiments in basic science. We will focus on measurements of some of the nuclear reaction probabilities that are important to nuclear astrophysics, the field that relates energy production and nucleosynthesis from nuclear reactions in stars and in the Big Bang to the environments in which those nuclear reactions occur. NIF, unlike previous nuclear-physics facilities, will enable measurements of nuclear reactions at the temperatures, densities, and ionization states similar to those that occur in stars.

42 ENGINEERING↗

SHELXT – Integrated space-group and crystal-structure determination

SHELXT automates routine small-molecule structure determination starting from single-crystal reflection data, the Laue group and a reasonable guess as to which elements might be present. The new computer program SHELXT employs a novel dual-space algorithm to solve the phase problem for single-crystal reflection data expanded to the space group P1. Missing data are taken into account and the resolution extended if necessary. All space groups in the specified Laue group are tested to find which are consistent with the P1 phases. After applying the resulting origin shifts and space-group symmetry, the solutions are subject to further dual-space recycling followed by a peak search and summation of the electron density around each peak. Elements are assigned to give the best fit to the integrated peak densities and if necessary additional elements are considered. An isotropic refinement is followed for non-centrosymmetric space groups by the calculation of a Flack parameter and, if appropriate, inversion of the structure. The structure is assembled to maximize its connectivity and centred optimally in the unit cell. SHELXT has already solved many thousand structures with a high success rate, and is optimized for multiprocessor computers. It is, however, unsuitable for severely disordered and twinned structures because it is based on the assumption that the structure consists of atoms.

75 CONDENSED MATTER PHYSICS, SUPERCONDUCTIVITY AND↗

SU-E-T-153: Establish a Comprehensive Patient-Specific Plan QA Database for Instituitional Quality Control Program

Purpose: Since the publication of TG-119, several new treatment techniques requiring new QA devices have been implemented in the clinic. To monitor and analyze our institutional QA performance, we have created a comprehensive QA database using Research Electronic Data Capture (REDCap). The database will also assist us in creating IMRT QA Analysis practice guidelines. Methods: Since Oct. 2013, 336 patient plan QA results were entered into the database. Plan parameters such as plan ID, treatment site, technique, energy, optimization constraints, modulation factor, leaf speed, leaf opening.etc were automatically extracted from the Varian Eclipse database to allow us to refine our evaluation and analysis method. Specific QA device, LINAC-related information, and measurement and analysis results were manually entered by the QA team. IMRT plans were measured using MapCHECK2 while RapidArc plans were measured using ArcCHECK. Distance-To-Agreement 3%/3mm without global maximum normalization was used. Results: The data indicates that different treatment techniques might benefit from a different site-specific action level(AL) depending on the complexity of the plan and optimization parameter used (e.g., breast IMRT QA= 97.8% and pelvis IMRT QA=93.1%). Different QA devices may also benefit from a different AL (MapCHECK2 = 94.1% while ArcCHECK = 83.0%). The relationship between the parameters and passing rate suggests that the complexity of each plan, characterized by leaf travel, leaf opening and modulation factor, affect the passing rate significantly. The database is reviewed regularly, and any abnormal point of the QA result or a trend of lower QA passing rate on a specific LINAC is further investigated. Conclusion: Establishing a comprehensive QA database provides an overview of the quality assurance program. It not only helps in answering the question “what is a reasonable and achievable standard for each institution”, but also saves time in monitoring and investigating the daily machine and QA performance.

07 ISOTOPE AND RADIATION SOURCES↗

HarDWR - Harmonized Water Rights Records

A dataset within the Harmonized Database of Western U.S. Water Rights (HarDWR). For a detailed description of the database, please see the meta-record v2.0. Changelog v2.0 - Recalculated based on data sourced from WestDAAT - Changed using a Site ID column to identify unique records to using aa combination of Site ID and Allocation ID - Removed the Water Management Area (WMA) column from the harmonized records. The replacement is a separate file which stores the relationship between allocations and WMAs. This allows for allocations to contribute to water right amounts to multiple WMAs during the subsequent cumulative process. - Added a column describing a water rights legal status - Added "Unspecified" was a water source category - Added an acre-foot (AF) column - Added a column for the classification of the right's owner v1.02 - Added a .RData file to the dataset as a convenience for anyone exploring our code. This is an internal file, and the one referenced in analysis scripts as the data objects are already in R data objects. v1.01 - Updated the names of each file with an ID number less than 3 digits to include leading 0s v1.0 - Initial public release Description Here we present an updated database of Western U.S. water right records. This database provides consistent unique identifiers for each water right record, and a consistent categorization scheme that puts each water right record into one of seven broad use categories. These data were instrumental in conducting a study of the multi-sector dynamics of inter-sectoral water allocation changes though water markets (Grogan et al., *in review*). Specifically, the data were formatted for use as input to a process-based hydrologic model, Water Balance Model (WBM), with a water rights module (Grogan et al., *in review*). While this specific study motivated the development of the database presented here, water management in the U.S. West is a rich area of study (e.g., Anderson and Woosly, 2005; Tidwell, 2014; Null and Prudencio, 2016; Carney et al., 2021) so releasing this database publicly with documentation and usage notes will enable other researchers to do further work on water management in the U.S. West. We produced the water rights database presented here in four main steps: (1) data collection, (2) data quality control, (3) data harmonization, and (4) generation of cumulative water rights curves. Each of steps (1)-(3) had to be completed in order to produce (4), the final product that was used in the modeling exercise in Grogan et al. (*in review*). All data in each step is associated with a spatial unit called a Water Management Area (WMA), which is the unit of water right administration utilized by the state in which the right came from. Steps (2) and (3) required use to make assumptions and interpretation, and to remove records from the raw data collection. We describe each of these assumptions and interpretations below so that other researchers can choose to implement alternative assumptions an interpretation as fits their research aims. Motivation for Changing Data Sources The most significant change has been a switch from collecting the raw water rights directly from each state to using the water rights records presented in WestDAAT, a product of the Water Data Exchange (WaDE) Program under the Western States Water Council (WSWC). One of the main reasons for this is that each state of interest is a member of the WSWC, meaning that WaDE is partially funded by these states, as well as many universities. As WestDAAT is also a database with consistent categorization, it has allowed us to spend less time on data collection and quality control and more time on answering research questions. This has included records from water right sources we had previously not known about when creating v1.0 of this database. The only major downside to utilizing the WestDAAT records as our raw data is that further updates are tied to when WestDAAT is updated, as some states update their public water right records daily. However, as our focus is on cumulative water amounts at the regional scale, it is unlikely most records updates would have a significant effect on our results. The structure of WestDAAT led to several important changes to how HarWR is formatted. The most significant change is that WaDE has calculated a field known as `SiteUUID`, which is a unique identifier for the Point of Diversion (POD), or where the water is drawn from. This separate from `AllocationNativeID`, which is the identifier for the allocation of water, or the amount of water associated with the water right. It should be noted that it is possible for a single site to have multiple allocations associated with it and for an allocation to be able to be extracted from multiple sites. The site-allocation structure has allowed us to adapt a more consistent, and hopefully more realistic, approach in organizing the water right records than we had with HarDWR v1.0. This was incredibly helpful as the raw data from many states had multiple water uses within a single field within a single row of their raw data, and it was not always clear if the first water use was the most important, or simply first alphabetically. WestDAAT has already addressed this data quality issue. Furthermore, with v1.0, when there were multiple records with the same water right ID, we selected the largest volume or flow amount and disregarded the rest. As WestDAAT was already a common structure for disparate data formats, we were better able to identify sites with multiple allocations and, perhaps more importantly, allocations with multiple sites. This is particularly helpful when an allocation has sites which cross WMA boundaries, instead of just assigning the full water amount to a single WMA we are now able to divide the amount of water between the number of relevant WMAs. As it is now possible to identify allocations with water used in multiple WMAs, it is no longer practical to store this information within a single column. Instead the stAllocationToWMATab.csv file was created, which is an allocation by WMA matrix containing the percent Place of Use area overlap with each WMA. We then use this percentage to divide the allocation's flow amount between the given WMAs during the cumulation process to hopefully provide more realistic totals of water use in each area. However, not every state provides areas of water use, so like HarDWR v1.0, a hierarchical decision tree was used to assign each allocation to a WMA. First, if a WMA could be identified based on the allocation ID, then that WMA was used; typically, when available, this applied to the entire state and no further steps were needed. Second was the spatial analysis of Place of Use to WMAs. Third was a spatial analysis of the POD locations to WMAs, with the assumption that allocation's POD is within the WMA it should belong to; if an allocation still had multiple WMAs based on its POD locations, then the allocation's flow amount would be divided equally between all WMAs. The fourth, and final, process was to include water allocations which spatially fell outside of the state WMA boundaries. This could be due to several reasons, such as coordinate errors / imprecision in the POD location, imprecision in the WMA boundaries, or rights attached with features, such as a reservoir, which crosses state boundaries. To include these records, we decided for any POD which was within one kilometer of the state's edge would be assigned to the nearest WMA. Other Changes WestDAAT has Allowed In addition to a more nuanced and consistent method of assigning water right's data to WMAs, there are other benefits gained from using the WestDAAT dataset. Among those is a consistent categorization of a water right's legal status. In HarDWR v1.0, legal status was effectively ignored, which led to many valid concerns about the quality of the database related to the amounts of water the rights allowed to be claimed. The main issue was that rights with legal status' such as "application withdrawn", "non-active", or "cancelled" were included within HarDWR v1.0. These, and other water rights status' which were deemed to not be in use have been removed from this version of the database. Another major change has been the addition of the "unspecified water source category. This is water that can come from either surface water or groundwater, or the source of which is unknown. The addition of this source category brings the total number of categories to three. Due to reviewer feedback, we decided to add the acre-foot (AF) column so that the data may be more applicable to a wider audience. We added the ownerClassification column so that the data may be more applicable to a wider audience. File Descriptions The dataset is a series of various files organized by state sub-directories. In addition, each file begins with the state's name, in case the file is separate from its sub-directory for some reason. After the state name is the text which describes the contents of the file. Here is each file described in detail. Note that st is a placeholder for the state's name. stFullRecords_HarmonizedRights.csv: A file of the complete water records for each state. The column headers for each of this type of file are: state - The name of the state to which the allocations belong to. FIPS - The two digit numeric state ID code. siteID - The site location ID for POD locations. A site may have multiple allocations, which are the actual amount of water which can be drawn. In a simplified hypothetical, a farm stead may have an allocation for "irrigation" and an allocation for "domestic" water use, but the water is drawn from the same pumping equipment. It should be noted that many of the site ID appear to have been added by WaDE, and therefore may not be recognized by a given state's water rights database. allocationID - The allocation ID for the water right. For most states this is the water right ID, and what is recommended to use should a right be looked up on a given state's water rights database. The water amounts associated with these IDs tend to be finer scaled than those associated with siteID. It should be noted that some allocations may be extracted from multiple sites, particularly for larger Places of Use. ownerClassification - A classification of the types of owners for water rights. The most common is `Private` which incorporates a wide range of entities. Several classifications would be grouped into a government category, most of which are for the U.S. Federal Government. These allocations could be listed as "Federal", "United States of America", or as the names of any number of federal agencies. The last major grouping of entities is for "Native American"s. priorityDate - The date we use as the water right priority date for our modeling analysis. This is the legal priority date when it is available. However, for some rights, specifically from California and New Mexico, we used a pseudo priority date (e.g. well completion date or start of well drilling date) when a legal priority date was not available. The most questionable dates come from New Mexico, where the only date associated with certain water right records was the date the allocation was recorded in the database. As the allocation record creation tended to be within a few months of the filing of the application of the water right, from manually double checking the water rights, and our analysis focuses on aggregating water rights on the timescale of years, we determined it was acceptable to use such dates to include as many records as possible. primaryBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories WestDAAT. This column is the original WaDE category for the primary water use at the PoD site. allocationBeneficialUse - From the numerous state water use categories, WaDE categorized them into 21 categories for WestDAAT. This column is the original WaDE category

Economics↗

Fatigue and fail-safe design features of the DC-10 airplane

The philosophy and methods used in the design of the DC-10 aircraft to assure structural reliability against cracks under repeated service loads are described in detail. The approach consists of three complementary parts: (1) the structure is designed to be fatigue resistant for a crack-free life of 60,000 flight hours; (2) inasmuch as small undetected cracks could develop from other sources, such as material flaws and manufacturing preloads, the structure also is designed to arrest and control cracks within a reasonable service-inspection interval; and (3) a meaningful service-inspection program has been defined on the basis of analysis and test experience from the design development program. This service-inspection program closes the loop to assure the structural integrity of the DC-10 airframe. Selected materials, fasteners, and structural arrangements are used to achieve these design features with minimum structural weight and with economy in manufacturing and maintenance. Extensive analyses and testing were performed to develop and verify the design. The basic design considerations for fatigue-resistant structure are illustrated in terms of material selection, design loads spectra, methods for accurate stress and fatigue damage analysis, and proven concepts for efficient detail design.

Stone, M. E.↗

Ada style guide (version 1.1)

Ada is a programming language of considerable expressive power. The Ada Language Reference Manual provides a thorough definition of the language. However, it does not offer sufficient guidance on the appropriate use of Ada's powerful features. For this reason, the Goddard Space Flight Center Ada User's Group has produced this style guide which addresses such program style issues. The guide covers three areas of Ada program style: the structural decomposition of a program; the coding and the use of specific Ada features; and the textural formatting of a program.

Seidewitz, Edwin V.↗

Artificial intelligence and the space station software support environment

In a software system the size of the Space Station Software Support Environment (SSE), no one software development or implementation methodology is presently powerful enough to provide safe, reliable, maintainable, cost effective real time or near real time software. In an environment that must survive one of the most harsh and long life times, software must be produced that will perform as predicted, from the first time it is executed to the last. Many of the software challenges that will be faced will require strategies borrowed from Artificial Intelligence (AI). AI is the only development area mentioned as an example of a legitimate reason for a waiver from the overall requirement to use the Ada programming language for software development. The limits are defined of the applicability of the Ada language Ada Programming Support Environment (of which the SSE is a special case), and software engineering to AI solutions by describing a scenario that involves many facets of AI methodologies.

Marlowe, Gilbert↗

Theoretical foundations for information representation and constraint specification

Research accomplished at the Knowledge Based Systems Laboratory of the Department of Industrial Engineering at Texas A&M University is described. Outlined here are the theoretical foundations necessary to construct a Neutral Information Representation Scheme (NIRS), which will allow for automated data transfer and translation between model languages, procedural programming languages, database languages, transaction and process languages, and knowledge representation and reasoning control languages for information system specification.

Menzel, Christopher P.↗

Computer model to simulate testing at the National Transonic Facility

A computer model has been developed to simulate the processes involved in the operation of the National Transonic Facility (NTF), a large cryogenic wind tunnel at the Langley Research Center. The simulation was verified by comparing the simulated results with previously acquired data from three experimental wind tunnel test programs in the NTF. The comparisons suggest that the computer model simulates reasonably well the processes that determine the liquid nitrogen (LN2) consumption, electrical consumption, fan-on time, and the test time required to complete a test plan at the NTF. From these limited comparisons, it appears that the results from the simulation model are generally within about 10 percent of the actual NTF test results. The use of actual data acquisition times in the simulation produced better estimates of the LN2 usage, as expected. Additional comparisons are needed to refine the model constants. The model will typically produce optimistic results since the times and rates included in the model are typically the optimum values. Any deviation from the optimum values will lead to longer times or increased LN2 and electrical consumption for the proposed test plan. Computer code operating instructions and listings of sample input and output files have been included.

Mineck, Raymond E.↗

Rocketdyne - SE-7 and SE-8 Engines

The 70-pound SE-7 engine is very similar with its two valves, ablative material, a silicon carbide liner, a silicon carbide throat, and overall configuration. There were different wraps. One had a ninety-degree ablative material orientation. That is important because it caused problems with the SE-8, but not for this application. It was not overly stressed. It was a validation of the off-the-shelf application approach. There were two SE-7 engines located on the stage near the bottom. They had their own propellant tanks. That was the application. All it did was give a little bit of gravity by firing to push the propellants to the bottom of the tanks for start or restart. It was not a particularly complicated setup. (See Slides 6 and 7, Appendix F) What had we learned? This was a proven engine in a space environment. There weren't any development issues. Off-the-shelf seemed to work. There were no operational issues, which made the SE-7 very cost-effective. Besides NASA, the customer for this application was the Douglas Aircraft Company. Douglas decided the off-the-shelf idea was cost-effective. With the Gemini Program, the company was McDonnell Aircraft Corporation, which was part of the reason the off-the-shelf idea was applied to the Apollo. (See Slide 8, Appendix F) However, here are some differences between Apollo and Gemini vehicles. For one thing, the Apollo vehicle was really moving at high speed when it re-entered the atmosphere. Instead of a mere 17,000 miles per hour, it was going 24,000 miles per hour. That meant the heat load was four times as high on the Apollo vehicle as on the Gemini craft. Things were vibrating a little more. We had two redundant systems. Apollo was redundant where it could be as much as possible. That was really a keystone or maybe an anchor point for Apollo. We decided to pursue the off-the-shelf approach. However, the prime contractor was a different entity - the North American Space Division. They thought they ought to tune up this off-the-shelf setup. It was a similar off-the-shelf application, but at a higher speed. They wanted to improve it. What they wanted to improve was the material performance of silicon carbide. They were uncomfortable with the cracks they were seeing. They were uncomfortable with the cracks in the throat, and feeling that the environment was a little tougher, that maybe it was going to rattle, perhaps something would fall out, and they would have a problem. They wanted to eliminate the ceramic liner, and they wanted a different throat material. (See Slides 9 and 10, Appendix F) The Rocketdyne solutions were to replace silicon carbide material with a more forgiving ceramic material. Also, due to the multiple locations within the vehicle, the shape of the nozzles varied. Some nozzles were long, and some nozzles were short. We came up with a single engine design with variable nozzle extensions and configurations to fit particular vehicle locations. (See Slides 10 and 11, Appendix F)

Harmon, Tim↗

Human Systems Integration (HSI) Framework and Training - Shifting the View of HSI for Better Implementation

The Implementation of Human Systems Integration (HSI) presents challenges within the acquisition community for two reasons. The first is that misconceptions of HSI still exist, with many Program Managers (PMs) and leadership uncertain of the value or where to begin. The second is due to an unbalanced approach to HSI in its own framework. These implementation challenges lead to barriers in the early prevention of mishaps. Understanding HSI practices and how they should be implemented in the Acquisition Product Life Cycle (PLC) has been a challenge across the government, leaving the value of HSI unknown and misunderstood with Program Managers. In the case for many acquisition programs, HSI is not implemented in early design, losing the perspective on human capabilities and limitations, creating impacts on human-centered design. Expectations in human performance are not clearly set and operations are baselined with no margin for changes in technology and processes that will affect system performance. The HSI framework addresses total system performance holistically using collaboration as the primary tool. The goal is to create a system with efficiencies while minimizing risk to the operators, maintainers, and support personnel, as well as any collateral personnel and systems. To accomplish this, HSI should be implemented as part of preemptive measures to minimize potential human error and mishaps during the operation phase. Investigative and assessment tools exist that consider events, issues, and other outside influences of a system that may not fall under the current construct of the HSI domains, leaving gaps in early HSI implementation and affecting the prevention of human errors and mishaps. This presentation will outline what NASA HSI is doing to support Early HSI implementation and Operational Performance shifts that affect human performance.

Anthony T Thomas↗

Idiomatic Correctness-Checking via Julienne in Fortran 2023

This paper presents a unified approach to unit testing and runtime assertion checking using Fortran 2023. The paper describes the support for our approach in the Julienne framework. Julienne leverages recent Fortran standards to implement object-oriented design patterns, support testing parallel programs, and implement functional programming patterns in order to craft idioms inspired by natural-language expressions. The presented idioms employ novel operators to write expressions that evaluate to a test-diagnosis object encapsulating two components: (1) the test outcome or assertion outcome and (2) an automatically generated diagnostic string. Two other novel aspects of the approach include (1) the ability to enforce assertions inside pure procedures and (2) the ability to output rich diagnostic information inside pure procedures during error termination when assertions fail. The latter capability mitigates against a reason that Fortran programmers commonly cite for not writing pure procedures: difficulty obtaining useful program output inside pure procedures when debugging code. This paper demonstrates how the adoption of the proposed idioms leads naturally to a unifying theme across two otherwise disparate technologies: unit testing and runtime assertion checking. Finally, this paper describes the usage of the Julienne testing framework for writing unit tests and assertions in the Matcha high-performance computing application and the Fiats deep learning library.

Rouson, Damian↗

A distributed version of the NASA Engine Performance Program

Distributed NEPP, a version of the NASA Engine Performance Program, uses the original NEPP code but executes it in a distributed computer environment. Multiple workstations connected by a network increase the program's speed and, more importantly, the complexity of the cases it can handle in a reasonable time. Distributed NEPP uses the public domain software package, called Parallel Virtual Machine, allowing it to execute on clusters of machines containing many different architectures. It includes the capability to link with other computers, allowing them to process NEPP jobs in parallel. This paper discusses the design issues and granularity considerations that entered into programming Distributed NEPP and presents the results of timing runs.

Cours, Jeffrey T.↗