Search NASA⌕ Search

SEARCH · Search NASA

Results for “Unit 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.

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

At least 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

Activate/Inhibit KGCS Gateway via Master Console EIC Pad-B Display

My internship consisted of two major projects for the Launch Control System.The purpose of the first project was to implement the Application Control Language (ACL) to Activate Data Acquisition (ADA) and to Inhibit Data Acquisition (IDA) the Kennedy Ground Control Sub-Systems (KGCS) Gateway, to update existing Pad-B End Item Control (EIC) Display to program the ADA and IDA buttons with new ACL, and to test and release the ACL Display.The second project consisted of unit testing all of the Application Services Framework (ASF) by March 21st. The XmlFileReader was unit tested and reached 100 coverage. The XmlFileReader class is used to grab information from XML files and use them to initialize elements in the other framework elements by using the Xerces C++ XML Parser; which is open source commercial off the shelf software. The ScriptThread was also tested. ScriptThread manages the creation and activation of script threads. A large amount of the time was used in initializing the environment and learning how to set up unit tests and getting familiar with the specific segments of the project that were assigned to us.

Computer Programming↗
NASA NTRS2008

Charge-Control Unit for Testing Lithium-Ion Cells

A charge-control unit was developed as part of a program to validate Li-ion cells packaged together in batteries for aerospace use. The lithium-ion cell charge-control unit will be useful to anyone who performs testing of battery cells for aerospace and non-aerospace uses and to anyone who manufacturers battery test equipment. This technology reduces the quantity of costly power supplies and independent channels that are needed for test programs in which multiple cells are tested. Battery test equipment manufacturers can integrate the technology into their battery test equipment as a method to manage charging of multiple cells in series. The unit manages a complex scheme that is required for charging Li-ion cells electrically connected in series. The unit makes it possible to evaluate cells together as a pack using a single primary test channel, while also making it possible to charge each cell individually. Hence, inherent cell-to-cell variations in a series string of cells can be addressed, and yet the cost of testing is reduced substantially below the cost of testing each cell as a separate entity. The unit consists of electronic circuits and thermal-management devices housed in a common package. It also includes isolated annunciators to signal when the cells are being actively bypassed. These annunciators can be used by external charge managers or can be connected in series to signal that all cells have reached maximum charge. The charge-control circuitry for each cell amounts to regulator circuitry and is powered by that cell, eliminating the need for an external power source or controller. A 110-VAC source of electricity is required to power the thermal-management portion of the unit. A small direct-current source can be used to supply power for an annunciator signal, if desired.

Reid, Concha M.↗
NASA NTRS1997

EOS-AM1 Nickel Hydrogen Cell

This paper reports the interim results of the Earth Observing System AM-1 project (EOS-AM-1) nickel hydrogen cell life test being conducted under contract to National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) at the Lockheed Martin Missile and Space (LMMS) facility in East Windsor, NJ; and at COMSAT Labs., Clarksburg, MD. The purpose of die tests is to verify that the EOS-AM-1 cell design can meet five years of real-time Low Earth Orbit (LEO) cycling. The tests include both real-time LEO and accelerated stress tests. At LMMS, the first real-time LEO simulated 99 minute orbital cycle started on February 7, 1994 and the test has been running continuously since that time, with 18,202 LEO cycles completed as of September 1, 1997. Each cycle consists of a 64 minute charge (VT at 1.507 volts per cell, 1.06 C/D ratio, followed by 0.6 ampere trickle charge) and a 35 minute constant power discharge at 177 watts (22.5% DOD). At COMSAT, the accelerated stress test consists of 90 minute orbital cycles at 60% DOD with a 30 minute discharge at 60 amperes and a 60 minute charge at 40 amperes (VT at 1.54 volts per cell to 1.09 C/D ratio, followed by 0.6 ampere trickle charge). The real-time LEO life test battery consists of seven, 50AH (nameplate rating) Eagle-Picher, Inc. (EPI) Mantech cells manufactured into three, 3-cell pack assemblies (there are two place holder cells that are not part of the life test electrical circuit). The test pack is configured to simulate the conductive thermal design of the spacecraft battery, including: conductive aluminum sleeves, 3-cell pack aluminum baseplate, and honeycomb panel all mounted to a liquid (-5 C) cold plate. The entire assembly is located in a thermal chamber operating at +30 C. The accelerated stress test unit consists of five cells mounted in machined aluminum test sleeves and is operating at +10 C. The real-time LEO life test battery has met all performance requirements through the first 18,202 cycles, including: end of charge mid discharge cell voltages and voltage gradients; end of charge and discharge cell pressures; within cell and between cell temperature gradients; discharge capacity; current and power levels; and all charge parameters. The accelerated stress test battery has completed 11,998 cycles when the test was terminated. The stress test unit met all test parameters. This paper reports battery perfortnances as a funcfion of cycle life for both the real-time LEO and the accelerated life test regimes.

