Search NASA⌕ Search

SEARCH · Search NASA

Results for “certified compilation”

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.

Efficient Type Representation in TAL

Certifying compilers generate proofs for low-level code that guarantee safety properties of the code. Type information is an essential part of safety proofs. But the size of type information remains a concern for certifying compilers in practice. This paper demonstrates type representation techniques in a large-scale compiler that achieves both concise type information and efficient type checking. In our 200,000-line certifying compiler, the size of type information is about 36% of the size of pure code and data for our benchmarks, the best result to the best of our knowledge. The type checking time is about 2% of the compilation time.

Chen, Juan↗

Research into language concepts for the mission control center

A final report is given on research into language concepts for the Mission Control Center (MCC). The Specification Driven Language research is described. The state of the image processing field and how image processing techniques could be applied toward automating the generation of the language known as COmputation Development Environment (CODE or Comp Builder) are discussed. Also described is the development of a flight certified compiler for Comps.

Dellenback, Steven W.↗

A Verified Optimizer for Quantum Circuits

We present VOQC, the first verified optimizer for quantum circuits, written using the Coq proof assistant. Quantum circuits are expressed as programs in a simple, low-level language called SQIR, a small quantum intermediate representation, which is deeply embedded in Coq. Optimizations and other transformations are expressed as Coq functions, which are proved correct with respect to a semantics of SQIR programs. SQIR programs denote complex-valued matrices, as is standard in quantum computation, but we treat matrices symbolically to reason about programs that use an arbitrary number of quantum bits. SQIR’s careful design and our provided automation make it possible to write and verify a broad range of optimizations in VOQC, including full-circuit transformations from cutting-edge optimizers.

97 MATHEMATICS AND COMPUTING↗

Hardware Development Process for Human Research Facility Applications

The simple goal of the Human Research Facility (HRF) is to conduct human research experiments on the International Space Station (ISS) astronauts during long-duration missions. This is accomplished by providing integration and operation of the necessary hardware and software capabilities. A typical hardware development flow consists of five stages: functional inputs and requirements definition, market research, design life cycle through hardware delivery, crew training, and mission support. The purpose of this presentation is to guide the audience through the early hardware development process: requirement definition through selecting a development path. Specific HRF equipment is used to illustrate the hardware development paths. The source of hardware requirements is the science community and HRF program. The HRF Science Working Group, consisting of SCientists from various medical disciplines, defined a basic set of equipment with functional requirements. This established the performance requirements of the hardware. HRF program requirements focus on making the hardware safe and operational in a space environment. This includes structural, thermal, human factors, and material requirements. Science and HRF program requirements are defined in a hardware requirements document which includes verification methods. Once the hardware is fabricated, requirements are verified by inspection, test, analysis, or demonstration. All data is compiled and reviewed to certify the hardware for flight. Obviously, the basis for all hardware development activities is requirement definition. Full and complete requirement definition is ideal prior to initiating the hardware development. However, this is generally not the case, but the hardware team typically has functional inputs as a guide. The first step is for engineers to conduct market research based on the functional inputs provided by scientists. CommerCially available products are evaluated against the science requirements as well as modifications needed to meet program requirements. Options are consolidated and the hardware development team reaches a hardware development decision point. Within budget and schedule constraints, the team must decide whether or not to complete the hardware as an in-house, subcontract with vendor, or commercial-off-the-shelf (COTS) development. An in-house development indicates NASA personnel or a contractor builds the hardware at a NASA site. A subcontract development is completed off-site by a commercial company. A COTS item is a vendor product available by ordering a specific part number. The team evaluates the pros and cons of each development path. For example, in-bouse developments utilize existing corporate knowledge regarding bow to build equipment for use in space. However, technical expertise would be required to fully understand the medical equipment capabilities, such as for an ultrasound system. It may require additional time and funding to gain the expertise that commercially exists. The major benefit of subcontracting a hardware development is the product is delivered as an end-item and commercial expertise is utilized. On the other hand, NASA has limited control over schedule delays. The final option of COTS or modified COTS equipment is a compromise between in-house and subcontracts. A vendor product may exist that meets all functional requirements but req uires in-house modifications for successful operation in a space environment. The HRF utilizes equipment developed using all of the paths described: inhouse, subcontract, and modified COTS.

Bauer, Liz↗

