Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “software verification and validation”

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.

442 records · Page 25

STK Integrated Message Production List Editor (SIMPLE) for CEO Operations

Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade and replace its mission planning and mission operations software systems, which were developed in the Space Shuttle era of the 1980s and 1990s. The impetuses for this change were the planned transition of all workstations to the Windows 7 64-bit operating system and the desire for more efficient and effective use of Satellite Tool Kit (STK) software required for reliable International Space Station (ISS) Earth location tracking. An additional requirement of this new system was the use of the same SQL database of CEO science sites from the SMMS, which was also being developed. STK Integrated Message Production List Editor (SIMPLE) is the essential, all-in-one tool now used by CEO staff to perform daily ISS mission planning to meet its requirement to acquire astronaut photography of specific sites on Earth. The sites are part of a managed, long-term database that has been defined and developed for scientific, educational, and public interest. SIMPLE's end product is a set of basic time and location data computed for an operator-selected set of targets that the ISS crew will be asked to photograph (photography is typically planned 12 to 36 hours out). The CEO operator uses SIMPLE to (a) specify a payload operations planning period; (b) acquire and validate the best available ephemeris data (vectors) for the ISS during the planning period; (c) ingest and display mission-specific site information from the CEO database; (d) identify and display potential current dynamic event targets as map features; (e) compute and display time and location information for each target; (f) screen and select targets based on known crew availability constraints, obliquity constraints, and real-time evaluated constraints to target visibility due to illumination (sun elevation) and atmospheric conditions (weather); and finally (g) incorporate basic, computed time and location information for each selected target into the daily CEO Target List product (message) for submission to ISS payload planning and integration teams for their review and approval prior to uplink. SIMPLE requires and uses the following resources: an ISS mission planning period Greenwich Mean Time start date/time and end date/time), the best available ISS mission ephemeris data (vectors) for that planning period, the STK software package configured for the ISS, and an ISS mission-specific subset of the CEO sites database. The primary advantages realized by the development and implementation of SIMPLE into the CEO payload operations support activity are a smooth transition to the Windows 7 operating system upon scheduled workstation refresh; streamlining of the input and verification of the current ISS ephemeris (vector data); seamless incorporation of selected contents of the SQL database of science sites; the ability to tag and display potential dynamic event opportunities on orbit track maps; simplification of the display and selection of encountered sites based on crew availability, illumination, obliquity, and weather constraints; the incorporation of high-quality mapping of the Earth with various satellite-based datasets for use in describing targets; and the ability to encapsulate and export the essential selected target elements in XML format for use by onboard Earth-location systems, such as Worldmap. SIMPLE is a carefully designed and crafted in-house software package that includes detailed help files for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in May 2012.

Trenchard, Mike↗

Jet Noise Reduction

The Acoustics Branch is responsible for reducing noise levels for jet and fan components on aircraft engines. To do this, data must be measured and calibrated accurately to ensure validity of test results. This noise reduction is accomplished by modifications to hardware such as jet nozzles, and by the use of other experimental hardware such as fluidic chevrons, elliptic cores, and fluidic shields. To insure validity of data calibration, a variety of software is used. This software adjusts the sound amplitude and frequency to be consistent with data taken on another day. Both the software and the hardware help make noise reduction possible. work properly. These software programs were designed to make corrections for atmosphere, shear, attenuation, electronic, and background noise. All data can be converted to a one-foot lossless condition, using the proper software corrections, making a reading independent of weather and distance. Also, data can be transformed from model scale to full scale for noise predictions of a real flight. Other programs included calculations of Over All Sound Pressure Level (OASPL), Effective Perceived Noise Level (EPNL). OASPL is the integration of sound with respect to frequency, and EPNL is weighted for a human s response to different sound frequencies and integrated with respect to time. With the proper software correction, data taken in the NATR are useful in determining ways to reduce noise. display any difference between two or more data files. Using this program and graphs of the data, the actual and predicted data can be compared. This software was tested on data collected at the Aero Acoustic Propulsion Laboratory (AAPL) using a variety of window types and overlaps. Similarly, short scripts were written to test each individual program in the software suite for verification. Each graph displays both the original points and the adjusted points connected with lines. During this summer, data points were taken during a live experiment at the AAPL to measure Nozzle Acoustic Test Rig (NATR) background noise levels. Six condenser microphones were placed in strategic locations around the dome and the inlet tunnel to measure different noise sources. From the control room the jet was monitored with the help of video cameras and other sensors. The data points were recorded, reduced, and plotted, and will be used to plan future modifications to the NATR. The primary goal to create data reduction test programs and provide verification was completed. As a result of the internship, I learned C/C++, UNIX/LINUX, Excel, and acoustic data processing methods. I also recorded data at the AAPL, then processed and plotted it. These data would be useful to compare against existing data. In addition, I adjusted software to work on the Mac OSX platform. And I used the available training resources.

