intro.php

<?php

// This file is part of BOINC.
// http:https://boinc.berkeley.edu
// Copyright (C) 2019 University of California
//
// BOINC is free software; you can redistribute it and/or modify it
// under the terms of the GNU Lesser General Public License
// as published by the Free Software Foundation,
// either version 3 of the License, or (at your option) any later version.
//
// BOINC is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
// See the GNU Lesser General Public License for more details.
//
// You should have received a copy of the GNU Lesser General Public License
// along with BOINC.  If not, see <http:https://www.gnu.org/licenses/>.

require_once("../inc/util.inc");

page_head("Intro to Science United for BOINC users");

text_start();
echo <<<EOT
<h3>How to use Science United</h3>
<p>
If you're already running BOINC on a computer,
you can use Science United as follows:
<ul>
<li> <a href=https://scienceunited.org/su_join.php>Create a Science United account.</a>
<li> <a href=https://boinc.berkeley.edu/download.php>Upgrade the computer</a> to BOINC version 7.16 or later
(preferably the current version).
<li> Go to the BOINC Manager.  If you're using the Simple View,
go to the View menu and select "Advanced view".
<li> In the Tools menu, select "Use account manager".
<li> Select Science United.
<li> Enter the email address and password of your Science United account.
</ul>
That's it.
Consider detaching from the projects you were previously running.

<h3>What is Science United?</h3>
<p>
Science United (SU) is a new way
to participate in BOINC-based volunteer computing.
SU doesn't replace the old way of doing things,
where you people attach to specific projects;
rather, it's an alternative where you choose science areas,
and SU picks the projects for you.
The computing power of SU participants is divided among
all approved BOINC projects.
<p>
SU is designed for people who
<ul>
<li> are not technical;
<li> don't want to spend much time on BOINC
(fiddling with settings or browsing project web sites);
<li> are motivated primarily by science goals.
</ul>
<p>

<h3>Science areas, not projects</h3>

<p>
When you participate in SU, you sign up for science areas, not projects.
You can choose the areas and sub-areas you want to support,
and the ones you don't.
Similarly for the location of the research.

<p>
SU is implemented as an "account manager", like BAM! and GridRepublic.
When you attach a computer to SU,
it tells your computer what projects to run,
based on your preferences and other factors.
These may change over time, even from day to day.
You may end up running a project that didn't exist when you first signed up.
You don't have to browse and evaluate projects;
in effect, SU does that for you.

<h3>Encourage new projects</h3>
<p>
This means that a new project can be assured of
a certain amount of computing power,
without doing any publicity or even developing a web site.
The need to do these things, and the risk of investing in BOINC,
have been major barriers to entry for scientists who might otherwise use BOINC.
The hope is that SU will lead to the creation of more projects.

<h3>User-friendliness</h3>

<p>
In my conversations with "average" computer owners
(e.g. friends and family) about the BOINC user interface,
several themes emerge:
<ul>
<li> It's too complex.
<li> It presents too much information, and especially textual information.
When people are shown information they
assume they need to understand it all.
<li> It emphasizes competition (e.g. leaderboards).
Some volunteers are intimidated and put off by this.
</ul>
SU tries to remedy these problems.
In looking at the SU site, there are few things that you might notice:

<ul>
<li> New users download BOINC by the "auto-attach" mechanism
where a) the download happens directly, rather than going through the
BOINC web site, and b) when BOINC starts up, it's already attached to SU.

<li> There are no leader boards.
Credit isn't shown anywhere.
Users see graphs of their own work history,
but no comparisons with other users.

<li> We try to minimize the use of technical terms like FLOPS.

<li> Computing preferences have been reduced to three options:
green, standard, and max.

<li> We avoid showing lots of information.

<li> We show information graphically rather than textually where possible.

<li> We de-emphasize the notion of project.
Users can see what projects they're contributing to,
but only by drilling down a bit.
</ul>

<p>
SU's target user wants to install the software in a couple of minutes,
set it, and forget it.
They may or may not ever return to the SU web site.
<p>
By default, SU sends users a weekly "status" email
whose purpose is to keep the user informed about their contribution,
and to alert them if any of their computers have stopped doing work.

<h3>Feedback</h3>
<p>
Give feedback (bugs, questions, feature requests)
on the SU message boards.
You can also email me (David Anderson) directly.
Remember that the target audience of SU is not BOINC 'power users'.
Pretend you're interested in science but know little about computers.
Would you understand the overall idea of SU?
Would you be able to follow the instructions?
Would you follow through to the end?

<h3>More information</h3>
<p>
Two more detailed documents are available:
<p>
<a href=doc/pearc_20.pdf>Coordinating Volunteer Computing</a>
describes the goals and motivations of Science United.
<p>
<a href=doc/implementation.pdf>Science United: Implementation</a>
explains how things work under the hood.

EOT;
text_end();

page_tail();
?>