Search NASA⌕ Search

SEARCH · Search NASA

Results for “Programming environments”

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 307 records · Page 17

Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions

The National Aeronautics and Space Administration (NASA) is asking more of its human spaceflight programs than ever before through the collective Artemis Missions. The NASA Independent Verification and Validation (IV&V) Program contributes to NASA’s human spaceflight goals by providing IV&V services for NASA’s critical spacecraft and ground software. The IV&V Program is tasked with providing assurance from both individual and integrated mission software perspectives. The Artemis IV&V organization is actively supporting six distinct development efforts: Orion, the Space Launch System (SLS), Exploration Ground Systems (EGS), Mission Control Center (MCC), the Lunar Gateway, and the Human Landing System (HLS), representing a wide diversity of developer organizations, management structures, and development approaches. With much of this extremely complex flight and ground software being essential to human safety both on the ground and in space, Artemis IV&V is likewise challenged to provide more value-added assurance to future Artemis missions within a constrained budget. To meet this challenge, Artemis IV&V employs a variety of novel and evolving “Adaptive IV&V” approaches for planning and executing IV&V analysis to increase both the efficiency and effectiveness of the IV&V Program’s assurance activities, and to address the difficulties imposed by assuring software for a large, highly integrated, multi-mission enterprise managed and executed by physically and organizationally distinct programs. Instilling agile principles like iterative planning cycles, self-organizing teams, and regular retrospectives, into IV&V planning and execution has led to a more rapid turnaround of a minimum viable assurance product and allowed for increased alignment of assurance activities with development progress. Adopting an assurance case methodology has led to greater consistency and clearer communication of assurance design and provided a foundation for long-term maintenance of assurance plans, products, and results across missions. The IV&V-developed Assurance / Safety Case Analytical Network (A-SCAN) framework and tool has enabled the quantification and tracking of system/software risk and confidence. These confidence measures provide a means to repeatedly express the impact of planned and completed assurance work and the remaining residual risk. Applied as part of a “Follow-the-Risk” organizational ethos, this allows consistent rightsizing of analysis rigor and intensity commensurate with the perceived risk of defects, as well as appropriate targeting of the highest risk areas of the software to find safety issues before they can manifest. Finally, the development of the IV&V Advanced Risk Reduction Integrated Software Test and Operations Tri-program Lightweight Environment (ARRISTOTLE), an integrated software-only simulation of Orion, SLS, and EGS systems, has made it possible to independently test integrated pad and flight scenarios and inject faults to observe how the Artemis multi-program, mission software behaves in degraded modes and in response to hazards. These adaptive IV&V investments have enabled Artemis IV&V to become more efficient and effective in IV&V planning and execution and respond more readily to changes in the risk landscape, increasing the breadth and depth of risk reduction possible within the available resources. Residual risk tracking allows IV&V to communicate more effectively with stakeholders, both internal and external at all levels, and inform key decision-making personnel. This evolving assurance design approach provides IV&V surety that work is performed in the highest risk, most value-added areas of the software, to keep our astronauts and ground crews safe and ensure mission success.

Gerek A Whitman↗

Adaptive Independent Verification and Validation (IV&V) Reduces Risk of Software Impacting Safety in Artemis Missions