Kenny, Patrick↗

Testing First-Order Logic Axioms in AutoCert

AutoCert [2] is a formal verification tool for machine generated code in safety critical domains, such as aerospace control code generated from MathWorks Real-Time Workshop. AutoCert uses Automated Theorem Provers (ATPs) [5] based on First-Order Logic (FOL) to formally verify safety and functional correctness properties of the code. These ATPs try to build proofs based on user provided domain-specific axioms, which can be arbitrary First-Order Formulas (FOFs). These axioms are the most crucial part of the trusted base, since proofs can be submitted to a proof checker removing the need to trust the prover and AutoCert itself plays the part of checking the code generator. However, formulating axioms correctly (i.e. precisely as the user had really intended) is non-trivial in practice. The challenge of axiomatization arise from several dimensions. First, the domain knowledge has its own complexity. AutoCert has been used to verify mathematical requirements on navigation software that carries out various geometric coordinate transformations involving matrices and quaternions. Axiomatic theories for such constructs are complex enough that mistakes are not uncommon. Second, adjusting axioms for ATPs can add even more complexity. The axioms frequently need to be modified in order to have them in a form suitable for use with ATPs. Such modifications tend to obscure the axioms further. Thirdly, speculating validity of the axioms from the output of existing ATPs is very hard since theorem provers typically do not give any examples or counterexamples.

Ahn, Ki Yung↗

Experimental Results from the Thermal Energy Storage-2 (TES-2) Flight Experiment

Thermal Energy Storage-2 (TES-2) is a flight experiment that flew on the Space Shuttle Endeavour (STS-72), in January 1996. TES-2 originally flew with TES-1 as part of the OAST-2 Hitchhiker payload on the Space Shuttle Columbia (STS-62) in early 1994. The two experiments, TES-1 and TES-2 were identical except for the fluoride salts to be characterized. TES-1 provided data on lithium fluoride (LiF), TES-2 provided data on a fluoride eutectic (LiF/CaF2). Each experiment was a complex autonomous payload in a Get-Away-Special payload canister. TES-1 operated flawlessly for 22 hr. Results were reported in a paper entitled, Effect of Microgravity on Materials Undergoing Melting and Freezing-The TES Experiment, by David Namkoong et al. A software failure in TES-2 caused its shutdown after 4 sec of operation. TES-1 and 2 were the first experiments in a four experiment suite designed to provide data for understanding the long duration microgravity behavior of thermal energy storage salts that undergo repeated melting and freezing. Such data have never been obtained before and have direct application for the development of space-based solar dynamic (SD) power systems. These power systems will store energy in a thermal energy salt such as lithium fluoride or a eutectic of lithium fluoride/calcium difluoride. The stored energy is extracted during the shade portion of the orbit. This enables the solar dynamic power system to provide constant electrical power over the entire orbit. Analytical computer codes were developed for predicting performance of a space-based solar dynamic power system. Experimental verification of the analytical predictions were needed prior to using the analytical results for future space power design applications. The four TES flight experiments were to be used to obtain the needed experimental data. This paper will address the flight results from the first and second experiments, TES-1 and 2, in comparison to the predicted results from the Thermal Energy Storage Simulation (TESSIM) analytical computer code. An analysis of the TES-2 data was conducted by Cleveland State University Professor, Mounir Ibrahim. TESSIM validation was based on two types of results; temperature history of various points on the containment vessel and TES material distribution within the vessel upon return from flight. The TESSIM prediction showed close comparison with the flight data. Distribution of the TES material within the vessel was obtained by a tomography imaging process. The frozen TES material was concentrated toward the colder end of the canister. The TESSIM prediction indicated a similar pattern. With agreement between TESSIM and the flight data, a computerized representation was produced to show the movement and behavior of the void during the entire melting and freezing cycles.

Tolbert, Carol↗

Europa Clipper Payload Verification and Validation: Avionics-Instrument Interface Test Campaign