Bennett, Charles W.↗
NASA NTRS1998

EOS-AM1 Nickel Hydrogen Cell Interim Life Test Report

This paper reports the interim results Earth Observing System AM-1 project (EOS-AM-1) nickel hydrogen cell life test being conducted under contract to National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) at the Lockheed Martin Missiles and Space (LMMS) facility in East Windsor, NJ; and at COMSAT Labs., Clarksburg, MD. The purpose of the tests is to verify that the EOS-AM-1 cell design can meet five years of real-time Low Earth Orbit (LEO) cycling. The tests include both real-time LEO and accelerated stress tests. At LMMS, the first real-time LEO simulated 99 minute orbital cycle started on February 7, 1994 and the test has been running continuously since that time, with 18202 LEO cycles completed as of September 1, 1997. Each cycle consists of a 64-minute charge (VT at 1,507 volts per cell, 1.06 C/D ratio, followed by 0.6 ampere trickle charge) and a 35 minute constant power discharge at 177 watts (22.5 percent DOD). At COMSAT, the accelerated stress test consists of 90 minute orbital cycles at 60 percent DOD with a 30 minute discharge at 60 amperes and a 60 minute charge at 40 amperes (VT at 1.54 volts per cell to 1.90 C/D ratio, followed by 0.6 ampere trickle charge). The real-time LEO life test battery consists of seven, 50AH (nameplate rating) Eagle-Picher, Inc. (EPI) Mantech cells manufactured into three, 3-cell pack assemblies (there are two place holder cells that are not part of the life test electrical circuit). The test pack is configured to simulate the conductive thermal design of the spacecraft battery, including: conductive aluminum sleeves, 3-cell pack aluminum baseplate, and honeycomb panel all mounted to a liquid (minus 5 deg) cold plate. The entire assembly is located in a thermal chamber operating at plus 3 deg. The accelerated stress test unit consists of five cells mounted in machined aluminum test sleeves and is operating at plus 10 deg. The real-time LEO life test battery has met all performance requirements through the first 18,202 cycles, including: end of charge and discharge cell voltages and voltage gradients; end of charge and discharge cells pressures; within cell and between cell temperature gradients dischare capacity; current and power levels; and all charge parameters. The accelerated stress test battery has completed 11998 cycles when the test was terminated. The stress test unit met all test parameters. This paper reports battery performances as a function of cycle life for both the real-time LEO and the accelerated life test regimes.

Bennett, Charles W.↗
NASA NTRS1999

EOS--AM1 Nickel Hydrogen Cell Interim Life Test Report