The National Aeronautics and Space Administration (NASA) is asking more of its human spaceflight programs than ever before through the collective Artemis Missions. The NASA Independent Verification and Validation (IV&V) Program contributes to NASA’s human spaceflight goals by providing IV&V services for NASA’s critical spacecraft and ground software. The IV&V Program is tasked with providing assurance from both individual and integrated mission software perspectives. The Artemis IV&V organization is actively supporting six distinct development efforts: Orion, the Space Launch System (SLS), Exploration Ground Systems (EGS), Mission Control Center (MCC), the Lunar Gateway, and the Human Landing System (HLS), representing a wide diversity of developer organizations, management structures, and development approaches. With much of this extremely complex flight and ground software being essential to human safety both on the ground and in space, Artemis IV&V is likewise challenged to provide more value-added assurance to future Artemis missions within a constrained budget. To meet this challenge, Artemis IV&V employs a variety of novel and evolving “Adaptive IV&V” approaches for planning and executing IV&V analysis to increase both the efficiency and effectiveness of the IV&V Program’s assurance activities, and to address the difficulties imposed by assuring software for a large, highly integrated, multi-mission enterprise managed and executed by physically and organizationally distinct programs. Instilling agile principles like iterative planning cycles, self-organizing teams, and regular retrospectives, into IV&V planning and execution has led to a more rapid turnaround of a minimum viable assurance product and allowed for increased alignment of assurance activities with development progress. Adopting an assurance case methodology has led to greater consistency and clearer communication of assurance design and provided a foundation for long-term maintenance of assurance plans, products, and results across missions. The IV&V-developed Assurance / Safety Case Analytical Network (A-SCAN) framework and tool has enabled the quantification and tracking of system/software risk and confidence. These confidence measures provide a means to repeatedly express the impact of planned and completed assurance work and the remaining residual risk. Applied as part of a “Follow-the-Risk” organizational ethos, this allows consistent rightsizing of analysis rigor and intensity commensurate with the perceived risk of defects, as well as appropriate targeting of the highest risk areas of the software to find safety issues before they can manifest. Finally, the development of the IV&V Advanced Risk Reduction Integrated Software Test and Operations Tri-program Lightweight Environment (ARRISTOTLE), an integrated software-only simulation of Orion, SLS, and EGS systems, has made it possible to independently test integrated pad and flight scenarios and inject faults to observe how the Artemis multi-program, mission software behaves in degraded modes and in response to hazards. These adaptive IV&V investments have enabled Artemis IV&V to become more efficient and effective in IV&V planning and execution and respond more readily to changes in the risk landscape, increasing the breadth and depth of risk reduction possible within the available resources. Residual risk tracking allows IV&V to communicate more effectively with stakeholders, both internal and external at all levels, and inform key decision-making personnel. This evolving assurance design approach provides IV&V surety that work is performed in the highest risk, most value-added areas of the software, to keep our astronauts and ground crews safe and ensure mission success.

Gerek Whitman↗

An evaluation of Turbo Prolog with an emphasis on its application to the development of expert systems

Turbo Prolog is a recently available, compiled version of the programming language Prolog. Turbo Prolog is designed to provide not only a Prolog compiler, but also a program development environment for the IBM Personal Computer family. An evaluation of Turbo Prolog was made, comparing its features to other versions of Prolog and to the community of languages commonly used in artificial intelligence (AI) research and development. Three programs were employed to determine the execution speed of Turbo Prolog applied to various problems. The results of this evaluation demonstrated that Turbo Prolog can perform much better than many commonly employed AI languages for numerically intensive problems and can equal the speed of development languages such as OPS5+ and CLIPS, running on the IBM PC. Applications for which Turbo Prolog is best suited include those which (1) lend themselves naturally to backward-chaining approaches, (2) require extensive use of mathematics, (3) contain few rules, (4) seek to make use of the window/color graphics capabilities of the IBM PC, and (5) require linkage to programs in other languages to form a complete executable image.

Loftin, Richard B.↗

Connecting a Community of Observers Directly to NASA Satellites

The Global Learning and Observations to Benefit the Environment (GLOBE) program is an international science and education initiative that gives students and the public worldwide an opportunity to participate in data collection and the scientific process and to contribute meaningfully to our understanding of Earth and the global environment. GLOBE launched in 1995, with the vision of bringing a worldwide community of students, teachers, scientists, and citizens together to better understand, sustain, and improve Earth's environment at local, regional, and global scales (https://www.globe.gov/about/overview).

Linda Hayden↗

Combustion of Interacting Droplet Arrays in a Microgravity Environment

This research program involves the study of single droplets and linear arrays of droplets in weakly-buoyant and non-bouyant environments. The primary purpose of the single droplet work was to (1) provide a data base from which to compare droplet array results and (2) to correlate the effects of buoyancy on flame shape. Traditionally convective effects in droplet combustion are represented in terms of the Reynolds number, Re, for forced convection and the Grashof number, Gr, for natural convection. Typically, corrections to the burning rate constant for convective effects are written in terms of Re or Gr(exp 1). The Stefan velocity is not included in these correlations, even though from purely physical reasons, one would expect it to be important, especially at higher burning rates. The flame distortion due to convective effects is less documented quantitatively. Kumagai and Isoda do predict flame shape in natural and forced convective flow fields. Their focus, however, was to predict the actual flame dimensions. Law and co-workers used reduced pressure, high oxidizer ambients to obtain spherical flames. This implies that buoyant flows were reduced at the low pressures, as indicated by a very small Grashof number. Ross et al, however, using scaling arguments showed that reducing the pressure does not have a large effect on the magnitude of the buoyant velocity. Struk et al showed elongated flame shapes during simulated (porous sphere) droplet combustion. The elongation of the flames was due to residual gravity levels aboard the reduced gravity aircraft on which the experiments were conducted. These flame shapes, as well as some data from the literature were interpreted based on a dimensionless grouping called the sphericity parameter, Sp. Sp is the ratio of a characteristic computed buoyant velocity to the Stefan velocity at the flame front. One purpose of the droplet arrays work is to extend the database and theories that exist for single droplets into the regime where droplet interactions are important. The eventual goal being to use the results of this work as inputs to models on spray combustion where droplets seldom burn individually; instead the combustion history of a droplet is strongly influenced by the presence of the neighboring droplets. Recently, Annamali and Ryan have summarized he current status of droplet array, cloud and spray combustion. A number of simplified theories led numerical studies of droplet vaporization/combustion where multiple droplet effects are present are now available. These theories all neglect the effect of buoyancy. Experimentally, most studies to date suffer the effects of buoyancy. It is the dominant transport mechanism in the problem. Only the works of Law and co-worker and more recently by Mikami et al were performed in an environment where buoyancy effects were small. Law and co-workers were limited to high oxygen index, low pressure ambient environments since there studies were conducted in normal gravity.