NASA's Europa Clipper mission will investigate Jupiter's icy moon Europa using a payload suite consisting of nine instruments to address a range of scientific objectives concerning Europa's habitability. As the project proceeds past its Critical Design Review, confidence is being built in the system's ability to achieve mission objectives through the implementation of a rigorous payload verification and validation (V&V) program. As part of this payload V&V program, instrument box-level testing was performed by the payload team to verify select instrument-avionics interface requirements. This testing was performed at JPL using the avionics testbed's Bulk Data Storage Emulator (BDSEM) with visiting instrument Test Models. This paper summarizes the Data Link test campaign involving roughly four days of functional testing per instrument, including planning, testing methods, types of issues found, and the requirement closure process. Detail is also provided on the development, deployment, and validation of a standardized analysis tool used in data reviews. This testing verified requirements related to commanding rates, loss of link, packet format, clock counters, loopback test capability, and SpaceWire jitter and skew margins. Additional risk reduction testing of basic commanding, counter behavior, science data collection and transfer, and interface swapping was also performed. Because the BDSEM venue was not originally designed to be a run for record venue, the process of characterizing venue fidelity and establishing suitability for requirement closure using data collected in this venue will also be addressed.In order to close requirements, an extensible tool was developed to post-process instrument command and telemetry data from their original binary to a human-readable format and give visibility to errors detected within the data, such as packets with Cyclic Redundancy Check errors. This tool, called payload-packet-parser, is a Python 3.9 command line tool built using a variety of open-source Python libraries. Payload-packet-parser was designed to support parsing command and telemetry packets for all Europa Clipper instruments and additional analysis tools were developed for verification of specific information interface requirements. This test campaign, including post-processing using a single parsing and verification toolset, allowed for early interface testing, alleviating testing burdens on instrument teams and buying down risk on the instrument-avionics interface by finding hardware and software issues and idiosyncrasies prior to integration with system test venues. Over twenty issues were discovered across the payload, resulting in software updates and instrument rework well in advance of any system impacts. This paper concludes with an assessment of benefits and costs of this type of testing and lessons learned.

Montanez, Leticia↗

Second International Airborne Remote Sensing Conference and Exhibition

The conference provided four days of displays and scientific presentations on applications, technology, a science of sub-orbital data gathering and analysis. The twelve displayed aircraft equipped with sophisticated instrumentation represented a wide range of environmental and reconnaissance missions,including marine pollution control, fire detection, Open Skies Treaty verification, thermal mapping, hydrographical measurements, military research, ecological and agricultural observations, geophysical research, atmospheric and meterological observations, and aerial photography. The U.S. Air Force and the On-Site Inspection Agency displayed the new Open Skies Treaty verification Boeing OC 135B that promotes international monitoring of military forces and activities. SRl's Jetstream uses foliage and ground penetrating SAR for forest inventories, toxic waste delineation, and concealed target and buried unexploded ordnance detection. Earth Search Sciences's Gulfstream 1 with prototype miniaturized airborne hyperspectral imaging equipment specializes in accurate mineral differentiation, low-cost hydrocarbon exploration, and nonproliferation applications. John E. Chance and the U.S. Army Corps of Engineers displayed the Bell 2 helicopter with SHOALS that performs hydrographic surveying of navigation projects, coastal environment assessment, and nautical charting surveys. Bechtel Nevada and U.S. DOE displayed both the Beech King AIR B-200 platform equipped to provide first response to nuclear accidents and routine environmental surveillance, and the MBB BO-105 helicopter used in spectral analysis for environmental assessment and military appraisal. NASA Ames Research Center's high-altitude Lockheed ER-2 assists in earth resources monitoring research in atmospheric chemistry, oceanography, and electronic sensors; ozone and greenhouse studies and satellite calibration and data validation. Ames also showcased the Learjet 24 Airborne Observatory that completed missions in Venus cloud cover analysis, Quadantid meteor shower studies, extra-solar far infrared ionic structure lines measurement, Cape Kennedy launch support, and studies in air pollution, The Products and Services Exhibit showcased new sensor and image processing technologies, aircraft data collection services, unmanned vehicle technology, platform equipment, turn-key services, software a workstations, GPS services, publications, and processing and integration systems by 58 exhibitors. The participation of aircraft users and crews provided unique dialogue between those who plan data collection a operate the remote sensing technology, and those who supply the data processing and integration equipment. Research results using hyperspectral imagery, radar and optical sensors, lidar, digital aerial photography, a integrated systems were presented. Major research and development programs and campaigns we reviewed, including CNR's LARA Project and European Space Agency's 1991-1995 Airborne Campaign. The pre-conference short courses addressed airborne video, photogrammetry, hyperspectral data analysis, digital orthophotography, imagery and GIS integration, IFSAR, GPS, and spectrometer calibration.

