SEARCH · Engineering Papers

Results for “Software testing”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

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

At least 1,009 records · Page 56

All sources NASA NTRS DOE OSTI

NASA NTRS1989

Software package for performing experiments about the convolutionally encoded Voyager 1 link

A software package enabling engineers to conduct experiments to determine the actual performance of long constraint-length convolutional codes over the Voyager 1 communication link directly from the Jet Propulsion Laboratory (JPL) has been developed. Using this software, engineers are able to enter test data from the Laboratory in Pasadena, California. The software encodes the data and then sends the encoded data to a personal computer (PC) at the Goldstone Deep Space Complex (GDSC) over telephone lines. The encoded data are sent to the transmitter by the PC at GDSC. The received data, after being echoed back by Voyager 1, are first sent to the PC at GDSC, and then are sent back to the PC at the Laboratory over telephone lines for decoding and further analysis. All of these operations are fully integrated and are completely automatic. Engineers can control the entire software system from the Laboratory. The software encoder and the hardware decoder interface were developed for other applications, and have been modified appropriately for integration into the system so that their existence is transparent to the users. This software provides: (1) data entry facilities, (2) communication protocol for telephone links, (3) data displaying facilities, (4) integration with the software encoder and the hardware decoder, and (5) control functions.

Cheng, U.↗

NASA NTRS2004

Theoretical Tools and Software for Modeling, Simulation and Control Design of Rocket Test Facilities

A rocket test stand and associated subsystems are complex devices whose operation requires that certain preparatory calculations be carried out before a test. In addition, real-time control calculations must be performed during the test, and further calculations are carried out after a test is completed. The latter may be required in order to evaluate if a particular test conformed to specifications. These calculations are used to set valve positions, pressure setpoints, control gains and other operating parameters so that a desired system behavior is obtained and the test can be successfully carried out. Currently, calculations are made in an ad-hoc fashion and involve trial-and-error procedures that may involve activating the system with the sole purpose of finding the correct parameter settings. The goals of this project are to develop mathematical models, control methodologies and associated simulation environments to provide a systematic and comprehensive prediction and real-time control capability. The models and controller designs are expected to be useful in two respects: 1) As a design tool, a model is the only way to determine the effects of design choices without building a prototype, which is, in the context of rocket test stands, impracticable; 2) As a prediction and tuning tool, a good model allows to set system parameters off-line, so that the expected system response conforms to specifications. This includes the setting of physical parameters, such as valve positions, and the configuration and tuning of any feedback controllers in the loop.

Richter, Hanz↗

NASA NTRS2011

NASA Technology Demonstrations Missions Program Overview

The National Aeronautics and Space Administration (NASA) Fiscal Year 2010 (FY10) budget introduced a new strategic plan that placed renewed emphasis on advanced missions beyond Earth orbit. This supports NASA s 2011 strategic goal to create innovative new space technologies for our exploration, science, and economic future. As a result of this focus on undertaking many and more complex missions, NASA placed its attention on a greater investment in technology development, and this shift resulted in the establishment of the Technology Demonstrations Missions (TDM) Program. The TDM Program, within the newly formed NASA Office of the Chief Technologist, supports NASA s grand challenges by providing a steady cadence of advanced space technology demonstrations (Figure 1), allowing the infusion of flexible path capabilities for future exploration. The TDM Program's goal is to mature crosscutting capabilities to flight readiness in support of multiple future space missions, including flight test projects where demonstration is needed before the capability can transition to direct mission The TDM Program has several unique criteria that set it apart from other NASA program offices. For instance, the TDM Office matures a small number of technologies that are of benefit to multiple customers to flight technology readiness level (TRL) 6 through relevant environment testing on a 3-year development schedule. These technologies must be crosscutting, which is defined as technology with potential to benefit multiple mission directorates, other government agencies, or the aerospace industry, and they must capture significant public interest and awareness. These projects will rely heavily on industry partner collaboration, and funding is capped for all elements of the flight test demonstration including planning, hardware development, software development, launch costs, ground operations, and post-test assessments. In order to inspire collaboration across government and industry, more than 70% of the TDM funds will be competitively awarded as a result of yearly calls for proposed flight demonstrators and selected based on possible payoff to NASA, technology maturity, customer interest, cost, and technical risk reduction. This paper will give an overview of the TDM Program s mission and organization, as well as its current status in delivering advanced space technologies that will enable more flexible and robust future missions. It also will provide several examples of missions that fit within these parameters and expected outcomes.

Turner, Susan↗

