scholarly journals Formal Methods for Multi Modal UI for Robotics

2019 ◽  
Author(s):  
Anil Kumar Bheemaiah

A formal system of mathematics the dog-ears, is introduced to describe javascript or object notation, sensor event and action event with state modelling in the framework of DPA for a smart home and work robotics . It is assumed that a multi modal interface can be developed similar to AWS APL for this purpose.The RAVA natural programming language is introduced, which simplifies coding by eliminating the need for syntax.

10.29007/5zjp ◽  
2018 ◽  
Author(s):  
Sylvia Grewe ◽  
Sebastian Erdweg ◽  
Mira Mezini

\noindent Developing provably sound type systems is a non-trivial task which, as of today, typically requires expert skills in formal methods and a considerable amount of time. Our Veritas~\cite{GreweErdwegWittmannMezini15} project aims at providing support for the development of soundness proofs of type systems and efficient type checker implementations from specifications of type systems. To this end, we investigate how to best automate typical steps within type soundness proofs.\noindent In this paper, we focus on progress proofs for type systems of domain-specific languages. As a running example for such a type system, we model a subset SQL and augment it with a type system. We compare two different approaches for automating proof steps of the progress proofs for this type system against each other: firstly, our own tool Veritas, which translates proof goals and specifications automatically to TPTP~\cite{Sutcliffe98} and calls Vampire~\cite{KovacsV13} on them, and secondly, the programming language Dafny~\cite{Leino2010}, which translates proof goals and specifications to the intermediate verification language Boogie 2~\cite{Leino2008} and calls the SMT solver Z3~\cite{DeMoura2008} on them. We find that Vampire and Dafny are equally well-suited for automatically proving simple steps within progress proofs.


2019 ◽  
Author(s):  
Anil Kumar Bheemaiah

AbstractThe Dog-Ears formal system (Bheemaiah, n.d.) is extended with MFA II architecture for the definition of Taskoids, needing adaptable designs and additive printing. We present a formal system to apply the formulation to illustrate Singularity#1 as an MFA II, application. The concept of Singularity and Singularity#1 and the MFA II design philosophy is explained, with an abstract photographic art.Keywords: Dog-Ears, Taskoids, Singularity, Singularity#1, Robotics, Conversational UI, additive printing.What:Singularity#1 is defined as an algorithmic machine evolution like genetic algorithms, in MFA II architecture, with the development of machine learning algorithms for the automated design of hardware and software and additive manufacturing of the hardware.MFA II is a multi-functional architecture, where side effects are primary too in a defined multi-functionality, it is inspired by MFA I architecture of form following function and behaviors from BEAM robotics, while BEAM is analog or mixed, MFA II is digital.Was:Singularity # 1 ist definiert als eine algorithmische Maschinenentwicklung wie genetische Algorithmen in der MFA II-Architektur mit der Entwicklung von Algorithmen für maschinelles Lernen für das automatisierte Design von Hardware und Software sowie für die additive Fertigung der Hardware. Es ähnelt der Singularität, die sich durch die Entwicklung von Hardware und Software für maschinelles Lernen durch A.I-Algorithmen auszeichnet.MFA II ist eine multifunktionale Architektur, bei der Nebenwirkungen auch bei einer definierten Multifunktionalität im Vordergrund stehen. Sie ist von der MFA I-Architektur mit Funktionen und Verhaltensweisen der BEAM-Robotik inspiriert, während BEAM analog oder gemischt und MFA II digital ist.How:We illustrate Singularity#1, in non-anthropomorphism in the design of Alexa skills and hardware tools for the sentient bot platform with additive manufacturing. Hardware extensions with the RetroSwitch are defined with a mathematical formulation, and templates with customization for the RetroSwitches and hardware designs are illustrated.TensorFlow is used for a mathematical formulation of MFA II with generalized Tensors.Wie:Wir veranschaulichen Singularität Nr. 1 im Nicht-Anthropomorphismus bei der Entwicklung von Alexa-Fertigkeiten und Hardware-Tools für die Plattform für empfindungsfähige Bots mit additiver Fertigung. Hardware-Erweiterungen mit dem RetroSwitch werden mit einer mathematischen Formulierung definiert, und Vorlagen mit Anpassungen für die RetroSwitches und Hardware-Designs werden veranschaulicht.TensorFlow wird für eine mathematische Formulierung von MFA II mit verallgemeinerten Tensoren mit eingebetteten Unendlichkeiten von Kovarianz und Kontravarianz und einer Konturintegralformulierung verwendet.