This paper reports the interim results of the Earth Observing System AM-1 project (EOS-AM-1) nickel hydrogen cell life test being conducted under contract to National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) at the Lockheed Martin Missiles and Space (LMMS) facility in East Windsor, NJ; and at COMSAT Labs., Clarksburg, MD. The purpose of the tests is to verify that the EOS-AM-1 cell design can meet five years of real-time Low Earth Orbit (LEO) cycling. The tests include both real-time LEO and accelerated stress tests. At LMMS, the first real-time LEO simulated 99 minute orbital cycle started on February 7, 1994 and the test has been running continuously since that time, with 18202 LEO cycles completed as of September 1, 1997. Each cycle consists of a 64 minute charge (VT at 1.507 volts per cell. 1.06 C/D ratio, followed by 0.6 ampere trickle charge) and a 35 minute constant power discharge at 177 watts (22.5% DOD). At COMSAT, the accelerated stress test consists of 90 minute orbital cycles at 60% DOD with a 30 minute discharge at 60 amperes and a 60 minute charge at 40 amperes (VT at 1.54 volts per cell to 1.09 C/D ratio, followed by 0.6 ampere trickle charge). The real-time LEO life test battery consists of seven, 50AH (nameplate rating) Eagle-Picher, Inc. (EPI) Mantech cells manufactured into three. 3-cell pack assemblies (there are two place holder cells that are not part of the life test electrical circuit). The test pack is configured to simulate the conductive thermal design of the spacecraft battery, including: conductive aluminum sleeves, 3-cell pack aluminum baseplate, and honeycomb panel all mounted to a liquid (-5 C) cold plate. The entire assembly is located in a thermal chamber operatina at +30 C. The accelerated stress test unit consists of five cells mounted in machined aluminum test sleeves and is operating at +10 C. The real-time LEO life test battery has met all performance requirements throuch the first 18,202 cycles, including: end of chargee and discharge cell voltages and voltace -radients; end of charge and discharge cell pressures; within cell and between cell temperature gradients; discharge capacity; current and power levels; and all charge parameters. The accelerated stress test battery has completed 11,998 cycles when the test was terminated. The stress test unit met all test parameters. This paper reports battery performances as a function of cycle life for both the real time LEO and the accelerated life test regimes.

Bennett, C. W.↗
NASA NTRS2001

Testing and Calibration of the NASA COR1 Coronagraph for the Solar Terrestrial Relations Observatory (STEREO)

This proposal is for a no cost extension on the period of performance of the existing grant. The period of performance shall be extended to the end of FY 2003. This extension is required due to schedule changes in the COR1 program. Funding for Phase II and Phase III of this grant has been obtained. This unsolicited proposal was for scientific and engineering collaboration between NASA s Goddard Space Flight Center (GSFC) and HAO. Performance testing of the COR1 engineering test unit has been partially completed. The COR1 coronagraph engineering test unit requires further testing at NASA s GSFC and the National Center for Atmospheric Research (NCAR) Mauna Loa Solar Observatory (MLSO), operated by the High Altitude Observatory (HAO). HAO personnel have recently supported efforts to test component and breadboard versions of the COR1 using the NCAR Vacuum Tunnel Facility (NVTF). HAO personnel will continue to work closely with scientists and engineers at NASA/GSFC in the development, design, assembly, testing, and operation of this key element of NASA's Solar Terrestrial Relations Observatory (STEREO) mission. The element is an internally-occulted coronagraphic telescope, and the design and development effort is already underway at GSFC.

Burkepile, J. T.↗
NASA NTRS2011

Development of the ASTRO-H Soft X-ray Telescope (SXT): Engineering Model Performance

The X-ray astronomy satellite ASTRO-H, being developed under the collaboration among JAXA, NASA's GSFC and ESA, will have two Soft X-ray Telescopes (SXTs), among other instuments onboard, with a sensitive energy band below 12 keV. One is for an X-ray micorocalorimeter detector and the other for a X-ray CCD detector. The SXT uses a conically approximated Wolter I grazing incidence optic implemented by thin aluminum foil substrates with thickness of 0.152, 0.229, and 0.305 mm. It is similar to the Suzaku XRT, but with larger diameter (45 cm) and longer focal length (5.6 m). Goal of the angular resolution and effective area are 1 arcmin and 390 cm$A2$ at 6 keV, respectively. We made serveral improvements from Suzaku to ASTRO-H, such as thicker substrates, more forming mandrels, thinner epoxy layer for replication, stiffer housings, precise alignment bars, etc. With all these changes, we have fabricated the engineering test unit of the SXT. In this paper, we will discuss all the changes made, their effects, and report X-ray performance of the SXT test unit. An angular resolution of the test unit was measured at new Goddard X-ray calibration facility (100 m X-ray beamline) and was found to be 1.1 arcmin. We will also discuss further improvements toward the flight unit to be delivered to JAXA in 2012.