Compiling the space shuttle wind tunnel data base: An exercise in technical and managerial innovators

Engineers evaluating Space Shuttle flight data and performance results are using a massive data base of wind tunnel test data. A wind tunnel test data base of the magnitude attained is a major accomplishment. The Apollo program spawned an automated wind tunnel data analysis system called SADSAC developed by the Chrysler Space Division. An improved version of this system renamed DATAMAN was used by Chrysler to document analyzed wind tunnel data and data bank the test data in standardized formats. These analysis documents, associated computer graphics and standard formatted data were disseminated nationwide to the Shuttle technical community. These outputs became the basis for substantiating and certifying the flight worthiness of the Space Shuttle and for improving future designs. As an aid to future programs this paper documents the lessons learned in compiling the massive wind tunnel test data base for developing the Space Shuttle. In particular, innovative managerial and technical concepts evolved in the course of conceiving and developing this successful DATAMAN system and the methods and organization for applying the system are presented.

Kemp, N. D.↗

Composite Overwrapped Pressure Vessels (COPV): Flight Rationale for the Space Shuttle Program

Each Orbiter Vehicle (Space Shuttle Program) contains up to 24 Kevlar49/Epoxy Composite Overwrapped Pressure Vessels (COPV) for storage of pressurized gases. In the wake of the Columbia accident and the ensuing Return To Flight (RTF) activities, Orbiter engineers reexamined COPV flight certification. The original COPV design calculations were updated to include recently declassified Kevlar COPV test data from Lawrence Livermore National Laboratory (LLNL) and to incorporate changes in how the Space Shuttle was operated as opposed to orinigially envisioned. 2005 estimates for the probability of a catastrophic failure over the life of the program (from STS-1 through STS-107) were one-in-five. To address this unacceptable risk, the Orbiter Project Office (OPO) initiated a comprehensive investigation to understand and mitigate this risk. First, the team considered and eventually deemed unfeasible procuring and replacing all existing flight COPVs. OPO replaced the two vessels with the highest risk with existing flight spare units. Second, OPO instituted operational improvements in ground procedures to signficiantly reduce risk, without adversely affecting Shuttle capability. Third, OPO developed a comprehensive model to quantify the likelihood of occurrance. A fully-instrumented burst test (recording a lower burst pressure than expected) on a flight-certified vessel provided critical understanding of the behavior of Orbiter COPVs. A more accurate model was based on a newly-compiled comprehensive database of Kevlar data from LLNL and elsewhere. Considering hardware changes, operational improvements and reliability model refinements, the mean reliability was determined to be 0.998 for the remainder of the Shuttle Program (from 2007, for STS- 118 thru STS-135). Since limited hardware resources precluded full model validation through multiple tests, additional model confidence was sought through the first-ever Accelerated Stress Rupture Test (ASRT) of a flown flight article. A Bayesian statistical approach was developed to interpret possible test results. Since the lifetime observed in the ASRT exceeded initial estimates by one to two orders of magnitude, the Space Shuttle Program deemed there was significant conservatism in the model and accepted continued operation with existing flight hardware. Given the variability in tank-to-tank original prooftest response, a non-destructive evaluation (NDE) technique utilizing Raman Spectroscopy was developed to directly measure COPV residual stress state. Preliminary results showed that patterns of low fiber elastic strains over the outside vessel surface, together with measured permanent volume growth during proof, could be directly correlated to increased fiber stress ratios on the inside fibers adjacent to the liner, and thus reduced reliability.

Kezirian, Michael T.↗

The Essence of Cryptol: A Denotational Cryptol Interpreter in Coq for Foundational Assurances for Quantum Resistant Cryptosystems