Dietrich, Daniel L.↗

Fiber Optic Repair and Maintainability (FORM) Program Progresses

Advanced aircraft will employ fiber-optic interconnection components to transmit information from airframe and propulsion sensors to the flight control computers. Although these optical interconnects have been rigorously tested under laboratory conditions to determine their operating and environmental limits, there is concern as to their repairability and maintainability when placed in actual service. The Fiber Optic Repair and Maintainability (FORM) flight test program will provide data to enable designers to improve these fiber-optic interconnection systems for the next generation of aircraft. FORM is identifying critical problems in installing, maintaining, testing, and repairing fiber-optic interconnection systems in an operational avionics environment. This program is a cooperative Government/industry effort to evaluate optical component acceptability and installation techniques for aircraft.

Source record↗

Acoustics Research of Propulsion Systems

The liftoff phase induces some of the highest acoustic loading over a broad frequency for a launch vehicle. These external acoustic environments are used in the prediction of the internal vibration responses of the vehicle and components. Thus, predicting these liftoff acoustic environments is critical to the design requirements of any launch vehicle but there are challenges. Present liftoff vehicle acoustic environment prediction methods utilize stationary data from previously conducted hold-down tests; i.e. static firings conducted in the 1960's, to generate 1/3 octave band Sound Pressure Level (SPL) spectra. These data sets are used to predict the liftoff acoustic environments for launch vehicles. To facilitate the accuracy and quality of acoustic loading, predictions at liftoff for future launch vehicles such as the Space Launch System (SLS), non-stationary flight data from the Ares I-X were processed in PC-Signal in two forms which included a simulated hold-down phase and the entire launch phase. In conjunction, the Prediction of Acoustic Vehicle Environments (PAVE) program was developed in MATLAB to allow for efficient predictions of sound pressure levels (SPLs) as a function of station number along the vehicle using semiempirical methods. This consisted, initially, of generating the Dimensionless Spectrum Function (DSF) and Dimensionless Source Location (DSL) curves from the Ares I-X flight data. These are then used in the MATLAB program to generate the 1/3 octave band SPL spectra. Concluding results show major differences in SPLs between the hold-down test data and the processed Ares IX flight data making the Ares I-X flight data more practical for future vehicle acoustic environment predictions.

Gao, Ximing↗

Transportability, distributability and rehosting experience with a kernel operating system interface set

For the past two years, PRC has been transporting and installing a software engineering environment framework, the Automated Product control Environment (APCE), at a number of PRC and government sites on a variety of different hardware. The APCE was designed using a layered architecture which is based on a standardized set of interfaces to host system services. This interface set called the APCE Interface Set (AIS), was designed to support many of the same goals as the Common Ada Programming Support Environment (APSE) Interface Set (CAIS). The APCE was developed to provide support for the full software lifecycle. Specific requirements of the APCE design included: automation of labor intensive administrative and logistical tasks: freedom for project team members to use existing tools: maximum transportability for APCE programs, interoperability of APCE database data, and distributability of both processes and data: and maximum performance on a wide variety of operating systems. A brief description is given of the APCE and AIS, a comparison of the AIS and CAIS both in terms of functionality and of philosophy and approach and a presentation of PRC's experience in rehosting AIS and transporting APCE programs and project data. Conclusions are drawn from this experience with respect to both the CAIS efforts and Space Station plans.

Blumberg, F. C.↗

Acoustics Research of Propulsion Systems