Source record↗

Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) is the software tool for use in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight-code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover-predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (IDD) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities. Thus, RSVP, being highly data driven, may be tailored to other missions with minimal effort. In addition, RSVP uses a distributed, message-passing architecture to allow multitasking, and collaborative visualization and sequence development by scattered team members.

Cooper, Brian↗

Update on Rover Sequencing and Visualization Program

The Rover Sequencing and Visualization Program (RSVP) has been updated. RSVP was reported in Rover Sequencing and Visualization Program (NPO-30845), NASA Tech Briefs, Vol. 29, No. 4 (April 2005), page 38. To recapitulate: The Rover Sequencing and Visualization Program (RSVP) is the software tool to be used in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (robotic arm) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities.

Cooper, Brian↗

Discrete Event Simulation-Based Timeline Validation Using R2U2

The Gateway Vehicle Systems Manager (VSM), the top-level software control system in a distributed, hierarchical Autonomous System Management Architecture is, like most modern spacecraft software control systems, heavily data-driven. For example, schedules (timelines) will be developed on the ground and, due to the high degree of autonomy, contain complex procedures involving conditional branching, variable timing, and resource contention resolution. In order to verify that an uploaded timeline will function correctly, it is necessary to explore the feasible set of possible executions. While it is possible to test a timeline using a mission simulation, the complexity of the system and duration of a timeline limits the number of trials and therefore the test coverage. To address this problem, the VSM team is using a discrete event system model that can rapidly generate from a timeline sets of event sequences using Monte Carlo techniques. To achieve rapid and trustworthy checking of the event sequences, we use an offline version of the runtime model checking tool R2U2. This presentation describes the approach the VSM team is using to implement the discrete event simulation and evaluate event sequences using R2U2. The presentation will discuss: 1. Description of the timelines by VSM in the context of VSM operations 2. Expansion of a timeline into a sequence of atomic events 3. Adjustment, in the Monte Carlo environment, of an event sequence to account for uncertainty, external events, and failures 4. Definition of R2U2 input and mission-time linear temporal logic files 5. Generation and use of R2U2 verdict sequences 6. Lessons learned and future work

Verification↗

Modal Correlation of Complex Aerospace Joints Using Automated Variable Substitution

A critical task involved with being able to predict flight loads accurately in aerospace finite element models (FEMs) is the prior verification of the FEMs by conducting modal survey testing (MST). Experience comparing dynamic response of initial FEMs to MST data tends to demonstrate that FEMs can have unacceptable accuracy even when best modeling practices are followed. One inherent source of inaccuracy in linear dynamic FEMs is the modeling of nonlinear joints with mechanisms such as spherical bearings. These joints are usually designed to freely translate or rotate under the high levels of loading experienced in flight. Engineers who create linear FEMs conventionally model these joints without any stiffness in the mechanism degrees of freedom to meet this design intent. However, inaccuracy is observed during test validation of these FEMs, which usually relies on low-level force excitation orders of magnitude below flight load levels. This low-level modal test rarely overcomes the joint friction that is present, and thus the mechanism joints are able to react loads. This divide between the test results and the FEM creates a significant challenge to the engineer who is performing the correlation, in that the engineer has no basis for what stiffness value should be used to make the FEM match the test results. A compounding challenge is that complicated built-up aerospace structures commonly have multiple joints through a load path where each joint will “stick” and “slip” at different levels of force input. Explicitly matching the dynamics of a system containing these nonlinear mechanisms would require a nonlinear FEM, which is prohibitively costly for dynamic simulations of most aerospace systems. The objective of this paper is to present a workflow that can efficiently cycle through many iterations of a FEM, allowing a Monte Carlo style examination of the design space to identify candidate stiffness values for nonlinear mechanism joints. The outlined approach is specific to MSC Nastran and utilizes MSC Nastran’s symbolic substitution capabilities, coupled with the IMAT™ and Attune™ software packages developed by ATA Engineering, Inc. (ATA). The workflow is demonstrated with a case study from the correlation effort for The Boeing Company’s Crew Space Transportation (CST)-100 Starliner FEM. Keywords: Correlation, MSC Nastran, IMAT™, Attune™, Finite Element Model, Modal Testing

Correlation↗