NASA NTRS1976

Analysis of test data on the simplex strapdown navigation system

The results of a study of test data taken on the simplex strapdown navigation system were presented. That system consisted of the following components: strapdown platform, altimeter, digital computer, tape recorder, typewriter, and power source. The objective of these tests was to isolate error sources which may cause degradation of the system's accuracy and to recommend appropriate changes to the system test procedures or computer software. The following recommendations were made: (1) addition of a gyro compassing alignment program into the navigation program, (2) addition of line drivers at the signal processor end of the transmission line, (3) need for extensive laboratory testing to determine sensor misalignments, biases, and scale factors, (4) need to stabilize the power source to prevent transients during power transfer, (5) need to isolate and eliminate the source of the large noise inputs.

Source record↗

DOE OSTI2023

Standards, dissemination, and best practices in systems biology

In this study, the reproducibility of scientific research is crucial to the success of the scientific method. Here, we review the current best practices when publishing mechanistic models in systems biology. We recommend, where possible, to use software engineering strategies such as testing, verification, validation, documentation, versioning, iterative development, and continuous integration. In addition, adhering to the Findable, Accessible, Interoperable, and Reusable modeling principles allows other scientists to collaborate and build off of each other’s work. Existing standards such as Systems Biology Markup Language, CellML, or Simulation Experiment Description Markup Language can greatly improve the likelihood that a published model is reproducible, especially if such models are deposited in well-established model repositories. Where models are published in executable programming languages, the source code and their data should be published as open-source in public code repositories together with any documentation and testing code. For complex models, we recommend container-based solutions where any software dependencies and the run-time context can be easily replicated.

59 BASIC BIOLOGICAL SCIENCES↗

DOE OSTI2020

UnitTesterSG

UnitTesterSG is a unit testing framework that is designed for nested and/or scientific/engineering data structures. It is designed primarily for testing the outputs if a single function or simulation run by storing the expected results file such that comparisons to the stored output can be made with unit tests after the function or software has been edited. This module is designed to be able to unit test arrays, strings, as well as nested and deeply nested objects (including arrays with tuples inside, arrays with strings inside, etc.). The module is compatable with nested objects, and thus has a dependency on the nestedObjectsFunctions module within. The module takes *calculated* results and then compares them to *expected* results. If no expected results are available (or they do not match the calculated results) the module then offers to store the calculated results as expected results for next time.

