Oops...I guess I got my facts mixed up!

Anyway, thanks for the correction, Didactylos. So, we have BOINC & UD running side by side, a hybrid infrastructure. This is interesting, it's the first time I heard of "hybrid infratructure".

Hmm...alright, at present, who provides all necessary data (that needs to be computed) to BOINC & UD? (Scripps or WCG?) After providing the data to BOINC & UD, do they (BOINC & UD) perform some sort of job scheduling and resource allocation, then distribute tasks to all WCG participants? After the tasks are completed, are the results being sent to WCG, or Scripps? (I'm quite confused here actually...please help me correct my facts... )

So, FightAIDS@Home runs on both BOINC & UD, there's no Globus involved? What about WCG? Is it just a web-portal (or account manager), or it's also part of the grid infrastructure that you've mentioned previously in your reply?

kimberrr

This diagram at the bottom of the page should also show you the flow of data between the various research participants:

http://www.worldcommunitygrid.org/projects_showcase/viewFaahPart.do

Globus is just another grid infrastructure - one of many.

WCG use BOINC (Berkeley Open Infrastructure for Network Computing) and Grid MP from United Devices.

Both of them consist of several parts. Grid MP is proprietary, so we don't know the precise details of how it all works. BOINC is OSS, so we know exactly what it does.

BOINC consists of a client (the part you download and run) and a scheduler, validator and a number of other tools and databases. WCG have extended this with a custom load balancer to better integrate with UD.

Then, there's the science application. FightAIDS@Home uses AutoDock. As it happens, AutoDock is developed in-house by Olson Labs. This isn't the case with all of our projects, sometimes complicated three way licensing agreements are required. Scripps provide the science application to WCG, and WCG adapt it to work with BOINC and UD.

Work is sent in batches from Scripps to WCG. WCG load the batches into the BOINC and UD systems, which handle sending out the work to individual computers and verifying and collating the results. WCG then return the results to Scripps for further study and eventual publication.

So, what do WCG do? They provide a lot of server power and storage space for the grid infrastucture. They perform the day to day management and maintenance of the grid. They do a lot of work adapting (porting) the science applications to run on the grid infrastructure and run on different processors and operating systems. From time to time they take on a project that requires a lot more work, writing much of the science application from scratch. They take all the headaches and pain away from the project scientists and simply deliver results. And of course, they are constantly seeking to grow a loyal and effective volunteer base, so they have sufficient capacity on the grid for future projects.

WCG have also contributed back to the development of BOINC, and have done a lot of additional work to make BOINC and UD work in harmony.

From the point of view of the scientists, WCG is a computing service. From the point of view of the members, WCG is a community of humanitarian volunteers.

So, in a way, WCG is the grid.

...and you thought it was going to be simple...

Your reply is a superb eye-opener for me, Didactylos!

From a client's point of view, the WCG agent running in the background (or as a screensaver) is invisible. However, from an application developer's point of view, it's far more comprehensive and there are many things to be learnt. Nice. Thank you so much~

kimberrr