The liftoff phase induces high acoustic loading over a broad frequency range for a launch vehicle. These external acoustic environments are used in the prediction of the internal vibration responses of the vehicle and components. Present liftoff vehicle acoustic environment prediction methods utilize stationary data from previously conducted hold-down tests to generate 1/3 octave band Sound Pressure Level (SPL) spectra. In an effort to update the accuracy and quality of liftoff acoustic loading predictions, non-stationary flight data from the Ares I-X were processed in PC-Signal in two flight phases: simulated hold-down and liftoff. In conjunction, the Prediction of Acoustic Vehicle Environments (PAVE) program was developed in MATLAB to allow for efficient predictions of sound pressure levels (SPLs) as a function of station number along the vehicle using semi-empirical methods. This consisted of generating the Dimensionless Spectrum Function (DSF) and Dimensionless Source Location (DSL) curves from the Ares I-X flight data. These are then used in the MATLAB program to generate the 1/3 octave band SPL spectra. Concluding results show major differences in SPLs between the hold-down test data and the processed Ares I-X flight data making the Ares I-X flight data more practical for future vehicle acoustic environment predictions.

Gao, Ximing↗

Flight Dynamics Analysis System

Flight Dynamics Analysis System (FDAS) collection of computer programs provides environment for configuration and study of Ada software. Designed to support flight-dynamics research and analysis activities concerning software models, algorithms, and techniques used within flight Dynamics Division at Goddard Space Flight Center. Assists analysts and programmers in building, testing, and evaluating applications software by providing integrated support system for modification and reconfiguration of software. Includes capability of assembling reusable software components into applications programs, and reconfiguring assembled program after partially or fully completed. Developed in Ada for use on DEC VAX computer operating under VMS 4.3 or higher and version 1.3 or higher of VAX Ada Compilation System (ACS).

Tasaki, Keiji↗

Modelling the near-Earth space environment using LDEF data

Near-Earth space is a dynamic environment, that is currently not well understood. In an effort to better characterize the near-Earth space environment, this study compares the results of actual impact crater measurement data and the Space Environment (SPENV) Program developed in-house at POD, to theoretical models established by Kessler (NASA TM-100471, 1987) and Cour-Palais (NASA SP-8013, 1969). With the continuing escalation of debris there will exist a definite hazard to unmanned satellites as well as manned operations. Since the smaller non-trackable debris has the highest impact rate, it is clearly necessary to establish the true debris environment for all particle sizes. Proper comprehension of the near-Earth space environment and its origin will permit improvement in spacecraft design and mission planning, thereby reducing potential disasters and extreme costs. Results of this study directly relate to the survivability of future spacecraft and satellites that are to travel through and/or reside in low Earth orbit (LEO). More specifically, these data are being used to: (1) characterize the effects of the LEO micrometeoroid an debris environment on satellite designs and components; (2) update the current theoretical micrometeoroid and debris models for LEO; (3) help assess the survivability of spacecraft and satellites that must travel through or reside in LEO, and the probability of their collision with already resident debris; and (4) help define and evaluate future debris mitigation and disposal methods. Combined model predictions match relatively well with the LDEF data for impact craters larger than approximately 0.05 cm, diameter; however, for smaller impact craters, the combined predictions diverge and do not reflect the sporadic clouds identified by the Interplanetary Dust Experiment (IDE) aboard LDEF. The divergences cannot currently be explained by the authors or model developers. The mean flux of small craters (approximately 0.05 cm diameter) is overpredicted by Kessler and underpredicted by Cour-Palais. This divergence may be a result of beta-meteoroid fluxes, elliptical orbits or a combination of the two. The results of this study illustrate the definite need for more intensive study of the near-Earth space environment, particularly the small particle regime, as it is the most degrading to spacecraft in LEO.

Atkinson, Dale R.↗

ATK Launch Vehicle (ALV-X1) Liftoff Acoustic Environments: Prediction vs. Measurement

Launched from the Mid-Atlantic Regional Spaceport (MARS) Pad 01B on August 22, 2008, the ATK Launch Vehicle (ALV-X1) provided an opportunity to measure liftoff acoustic noise data. Predicted lift-off acoustic environments were developed by both NASA MSFC and ATK engineers. ATK engineers developed predictions for use in determining vibro-acoustic loads using the method described in the monograph NASA SP-8072. The MSFC ALV-X1 lift-off acoustic prediction was made with the Vehicle Acoustic Environment Prediction Program (VAEPP). The VAEPP and SP-8072 methods predict acoustic pressures of rocket systems generally scaled to existing rocket motor data based upon designed motor or engine characteristics. The predicted acoustic pressures are sound-pressure spectra at specific positions on the vehicle. This paper presents the measured liftoff acoustics on the vehicle and tower. This data is useful for the ALV-X1 in validating the pre-launch environments and loads predictions.