Savara, Aditya [Oak Ridge National Lab. (ORNL), Oa↗

NASA NTRS1989

Hardware impacts to software development strategies - The history of the development of the Mars Observer Payload Data Subsystem embedded real-time software

Ways in which parallel hardware development and high level requirements changes have influenced Mars Observer Payload Data Subsystem (PDS) flight software development are discussed. Particular attention is given to ways in which the evolving hardware product and changing requirements have led to repeated modification to software requirements, design, code, and test tools and a delay in the closure of corresponding phases of the software development life cycle. Design and implementation problems which were encountered during the PDS software development effort are described.

Elson, Anne B.↗

NASA NTRS1976

Time Series Analysis in Flight Flutter Testing at the Air Force Flight Test Center: Concepts and Results

The Air Force Flight Test Center (AFFTC) flight flutter facility is described. Concepts of using a minicomputer-based time series analyzer and a modal analysis software package for flight flutter testing are examined. The results of several evaluations of the software package are given. The reasons for employing a minimum phase concept in analyzing response only signals are discussed. The use of a Laplace algorithm is shown to be effective for the modal analysis of time histories in flutter testing. Sample results from models and flight tests are provided. The limitations inherent in time series analysis methods are discussed, and the need for effective noise reduction techniques is noted. The use of digital time series analysis techniques in flutter testing is shown to be fast, accurate, and cost effective.

Lenz, R. W.↗

NASA NTRS1994

A study of a multi-pinned phase CCD detector for use as a star tracker

This grant has supported studies of the use of charge coupled devices (CCD's) in star trackers in a number of different areas. Among the tasks we have pursued are the following: (1) radiation modeling and the increase in noise equivalent angle as a result of exposure to protons and bremsstrahlung gamma rays; (2) the development of pattern matching software to identify field locations from a CCD image and a pre-existing map of the local area; (3) observations of various stellar fields from the 24 inch telescope at the Offit Observatory at JHU, primarily to test the pattern matching software (these included crowded fields as well as moving objects, like comets); and (4) tracking of very faint objects to determine the faint limit of the CCD system.

Friedman, Scott D.↗

NASA NTRS2016

Liquid Oxygen/Liquid Methane Integrated Power and Propulsion

The proposed paper will cover ongoing work at the National Aeronautics and Space Administration (NASA) Johnson Space Center (JSC) on integrated power and propulsion for advanced human exploration. Specifically, it will present findings of the integrated design, testing, and operational challenges of a liquid oxygen / liquid methane (LOx/LCH4) propulsion brassboard and Solid Oxide Fuel Cell (SOFC) system. Human-Mars architectures point to an oxygen-methane economy utilizing common commodities, scavenged from the planetary atmosphere and soil via In-Situ Resource Utilization (ISRU), and common commodities across sub-systems. Due to the enormous mass gear-ratio required for human exploration beyond low-earth orbit, (for every 1 kg of payload landed on Mars, 226 kg will be required on Earth) increasing commonality between spacecraft subsystems such as power and propulsion can result in tremendous launch mass and volume savings. Historically, propulsion and fuel cell power subsystems have had little interaction outside of the generation (fuel cell) and consumption (propulsion) of electrical power. This was largely due to a mismatch in preferred commodities (hypergolics for propulsion; oxygen & hydrogen for fuel cells). Although this stove-piped approach benefits from simplicity in the design process, it means each subsystem has its own tanks, pressurization system, fluid feed system, etc. increasing overall spacecraft mass and volume. A liquid oxygen / liquid methane commodities architecture across propulsion and power subsystems would enable the use of common tankage and associated pressurization and commodity delivery hardware for both. Furthermore, a spacecraft utilizing integrated power and propulsion could use propellant residuals - propellant which could not be expelled from the tank near depletion due to hydrodynamic considerations caused by large flow demands of a rocket engine - to generate power after all propulsive maneuvers are complete thus utilizing previously wasted mass. Such is the case for human and robotic planetary landers. Although many potential benefits through integrated power & propulsion exist, integrated operations have yet to be successfully demonstrated and many challenges have already been identified the most obvious of which is the large temperature gradient. SOFC chemistry is exothermic with operating temperatures in excess of 1,000 K; however, any shared commodities will be undoubtedly stored at cryogenic temperatures (90-112 K) for mass efficiency reasons. Spacecraft packaging will drive these two subsystems in close proximity thus heat leak into the commodity tankage must be minimized and/or mitigated. Furthermore, commodities must be gasified prior to consumption by the SOFC. Excess heat generated by the SOFC could be used to perform this phase change; however, this has yet to be demonstrated. A further identified challenge is the ability of the SOFC to handle the sudden power spikes created by the propulsion system. A power accumulator (battery) will likely be necessary to handle these sudden demands while the SOFC thermally adjusts. JSC's current SOFC test system consists of a 1 kW fuel cell designed by Delphi. The fuel cell is currently undergoing characterization testing at the NASA JSC Energy Systems Test Area (ESTA) after which a Steam Methane Reformer (SMR) will be integrated and the combined system tested in closed-loop. The propulsion brassboard is approximately the size of what could be flown on a sounding rocket. It consists of one 100 lbf thrust "main" engine developed for NASA by Aerojet and two 10 lbf thrusters to simulate a reaction control system developed at NASA JSC. This system is also under development and initial testing at ESTA. After initial testing, combined testing will occur which will provide data on the fuel cell's ability to sufficiently handle the power spikes created by the propulsion system. These two systems will also be modeled using General-Use Nodal Network Solver (GUNNS) software. Once anchored with test data, this model will be used to extrapolate onto other firing profiles and used to size the power accumulator.

Banker, Brian↗

DOE OSTI2021

Influence of Fuel Properties on Gasoline Direct Injection Particulate Matter Emissions Over First 200 s of World-Harmonized Light-Duty Test Procedure Using an Engine Dynamometer and Novel “Virtual Drivetrain” Software

Abstract The influence of fuel properties on particulate matter (PM) emissions from a catalytic gasoline particulate filter (GPF) equipped gasoline direct injection (GDI) engine was investigated using novel “virtual drivetrain” software and an engine mated to an engine dynamometer. The virtual drivetrain software was developed in labview to operate the engine on an engine dynamometer as if it were in a vehicle undergoing a driving cycle. The software uses a physics-based approach to determine vehicle acceleration and speed based on engine load and a programed “shift” schedule to control engine speed. The software uses a control algorithm to modulate engine load and braking to match a calculated vehicle speed with the prescribed speed trace of the driving cycle of choice. The first 200 s of the World-harmonized Light-duty Test Procedure (WLTP) driving cycle was tested using six different fuel formulations of varying volatility, aromaticity, and ethanol concentration. The first 200 s of the WLTP was chosen as the test condition because it is the most problematic section of the driving cycle for controlling PM emissions due to the cold start and cold drive off. It was found that there was a strong correlation between aromaticity of the fuel and the engine-out PM emissions, with the highest emitting fuel producing more than double the mass emissions of the low PM production fuel. However, the post-GPF PM emissions depended greatly on the soot loading state of the GPF. The fuel with the highest engine-out PM emissions produced comparable post-GPF emissions to the lowest PM producing fuel over the driving cycle when the GPF was loaded over three cycles with the respective fuels. These results demonstrate the importance of GPF loading state when aftertreatment systems are used for PM reduction. It also shows that GPF control may be more important than fuel properties, and that regulatory compliance for PM can be achieved with proper GPF control calibration irrespective of fuel type.

Energy & Fuels↗

NASA NTRS2016

Experimenting Galileo on Board the International Space Station

The SCaN Testbed is an advanced integrated communications system and laboratory facility installed on the International Space Station (ISS) in 2012. The testbed incorporates a set of new generation of Software Defined Radio (SDR) technologies intended to allow researchers to develop, test, and demonstrate new communications, networking, and navigation capabilities in the actual environment of space. Qascom, in cooperation with ESA and NASA, is designing a Software Defined Radio GalileoGPS Receiver capable to provide accurate positioning and timing to be installed on the ISS SCaN Testbed. The GalileoGPS waveform will be operated in the JPL SDR that is constituted by several hardware components that can be used for experimentations in L-Band and S-Band. The JPL SDR includes an L-Band Dorne Margolin antenna mounted onto a choke ring. The antenna is connected to a radio front end capable to provide one bit samples for the three GNSS frequencies (L1, L2 and L5) at 38 MHz, exploiting the subharmonic sampling. The baseband processing is then performed by an ATMEL AT697 processor (100 MIPS) and two Virtex 2 FPGAs. The JPL SDR supports the STRS (Space Telecommunications Radio System) that provides common waveform software interfaces, methods of instantiation, operation, and testing among different compliant hardware and software products. The standard foresees the development of applications that are modular, portable, reconfigurable, and reusable. The developed waveform uses the STRS infrastructure-provided application program interfaces (APIs) and services to load, verify, execute, change parameters, terminate, or unload an application. The project is divided in three main phases. 1)Design and Development of the GalileoGPS waveform for the SCaN Testbed starting from Qascom existing GNSS SDR receiver. The baseline design is limited to the implementation of the single frequency Galileo and GPS L1E1 receiver even if as part of the activity it will be to assess the feasibility of a dual frequency implementation (L1E1+L5E5a) in the same SDR platform.2)Qualification and test the GalileoGPS waveform using ground systems available at the NASA Glenn Research Center. Experimenters can have access to two SCaN Testbed ground based systems for development and verification: the Experimenter Development System (EDS) that is intended to provide initial opportunity for software testing and basic functional validation and the Ground Integration Unit (GIU) that is a high fidelity version of the SCaN Testbed flight system and is therefore used for more controlled final development testing and verification testing.3)Perform in-orbit validation and experimentation: The experimentation phase will consists on the collection of raw measurements (pseudorange, Carrier phase, CN0) in space, assessment on the quality of the measurements and the receiver performances in terms of signal acquisition, tracking, etc. Finally computation of positioning in space (Position, Velocity and time) and assessment of its performance.(Complete abstract in attached document).

