Abstract
Volunteer computing (VC) or distributed computing projects are common in the citizen cyberscience (CCS) community and present extensive opportunities for scientists to make use of computing power donated by volunteers to undertake large-scale scientific computing tasks. VC is generally a noninteractive process for those contributing computing resources to a project, whereas volunteer thinking (VT) or distributed thinking allows volunteers to participate interactively in CCS projects to solve human computation tasks. In this paper, we describe the integration of three tools, the Virtual Atom Smasher (VAS) game developed by CERN, LiveQ, a job distribution middleware, and CitizenGrid, an online platform for hosting and providing computation to CCS projects. This integration demonstrates the combining of VC and VT to help address the scientific and educational goals of games like VAS. This paper introduces the three tools and provides details of the integration process along with further potential usage scenarios for the resulting platform.
Highlights
I N the last few years, citizen cyberscience (CCS) has evolved as a new way of inspiring and supporting learning and participation in science
Existing CCS projects are mainly categorized as volunteer computing (VC) or volunteer thinking (VT) projects, examples of this are provided in [1]–[3]
By this we mean that when a VT task requires some data that must be generated to order, this must trigger a related VC task that must be scheduled such that results are provided to best support the interactivity requirements of the VT task the end user is undertaking
Summary
I N the last few years, citizen cyberscience (CCS) has evolved as a new way of inspiring and supporting learning and participation in science It provides a means for citizens, who may not have a scientific background, to interact with and contribute to scientific projects or studies. The second scenario is more complex to implement since a common framework must be provided that can link the task lifecycles of both VT and VC tasks By this we mean that when a VT task requires some data that must be generated to order, this must trigger a related VC task that must be scheduled such that results are provided to best support the interactivity requirements of the VT task the end user is undertaking.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
