Programs for Visual Psychophysics on the Amiga: a Tutorial
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
MAGIC Summoning: Towards Automatic Suggesting and Testing of Gestures with Low Probability of False Positives During Use
JournalofMachineLearningResearch14(2013)209-242 Submitted 10/11; Revised 6/12; Published 1/13 MAGIC Summoning: Towards Automatic Suggesting and Testing of Gestures With Low Probability of False Positives During Use Daniel Kyu Hwa Kohlsdorf [email protected] Thad E. Starner [email protected] GVU & School of Interactive Computing Georgia Institute of Technology Atlanta, GA 30332 Editors: Isabelle Guyon and Vassilis Athitsos Abstract Gestures for interfaces should be short, pleasing, intuitive, and easily recognized by a computer. However, it is a challenge for interface designers to create gestures easily distinguishable from users’ normal movements. Our tool MAGIC Summoning addresses this problem. Given a specific platform and task, we gather a large database of unlabeled sensor data captured in the environments in which the system will be used (an “Everyday Gesture Library” or EGL). The EGL is quantized and indexed via multi-dimensional Symbolic Aggregate approXimation (SAX) to enable quick searching. MAGIC exploits the SAX representation of the EGL to suggest gestures with a low likelihood of false triggering. Suggested gestures are ordered according to brevity and simplicity, freeing the interface designer to focus on the user experience. Once a gesture is selected, MAGIC can output synthetic examples of the gesture to train a chosen classifier (for example, with a hidden Markov model). If the interface designer suggests his own gesture and provides several examples, MAGIC estimates how accurately that gesture can be recognized and estimates its false positive rate by comparing it against the natural movements in the EGL. We demonstrate MAGIC’s effectiveness in gesture selection and helpfulness in creating accurate gesture recognizers. -
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 -
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. -
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 . -
Amitools Release 0.6.0
amitools Release 0.6.0 Jul 09, 2021 Contents 1 xdftool 1 1.1 Introduction...............................................1 1.2 Usage...................................................1 1.3 Commands................................................2 2 xdfscan 13 2.1 Introduction............................................... 13 2.2 Usage................................................... 13 2.3 Scanner Output.............................................. 14 3 rdbtool 15 3.1 Introduction............................................... 15 3.2 Usage................................................... 15 3.3 Commands................................................ 16 4 romtool 25 4.1 Features.................................................. 25 4.2 General Commands........................................... 25 4.3 Inspect a ROM.............................................. 26 4.4 Split a ROM into modules........................................ 28 4.5 Build a new ROM............................................ 30 5 Tools 33 6 Project Links 35 i ii CHAPTER 1 xdftool the universal Amiga disk image file tool 1.1 Introduction The xdftool is a tool from the amitools tool set that allows to read disk images intended for Amiga emulators like ADF or HDF files and display or extract their contents. Furthermore, you can • create new ADF or HDF images • copy files from the image • copy your own files to it • master own images • repack existing images • work on partitions inside RDISK/RDB hdf images or on real disks 1.2 Usage xdftool is a command line utility that is always called with an image file path name as the first argument and with one or more commands working on this image: > xdftool <image.adf|image.hdf> <command> [option] You can issue multiple commands on a single image by concatenating them with a plus character: > xdftool <image.[ah]df> <command1> [options1] + <command2> [options2] ... For Example:: 1 amitools, Release 0.6.0 > xdftool test.adf format ``My Image`` + makedir c + write myfile c 1.3 Commands This section describes the commands available for xdftool. -
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. -
Metadefender Core V4.17.3
MetaDefender Core v4.17.3 © 2020 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of MetaDefender Core 14 1. Quick Start with MetaDefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Process Files with MetaDefender Core 21 2. Installing or Upgrading MetaDefender Core 22 2.1. Recommended System Configuration 22 Microsoft Windows Deployments 22 Unix Based Deployments 24 Data Retention 26 Custom Engines 27 Browser Requirements for the Metadefender Core Management Console 27 2.2. Installing MetaDefender 27 Installation 27 Installation notes 27 2.2.1. Installing Metadefender Core using command line 28 2.2.2. Installing Metadefender Core using the Install Wizard 31 2.3. Upgrading MetaDefender Core 31 Upgrading from MetaDefender Core 3.x 31 Upgrading from MetaDefender Core 4.x 31 2.4. MetaDefender Core Licensing 32 2.4.1. Activating Metadefender Licenses 32 2.4.2. Checking Your Metadefender Core License 37 2.5. Performance and Load Estimation 38 What to know before reading the results: Some factors that affect performance 38 How test results are calculated 39 Test Reports 39 Performance Report - Multi-Scanning On Linux 39 Performance Report - Multi-Scanning On Windows 43 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. -
A VALIANT LITTLE TERMINAL a VLT User's Manual
SLAC-370tREV.4) A VALIANT LITTLE TERMINAL A VLT User’s Manual Amanda Weinstein SLAC-Report-370cREV.4) Revised August 1992 Prepared for the Department of Energy under contract number DE-AC03-76SF00515 I ? This document and the material and data contained therein, was devel- oped under sponsorship of the United States Government. Neither the United States nor the Department of Energy, nor the Leland Stanford Junior University, nor their employees, nor their respective contractors, subcontractors, or their employees, makes any warranty, express or im- plied, or assumes any liability or responsibility for accuracy, complete- ness or usefulness of any information, apparatus, product or process disclosed, or represents that its use will not infringe privately-owned rights. Mention of any product, its manufacturer, or suppliers shall not, nor is it intended to, imply approval, disapproval, or fitness for any particular use. A royalty-free, nonexclusive right to use and dis- seminate same for any purpose whatsoever, is expressly reserved to the United States and the University. I ;ft,;70( REV.4) Pi A VALIANT LITTLE TERMINAL A VLT User’s Manual Amanda Weinstein Stanford Linear Accelerator Center Stanford University, Stanford, CA 94309 August 1990 Revised December 1990 July 1991 September 1992 Prepared for the Department of Energy under contract number DE-AC03-76SF00515 Printed in the United States of America. Available from the National Technical Information Service, U.S. Department of Commerce, 5285 Port Royal Road, Springfield, Virginia 22161 \// \- A Valiant Little Terminal A VLT User’s Manual bY Amanda Weinstein Fourth Edition-August 1992 Trademarks and Copyrights IBM and VM/CMS are trademarks of International Business Machines. -
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.