Galileo↗

NASA NTRS2016

Experimenting Galileo on Board the International Space Station

GPS↗

NASA NTRS2013

Final Report - Regulatory Considerations for Adaptive Systems

This report documents the findings of a preliminary research study into new approaches to the software design assurance of adaptive systems. We suggest a methodology to overcome the software validation and verification difficulties posed by the underlying assumption of non-adaptive software in the requirementsbased- testing verification methods in RTCA/DO-178B and C. An analysis of the relevant RTCA/DO-178B and C objectives is presented showing the reasons for the difficulties that arise in showing satisfaction of the objectives and suggested additional means by which they could be satisfied. We suggest that the software design assurance problem for adaptive systems is principally one of developing correct and complete high level requirements and system level constraints that define the necessary system functional and safety properties to assure the safe use of adaptive systems. We show how analytical techniques such as model based design, mathematical modeling and formal or formal-like methods can be used to both validate the high level functional and safety requirements, establish necessary constraints and provide the verification evidence for the satisfaction of requirements and constraints that supplements conventional testing. Finally the report identifies the follow-on research topics needed to implement this methodology.

Wilkinson, Chris↗

NASA NTRS2007

Triaxial Probe Magnetic Data Analysis

The Triaxial Magnetic Moment Analysis software uses measured magnetic field test data to compute dipole and quadrupole moment information from a hardware element. It is used to support JPL projects needing magnetic control and an understanding of the spacecraft-generated magnetic fields. Evaluation of the magnetic moment of an object consists of three steps: acquisition, conditioning, and analysis. This version of existing software was extensively rewritten for easier data acquisition, data analysis, and report presentation, including immediate feedback to the test operator during data acquisition. While prior JPL computer codes provided the same data content, this program has a better graphic display including original data overlaid with reconstructed results to show goodness of fit accuracy and better appearance of the report graphic page. Data are acquired using three magnetometers and two rotations of the device under test. A clean acquisition user interface presents required numeric data and graphic summaries, and the analysis module yields the best fit (least squares) for the magnetic dipole and/or quadrupole moment of a device. The acquisition module allows the user to record multiple data sets, selecting the best data to analyze, and is repeated three times for each of the z-axial and y-axial rotations. In this update, the y-axial rotation starting position has been changed to an option, allowing either the x- or z-axis to point towards the magnetometer. The code has been rewritten to use three simultaneous axes of magnetic data (three probes), now using two "rotations" of the device under test rather than the previous three rotations, thus reducing handling activities on the device under test. The present version of the software gathers data in one-degree increments, which permits much better accuracy of the fit ted data than the coarser data acquisition of the prior software. The data-conditioning module provides a clean data set for the analysis module. For multiple measurements at a given degree, the first measurement is used. For omitted measurements, the missing field is estimated by linear interpolation between the two nearest measurements. The analysis module was rewritten for the dual rotation, triaxial probe measurement process and now has better moment estimation accuracy, based on the finer one degree of data acquisition resolution. The magnetic moments thus computed are used as an input to summarize the total spacecraft field.

