{"id":606,"date":"2017-07-27T02:44:11","date_gmt":"2017-07-27T02:44:11","guid":{"rendered":"http:\/\/uscictdialdev.wpenginepowered.com\/?page_id=606"},"modified":"2017-07-27T02:45:05","modified_gmt":"2017-07-27T02:45:05","slug":"turkit","status":"publish","type":"page","link":"https:\/\/dialport.ict.usc.edu\/index.php\/resources\/collecting-annotationsdata\/turkit\/","title":{"rendered":"TurKit"},"content":{"rendered":"<p><a href=\"http:\/\/up.csail.mit.edu\/turkit\/\">About<\/a>\u00a0 <a href=\"http:\/\/up.csail.mit.edu\/projects\/turkit\/uist2010-turkit.pdf\">Paper<\/a><\/p>\n<p>&nbsp;<\/p>\n<p>TurKit is a Java\/JavaScript API for running iterative tasks on Mechanical Turk. You can safely re-execute TurKit programs without re-running costly side effects on Mechanical Turk, like creating new HITs, but still write your program in a straightforward imperative manner\u2014there is no need to unravel the program into a state machine. For a detailed description, please\u00a0<a href=\"http:\/\/groups.csail.mit.edu\/uid\/projects\/turkit\/uist2010-turkit.pdf\">read the paper<\/a>.<\/p>\n<p>&nbsp;<\/p>\n<p><strong>Abstract (from the paper)<\/strong><\/p>\n<p>Mechanical Turk provides an on-demand source of human computation. This provides a tremendous opportunity to explore algorithms which incorporate human computation as a function call. However, various systems challenges make this difficult in practice, and most uses of Mechanical Turk post large numbers of independent tasks. TurKit is a toolkit for prototyping and exploring truly algorithmic human computation, while maintaining a straight-forward imperative programming style. We present the crash-and rerun programming model that makes TurKit possible, along with a variety of applications for human computation algorithms. We also present a couple case studies of TurKit used for real experiments outside our lab.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>About\u00a0 Paper &nbsp; TurKit is a Java\/JavaScript API for running iterative tasks on Mechanical Turk. You can safely re-execute TurKit programs without re-running costly side effects on Mechanical Turk, like creating new HITs, but still write your program in a straightforward imperative manner\u2014there is no need to unravel the program into a state machine. For [&hellip;]<\/p>\n","protected":false},"author":18,"featured_media":0,"parent":599,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-606","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/dialport.ict.usc.edu\/index.php\/wp-json\/wp\/v2\/pages\/606","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dialport.ict.usc.edu\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/dialport.ict.usc.edu\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/dialport.ict.usc.edu\/index.php\/wp-json\/wp\/v2\/users\/18"}],"replies":[{"embeddable":true,"href":"https:\/\/dialport.ict.usc.edu\/index.php\/wp-json\/wp\/v2\/comments?post=606"}],"version-history":[{"count":0,"href":"https:\/\/dialport.ict.usc.edu\/index.php\/wp-json\/wp\/v2\/pages\/606\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/dialport.ict.usc.edu\/index.php\/wp-json\/wp\/v2\/pages\/599"}],"wp:attachment":[{"href":"https:\/\/dialport.ict.usc.edu\/index.php\/wp-json\/wp\/v2\/media?parent=606"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}