Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “logic”

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 1,351 records · Page 75

Formal Requirements Elicitation with FRET

FRET is a tool for writing, understanding, formalizing and analyzing requirements. Users write requirements in an intuitive, restricted natural language, called FRETISH, with precise, unambiguous meaning. For a FRETISH requirement, FRET: 1) produces natural language and diagrammatic explanations of its exact meaning, 2) formalizes the requirement in logics, and 3) supports interactive simulation of produced logic formulas to ensure that they capture user intentions. FRET connects to analysis tools by facilitating the mapping between requirements and models/code, and by generating verification code. FRET is available open source at https://github.com/NASA-SW-VnV/fret; a video can be accessed at : https://tinyurl.com/fretForREFSQ.

Giannakopoulou, Dimitra↗

Bridging the Gap Between Requirements and Model Analysis : Evaluation on Ten Cyber-Physical Challenge Problems

Formal verfication and simulation are powerful tools to validate requirements against complex systems. [Problem] Requirements are developed in early stages of the software lifecycle and are typically written in ambiguous natural language. There is a gap between such requirements and formal notations that can be used by verification tools, and lack of support for proper association of requirements with software artifacts for verification. [Principal idea] We propose to write requirements in an intuitive, structured natural language with formal semantics, and to support formalization and model/code verification as a smooth, well-integrated process. [Contribution] We have developed an end-to-end, open source requirements analysis framework that checks Simulink models against requirements written in structured natural language. Our framework is built in the Formal Requirements Elicitation Tool (fret); we use fret's requirements language named fretish, and formalization of fretish requirements in temporal logics. Our proposed framework contributes the following features: 1) automatic extraction of Simulink model information and association of fretish requirements with target model signals and components; 2) translation of temporal logic formulas into synchronous dataflow cocospec specifications as well as Simulink monitors, to be used by verification tools; we establish correctness of our translation through extensive automated testing; 3) interpretation of counterexamples produced by verification tools back at requirements level. These features support a tight integration and feedback loop between high level requirements and their analysis. We demonstrate our approach on a major case study: the Ten Lockheed Martin Cyber-Physical, aerospace-inspired challenge problems.

Mavridou, Anastasia↗

Runtime Analysis with R2U2: A Tool Exhibition Report

We present R2U2 (Realizable, Responsive, Unobtrusive Unit), a hardware- supported tool and framework for the continuous monitoring of safetycritical and embedded cyber-physical systems.With the widespread advent of autonomous systems such as Unmanned Aerial Systems (UAS), satellites, rovers, and cars, real-time, on-board decision making requires unobtrusive monitoring of properties for safety, performance, security, and system health. R2U2 models combine past-time and future-time Metric Temporal Logic, “mission time” Linear Temporal Logic, probabilistic reasoning with Bayesian Networks, and modelbased prognostics. The R2U2 monitoring engine can be instantiated as a hardware solution, running on an FPGA, or as a software component. The FPGA realization enables R2U2 to monitor complex cyber-physical systems without any overhead or instrumentation of the flight software. In this tool exhibition report, we present R2U2 and demonstrate applications on system runtime monitoring, diagnostics, software health management, and security monitoring for a UAS. Our tool demonstration uses a hardware-based processor-in-the-loop “iron-bird” configuration.

Johann Martin Schumann↗

Abrstract - OnePlace Redesign Spring 2020 Internship

The project I worked on was the OnePlace Redesign. In that, I converted the OnePlace home page to the Service Portal to match NASA OnePlace’s current application design standards, I was able to allow users to easily find applications in OnePlace and I was able to allow users to easily find and request OnePlace services (new app development, new knowledge base, etc.). It was a major accomplishment to be able to remodel a website that soon the entire Langley center that uses OnePlace will use. The website was made through ServiceNow’s Service Portal, and I organized the applications like never before, allowed a clear styling to applications a user does not have access to and/or are new applications, browsing of applications with clear button divisions, and allowing for different options depending if app is accessible or not, with proper error checking in place and very-well documented code. It was amazing to incorporate all this logic into one widget so that whoever wants to utilize this feature has no trouble at all to do so. The 3 most important things I learned were being able to do this work within ServiceNow, as it is such an important enterprise platform for CRM and boosting the connected workforce of NASA, incorporate built-in APIs from ServiceNow Glide Records to connect Server Scripts to Client Scripts and HTML, and be able to use agile to get another experience of managing work capacity with stories, and having proper communication with the team if every feature is done correctly and steps for continuing forward. The part that I enjoyed the most was the training I did for ServiceNow and I freedom I had to experiment to see how to structure the Service Portal. I was not tied down, and I believe this allowed for a better outcome of the product. As part of the internship, I created a very in-depth design document with the help of my team to document the project goals before it was started and technical documentation (including the design document) summarizing the final result of the product in terms of the new features added and the explanation of the logic thoroughly so that anyone can understand the project easily. The technical documentation will be published as a Knowledge Article within OnePlace Knowledge Base documentation.