Systems of the utmost consequence need a means to establish authenticity of software and data. Cryptosystems implement authentication, but can be vulnerable to cryptographic and implementation attacks. With the threat of quantum cryptographic attacks, “post-quantum” cryptosystems (PQCs) must be henceforth used in these systems. However, the new cryptography needs new ways to, rigorously and machine-checkably, prove systems free of vulnerabilities. We propose a retargetable capability to rapidly instantiate proven correct postquantum cryptosystems through novel proof-carrying synthesis and proof-automation technique, extending those proven successful on existing systems. This capability is crucial to meeting the cryptographic requirements for future high-consequence systems. Since specifications for high consequence cryptography are presently captured in a domain specific language known as Cryptol. While this can enable convenient fully automated reasoning about Cryptol specificaitons and implementations via the Software Analysis Workbench (SAW), Cryptol has expressivity gaps, so that cryptosystems with probabilistic programming features like Falcon cannot be fully expressed in the language. Moreover, SAW’s automation fails for programs and specificaitons with inductive and recursive structure, as in the Sphincs+ PQC. Finally, Cryptol and SAW together represent some 200,000 lines of unverified Haskell, so that the any guarantees about high consequence cryptography are presently contingent on a large, unverified, yet trusted computing base. The first step of the larger project of agile, assured crpytography is therefore to provide a formal, mechanized semantics for Cryptol, so that the specifications expressed by cryptographers in Cryptol can be reasoned about and compiled into performant implementations with a foundational, machine checkable certificate of correctness. This report describes our work on this first step, culminating in the design of a certified denotational interpreter, in Coq, for core Cryptol.

97 MATHEMATICS AND COMPUTING↗

Skylab food system laboratory support

A summary of support activities performed to ensure the quality and reliability of the Skylab food system design is reported. The qualification test program was conducted to verify crew compartment compatibility, and to certify compliance of the food system with nutrition, preparation, and container requirements. Preflight storage requirements and handling procedures were also determined. Information on Skylab food items was compiled including matters pertaining to serving size, preparation information, and mineral, calorie, and protein content. Accessory hardware and the engraving of food utensils were also considered, and a stowage and orientation list was constructed which takes into account menu use sequences, menu items, and hardware stowage restrictions. A food inventory system was established and food thermal storage tests were conducted. Problems and comments pertaining to specific food items carried onboard the Skylab Workshop were compiled.

Sanford, D.↗

Towards a Certified Lightweight Array Bound Checker for Java Bytecode

Dynamic array bound checks are crucial elements for the security of a Java Virtual Machines. These dynamic checks are however expensive and several static analysis techniques have been proposed to eliminate explicit bounds checks. Such analyses require advanced numerical and symbolic manipulations that 1) penalize bytecode loading or dynamic compilation, 2) complexify the trusted computing base. Following the Foundational Proof Carrying Code methodology, our goal is to provide a lightweight bytecode verifier for eliminating array bound checks that is both efficient and trustable. In this work, we define a generic relational program analysis for an imperative, stackoriented byte code language with procedures, arrays and global variables and instantiate it with a relational abstract domain as polyhedra. The analysis has automatic inference of loop invariants and method pre-/post-conditions, and efficient checking of analysis results by a simple checker. Invariants, which can be large, can be specialized for proving a safety policy using an automatic pruning technique which reduces their size. The result of the analysis can be checked efficiently by annotating the program with parts of the invariant together with certificates of polyhedral inclusions. The resulting checker is sufficiently simple to be entirely certified within the Coq proof assistant for a simple fragment of the Java bytecode language. During the talk, we will also report on our ongoing effort to scale this approach for the full sequential JVM.

Pichardie, David↗

Generating Customized Verifiers for Automatically Generated Code

Program verification using Hoare-style techniques requires many logical annotations. We have previously developed a generic annotation inference algorithm that weaves in all annotations required to certify safety properties for automatically generated code. It uses patterns to capture generator- and property-specific code idioms and property-specific meta-program fragments to construct the annotations. The algorithm is customized by specifying the code patterns and integrating them with the meta-program fragments for annotation construction. However, this is difficult since it involves tedious and error-prone low-level term manipulations. Here, we describe an annotation schema compiler that largely automates this customization task using generative techniques. It takes a collection of high-level declarative annotation schemas tailored towards a specific code generator and safety property, and generates all customized analysis functions and glue code required for interfacing with the generic algorithm core, thus effectively creating a customized annotation inference algorithm. The compiler raises the level of abstraction and simplifies schema development and maintenance. It also takes care of some more routine aspects of formulating patterns and schemas, in particular handling of irrelevant program fragments and irrelevant variance in the program structure, which reduces the size, complexity, and number of different patterns and annotation schemas that are required. The improvements described here make it easier and faster to customize the system to a new safety property or a new generator, and we demonstrate this by customizing it to certify frame safety of space flight navigation code that was automatically generated from Simulink models by MathWorks' Real-Time Workshop.

Denney, Ewen↗

Certification of Ada parts for reuse