Okajima, Takashi↗
NASA NTRS2019

Command and Control System Software Development

With the first launch of the National Aeronautics and Space Administration's Space Launch System heavy-lift expendable launch vehicle and Lockheed Martin's Orion Multi-Purpose Crew Vehicle scheduled for the year 2020, there exists a need to complete development of a new command and control system that will provide systems monitoring and launch control for NASA's Exploration Missions. One remaining task necessary for completion of this command and control system is to create and maintain comprehensive unit tests of the control system software packages. These tests should verify that the implementation of all required and desired functionality works as intended. This testing infrastructure is mostly in place, but the control system's open source automation server still reports software "bugs" (possible flaws or failures which may lead to unintended behavior) and intermittently failing unit tests. Since code correctness is of critical importance for human rated software systems, I was assigned to diagnose the root cause of failing unit tests, eliminate non-determinism in these tests, and fix bugs as reported by the automation server.

GUI↗
NASA NTRS1996

Cassini Stellar Reference Unit: Performance Test Approach and Results

The Cassini Stellar Reference Unit (SRU) is the prime attitude determination sensor on the Cassini spacecraft...To ensure that the SRU will operate within specification for the entire mission, an extensive test program has been undertaken to characterize the SRU performance prior to launch and to quantify any expected performance degradation. Results from several eomplimentary test programs are presented and compared with pre-test performance predictions.

star↗
NASA NTRS1990

Development and fabrication of structural components for a scramjet engine

A program broadly directed toward design and development of long-life (100 hours and 1,000 cycles with a goal of 1,000 hours and 10,000 cycles) hydrogen-cooled structures for application to scramjets is presented. Previous phases of the program resulted in an overall engine design and analytical and experimental characterization of selected candidate materials and concepts. The latter efforts indicated that the basic life goals for the program can be reached with available means. The main objective of this effort was an integrated, experimental evaluation of the results of the previous program phases. The fuel injection strut was selected for this purpose, including fabrication development and fabrication of a full-scale strut. Testing of the completed strut was to be performed in a NASA-Langley wind tunnel. In addition, conceptual designs were formulated for a heat transfer test unit and a flat panel structural test unit. Tooling and fabrication procedures required to fabricate the strut were developed, and fabrication and delivery to NASA of all strut components, including major subassemblies, were completed.

Buchmann, O. A.↗
NASA NTRS2003

Rapid Prototyping of an Aircraft Model in an Object-Oriented Simulation

A team was created to participate in the Mars Scout Opportunity. Trade studies determined that an aircraft provided the best opportunity to complete the science objectives of the team. A high fidelity six degree of freedom flight simulation was required to provide credible evidence that the aircraft design fulfilled mission objectives and to support the aircraft design process by providing performance evaluations. The team created the simulation using the Langley Standard Real-Time Simulation in C++ (LaSRS++) application framework. A rapid prototyping approach was necessary because the team had only three months to both develop the aircraft simulation model and evaluate aircraft performance as the design and mission parameters matured. The design of LaSRS++ enabled rapid-prototyping in several ways. First, the framework allowed component models to be designed, implemented, unit-tested, and integrated quickly. Next, the framework provides a highly reusable infrastructure that allowed developers to maximize code reuse while concentrating on aircraft and mission specific features. Finally, the framework reduces risk by providing reusable components that allow developers to build a quality product with a compressed testing cycle that relies heavily on unit testing of new components.