Houston, J.↗

Some key considerations in evolving a computer system and software engineering support environment for the space station program

The space station data management system involves networks of computing resources that must work cooperatively and reliably over an indefinite life span. This program requires a long schedule of modular growth and an even longer period of maintenance and operation. The development and operation of space station computing resources will involve a spectrum of systems and software life cycle activities distributed across a variety of hosts, an integration, verification, and validation host with test bed, and distributed targets. The requirement for the early establishment and use of an apporopriate Computer Systems and Software Engineering Support Environment is identified. This environment will support the Research and Development Productivity challenges presented by the space station computing system.

Mckay, C. W.↗

Architecture-Adaptive Computing Environment: A Tool for Teaching Parallel Programming

Recently, networked and cluster computation have become very popular. This paper is an introduction to a new C based parallel language for architecture-adaptive programming, aCe C. The primary purpose of aCe (Architecture-adaptive Computing Environment) is to encourage programmers to implement applications on parallel architectures by providing them the assurance that future architectures will be able to run their applications with a minimum of modification. A secondary purpose is to encourage computer architects to develop new types of architectures by providing an easily implemented software development environment and a library of test applications. This new language should be an ideal tool to teach parallel programming. In this paper, we will focus on some fundamental features of aCe C.

Dorband, John E.↗

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↗

Advanced space system concepts and their orbital support needs (1980 - 2000). Volume 4: Detailed data. Part 2: Program plans and common support needs (a study of the commonality of space vehicle applications to future national needs

The methodology of alternate world future scenarios is utilized for selecting a plausible, though not advocated, set of future scenarios each of which results in a program plan appropriate for the respective environment. Each such program plan gives rise to different building block and technology requirements, which are analyzed for common need between the NASA and the DoD for each of the alternate world scenarios. An essentially invariant set of system, building block, and technology development plans is presented at the conclusion, intended to allow protection of most of the options for system concepts regardless of what the actual future world environment turns out to be. Thus, building block and technology needs are derived which support: (1) each specific world scenario; (2) all the world scenarios identified in this study; or (3) generalized scenarios applicable to almost any future environment. The output included in this volume consists of the building blocks, i.e.: transportation vehicles, orbital support vehicles, and orbital support facilities; the technology required to support the program plans; identification of their features which could support the DoD and NASA in common; and a complete discussion of the planning methodology.

Bekey, I.↗

System Administration Support/SWORDS G2

The Soldier-Warfighter Operationally Responsive Deployer for Space (SWORDS) rocket is a dedicated small satellite launcher that will minimize danger and complexity in order to allow soldiers in the field to put payloads of up to 25kg into orbit from the field. The SWORDSG2 project is the development of a model, simulation, and ultimately a working application that will control and monitor the cryogenic fluid delivery to the SWORDS rocket for testing purposes. To accomplish this, the project is using the programming language environment Gensym G2. The environment is an all-inclusive application that allows development, testing, modeling, and finally operation of the unique application through graphical and programmatic methods. In addition, observation of the current cryogenic fluid delivery system in the Kennedy Space Center Cry Lab has allowed me to gain valuable experience of fluid systems and propelant delivery that is valuable to our team when developing amd modeling our own system.The ultimate goal of having a test-ready application to show to the heads of the project, and demonstrating G2's capabilities, by late 2014 will require hard work and intense study and understanding of not only the programming aspect but also the physical phenomena we want to model, observe, and control.

cryogenic fluids↗

Evaluation of dispersion strengthened nickel-base alloy heat shields for space shuttle application

The work reported constitutes the first phase of a two-phase program. Vehicle environments having critical effects on the thermal protection system are defined; TD Ni-20Cr material characteristics are reviewed and compared with TD Ni-20Cr produced in previous development efforts; cyclic load, temperature, and pressure effects on TD Ni-20Cr sheet material are investigated; the effects of braze reinforcement in improving the efficiency of spotwelded, diffusion-bonded, or seam-welded joints are evaluated through tests of simple lap-shear joint samples; parametric studies of metallic radiative thermal protection systems are reported; and the design, instrumentation, and testing of full-scale subsize heat shield panels are described. Tests of full-scale subsize panels included simulated meteoroid impact tests; simulated entry flight aerodynamic heating in an arc-heated plasma stream; programmed differential pressure loads and temperatures simulating mission conditions; and acoustic tests simulating sound levels experienced by heat shields during about boost flight. Test results are described, and the performances of two heat shield designs are compared and evaluated.

Johnson, R., Jr.↗