Ariel Wald↗

From Requirements to Autonomous Flight: An Overview of the Monitoring ICAROUS Project

The Independent Configurable Architecture for Reliable Operations of Unmanned Systems(ICAROUS) is a software architecture incorporating a set of algorithms to enable autonomous operations of unmanned aircraft applications. This paper provides an overview of Monitoring ICAROUS, a project whose objective is to provide a formal approach to generating runtime monitors for autonomous systems from requirements written in a structured natural language. This approach integrates FRET, a formal requirement elicitation and authoring tool, and Copilot, a runtime verification framework. FRET is used to specify formal requirements in structured natural language. These requirements are translated into temporal logic formulae. Copilot is then used to generate executable runtime monitors from these temporal logic specifications. The generated monitors are directly integrated into ICAROUS to perform runtime verification during flight.

Formal Methods↗

Monitoring ICAROUS: From Requirements to Autonomous Flight

The Independent Configurable Architecture for Reliable Operations of Unmanned Systems (ICAROUS) is a software architecture incorporating a set of algorithms to enable autonomous operations of unmanned aircraft applications. This paper provides an overview of Monitoring ICAROUS, a project whose objective is to provide a formal approach to generating runtime monitors for autonomous systems from requirements written in a structured natural language. This approach integrates FRET, a formal requirement elicitation and authoring tool, and Copilot, a runtime verification framework. FRET is used to specify formal requirements in structured natural language. These requirements are translated into temporal logic formulae. Copilot is then used to generate executable runtime monitors from these temporal logic specifications. The generated monitors are directly integrated into ICAROUS to perform runtime verification during flight.

Formal Methods↗

ELIPS: Toward a Sensor Fusion Processor on a Chip

The paper presents the concept and initial tests from the hardware implementation of a low-power, high-speed reconfigurable sensor fusion processor. The Extended Logic Intelligent Processing System (ELIPS) processor is developed to seamlessly combine rule-based systems, fuzzy logic, and neural networks to achieve parallel fusion of sensor in compact low power VLSI.

sensor↗

Towards Resilient Autonomous Navigation of Drones

Robots and particularly drones are especially useful in exploring extreme environments that pose hazards to humans. To ensure safe operations in these situations, usually perceptually degraded and without good GNSS, it is critical to have a reliable and robust state estimation solution. The main body of literature in robot state estimation focuses on developing complex algorithms favoring accuracy. Typically, these approaches rely on a strong underlying assumption: the main estimation engine will not fail during operation. In contrast, we propose an architecture that pursues robustness in state estimation by considering redundancy and heterogeneity in both sensing and estimation algorithms. The architecture is designed to expect and detect failures and adapt the behavior of the system to ensure safety. To this end, we present HeRO (Heterogeneous Redundant Odometry): a stack of estimation algorithms running in parallel supervised by a resiliency logic. This logic carries out three main functions: a) perform confidence tests both in data quality and algorithm health; b) re-initialize those algorithms that might be malfunctioning; c) generate a smooth state estimate by multiplexing the inputs based on their quality. The state and quality estimates are used by the guidance and control modules to adapt the mobility behaviors of the system. The validation and utility of the approach are shown with real experiments on a ying robot for the use case of autonomous exploration of subterranean environments, with particular results from the STIX event of the DARPA Subterranean Challenge.

Agha-mohammadi, Ali-akbar↗

A ROS-based Simulator for Testing the Enhanced Autonomous Navigation of the Mars 2020 Rover

