WEEKLY UPDATE - based on work averaged over the last 8 weeks:

Current Batch - 37,879

Days Left - 402

End Date - March 5, 2014

Experiment Completion - 37.11 %

WEEKLY UPDATE - based on work averaged over the last 8 weeks:

Current Batch - 37,998

Days Left - 395

End Date - March 5, 2014

Experiment Completion - 38.12 %

** 2 new developments that might speed up our project completion **

development # 1 - Computing for Clean Water project appears to be coming to completion soon on target 7. Latest dashboard has 11 days remaning, so in about two weeks more computing resources could be freed up for FAAH. Right now the scientists have not released any plans for target 8 .

development # 2 - Last week a Beta was sent out with FAAH units. Based on my reading of the discussion it looks like some upgrades are being made to the FAAH application to support 64-bit in addition to the current 32-bit. Whatever changes are being made, I hope it will help increase our overall production and speed up this project.

WEEKLY UPDATE - based on work averaged over the last 8 weeks:

Current Batch - 38,097

Days Left - 400

End Date - March 17, 2014

Experiment Completion - 38.97 %

In related project news:

development # 1 - Computing for Clean Water project appears to be coming to completion soon on target 7. Latest dashboard has 3 days remaning, and soon more computing resources could be freed up for FAAH.

development # 2 - Our project has slowed down in overall production about 30% this week. I am not sure what has caused this. We went from about 55 years of run time per day to 37.5 year of run time. The decline can be seen this chart . Anyone have any information on this slowdown?

development # 3 - This week there was an update on the FA@H project status website. Volume 11 of the FightAIDS@Home News was also put up.

Apologies for lack of details about what is going on with FightAIDS@Home.

We are in the process of upgrading the AutoDock software to the latest version. I will let the researchers articulate the advantages that it brings to them to use this latest version.

We are currently testing it in beta testing. Unfortunately, we hit a snag in our first couple of rounds that caught us off guard and necessitated more work than expected to get a stable version.

We are almost there with the exception that the 64 bit graphics don't work properly. We are currently re-testing beta without the 64 bit graphics while we work on fixing the issue.

The challenge that we are working against is that SekeRob's wild guess is pretty close to the mark. The new batches sent to us from Scripps are formatted for the new version and we have to time the release of the new version with the new batches. This means that we will have a short outage when we get to that point when the old batches finish sending out there initial copies. That short outage will let us release the new version and then start sending out the new batches. Due to the new'ish 'homogeneous_app_version' feature, the resends of the old batches will continue to be sent using the old app version and the new batches will get the new app version.

However, due to our 'snag's' during the beta testing we were in a bind because we weren't sure we would have a stable version ready before we finished sending out the old batches. As a result, we have lowered the rate that we are sending work for FAAH until we can get a stable version through beta testing. Once that is done, we will return the project to full speed and finish sending out the 'old' batches.

Thanks for the update knreed.