CCIT Journal ◽  
2015 ◽  
Vol 8 (3) ◽  
pp. 215-222
Author(s):  
Ageng Setiani Rafika ◽  
Meidy Surya Hadi Putra ◽  
Winda Larasati

The development of technology over time has proven to give a lot of changes in humans. Changes that occur generally for the better, as it easier to do a job One of the technologies developed at this time is with the development of mobile technology is not only used as a telephone and sms only, but also can be used as a device to control a microcontroller. Microcontroller is a chip that can perform digital data processing in accordance with the command given programming language. So today microcontroller applied to many everyday life, one of which is in use in smart home automatic Bluetooth media ATMEGA 328 microcontroller based smart home automatic is a tool that can function automatically based on the input to the bluetooth and the existence of programs that are embedded in in an IC microcontroller. Bluetooth as a communication medium to transmit data or input from android application that is using BlueTerm application that acts as a device to control home appliances remotely. In general, the control of home appliances is still work manually so it is less effective, the objective of the design tool automatic smart home is to create a tool that can help people to carry out activities in the home that is to control the home appliances using smartphones automatically through the application BlueTerm with media bluetooth


Author(s):  
Laila Khoirunnisa Nurul Imani ◽  
Nanda Alicia ◽  
Fahmizal Fahmizal ◽  
Unan Yusmaniar Oktiawati

The control of household electronic equipment can now be done remotely using a website, or better known as the smart home controller application to reduce waste of electricity usage. The electronic equipment that is controlled changes the lights and sockets. This electronic equipment controller website is made with the Laravel framework which uses the PHP 5.8 programming language which is closed, therefore a connection is made with the REST API that uses the Javascript programming language to bridge the communication between electronic equipment and the website. Delivery of data between the website and components requires a server and broker to broker data paths. Thus MQTT is needed as a means of exchanging data on the hardware side so it requires a gateway in the form of Node Js to connect PHP with MQTT. Test results are done by testing the speed of the lights using various internet connection media. The test results showed the fastest internet connection media, namely using a laptop connected to a WiFi internet network with an average speed of 0.691 seconds. The smart home controller website named Pantaw can be accessed using the UGM hotspot WiFi network.Keywords: Website, smarthome, MQTT, Laravel, Node Js.


2015 ◽  
Vol 19 (5) ◽  
pp. 81-99
Author(s):  
M. S. Kropacheva ◽  
A. I. Legalov

The article is devoted to the methods of proving parallel programs correctness that are based on the axiomatic approach. Formal system for functional data-flow parallel programming language Pifagor is described. On the basis of this system programs correctness could be proved.


Author(s):  
E. A. Ashcroft ◽  
A. A. Faustini ◽  
R. Jaggannathan ◽  
W. W. Wadge

The ability to verify and reason about programs was one of the main goals behind the design and development of Lucid. In fact, from its very inception Lucid was intended to be not just a programming language, but also a formal system in which program specifications and correctness proofs could be expressed as well. Our goal was a formal programming system in which programs for “realistically” complicated problems could be proved correct with only a realistic amount of effort. The nonprocedural nature of Lucid and its mathematical semantics led naturally to a reasoning technique where properties proved of variables and functions (assertions) are true throughout the where clauses in which the variables and functions are defined, and are not just thought of as being true at particular points where they are “attached” (as would be the case in the usual verification technique for procedural programs). In that respect, Lucid verification is like verification of functional programs. The assertions proved for Lucid, however, have the basic simplicity of the assertions proved in the procedural case, and the proofs are very similar. We will illustrate the differences by using a very simple program for computing integer square roots. We will express it in an imperative language, in a functional language, and in Lucid and show how verification would be performed for each language using the different techniques. In all three techniques, we will use the following terminology from the procedural approach, namely that the precondition is a restriction on the inputs of a program and the postcondition is a desired property of the outputs of the program, assuming that the inputs satisfied the precondition.


Author(s):  
Roderick Chapman

As the only obvious ‘industrial’ member of the panel, I would like to introduce myself and the work I am involved with. Praxis is a practising software engineering company that is well known for applying so-called ‘Formal Methods’ in the development of high-integrity software system. We are also responsible for the Spark programming language and verification tools ( John Barnes with Praxis High Integrity Systems 2003 ). Spark remains one of the very few technologies to offer a sound verification system for an industrially usable imperative programming language. Despite the popular belief that ‘no one does formal methods’, we (and our customers) regularly employ strong verification techniques on industrial-scale software systems. I would like to address three main points:


Sign in / Sign up

Export Citation Format

Share Document