In order to achieve the ambitious objectives of the Mars 2020 (M2020) mission, in particular the ability to autonomously traverse more challenging terrains more efficiently, new surface mobility software was developed for Enhanced Navigation (ENav). That decision was made early in the project, before most of the new surface flight software (FSW) existed, which created a need for a separate framework where the new navigation algorithms could be quickly prototyped and tested, before more realistic FSW-based testbeds became available. The JPL robotics team chose the Robot Operating System [1] (ROS) as the environment in which to test the new ENav algorithms. This made it possible to write the algorithms in the C language required by the FSW, so they could be directly ported over to the flight module later on, while leveraging all the C++ libraries and tools provided by ROS for simulation and testing. The ENav algorithms were developed as a separate C library, and stubs were used to replace any FSW-specific code, such as Event Reporting (EVRs) and data products (DPs). A ROS simulator was developed to generate a rich set of varied 3D terrains representative of the candidate Mars landing sites and simulate the physics of the rover motion, the point cloud perceived by the rover’s stereo vision system, and the new thinking-while-driving (TWD) navigation logic which directs the rover to drive autonomously to user-specified waypoints. To simulate the rover motion and perception, a ROS node was developed that uses a software library called HyperDrive Sim (HDSim), which is a wrapper for the Rover Sequencing and Visualization Program [2] (RSVP). That library provides roverterrain settling, realistic slip modelling, and camera rendering capability based on the rover’s NavCam machine vision models. To simulate the navigation logic, a ROS node was created that initializes and runs the ENav algorithms in a way that mimics the FSW execution, while also providing the capability to load and replay data products, including re-running the recorded inputs through the ENav algorithms for testing. An engineering Graphical User Interface (GUI) was also developed to visualize various elements, such as the rover pose during the drive, the simulated and perceived terrain, the selected local and global paths to the goal, the evaluated candidate paths and the reasons why they were rejected, the keep-in and keep-out zones (KIOZs), etc. Finally, an advanced Monte Carlo (MC) framework that can run many simulations in parallel on the Cloud and automatically generate reports that capture the key ENav performance metrics was developed to evaluate the system in a statisticallymeaningful way. This paper provides an overview of the ROSbased simulator used for testing the M2020 ENav algorithms.

Toupet, Olivier↗

Oversimplification of Systems Engineering Goals, Processes, and Criteria in NASA Space Life Support

This paper investigates the oversimplification of the inherently complex systems engineering process in space life support. The standard systems engineering process steps are described. The International Space Station (ISS) life support system is explained with its goals and performance criteria. Although it is not usually emphasized, the essential function of developing a hierarchy of systems and subsystems is to simplify the design process. The System Complexity Metric (SCM) shows how this di-vide-and-conquer approach also reduces the system complexity. The complete systems engineering process has many detailed steps. It is often simplified because of the effort required and the human limitations on working memory and decision span. Systems analysis demands slow, logical, and fo-cused thinking but is often bypassed in favor of quick, intuitive, subconscious “gut feel.” A study of 100 system designs found examples of 12 specific mental mistakes, such as ignoring stakeholder needs, and these mistakes are essentially oversimplifications of the systems engineering process. An analysis of space life support goals, options, criteria, and processes found 11 examples of oversimplifications in systems engineering, such as neglecting safety and cost. All these 11 oversimplifications could be traced to one or more of the 12 previously identified mental mistakes or other well-known ones, such as ig-noring sunk costs. Oversimplification of the systems engineering process is rarely noticed but is a common and harmful problem. A study of failures in 50 different space systems found that problems in systems engineering caused failures and often led to errors in design, development, and test that further contributed to failure. It seems that more diligent systems engineering could prevent many project problems and failures, but projects seem to be more guided by “gut feel” based on tradition, authority, and consensus than on the logical, rational systems engineering approach.

Simplified systems engineering↗

Monitoring ROS2: From Requirements to Autonomous Robots

Context/Goals - Capture mission requirements in high-level language. - Monitor requirements for robots. At a Glance - Transform requirements into runtime monitors for ROS2: - Requirements elicitation.* - Transform requirements into Temporal Logic formulas.* - Transform Temporal Logic formulas into runtime monitors.* - Generate hard real-time code for monitors.* - Generate ROS2 application directly from requirements.+ *Steps done in prior work. +Steps extended from prior work.

Runtime verification↗

Model Predictive Control Strategies for Turbine Electrified Energy Management