One of the claims made by proponents of Ada is that Ada software is highly reusable. The fact that specifications are compiled and accessible would make reusability seem easily achievable. However, specifications give only a limited amount of information about a package; moreover, a specification cannot help determine whether a package worked, or how well it worked. This problem has led to the concept of certifying Ada parts for reuse; that is, determining the worthiness of a part as a reusable component. Issues that are critical to reuse are addressed: the characterization of part performance, design for reuse, and correct utilization of parts. Current areas of study beneficial in the development of a certification process are then addressed.

Hansen, Gregory A.↗

High-Performance Reaction Wheel Optimization for Fine-Pointing Space Platforms: Minimizing Induced Vibration Effects on Jitter Performance plus Lessons Learned from Hubble Space Telescope for Current and Future Spacecraft Applications

The Hubble Space Telescope (HST) applies large-diameter optics (2.5-m primary mirror) for diffraction-limited resolution spanning an extended wavelength range (approx. 100-2500 nm). Its Pointing Control System (PCS) Reaction Wheel Assemblies (RWAs), in the Support Systems Module (SSM), acquired an unprecedented set of high-sensitivity Induced Vibration (IV) data for 5 flight-certified RWAs: dwelling at set rotation rates. Focused on 4 key ratios, force and moment harmonic values (in 3 local principal directions) are extracted in the RWA operating range (0-3000 RPM). The IV test data, obtained under ambient lab conditions, are investigated in detail, evaluated, compiled, and curve-fitted; variational trends, core causes, and unforeseen anomalies are addressed. In aggregate, these values constitute a statistically-valid basis to quantify ground test-to-test variations and facilitate extrapolations to on-orbit conditions. Accumulated knowledge of bearing-rotor vibrational sources, corresponding harmonic contributions, and salient elements of IV key variability factors are discussed. An evolved methodology is presented for absolute assessments and relative comparisons of macro-level IV signal magnitude due to micro-level construction-assembly geometric details/imperfections stemming from both electrical drive and primary bearing design parameters. Based upon studies of same-size/similar-design momentum wheels' IV changes, upper estimates due to transitions from ground tests to orbital conditions are derived. Recommended HST RWA choices are discussed relative to system optimization/tradeoffs of Line-Of-Sight (LOS) vector-pointing focal-plane error driven by higher IV transmissibilities through low-damped structural dynamics that stimulate optical elements. Unique analytical disturbance results for orbital HST accelerations are described applicable to microgravity efforts. Conclusions, lessons learned, historical context/insights, and perspectives on future applications are given; these previously unpublished data and findings represents a valuable resource for fine-pointing spacecraft or space-based platforms using RWAs, Control Moment Gyros (CMGs), Momentum Wheels, or other ball-bearing-based rotational units.

Hasha, Martin D.↗

Space Shuttle reaction control system thruster metal nitrate removal and characterization

