DOCSLIB.ORG

Harnessing Collective Intelligence for Translation: an Assessment of Crowdsourcing As a Means of Bridging the Canadian Linguistic Digital Divide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Harnessing Collective Intelligence for Translation: an Assessment of Crowdsourcing As a Means of Bridging the Canadian Linguistic Digital Divide HARNESSING COLLECTIVE INTELLIGENCE FOR TRANSLATION: AN ASSESSMENT OF CROWDSOURCING AS A MEANS OF BRIDGING THE CANADIAN LINGUISTIC DIGITAL DIVIDE Steven O’Brien Supervisor: Dr. Ajax Persaud Thesis submitted to the Faculty of Graduate and Postdoctoral Studies in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE IN ELECTRONIC BUSINESS TECHNOLOGIES Telfer School of Management Faculty of Graduate and Postdoctoral Studies University of Ottawa © Steven O‟Brien, Ottawa, Canada, 2011 Table of Contents List of Tables .................................................................................................................................. vii List of Figures ................................................................................................................................... x List of Equations ............................................................................................................................. xii Acknowledgments......................................................................................................................... xiii Abstract ......................................................................................................................................... xiv Chapter 1: Introduction .................................................................................................................. 1 1.1 Rationale and Significance .................................................................................................... 3 1.2 Anticipated Contribution ...................................................................................................... 6 Chapter 2: Theoretical Framework ................................................................................................. 7 2.1 Collaborative Online Language Transfer ............................................................................... 8 2.2 Performance Criteria ............................................................................................................. 9 2.3 Lightweight Peer Production .............................................................................................. 14 2.4 The Landscape of Document Engineering .......................................................................... 18 2.5 Problem Statement ............................................................................................................. 19 Chapter 3: Phase I (Translation Creation) - Methodology ............................................................ 21 3.1 Overview ............................................................................................................................. 21 3.2 Source Text.......................................................................................................................... 23 3.3 Qualitative Translation Goals (Translation Brief) ............................................................... 25 3.4 Amazon Mechanical Turk .................................................................................................... 25 3.5 Confluence Software ........................................................................................................... 27 3.6 Paragraph Translation Process ........................................................................................... 27 3.7 Paragraph Evaluation Process ............................................................................................. 27 3.8 Revision Creation Process ................................................................................................... 28 3.9 Revision Evaluation Process ................................................................................................ 29 Chapter 4: Phase I (Translation Creation) - Analysis ..................................................................... 30 4.1 Key Performance Indicators ................................................................................................ 30 4.2 Participation ........................................................................................................................ 30 4.3 Non-Participation ................................................................................................................ 31 4.4 Time .................................................................................................................................... 32 ii 4.5 Cost ..................................................................................................................................... 32 4.6 Evaluation Selection ............................................................................................................ 32 4.7 Diversity .............................................................................................................................. 33 4.8 Approximate Translation Quality ........................................................................................ 36 Chapter 5: Phase II (Translation Evaluation) - Methodology ........................................................ 37 5.1 Overall Translation Quality ................................................................................................. 37 5.2 Task Repetition ................................................................................................................... 38 5.3 Knowledge of Translation Methods .................................................................................... 38 5.4 General Translation Errors .................................................................................................. 38 5.5 Overt Errors ......................................................................................................................... 39 5.6 Usage Errors ........................................................................................................................ 39 5.7 Author Errors ...................................................................................................................... 40 5.8 Contextual Translation Errors ............................................................................................. 40 5.9 Translation Diversity ........................................................................................................... 40 5.10 Machine Translation ......................................................................................................... 41 5.11 Professional Translation.................................................................................................... 41 5.12 Crowdsourced Translation ................................................................................................ 41 5.13 Crowdsourced Translation Acceptance ............................................................................ 41 5.14 Research Hypotheses ........................................................................................................ 42 5.15 Hypothesis Testing ............................................................................................................ 45 5.16 Partial Least Squares – Path Modeling with Smart PLS 2.0 .............................................. 45 5.17 Structural Equation Modeling using PLS-PM .................................................................... 46 5.18 Study Participants ............................................................................................................. 48 5.19 Instrument and Measurement ......................................................................................... 51 Chapter 6: Phase II (Translation Evaluation) - Analysis ................................................................ 53 6.1 Overview ............................................................................................................................. 53 6.2 Hypothesis (H1) ................................................................................................................... 55 6.3 Hypothesis (H2) ................................................................................................................... 58 6.4 Hypothesis (H3) ................................................................................................................... 61 iii 6.5 Hypothesis (H4) ................................................................................................................... 64 6.6 Hypothesis (H5) ................................................................................................................... 66 6.7 Hypothesis (H6) ................................................................................................................... 69 6.8 Hypothesis (H7) ................................................................................................................... 73 6.9 Hypothesis (H8) ................................................................................................................... 76 6.9 Crowdsourced Translation Acceptance .............................................................................. 79 6.10 Rank Order Positively Influences Overall Translation Quality .......................................... 84 6.11 Multivariate Model of Crowdsourced Translation ........................................................... 86 Chapter 7: Discussion .................................................................................................................... 94 7.1 Limitations and Future Research .......................................................................................
Load more