The increasing electrification of aircraft propulsion systems is leading to new control architectures being developed to address integration between electric machines and gas-based turbine engines. For hybrid-electric propulsion systems, current conceptual architectures often couple electric machines with the shafts of gas turbine engines and introduce energy storage. Leveraging the electrical power system of hybridized engines, Turbine Electrified Energy Management (TEEM) is a recent control approach that improves transient operability in an effort to enable more efficient and lighter weight turbomachinery. This study seeks to expand TEEM’s application beyond traditional proportional-integral (PI) control by presenting linear model predictive control (MPC) schemes to execute the TEEM concept. Through constraint selection and cost function design, transient operability goals for TEEM are considered with no external logic or saturation. Unique to the designs are the use of a washout filter, which simplifies transient detection and motor activation logic. The proposed architectures are implemented with both centralized MPC and distributed MPC approaches, and comparisons are drawn to a benchmark PI controller simulated on a nonlinear turbofan engine model at one ground condition and one cruise condition. Performance is evaluated using compressor maps, stall margin performance, and two novel metrics: transient stack usage and transient excursion integral. Results reveal the linear MPC scheme performs comparably to the baseline controller and can be implemented in at least two distinct configurations with potential for further modifications, thus establishing the groundwork for future investigations.

Model Predictive Control↗

Feedback-Directed Random Sequence Generation for Verifying Spacecraft Flight Rule Violations

The Psyche: Journey to a Metal World mission will be launched in 2022 to study the largest metal asteroid in the main asteroid belt, (16) Psyche. The spacecraft will perform a Mars Flyby in 2023 and enter (16) Psyche’s orbit in 2026. Throughout the mission, safely operating the spacecraft will require abiding by a set of flight rules that can be defined at any point in the mission lifecycle. These flight rules ensure that the spacecraft is operating within allowed regimes and a discrete event simulation tool, SEQGEN, will be used to model all command sequences prior to uplink. One of SEQGEN’s responsibilities is to determine if a command sequence violates any flight rules. For each flight rule, the necessary logic to determine if a violation has occurred is implemented in the SEQGEN adaptation, which is maintained by the mission. This adaptation must be tested thoroughly to ensure that the flight rule logic was interpreted and implemented correctly. This work describes a tool, RandSEQ, that autogenerates a suite of flight rule violating test sequences for each flight rule implemented in SEQGEN, and can be used by any mission using SEQGEN. The Psyche SEQGEN adaptation is still being developed, but so far, RandSEQ has been used to generate 532 test cases, that can be reviewed by various stakeholders, for 40 flight rules. The ability to autogenerate these test cases has significantly reduced the amount of time required to implement and test each flight rule.

Su, Laura↗

Flight Simulator Demonstration and Certification Implications of Powertrain Failure Mitigation in a Partial Turboelectric Aircraft

The Single-aisle Turboelectric AiRCraft with Aft Boundary Layer propulsor (STARC ABL) is a concept aircraft with a partial turboelectric powertrain. The complexity and integrated nature of the partial turboelectric powertrain architecture presents failure modes and hazards not found in conventional aircraft propulsion designs. Previously, various electrical and mechanical faults and associated recovery modes were demonstrated in a dynamic model of the powertrain. It was shown that certain faults were catastrophic without recovery logic, due specifically to the interaction of the subsystems. However, in each case, the logic, known as a reversionary control mode, enabled continued operation with assumed sufficient thrust to maintain safe flight. The current work evaluates the powertrain faults and recovery strategies using a full aircraft model in a piloted flight simulator, and places it in the context of current regulatory practice. Faults initiated in flight were successfully mitigated, with the accommodated aircraft subsequently evaluated against certification requirements for three-engine aircraft, which were shown to be appropriate for the STARC-ABL configuration.

STARC-ABL↗

Flight Simulator Demonstration and Certification Implications of Powertrain Failure Mitigation in a Partial Turboelectric Aircraft

The Single-aisle Turboelectric AiRCraft with Aft Boundary Layer propulsor (STARC ABL) is a concept aircraft with a partial turboelectric powertrain. The complexity and integrated nature of the partial turboelectric powertrain architecture presents failure modes and hazards not found in conventional aircraft propulsion designs. Previously, various electrical and mechanical faults and associated recovery modes were demonstrated in a dynamic model of the powertrain. It was shown that certain faults were catastrophic without recovery logic, due specifically to the interaction of the subsystems. However, in each case, the logic, known as a reversionary control mode, enabled continued operation with assumed sufficient thrust to maintain safe flight. The current work evaluates the powertrain faults and recovery strategies using a full aircraft model in a piloted flight simulator, and places it in the context of current regulatory practice. Faults initiated in flight were successfully mitigated, with the accommodated aircraft subsequently evaluated against certification requirements for three-engine aircraft, which were shown to be appropriate for the STARC-ABL configuration.