Kenney, P. Sean↗
NASA NTRS2018

Global Ecosystem Dynamics Investigation (GEDI) Structural Verification Unit (SVU) Vibration Test

This presentation describes the vibration test campaign of the Structural Verification Unit for the Global Ecosystem Dynamics Investigation (GEDI) mission The Structural Verification Unit test campaign served multiple purposes including the qualification of the instrument primary structure, verification of the structure's stiffness, Aperture Control Mechanism assembly level verification, and validation of the control approach for protoflight instrument vibration testing. Testing included three axes of sine burst, random, and sine vibration excitation. This test sequence required a high number of response instrumentation sensors that included tri-axial accelerometers and tri-axial force gauges. Multiple response limiting methods that included acceleration, force, and moment measurements were used to ensure the safety of the flight hardware. The lessons and specific test details learned on the structural verification unit test campaign will reduce test risks for the upcoming instrument-level vibration tests.

Structural Verification Unit↗
NASA NTRS2014

Remote Software Application and Display Development

The era of the shuttle program has come to an end, but only to give rise to newer and more exciting projects. Now is the time of the Orion spacecraft, a work of art designed to exceed all previous endeavors of man. NASA is exiting the time of exploration and is entering a new period, a period of pioneering. With this new mission, many of NASAs organizations must undergo a great deal of change and development to support the Orion missions. The Spaceport Command and Control System (SCCS) is the new system that will provide NASA the ability to launch rockets into orbit and thus control Orion and other spacecraft as the goal of populating Mars becomes ever increasingly tangible. Since the previous control system, Launch Processing System (LPS), was primarily designed to launch the shuttles, SCCS was needed as Kennedy Space Center (KSC) reorganized to a multiuser spaceport for commercial flights, providing a more versatile control over rockets. Within SCCS, is the Launch Control System (LCS), which is the remote software behind the command and monitoring of flight and ground system hardware. This internship at KSC has involved two main components in LCS, including Remote Software Application and Display development. The display environment provides a graphical user interface for an operator to view and see if any cautions are raised, while the remote applications are the backbone that communicate with hardware, and then relay the data back to the displays. These elements go hand in hand as they provide monitoring and control over hardware and software alike from the safety of the Launch Control Center. The remote software applications are written in Application Control Language (ACL), which must undergo unit testing to ensure data integrity. This paper describes both the implementation and writing of unit tests in ACL code for remote software applications, as well as the building of remote displays to be used in the Launch Control Center (LCC).

ACL↗
NASA NTRS2002

Ultrawideband Electromagnetic Interference to Aircraft Radios: Results of Limited Functional Testing With United Airlines and Eagles Wings Incorporated, in Victorville, California

On February 14, 2002, the FCC adopted a FIRST REPORT AND ORDER, released it on April 22, 2002, and on May 16, 2002 published in the Federal Register a Final Rule, permitting marketing and operation of new products incorporating UWB technology. Wireless product developers are working to rapidly bring this versatile, powerful and expectedly inexpensive technology into numerous consumer wireless devices. Past studies addressing the potential for passenger-carried portable electronic devices (PEDs) to interfere with aircraft electronic systems suggest that UWB transmitters may pose a significant threat to aircraft communication and navigation radio receivers. NASA, United Airlines and Eagles Wings Incorporated have performed preliminary testing that clearly shows the potential for handheld UWB transmitters to cause cockpit failure indications for the air traffic control radio beacon system (ATCRBS), blanking of aircraft on the traffic alert and collision avoidance system (TCAS) displays, and cause erratic motion and failure of instrument landing system (ILS) localizer and glideslope pointers on the pilot horizontal situation and attitude director displays. This report provides details of the preliminary testing and recommends further assessment of aircraft systems for susceptibility to UWB electromagnetic interference.

Ely, Jay J.↗
NASA NTRS2019

