MAGIC Summoning: Towards Automatic Suggesting and Testing of Gestures with Low Probability of False Positives During Use
Total Page:16
File Type:pdf, Size:1020Kb

Load more
Recommended publications
-
Amigaos 3.2 FAQ 47.1 (09.04.2021) English
$VER: AmigaOS 3.2 FAQ 47.1 (09.04.2021) English Please note: This file contains a list of frequently asked questions along with answers, sorted by topics. Before trying to contact support, please read through this FAQ to determine whether or not it answers your question(s). Whilst this FAQ is focused on AmigaOS 3.2, it contains information regarding previous AmigaOS versions. Index of topics covered in this FAQ: 1. Installation 1.1 * What are the minimum hardware requirements for AmigaOS 3.2? 1.2 * Why won't AmigaOS 3.2 boot with 512 KB of RAM? 1.3 * Ok, I get it; 512 KB is not enough anymore, but can I get my way with less than 2 MB of RAM? 1.4 * How can I verify whether I correctly installed AmigaOS 3.2? 1.5 * Do you have any tips that can help me with 3.2 using my current hardware and software combination? 1.6 * The Help subsystem fails, it seems it is not available anymore. What happened? 1.7 * What are GlowIcons? Should I choose to install them? 1.8 * How can I verify the integrity of my AmigaOS 3.2 CD-ROM? 1.9 * My Greek/Russian/Polish/Turkish fonts are not being properly displayed. How can I fix this? 1.10 * When I boot from my AmigaOS 3.2 CD-ROM, I am being welcomed to the "AmigaOS Preinstallation Environment". What does this mean? 1.11 * What is the optimal ADF images/floppy disk ordering for a full AmigaOS 3.2 installation? 1.12 * LoadModule fails for some unknown reason when trying to update my ROM modules. -
Understanding and Mitigating the Security Risks of Apple Zeroconf
2016 IEEE Symposium on Security and Privacy Staying Secure and Unprepared: Understanding and Mitigating the Security Risks of Apple ZeroConf Xiaolong Bai*,1, Luyi Xing*,2, Nan Zhang2, XiaoFeng Wang2, Xiaojing Liao3, Tongxin Li4, Shi-Min Hu1 1TNList, Tsinghua University, Beijing, 2Indiana University Bloomington, 3Georgia Institute of Technology, 4Peking University [email protected], {luyixing, nz3, xw7}@indiana.edu, [email protected], [email protected], [email protected] Abstract—With the popularity of today’s usability-oriented tend to build their systems in a “plug-and-play” fashion, designs, dubbed Zero Configuration or ZeroConf, unclear are using techniques dubbed zero-configuration (ZeroConf ). For the security implications of these automatic service discovery, example, the AirDrop service on iPhone, once activated, “plug-and-play” techniques. In this paper, we report the first systematic study on this issue, focusing on the security features automatically detects another Apple device nearby running of the systems related to Apple, the major proponent of the service to transfer documents. Such ZeroConf services ZeroConf techniques. Our research brings to light a disturb- are characterized by automatic IP selection, host name ing lack of security consideration in these systems’ designs: resolving and target service discovery. Prominent examples major ZeroConf frameworks on the Apple platforms, includ- include Apple’s Bonjour [3], and the Link-Local Multicast ing the Core Bluetooth Framework, Multipeer Connectivity and -
Prozessunterstützung Für Den Entwurf Von Wearable-Computing-Systemen
Prozessunterstutzung¨ fur¨ den Entwurf von Wearable-Computing-Systemen Vom Fachbereich Informatik der Technischen Universit¨at Darmstadt genehmigte Dissertation zur Erlangung des akademischen Grades Dr. rer. nat. vorgelegt von Dipl.-Inform. Tobias Klug geboren in Frankfurt Tag der Einreichung: 15.4.2008 Tag der Disputation: 30.5.2008 Referenten: Prof. Dr. Max Muhlh¨ ¨auser, Darmstadt Prof. Dr.-Ing. Ralph Bruder, Darmstadt Darmstadt 2008 Darmst¨adter Dissertationen D17 i Danksagung Diese Dissertation ist weder Steffi Graf, noch Andr´eAgassi gewidmet. Dafur¨ je- doch den vielen Personen, die mich in den letzten dreieinhalb Jahren begleitet und unterstutzt¨ haben. An erster Stelle m¨ochte ich hier meinem Doktorvater Prof. Max Muhlh¨ ¨auser fur¨ die Anregungen und Diskussionen danken, die entscheidend zum Entstehen dieser Arbeit beigetragen haben. Außerdem m¨ochte ich meiner Freundin Nina Steinert und meinen Eltern danken, die meine Entscheidung zu promovieren unterstutzt¨ und mich die gesamte Zeit uber¨ begleitet haben. Sie haben mich immer wieder motiviert und auch bei der Korrektur des endgultigen¨ Textes tatkr¨aftige Unterstutzung¨ geleistet. Des weiteren m¨ochte ich Markus Roth, Hristo Indzhov und Svenja Kahn danken, die mit ihren Diplom- und Bachelorarbeiten entscheidend zur Entstehung dieser Arbeit beigetragen haben. Außerdem m¨ochte ich den vielen Kollegen an der Universit¨at und bei SAP Rese- arch fur¨ die freundliche und lockere Arbeitsatmosph¨are danken. Victoria Carlsson, Andreas Zinnen und Thomas Ziegert danke ich fur¨ die gute Zusammenarbeit und fruchtbaren Diskussionen im Rahmen des wearIT@work-Projektes und auch daruber¨ hinaus. Ich danke meinen Zimmerkollegen an der Universit¨at Melanie Hartmann und Fernando Lyardet, die sich immer wieder meine wilden Ideen anh¨oren und kommen- tieren mussten. -
Cooper ( Interaction Design
Cooper ( Interaction Design Inspiration The Myth of Metaphor Cooper books by Alan Cooper, Chairman & Founder Articles June 1995 Newsletter Originally Published in Visual Basic Programmer's Journal Concept projects Book reviews Software designers often speak of "finding the right metaphor" upon which to base their interface design. They imagine that rendering their user interface in images of familiar objects from the real world will provide a pipeline to automatic learning by their users. So they render their user interface as an office filled with desks, file cabinets, telephones and address books, or as a pad of paper or a street of buildings in the hope of creating a program with breakthrough ease-of- learning. And if you search for that magic metaphor, you will be in august company. Some of the best and brightest designers in the interface world put metaphor selection as one of their first and most important tasks. But by searching for that magic metaphor you will be making one of the biggest mistakes in user interface design. Searching for that guiding metaphor is like searching for the correct steam engine to power your airplane, or searching for a good dinosaur on which to ride to work. I think basing a user interface design on a metaphor is not only unhelpful but can often be quite harmful. The idea that good user interface design is based on metaphors is one of the most insidious of the many myths that permeate the software community. Metaphors offer a tiny boost in learnability to first time users at http://www.cooper.com/articles/art_myth_of_metaphor.htm (1 of 8) [1/16/2002 2:21:34 PM] Cooper ( Interaction Design tremendous cost. -
The Challenges of Wearable Computing: Part 2
THE CHALLENGES OF WEARABLE COMPUTING: PART 2 WEARABLE COMPUTING PURSUES AN INTERFACE IDEAL OF A CONTINUOUSLY WORN, INTELLIGENT ASSISTANT THAT AUGMENTS MEMORY, INTELLECT, CREATIVITY, COMMUNICATION, AND PHYSICAL SENSES AND ABILITIES. MANY CHALLENGES AWAIT WEARABLE DESIGNERS. PART 2 BEGINS WITH THE CHALLENGES OF NETWORK RESOURCES AND PRIVACY CONCERNS. THIS SURVEY DESCRIBES THE POSSIBILITIES OFFERED BY WEARABLE SYSTEMS AND, IN DOING SO, DEMONSTRATES ATTRIBUTES UNIQUE TO THIS CLASS OF COMPUTING. Challenges throughput. Another serious issue is open The most immediately striking challenge standards to enable interoperability between in designing wearable computers is creating different services. For example, only one long- appropriate interfaces. However, the issues of range radio should be necessary to provide power use, heat dissipation, networking, and telephony, text messaging, Global Positioning privacy provide a necessary framework in System (GPS) correction signals, and so on. which to discuss interface. Part 1 of this arti- For wearable computers, networking cle covers the first two of these issues; Part 2 involves communication off body to the fixed begins with the networking discussion. network, on body among devices, and near Thad Starner body with objects near the user. Each of these Networking three network types requires different design Georgia Institute of As with any wireless mobile device, the decisions. Designers must also consider pos- amount of power and the type of services sible interference between the networks. Technology available can constrain networking. Wearable computers could conserve resources through Off-body communications. Wireless commu- improved coordination with the user inter- nication from mobile devices to fixed infra- face. For example, the speed at which a given structure is the most thoroughly researched of information packet is transferred can be bal- these issues. -
UC Santa Cruz UC Santa Cruz Electronic Theses and Dissertations
UC Santa Cruz UC Santa Cruz Electronic Theses and Dissertations Title Efficient Bug Prediction and Fix Suggestions Permalink https://escholarship.org/uc/item/47x1t79s Author Shivaji, Shivkumar Publication Date 2013 Peer reviewed|Thesis/dissertation eScholarship.org Powered by the California Digital Library University of California UNIVERSITY OF CALIFORNIA SANTA CRUZ EFFICIENT BUG PREDICTION AND FIX SUGGESTIONS A dissertation submitted in partial satisfaction of the requirements for the degree of DOCTOR OF PHILOSOPHY in COMPUTER SCIENCE by Shivkumar Shivaji March 2013 The Dissertation of Shivkumar Shivaji is approved: Professor Jim Whitehead, Chair Professor Jose Renau Professor Cormac Flanagan Tyrus Miller Vice Provost and Dean of Graduate Studies Copyright c by Shivkumar Shivaji 2013 Table of Contents List of Figures vi List of Tables vii Abstract viii Acknowledgments x Dedication xi 1 Introduction 1 1.1 Motivation . .1 1.2 Bug Prediction Workflow . .9 1.3 Bug Prognosticator . 10 1.4 Fix Suggester . 11 1.5 Human Feedback . 11 1.6 Contributions and Research Questions . 12 2 Related Work 15 2.1 Defect Prediction . 15 2.1.1 Totally Ordered Program Units . 16 2.1.2 Partially Ordered Program Units . 18 2.1.3 Prediction on a Given Software Unit . 19 2.2 Predictions of Bug Introducing Activities . 20 2.3 Predictions of Bug Characteristics . 21 2.4 Feature Selection . 24 2.5 Fix Suggestion . 25 2.5.1 Static Analysis Techniques . 25 2.5.2 Fix Content Prediction without Static Analysis . 26 2.6 Human Feedback . 28 iii 3 Change Classification 30 3.1 Workflow . 30 3.2 Finding Buggy and Clean Changes . -
Automatic Program Repair Using Genetic Programming
Automatic Program Repair Using Genetic Programming A Dissertation Presented to the Faculty of the School of Engineering and Applied Science University of Virginia In Partial Fulfillment of the requirements for the Degree Doctor of Philosophy (Computer Science) by Claire Le Goues May 2013 c 2013 Claire Le Goues Abstract Software quality is an urgent problem. There are so many bugs in industrial program source code that mature software projects are known to ship with both known and unknown bugs [1], and the number of outstanding defects typically exceeds the resources available to address them [2]. This has become a pressing economic problem whose costs in the United States can be measured in the billions of dollars annually [3]. A dominant reason that software defects are so expensive is that fixing them remains a manual process. The process of identifying, triaging, reproducing, and localizing a particular bug, coupled with the task of understanding the underlying error, identifying a set of code changes that address it correctly, and then verifying those changes, costs both time [4] and money. Moreover, the cost of repairing a defect can increase by orders of magnitude as development progresses [5]. As a result, many defects, including critical security defects [6], remain unaddressed for long periods of time [7]. Moreover, humans are error-prone, and many human fixes are imperfect, in that they are either incorrect or lead to crashes, hangs, corruption, or security problems [8]. As a result, defect repair has become a major component of software maintenance, which in turn consumes up to 90% of the total lifecycle cost of a given piece of software [9]. -
Intuition As Evidence in Philosophical Analysis: Taking Connectionism Seriously
Intuition as Evidence in Philosophical Analysis: Taking Connectionism Seriously by Tom Rand A thesis submitted in conformity with the requirements for the degree of Ph.D. Graduate Department of Philosophy University of Toronto (c) Copyright by Tom Rand 2008 Intuition as Evidence in Philosophical Analysis: Taking Connectionism Seriously Ph.D. Degree, 2008, by Tom Rand, Graduate Department of Philosophy, University of Toronto ABSTRACT 1. Intuitions are often treated in philosophy as a basic evidential source to confirm/discredit a proposed definition or theory; e.g. intuitions about Gettier cases are taken to deny a justified-true-belief analysis of ‘knowledge’. Recently, Weinberg, Nichols & Stitch (WN&S) provided evidence that epistemic intuitions vary across persons and cultures. In- so-far as philosophy of this type (Standard Philosophical Methodology – SPM) is committed to provide conceptual analyses, the use of intuition is suspect – it does not exhibit the requisite normativity. I provide an analysis of intuition, with an emphasis on its neural – or connectionist – cognitive backbone; the analysis provides insight into its epistemic status and proper role within SPM. Intuition is initially characterized as the recognition of a pattern. 2. The metaphysics of ‘pattern’ is analyzed for the purpose of denying that traditional symbolic computation is capable of differentiating the patterns of interest. 3. The epistemology of ‘recognition’ is analyzed, again, to deny that traditional computation is capable of capturing human acts of recognition. 4. Fodor’s informational semantics, his Language of Thought and his Representational Theory of Mind are analyzed and his arguments denied. Again, the purpose is to deny traditional computational theories of mind. -
THAD E. STARNER, Ph.D. Associate Professor of Computing Georgia Institute of Technology
THAD E. STARNER, Ph.D. Associate Professor of Computing Georgia Institute of Technology Research Interest: Wearable/mobile computing interfaces and pattern recognition. Educational Background B.S. 1991 MIT, Cambridge MA Computer Science B.S. 1991 MIT, Cambridge MA Brain and Cognitive Science M.S. 1995 MIT Media Laboratory, Cambridge MA Media Arts and Sciences Ph.D. 1999 MIT Media Laboratory, Cambridge MA Media Arts and Sciences Professional Employment Associate Professor of Computing, Georgia Tech (Atlanta, GA), 2006-present Assistant Professor of Computing, Georgia Tech (Atlanta, GA), 1999-2006 Visiting Professor, ECE, Swiss Federal Inst. of Technology (ETH) (Zurich, Switzerland), 2002 Research Assistant, MIT Media Laboratory (Cambridge, MA), 1993-1999 Associate Scientist, Speech Systems Group, BBN (Cambridge, MA), 1992-1993 Experience Summary Thad Starner is a wearable computing pioneer, being the first person to advocate wearing a computer as an everyday personal assistant and having done so in his own life since 1993. He is a founder of the MIT Wearable Computing Project and the IEEE Technical Committee on Wearable Information Systems, which supervises the annual International Symposium on Wearable Computers. Professor Starner’s most recent work demonstrates a new speech interface paradigm where the user can control a mobile computer directly through his conversation with another party. Other recent work has shown that desktop typing speeds are achievable on small mobile keypads. Trained in computer vision, Professor Starner’s work on computer recognition of American Sign Language (ASL) is one of the most cited works on gesture recognition. Recent extensions of this work have shown the feasibility of an ASL tutor for deaf children and gesture interfaces appropriate for mobile devices. -
The Impact of Code Review Coverage and Code Review Participation on Software Quality
The Impact of Code Review Coverage and Code Review Participation on Software Quality A Case Study of the Qt, VTK, and ITK Projects Shane McIntosh1, Yasutaka Kamei2, Bram Adams3, and Ahmed E. Hassan1 1Queen’s University, Canada 2Kyushu University, Japan 3Polytechnique Montréal, Canada 1{mcintosh, ahmed}@cs.queensu.ca [email protected] [email protected] ABSTRACT 1. INTRODUCTION Software code review, i.e., the practice of having third-party Software code reviews are a well-documented best practice team members critique changes to a software system, is a for software projects. In Fagan's seminal work, formal design well-established best practice in both open source and pro- and code inspections with in-person meetings were found prietary software domains. Prior work has shown that the to reduce the number of errors detected during the testing formal code inspections of the past tend to improve the qual- phase in small development teams [8]. Rigby and Bird find ity of software delivered by students and small teams. How- that the modern code review processes that are adopted in a ever, the formal code inspection process mandates strict re- variety of reviewing environments (e.g., mailing lists or the view criteria (e.g., in-person meetings and reviewer check- Gerrit web application1) tend to converge on a lightweight lists) to ensure a base level of review quality, while the mod- variant of the formal code inspections of the past, where ern, lightweight code reviewing process does not. Although the focus has shifted from defect-hunting to group problem- recent work explores the modern code review process qual- solving [34]. -
Johnny Bock Andersen CV for Software Consultancy 1 Summary
Johnny Bock Andersen CV for Software Consultancy 1 Summary and Introduction The consultant specializes in development and design of advanced and high- performance software. In the areas of compiler, programming language and computer vision and graphics technologies, he has particularly strong skills that he uses in his company, Hardcore Processing, to turn cutting edge technologies into real-life applications. In doing this, he has also gained considerable experience in implementing numerical algorithms where nu- merical stability is often a challenge. He has worked both as an employee and even more so as a consultant for several companies over the years us- ing a very broad spectrum of platforms, tools and languages with many of which he has thorough in-depth experience, which he often gains relatively quickly. He is usually in a good mood, well-liked among colleagues and gladly answers questions. He performs best when focusing on larger tasks alone. From his 32 years of experience, out of which 22 are professional, he has a very strong intuition about what the best, or at least near-optimal, solution is to many complex problems, even when it would be very hard and time-consuming to find the optimal solution by thorough analysis. He has worked more than full time over many of the years, which is hard to reflect with this style of CV where the workload is not fully specified. YearofBirth : 1975 Citizenship: Danish(Denmark) Current residence : Copenhagen, Denmark Education Year Education Place 2004-2010 M.Sc.ComputerScience UniversityofCopenhagen, Denmark The last 102.5 ECTS points were passed in 1.5 years, i.e. -
Google Glass
International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395-0056 Volume: 02 Issue: 01 | Mar-2015 www.irjet.net p-ISSN: 2395-0072 ADVANCE TECHNOLOGY- GOOGLE GLASS Pooja S. Mankar Computer science & engineering, J.D.I.E.T ---------------------------------------------------------------------***---------------------------------------------------------------------- ABSTRACT- Most of the people who have seen the the Project Glass research and development project,[2] with glasses, but may not allowed speaking publicly; a major the mission of producing a mass-market ubiquitous computer. The frames do not currently have fitted lenses, feature of the glasses was the location information. Google is on the process of considering sunglass retailers Google will be able to capture images to its computers partnership such as Ray-Ban or Warby Parker, wish to open and augmented reality information returns to the person retail shop to try on the device for users. People who wear wearing them through the camera already built-in on the prescription glasses cannot use explorer edition, but Google glasses. For moment, if a person looking at a landmark has confirmed that Glass will be compatible with frames and then he could see historical and detailed information. lenses [3] according to the wearer's prescription and possibly attachable to normal prescription glasses. Google X Also comments about it that their friend’s left. If it’s facial Lab developed this Glass, which has experience with other recognition software becomes moderate and accurate futuristic technologies such as driverless cars. enough, the glasses could remind a wearer and also tells us when and how he met the foggy familiar person standing in front of him at a function or party.