STARC-ABL↗

Model Predictive Control Strategies for Turbine Electrified Energy Management

The increasing electrification of aircraft propulsion systems is leading to new control architectures being developed to address integration between electric machines and gas-based turbine engines. For hybrid-electric propulsion systems, current conceptual architectures often couple electric machines with the shafts of gas turbine engines and introduce energy storage. Leveraging the electrical power system of hybridized engines, Turbine Electrified Energy Management (TEEM) is a recent control approach that improves transient operability in an effort to enable more efficient and lighter weight turbomachinery. This study seeks to expand TEEM’s application beyond traditional proportional integral (PI) control by presenting linear model predictive control (MPC) schemes to execute the TEEM concept. Through constraint selection and cost function design, transient operability goals for TEEM are considered with no external logic or saturation. Unique to the designs are the use of a washout filter, which simplifies transient detection and motor activation logic. The proposed architectures are implemented with both centralized MPC and distributed MPC approaches, and comparisons are drawn to a benchmark PI controller simulated on a nonlinear turbofan engine model at one ground condition and one cruise condition. Performance is evaluated using compressor maps, stall margin performance, and two novel metrics: transient stack usage and transient excursion integral. Results reveal the linear MPC scheme performs comparably to the baseline controller and can be implemented in at least two distinct configurations with potential for further modifications, thus establishing the groundwork for future investigations.

Model Predictive Control↗

Flight Simulator Demonstration and Certification Implications of Powertrain Failure Mitigation in a Partial Turboelectric Aircraft

The Single-aisle Turboelectric AiRCraft with Aft Boundary Layer propulsor (STARC ABL) is a concept aircraft with a partial turboelectric powertrain. The complexity and integrated nature of the partial turboelectric powertrain architecture presents failure modes and hazards not found in conventional aircraft propulsion designs. Previously, various electrical and mechanical faults and associated recovery modes were demonstrated in a dynamic model of the powertrain. It was shown that certain faults were catastrophic without recovery logic, due specifically to the interaction of the subsystems. However, in each case, the logic, known as a reversionary control mode, enabled continued operation with assumed sufficient thrust to maintain safe flight. The current work evaluates the powertrain faults and recovery strategies using a full aircraft model in a piloted flight simulator, and places it in the context of current regulatory practice. Faults initiated in flight were successfully mitigated, with the accommodated aircraft subsequently evaluated against certification requirements for three-engine aircraft, which were shown to be appropriate for the STARC-ABL configuration.

certification↗

Model Predictive Control Strategies for Turbine Electrified Energy Management

The increasing electrification of aircraft propulsion systems is leading to new control architectures being developed to address integration between electric machines and gas-based turbine engines. For hybrid-electric propulsion systems, current conceptual architectures often couple electric machines with the shafts of gas turbine engines and introduce energy storage. Leveraging the electrical power system of hybridized engines, Turbine Electrified Energy Management (TEEM) is a recent control approach that improves transient operability in an effort to enable more efficient and lighter weight turbomachinery. This study seeks to expand TEEM’s application beyond traditional proportional-integral (PI) control by presenting linear model predictive control (MPC) schemes to execute the TEEM concept. Through constraint selection and cost function design, transient operability goals for TEEM are considered with no external logic or saturation. Unique to the designs are the use of a washout filter, which simplifies transient detection and motor activation logic. The proposed architectures are implemented with both centralized MPC and distributed MPC approaches, and comparisons are drawn to a benchmark PI controller simulated on a nonlinear turbofan engine model at one ground condition and one cruise condition. Performance is evaluated using compressor maps, stall margin performance, and two novel metrics: transient stack usage and transient excursion integral. Results reveal the linear MPC scheme performs comparably to the baseline controller and can be implemented in at least two distinct configurations with potential for further modifications, thus establishing the groundwork for future investigations.

Model Predictive Control↗