The Space Shuttle hypergolic primary reaction control system (PRCS) thrusters continue to fail-leak or fail-off at a rate of approximately 1.5 per flight, attributed primarily to metal nitrate formation in the nitrogen tetroxide (N2O4) pilot operated valves (POV's). The failures have continued despite ground support equipment (GSE) and subsystem operational improvements. As a result, the Johnson Space Center (JSC) White Sands Test Facility (WSTF) performed a study to characterize the contamination in the N204 valves. This study prompted the development and implementation of a highly successful flushing technique using deionized (DI) water and gaseous nitrogen (GN2) to remove the contamination while minimizing Teflon seat damage. Following flushing a comprehensive acceptance test is performed before the thruster is deemed recovered. Between the time WSTF was certified to process flight thrusters (March 1992) and September 1993, a 68 percent thruster recovery rate was achieved. The contamination flushed from these thrusters was analyzed and has provided insight into the corrosion process, which is reported in this publication. Additionally, the long-term performance of 24 flushed thrusters installed in the WSTF Fleet Leader Shuttle reaction control subsystem (RCS) test articles is being assessed. WSTF continues to flush flight and test article thrusters and compile data to investigate metal nitrate formation characteristics in leaking and nonleaking valves.

Saulsberry, R. L.↗

Determining the Solubility Behavior of Kogarkoite in Simulated Nuclear Waste

Kogarkoite (Na 3 FSO 4 ) is a sparingly soluble fluoride–sulfate double salt that has been identified in high level nuclear waste sludge at the Hanford Site and, more recently, in sludge batch compilation samples at the Savannah River Site (SRS). Due to its complex dissolution behavior, which exhibits an inverse dependence on sodium ion activity, the presence of this mineral poses significant challenges to waste retrieval and processing. Incomplete dissolution during sludge washing can lead to the retention of fluoride and sulfate in the high-level waste feed, potentially causing the formation of corrosive, immiscible molten salt layers, known as "glass gall,” in vitrification melters. Current efforts to optimize flowsheet parameters and wash-water volumes are hindered by the absence of a commercially available, certified reference material, which prevents the accurate calibration of analytical methods and the verification of dissolution kinetics. To address this critical gap, this research focuses on the laboratory synthesis of pure Kogarkoite to serve as a standard for comprehensive solubility and washing performance testing. A coupled synthesis and simulant campaign was executed using an evaporative crystallization protocol designed to replicate the dynamic concentration effects observed in tank farm operations. Thirteen simulant matrices were prepared by dissolving systematically varied ratios of sodium fluoride (NaF) and sodium sulfate (Na 2 SO 4 ) in deionized water under three distinct caustic regimes: 0.0 g (control), 4.0 g (~1 M), and 12.0 g (~3 M) sodium hydroxide (NaOH). While thermodynamic equilibrium models suggest that high-caustic environments should favor the stability of the double salt7, results from this evaporative study at 25 0 C revealed a distinct kinetic divergence. Simulants with high hydroxide loading predominantly yielded large, blocky crystals of sodium sulfate decahydrate (Na 2 SO 4 .10H 2 O). Successful synthesis of pure Kogarkoite was achieved exclusively in specific NaOH-free compositional windows, where the precipitate manifested as fine, opaque granular aggregates. Ion chromatography (IC) analysis confirmed phase purity through the simultaneous stoichiometric depletion of both fluoride and sulfate from the supernatant. This successful synthesis establishes a reproducible route to generate bulk Kogarkoite, enabling the subsequent phase of quantitative dissolution testing using inhibited water to optimize sludge-batch assembly.

Sarker, Md Sharif [Florida International Univ. (FI↗

Analysis of Data in Accordance with Space Flight Mission Environmental Requirements

The Environmental Assurance Program sets forth standards to ensure that all flight hardware is compatible with the environments that will be encountered during a spacecraft mission. It outlines the design, test and analysis, and risk control standards for the mission and certifies that it will survive in any external or self-induced environments that the spacecraft may experience. The Environmental Requirements Document (ERD) is the most important document in the Environmental Assurance Program, providing the design and test requirements for the project's flight system, subsystems, assemblies, and instruments. This summer's project was to assist Environmental Requirements Engineers (ERE's) in completing the Environmental Assurance Program Summary Report for both the Juno Project and Mars Science Laboratory (MSL) Project. The Summary Report is a document summarizing the environmental tests and analyses of each spacecraft at both the assembly and system level. It compiles a source of all relevant information such as waivers and Problem/Failure Reports (PFRs) into a single report for easy reference of how well the spacecraft met the requirements of the project.

Jupiter properties↗

The Effects of Use of Civil Airworthiness Criteria on U.S. Air Force Acquisition, Test and Evaluation Practices

In response to the initiatives to streamline, not to mention comply with the Public Law for Non-Developmental Item Preference, the Department of Defense (DOD) has increased its use of commercial products. The Air Force has, over the past 15 years, been adapting Federal Aviation Administration (FAA) certified aircraft to perform many of its airlift and training missions. Counting the T-1A Jayhawk Trainer (Beechjet 400), in excess of 500 total aircraft, covering 15 different types, will have been procured since 1978. Needless to say, significant reform of the "classical" DOD and Air Force way of doing business has been necessary. Major strides have been made by the Transport Directorate of the Aircraft Program Office in the area of test and evaluation, with integrated qualification and operational testing (QT &E/QOT &E) and airworthiness certification testing by the FAA. As well, significant changes in contracting practices and the use of commercial (vice military) specifications for qualification criteria have been realized. This paper will relate some of these significant strides in "commercializing" and streamlining the DOD acquisition and test and evaluation processes. Additionally, it will review both regulatory changes made and recommended. It concludes with a compilation of lessons learned and recommendations for further streamlining of the DOD processes.

Flight Testing↗