Shultz, Kimberly↗

NASA NTRS1998

Antiterrorist Software

In light of the escalation of terrorism, the Department of Defense spearheaded the development of new antiterrorist software for all Government agencies by issuing a Broad Agency Announcement to solicit proposals. This Government-wide competition resulted in a team that includes NASA Lewis Research Center's Computer Services Division, who will develop the graphical user interface (GUI) and test it in their usability lab. The team launched a program entitled Joint Sphere of Security (JSOS), crafted a design architecture (see the following figure), and is testing the interface. This software system has a state-ofthe- art, object-oriented architecture, with a main kernel composed of the Dynamic Information Architecture System (DIAS) developed by Argonne National Laboratory. DIAS will be used as the software "breadboard" for assembling the components of explosions, such as blast and collapse simulations.

Clark, David A.↗

DOE OSTI2024

Julienne v1.0.0

Julienne is a compiler-portable unit-testing framework for Fortran software projects, including those that use the parallel/accelerator-programming features of Fortran 2023. Julienne achieves portability across compilers through minimalism and isolation. The minimal design ensures that Julienne uses only features supported by the majority of Fortran compilers. The isolation through zero dependencies ensures that no other projects block Julienne from building with a particular compiler. Julienne also contains with additional services that support its unit-testing code. These include functions for manipulating strings, command lines and input/output format strings; and a user-defined collective subroutine for verifying that all processes pass a test in parallel testing. Julienne's name derives from the term for vegetables sliced into thin strings: julienne vegetables. Julienne captures the authors' most frequently used thin slice of the Veggies and Sourcery software repositories while avoiding certain compiler limitations of the those two packages.

Rouson, Damian↗

NASA NTRS1993

From requirements to acceptance tests

From user requirements definition to accepted software system, the software project management wants to be sure that the system will meet the requirements. For the development of a telecommunication satellites Control Centre, C.N.E.S. has used new rules to make the use of tracing matrix easier. From Requirements to Acceptance Tests, each item of a document must have an identifier. A unique matrix traces the system and allows the tracking of the consequences of a change in the requirements. A tool has been developed, to import documents into a relational data base. Each record of the data base corresponds to an item of a document, the access key is the item identifier. Tracing matrix is also processed, providing automatically links between the different documents. It enables the reading on the same screen of traced items. For example one can read simultaneously the User Requirements items, the corresponding Software Requirements items and the Acceptance Tests.

Baize, Lionel↗