Property:Has system overview
From EduTech Wiki
This is a property of type Text.
Pages using the property "Has system overview"
Showing 14 pages using this property.
|Amazon mechanical turk +||According to [ Amazon] (nov. 7 2013), Mechanical Turk allows you to: * Define your HITs, including the specific output desired, the format of the output, how you display your work items and how much you will pay to have them completed. * Load millions of HITs into the marketplace to be completed. * Qualify your workforce: if special skills are required to complete your tasks, you can require that workers pass a qualification test before they are allowed to work on your HITs. Alternately, you can require that a worker has historically completed a minimum percentage of their tasks correctly or a minimum number of previous HITs in order to qualify for your HIT. * Only pay for quality work. Once your work items have been completed, you have the ability to review the results and accept or reject them. You only pay for accepted work. * Retrieve the results. Using the web services APIs, developers can retrieve the results and integrate them directly into their applications. +|
|Amazon mechanical turk API +||Amazon Mechanical Turk Workflow, according to [http://docs.aws.amazon.com/AWSMechTurk/latest/AWSMechanicalTurkRequester/IntroductionArticle.html Introduction to Amazon Mechanical Turk] (nov. 6 2013) # A developer creates an Amazon Mechanical Turk application. # A Requester uses an Amazon Mechanical Turk application, command line interface, or the Requester UI to create work, called a HIT, and advertises the work using Amazon Mechanical Turk. # Workers visit the Amazon Mechanical Turk website and decide which work to undertake. # Optionally, the Requester can require the Worker to pass a qualification test before being granted the opportunity to do the work. # The Workers complete one or more HITs and submit their answers using Amazon Mechanical Turk. # The Requester reviews the work and pays the Worker for work done well or rejects the work and does not pay the Worker. +|
|BOINC +||The system is comprised of: * Sever software * Client software (Win/Mac/Linux/others) As explained in [http://boinc.berkeley.edu/wiki/How_BOINC_works How BOINC works] (Sept. 24, 2013), # Your PC gets a set of tasks from the project's scheduling server. The tasks depend on your PC: for example, the server won't give it tasks that requires more RAM than you have. Projects can support several applications, and the server may send you tasks from any of them. # Your PC downloads executable and input files from the project's data server. If the project releases new versions of its applications, the executable files are downloaded automatically to your PC. # Your PC runs the application programs, producing output files. # Your PC uploads the output files to the data server. # Later (up to several days later, depending on your preferences) your PC reports the completed tasks to the scheduling server, and gets new tasks. +|
|BOINC client software +||The BOINC client includes the following components ; boinc - The BOINC core client. : ;BOINC Screensaver. :It can do three things: The overview screensaver displays general information, such as the BOINC status, a list of projects, etc. The project graphics display the graphics for one of the currently running tasks, e.g., SETI@home. However, many projects do not have screensaver graphics. The screensaver coordinator controls the screensaver, selecting either the default screensaver or project graphics. ; List of scripts: :boincmgr - The BOINC Manager. :boinccmd - A command line tool for controlling a running core client. :run_client - A script that cd's into the BOINC directory and runs the core client. :run_manager - A script that cd's into the BOINC directory and runs the manager. +|
|Citizen science custom software +||N/A +|
|Cornell Lab citizen science technology +||Tools do not seem to be available (to verify) +|
|Crowdcrafting +||Crowdcrafting.org is made with the PyBossa software. I.e. you could create your own. +|
|Experimental tribe +||XTribe has been designed with a modular structure through which most of the complexity associated to running an experiment is hidden into a Main Server, while the experimentalist is left with the only duty of devising a suitable interface for the actual experiment. In this way most of the coding difficulties related to the realization of a dynamic web application are already taken care by the ET Server and the realization of an experiment should be as easy as constructing a webpage with the main utilities for it. +|
|Infrastructure test +||Nunc rhoncus augue nec metus pharetra tincidunt. Proin dignissim dolor id nunc vehicula lacinia. Ut malesuada ante sem, sit amet condimentum magna consectetur eu. Integer interdum, risus sed bibendum imperdiet, metus leo consequat dolor, quis venenatis nisl libero sit amet erat. Praesent euismod lectus vel massa semper, vitae ullamcorper dolor egestas. Nulla facilisi. Sed turpis odio, molestie sit amet ultrices vel, mollis sed tortor. Curabitur vestibulum libero ut felis posuere, sit amet elementum felis placerat. Mauris auctor porta urna, nec vehicula sem vulputate molestie. Pellentesque mattis nec velit vitae commodo. Phasellus sapien sem, consequat a nunc at, congue imperdiet metus. Suspendisse quis urna nibh. +|
|Sapelli Suite +||The client system runs on Android. +|
|Semantic Forms extension +||Semantic Forms allows to create input forms that allow users to enter structured "semantic" data which then can be queried and assembled. See [[Semantic Forms]] for a technical introduction in this wiki +|
|Testing Sandbox +||The Platform In Depth XTribe has been designed with a modular structure through which most of the complexity associated to running an experiment is hidden into a Main Server, while the experimentalist is left with the only duty of devising a suitable interface for the actual experiment. In this way most of the coding difficulties related to the realization of a dynamic web application are already taken care by the ET Server and the realization of an experiment should be as easy as constructing a webpage with the main utilities for it. +|
|Zooniverse +||Zooniverse is a hub that allows members to transparently sign in to various projects. +|