Testing Fortran Software with pFunit

Over the past two decades, the emergence of highly effective software testing frameworks has greatly simplified the development and use of unit tests and has led to new software development paradigms such as test driven development (TDD). However, technical computing introduces a number of unique testing challenges, including distributed parallelism and numerical accuracy. This webinar will begin with a basic introduction to the use of pFUnit (parallel Fortran Unit testing framework) to develop tests for Message Passing Interface (MPI) plus Fortran (MPI+Fortran) software and then present some of the new capabilities in the latest release. We will also discuss some specialized methodologies for testing numerical algorithms and speculate about future framework capabilities that may improve our ability to test at exascale.

Clune, Tom↗
NASA NTRS1986

Orbital flight simulation utility software unit specifications, revision 1

The HP PASCAL source code defines the specifications for a Utility Software Unit (USU) designed to support orbital flight simulators such as MANHANDLE and GREAS (General Research and Engineering Analysis Simulator). Besides providing basic input/output, mathematical, matrix, quaternion, and statistical routines for such simulators, one of the primary functions of the USU is to isolate all system-dependent codes in one well-defined compartment, thereby facilitating transportation of the simulations from one computer to another. Directives are given for the PASCAL compilers of the HP-9000 Series 200 Pascal 3.0 and the HP-9000 Series 500 HP-UX 5.0 operating systems that produce a single file of relocatable code from four separate files of source code. Three of the source code files are common to both operating systems. The fourth source code file (utilspif.I) contains all of the system-dependent PASCAL code for the USU. A fifth file of source code written in C is required to interface utilspif.I with the HP-UX I/O package. The Pascal 3.0 compiler directives and the driver source code for a unit rest program and counterparts for the HP-UX 5.0 operating system are given. The major portion of the unit test program source code is common to both operating systems. Unit test results from the Pascal 3.0 operating system and results from the HP-UX operating system are given.

Wilson, S. W.↗
NASA NTRS2014

pFUnit 3.0 Tutorial Advanced

This tutorial will introduce Fortran developers to unit-testing and test-driven development (TDD) using pFUnit. As with other unit-testing frameworks, pFUnit, simplifies the process of writing, collecting, and executing tests while providing clear diagnostic messages for failing tests. pFUnit specifically targets the development of scientific-technical software written in Fortran and includes customized features such as: assertions for multi-dimensional arrays, distributed (MPI) and thread-based (OpenMP) parallellism, and flexible parameterized tests.These sessions will include numerous examples and hands-on exercises that gradually build in complexity. Attendees are expected to have working knowledge of F90, but familiarity with object-oriented syntax in F2003 and MPI will be of benefit for the more advanced examples. By the end of the tutorial the audience should feel comfortable in applying pFUnit within their own development environment.

Test Driven using pFUnit↗
NASA NTRS1989

Experiments in fault tolerant software reliability

Twenty functionally equivalent programs were built and tested in a multiversion software experiment. Following unit testing, all programs were subjected to an extensive system test. In the process sixty-one distinct faults were identified among the versions. Less than 12 percent of the faults exhibited varying degrees of positive correlation. The common-cause (or similar) faults spanned as many as 14 components. However, a majority of these faults were trivial, and easily detected by proper unit and/or system testing. Only two of the seven similar faults were difficult faults, and both were caused by specification ambiguities. One of these faults exhibited variable identical-and-wrong response span, i.e. response span which varied with the testing conditions and input data. Techniques that could have been used to avoid the faults are discussed. For example, it was determined that back-to-back testing of 2-tuples could have been used to eliminate about 90 percent of the faults. In addition, four of the seven similar faults could have been detected by using back-to-back testing of 5-tuples. It is believed that most, if not all, similar faults could have been avoided had the specifications been written using more formal notation, the unit testing phase was subject to more stringent standards and controls, and better tools for measuring the quality and adequacy of the test data (e.g. coverage) were used.

Mcallister, David F.↗