Frequently Asked Questions (FAQ)
The Genome@home distributed computing project currently supports two different clients: the original version 0.99 (also called G@h Classic), and the newer G@h 2.06 client/core system (also called the F@h3.0/G@h2.0 combi client). As of May 1, 2003, we will stop supporting the 0.99 client. We encourage all Genome@home users to upgrade to the G@h 2.06 client/core system.
No. Not at all. The scientific research effort behind Genome@home is alive and well, stronger than ever. As well, the Genome@home distributed computing project will continue, with no major changes. The only difference is that the original 0.99 client is being discontinued.
The Genome@home project began over two years ago, with a very specific set of scientific research goals. The 0.99 client was designed to specifically address these goals. We have now completed the initial phases of the project, and the architecture inherent in our original client-server infrastructure cannot support the functionality necessary for the next set of scientific questions we'll be tackling. More specifically, the auto-update feature of the G@h 2.06 client/core system is much more sophisticated than the 0.99 architecture and allows us to explore new protein design algorithms "on the fly".
What we refer to as the Genome@home 2.06 client/core system is technically the combination of the F@h 3.24 client, running the Core_ca 2.06 protein design core. The F@h client system has the ability to run several different scientific "cores", which are simply the programs that do the actual scientific calculations of interest to us. When the F@h client downloads a "G@h" workunit and runs the Core_ca core, it is actually running the Genome@home protein design algorithm!
Running the Genome@home 2.06 system simply involves downloading the client, and choosing the "Genome@home" option in the Advanced tab during the initial configuration. You will receive only G@h protein design workunits and will run the G@h protein design algorithm (in Core_ca) exclusively. Also, as long as you enter your existing Genome@home username and a valid G@h team number (i.e. greater than 100,000), all your workunits will be credited towards your Genome@home stats. If you're not part of a Genome@home team, but would still like to remain exclusively within the Genome@home stats system, just use team number 100,000.
We have recently changed our assignment server to make it impossible for the Genome@home 2.06 client/core system to receive F@h workunits. Choosing the "Genome@home" option as described above guarantees exclusively G@h workunits.
It won't affect them at all. The Genome@home project will continue as is. Because the project itself continuing, the stats will be unaffected. They will not start over from zero; they will continue on from where they are now. If you choose to continue participating in the project, by upgrading to the G@h 2.06 client/core system and entering your current username and team number, all your complete work units will be credited to your G@h stats.
We're very proud of all the users that have helped to make Genome@home as successful as it is. Our number one priority is to ensure that the scientific work behind this project is truly world-class, so that no CPU-time is wasted. Though many of our die-hard Genomers will mourn the loss of the 0.99 client, we simply cannot continue to do useful science within it's architecture. We're working hard to continue the success of the Genome@home project, and to take into account the needs and wants of the user community.
The infrastructure inherent in the G@h 2.06 client/core system, has been the major focus of the Pande Group's software development and methods research efforts over the last three years. The client and server software is more stable, versatile, and advanced than the G@h 0.99 system. Most importantly, the 2.06 system allows us to update our protein design algorithms "on the fly", by allowing auto-updates of the scientific cores. As our scientific research focus turns to developing and testing new design algorithms (based on our insights from two years of work with the 0.99 algorithm), this capability is imperative.
The G@h 2.06 client/core system does not support nonetting in the same way as the G@h 0.99 client. We are currently testing a modifiation to the client that would allow pre-fetching of several workunits and subsequent batch uploading of results. However, in the long run, our next-generation protein design algorithms will likely not be amenable to nonetting, as they will require much more communication between individual workunits.