Recommended publications
  • BSD – Alternativen Zu Linux
    ∗BSD { Alternativen zu Linux Karl Lockhoff March 19, 2015 Inhaltsverzeichnis I Woher kommt BSD? I Was ist BSD? I Was ist sind die Unterschiede zwischen FreeBSD, NetBSD und OpenBSD? I Warum soll ich *BSD statt Linux einsetzen? I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I 1978 I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den
    [Show full text]
  • PITAC Report to the President Information Technology Information Research: Investing in Our Future PITAC to the President Report
    PITAC Report to the PresidentPITAC Research: Investing in Our Future Information Technology PRESIDENT’S INFORMATION TECHNOLOGY ADVISORY COMMITTEE REPORT TO THE PRESIDENT Information Technology Research: Investing in Our Future February 1999 PRESIDENT’S INFORMATION TECHNOLOGY ADVISORY COMMITTEE REPORT TO THE PRESIDENT Information Technology Research: Investing in Our Future February 1999 P RESIDENT’ S I NFORMATION T ECHNOLOGY A DVISORY C OMMITTEE February 24, 1999 The President of the United States The White House Dear Mr. President: We are pleased to present our final report, “Information Technology Research: Investing in Our Future,” on future directions for Federal support of research and development for information tech- nology. This report adds detail to the findings and recommendations in our interim report dated August 1998, and strengthens our previous recommendations regarding the importance of social and economic research on the impacts of information technology to inform key policy decisions. PITAC members are strongly encouraged by and enthusiastically supportive of the Administration’s Information Technology for the Twenty-First Century (IT2) initiative. This initiative is a vital first step in increasing funding for long-term, high-risk information technology research and develop- ment. Increased Federal support is critical to meeting the challenge of capturing the opportunities available from information technology in the 21st Century through appropriate research and development. The economic and strategic importance of information technology and the unique role of the Federal Government in sponsoring information technology research make it necessary to increase Federal support over a period of years to ensure our Nation’s future well-being. We hope that our recommendations will be helpful as you consider the priorities for Federal invest- ments.
    [Show full text]
  • Why the Future Doesn't Need Us
    BILL JOY OPINION 04.01.00 12:00 PM WHY THE FUTURE DOESN'T NEED US FROM THE MOMENT I became involved in the creation of new technologies, their ethical dimensions have concerned me, but it was only in the autumn of 1998 that I became anxiously aware of how great are the dangers facing us in the 21st century. I can date the onset of my unease to the day I met Ray Kurzweil, the deservedly famous inventor of the first reading machine for the blind and many other amazing things. Ray and I were both speakers at George Gilder's Telecosm conference, and I encountered him by chance in the bar of the hotel after both our sessions were over. I was sitting with John Searle, a Berkeley philosopher who studies consciousness. While we were talking, Ray approached and a conversation began, the subject of which haunts me to this day. I had missed Ray's talk and the subsequent panel that Ray and John had been on, and they now picked right up where they'd left off, with Ray saying that the rate of improvement of technology was going to accelerate and that we were going to become robots or fuse with robots or something like that, and John countering that this couldn't happen, because the robots couldn't be conscious. While I had heard such talk before, I had always felt sentient robots were in the realm of science fiction. But now, from someone I respected, I was hearing a strong argument that they were a near-term possibility.
    [Show full text]
  • Twenty Years of Berkeley Unix : from AT&T-Owned to Freely
    Twenty Years of Berkeley Unix : From AT&T-Owned to Freely Redistributable Marshall Kirk McKusick Early History Ken Thompson and Dennis Ritchie presented the first Unix paper at the Symposium on Operating Systems Principles at Purdue University in November 1973. Professor Bob Fabry, of the University of California at Berkeley, was in attendance and immediately became interested in obtaining a copy of the system to experiment with at Berkeley. At the time, Berkeley had only large mainframe computer systems doing batch processing, so the first order of business was to get a PDP-11/45 suitable for running with the then-current Version 4 of Unix. The Computer Science Department at Berkeley, together with the Mathematics Department and the Statistics Department, were able to jointly purchase a PDP-11/45. In January 1974, a Version 4 tape was delivered and Unix was installed by graduate student Keith Standiford. Although Ken Thompson at Purdue was not involved in the installation at Berkeley as he had been for most systems up to that time, his expertise was soon needed to determine the cause of several strange system crashes. Because Berkeley had only a 300-baud acoustic-coupled modem without auto answer capability, Thompson would call Standiford in the machine room and have him insert the phone into the modem; in this way Thompson was able to remotely debug crash dumps from New Jersey. Many of the crashes were caused by the disk controller's inability to reliably do overlapped seeks, contrary to the documentation. Berkeley's 11/45 was among the first systems that Thompson had encountered that had two disks on the same controller! Thompson's remote debugging was the first example of the cooperation that sprang up between Berkeley and Bell Labs.
    [Show full text]
  • Openbsd Gaming Resource
    OPENBSD GAMING RESOURCE A continually updated resource for playing video games on OpenBSD. Mr. Satterly Updated August 7, 2021 P11U17A3B8 III Title: OpenBSD Gaming Resource Author: Mr. Satterly Publisher: Mr. Satterly Date: Updated August 7, 2021 Copyright: Creative Commons Zero 1.0 Universal Email: [email protected] Website: https://MrSatterly.com/ Contents 1 Introduction1 2 Ways to play the games2 2.1 Base system........................ 2 2.2 Ports/Editors........................ 3 2.3 Ports/Emulators...................... 3 Arcade emulation..................... 4 Computer emulation................... 4 Game console emulation................. 4 Operating system emulation .............. 7 2.4 Ports/Games........................ 8 Game engines....................... 8 Interactive fiction..................... 9 2.5 Ports/Math......................... 10 2.6 Ports/Net.......................... 10 2.7 Ports/Shells ........................ 12 2.8 Ports/WWW ........................ 12 3 Notable games 14 3.1 Free games ........................ 14 A-I.............................. 14 J-R.............................. 22 S-Z.............................. 26 3.2 Non-free games...................... 31 4 Getting the games 33 4.1 Games............................ 33 5 Former ways to play games 37 6 What next? 38 Appendices 39 A Clones, models, and variants 39 Index 51 IV 1 Introduction I use this document to help organize my thoughts, files, and links on how to play games on OpenBSD. It helps me to remember what I have gone through while finding new games. The biggest reason to read or at least skim this document is because how can you search for something you do not know exists? I will show you ways to play games, what free and non-free games are available, and give links to help you get started on downloading them.
    [Show full text]
  • Free As in Freedom (2.0): Richard Stallman and the Free Software Revolution
    Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution Sam Williams Second edition revisions by Richard M. Stallman i This is Free as in Freedom 2.0: Richard Stallman and the Free Soft- ware Revolution, a revision of Free as in Freedom: Richard Stallman's Crusade for Free Software. Copyright c 2002, 2010 Sam Williams Copyright c 2010 Richard M. Stallman Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License." Published by the Free Software Foundation 51 Franklin St., Fifth Floor Boston, MA 02110-1335 USA ISBN: 9780983159216 The cover photograph of Richard Stallman is by Peter Hinely. The PDP-10 photograph in Chapter 7 is by Rodney Brooks. The photo- graph of St. IGNUcius in Chapter 8 is by Stian Eikeland. Contents Foreword by Richard M. Stallmanv Preface by Sam Williams vii 1 For Want of a Printer1 2 2001: A Hacker's Odyssey 13 3 A Portrait of the Hacker as a Young Man 25 4 Impeach God 37 5 Puddle of Freedom 59 6 The Emacs Commune 77 7 A Stark Moral Choice 89 8 St. Ignucius 109 9 The GNU General Public License 123 10 GNU/Linux 145 iii iv CONTENTS 11 Open Source 159 12 A Brief Journey through Hacker Hell 175 13 Continuing the Fight 181 Epilogue from Sam Williams: Crushing Loneliness 193 Appendix A { Hack, Hackers, and Hacking 209 Appendix B { GNU Free Documentation License 217 Foreword by Richard M.
    [Show full text]
  • UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM
    UNIX History Page 1 Tuesday, December 10, 2002 7:02 PM CHAPTER 1 UNIX Evolution and Standardization This chapter introduces UNIX from a historical perspective, showing how the various UNIX versions have evolved over the years since the very first implementation in 1969 to the present day. The chapter also traces the history of the different attempts at standardization that have produced widely adopted standards such as POSIX and the Single UNIX Specification. The material presented here is not intended to document all of the UNIX variants, but rather describes the early UNIX implementations along with those companies and bodies that have had a major impact on the direction and evolution of UNIX. A Brief Walk through Time There are numerous events in the computer industry that have occurred since UNIX started life as a small project in Bell Labs in 1969. UNIX history has been largely influenced by Bell Labs’ Research Editions of UNIX, AT&T’s System V UNIX, Berkeley’s Software Distribution (BSD), and Sun Microsystems’ SunOS and Solaris operating systems. The following list shows the major events that have happened throughout the history of UNIX. Later sections describe some of these events in more detail. 1 UNIX History Page 2 Tuesday, December 10, 2002 7:02 PM 2 UNIX Filesystems—Evolution, Design, and Implementation 1969. Development on UNIX starts in AT&T’s Bell Labs. 1971. 1st Edition UNIX is released. 1973. 4th Edition UNIX is released. This is the first version of UNIX that had the kernel written in C. 1974. Ken Thompson and Dennis Ritchie publish their classic paper, “The UNIX Timesharing System” [RITC74].
    [Show full text]
  • S Tudy of “A Response to Bill Joy and the Doom-And-Gloom Technofuturists”
    Fanouillère Jean-Baptiste S tudy of “A Response to Bill Joy and the Doom-and-Gloom Technofuturists” by John Seely Brown and Paul Duguid Just a few months after mankind entered the third millennium, a long article was published about the development of new technologies and the future of the human race, that would create many reactions and spur an intense debate in all intellectual and scientific circles. By writing “Why the future doesn't need us”1, and by deliberately giving it a provocative and alarmist tone, Bill Joy knew he would not fail to stir up a controversy which he thought was highly needed, since it was to draw the attention of the public on the dangers of the famous GNR - Genetics, Nanotechnology, Robotics - and to initiate a general reflection on the foundations of scientific research. Undeniably, his endeavors were successful. The article, published in the “Wired” magazine, created a major debate and received thousands of reactions, ranging from total catastrophism to full rejection of the author's warnings. Some even said that this document's importance equated that of the 1939 letter from Albert Einstein to President Roosevelt to warn him of the possibility of a nuclear bomb. It must be said that the computer scientist behind this article is none other than the co-founder of Sun Microsystems2 and the leading developer of BSD Linux and Java, among other things. A figure recognized and respected in the world of technology, he is one of the pillars of the community inventing and developing the very machines cited in his article, which is why his call caused great surprise.
    [Show full text]
  • Robert Garner
    San José State University The Department of Computer Science and The Department of Computer Engineering jointly present THE HISTORY OF COMPUTING SPEAKER SERIES Robert Garner Tales of CISC and RISC from Xerox PARC and Sun Wednesday, December 7 6:00 – 7:00 PM Auditorium ENGR 189 Engineering Building CISCs emerged in the dawn of electronic digital computers, evolved flourishes, and held sway over the first half of the computing revolution. As transistors shrank and memories became faster, larger, and cheaper, fleet- footed RISCs dominated in the second half. In this talk, I'll describe the paradigm shift as I experienced it from Xerox PARC's CISC (Mesa STAR) to Sun's RISC (SPARC Sun-4). I'll also review the key factors that affected microprocessor performance and appraise how well I predicted its growth for the next 12 years back in 1996. I'll also share anecdotes from PARC and Sun in the late 70s and early 80s. Robert’s Silicon Valley career began with a Stanford MSEE in 1977 as his bike route shifted slightly eastward to Xerox’s Palo Alto Research facility to work with Bob Metcalfe on the 10-Mbps Ethernet and the Xerox STAR workstation, shipped in 1981. He subsequently joined Lynn Conway’s VLSI group at Xerox PARC. In 1984, he jumped to the dazzling start-up Sun Microsystems, where with Bill Joy and David Patterson, he led the definition of Sun’s RISC (SPARC) while co-designing the Sun-4/200 workstation, shipped in 1986. He subsequently co-managed several engineering product teams: the SunDragon/SPARCCenter multiprocessor, the UltraSPARC-I microprocessor, the multi-core/threaded Java MAJC microprocessor, and the JINI distributed devices project.
    [Show full text]
  • An Introduction to Display Editing with Vi
    An Introduction to Display Editing with Vi William Joy Mark Horton Computer Science Division Department of Electrical Engineering and Computer Science University of California, Berkeley Berkeley, Ca. 94720 ABSTRACT Vi (visual) is a display oriented interactive text editor. When using vi the screen of your terminal acts as a window into the file which you are editing. Changes which you make to the file are reflected in what you see. Using vi you can insert new text any place in the file quite easily. Most of the commands to vi move the cursor around in the file. There are commands to move the cursor forward and backward in units of characters, words, sentences and paragraphs. A small set of operators, like d for delete and c for change, are combined with the motion commands to form operations such as delete word or change paragraph, in a simple and natural way. This regularity and the mnemonic assignment of commands to keys makes the editor command set easy to remember and to use. Vi will work on a large number of display terminals, and new terminals are easily driven after editing a terminal description file. While it is advantageous to have an intelligent terminal which can locally insert and delete lines and characters from the display, the editor will function quite well on dumb terminals over slow phone lines. The editor makes allowance for the low bandwidth in these situations and uses smaller window sizes and different display updating algo- rithms to make best use of the limited speed available. It is also possible to use the command set of vi on hardcopy terminals, storage tubes and ‘‘glass tty’s’’ using a one line editing window; thus vi’s command set is available on all termi- nals.
    [Show full text]
  • Ray Kurzweil Reader Pdf 6-20-03
    Acknowledgements The essays in this collection were published on KurzweilAI.net during 2001-2003, and have benefited from the devoted efforts of the KurzweilAI.net editorial team. Our team includes Amara D. Angelica, editor; Nanda Barker-Hook, editorial projects manager; Sarah Black, associate editor; Emily Brown, editorial assistant; and Celia Black-Brooks, graphics design manager and vice president of business development. Also providing technical and administrative support to KurzweilAI.net are Ken Linde, systems manager; Matt Bridges, lead software developer; Aaron Kleiner, chief operating and financial officer; Zoux, sound engineer and music consultant; Toshi Hoo, video engineering and videography consultant; Denise Scutellaro, accounting manager; Joan Walsh, accounting supervisor; Maria Ellis, accounting assistant; and Don Gonson, strategic advisor. —Ray Kurzweil, Editor-in-Chief TABLE OF CONTENTS LIVING FOREVER 1 Is immortality coming in your lifetime? Medical Advances, genetic engineering, cell and tissue engineering, rational drug design and other advances offer tantalizing promises. This section will look at the possibilities. Human Body Version 2.0 3 In the coming decades, a radical upgrading of our body's physical and mental systems, already underway, will use nanobots to augment and ultimately replace our organs. We already know how to prevent most degenerative disease through nutrition and supplementation; this will be a bridge to the emerging biotechnology revolution, which in turn will be a bridge to the nanotechnology revolution. By 2030, reverse-engineering of the human brain will have been completed and nonbiological intelligence will merge with our biological brains. Human Cloning is the Least Interesting Application of Cloning Technology 14 Cloning is an extremely important technology—not for cloning humans but for life extension: therapeutic cloning of one's own organs, creating new tissues to replace defective tissues or organs, or replacing one's organs and tissues with their "young" telomere-extended replacements without surgery.
    [Show full text]
  • Limits and the Practical Usability of Bsds, a Big Data Prospective
    Limits and the Practical Usability of BSDs, a Big Data Prospective Predrag Punosevacˇ [email protected] The Auton Lab Carnegie Mellon University June 11, 2016 1 / 22 Thanks Thanks to organizers for this great meeting and for giving me the op- portunity to speak. note 1 of slide 1 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ❖ General Limitations ❖ Scientific Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific ● Why don’t we just use SCS computing facilities? Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific ● Why don’t we just use SCS computing facilities? Computing ❖ Continuation ❖ misc issues ● How did
    [Show full text]