I have affialiated with
Einstein@Home
climateprediction.net
LHC@home
SETI@home
BBC Climate Change
SZTAKI Desktop Grid

this is on a Pentium 4 running Windows XP Pro. I had been accumulating work units and transmitting them to the clients without problems prior to attempting to setup with BBC Climate Change. I accidentally installed the BOINC Manager for the BBC experiment and eliminated the original Manager. I was advised to then remove that BOINC Manager and reinstall a new BOINC manager from the BOINC site. I did so and found my projects again listed. All seemed to be well but climate prediction.net has been running without rotation to another client for about 1 month now. I show only workunits for climateprediction.net and BBC Climate Change experiment. I am unable to download work units from Einstein, LHC, SETI, or SZTAKI. Constant updating nets no results. Below is an excerpt from the Messages section of BOINC Manager.

3/15/2006 9:36:32 AM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
3/15/2006 9:36:32 AM|Einstein@Home|Reason: Requested by user
3/15/2006 9:36:32 AM|Einstein@Home|Note: not requesting new work or reporting results
3/15/2006 9:36:37 AM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
3/15/2006 9:36:45 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
3/15/2006 9:36:45 AM|SETI@home|Reason: Requested by user
3/15/2006 9:36:45 AM|SETI@home|Note: not requesting new work or reporting results
3/15/2006 9:36:47 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
3/15/2006 9:36:53 AM|SZTAKI Desktop Grid|Sending scheduler request to http://szdg.lpds.sztaki.hu/szdg/cgi-bin/scheduler
3/15/2006 9:36:53 AM|SZTAKI Desktop Grid|Reason: Requested by user
3/15/2006 9:36:53 AM|SZTAKI Desktop Grid|Note: not requesting new work or reporting results
3/15/2006 9:36:57 AM|SZTAKI Desktop Grid|Scheduler request to http://szdg.lpds.sztaki.hu/szdg/cgi-bin/scheduler succeeded
3/15/2006 11:37:41 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
3/15/2006 11:37:41 PM|climateprediction.net|Reason: To send trickle-up message
3/15/2006 11:37:41 PM|climateprediction.net|Note: not requesting new work or reporting results

As I have no knowledge of this software (and not a great deal of knowledge in this area anyway)I am at a loss to get BOINC to function normally rotating to different client workunits. In short HELP!!!

Further I have a new HP Pavillion 8000 (AMD Turon x64processor)laptop running most of the same clients on BOINC with no problems. (I didn't make the same mistake with BBC on this one and affiliated correctly the first time)

Your assistance will be appreciated.
Thanks (I hope) in advance,

---

FAQ CPDN: HOw long will it take?

How long will it take?

This depends on how fast your machine is and how often you switch it off and also which Model you are running. The original Slab Model took a 1.4 GHz machine will take about 4 weeks if it is left running all the time. An 800MHz G4 Mac will take almost three months. A 2.8 GHz P4 or Mac G5 machine will take about 3 weeks. We recommend that you do not download the software if you only have your computer switched on for a couple of hours a week. The experiment will run when the screen is switched off.

The sulphur Cycle model was introduced on 26th August 2005. This is approximately 2.8 times longer.

A Transient Coupled Model is due to be launched shortly. This is estimated to take 6.6 times longer than the original slab model (2.3 times longer than the sulphur model). It should be more interesting as it is the first experiment that is meant to be realistic. Previous models have been more about finding out what the model does in response to some fairly extreme forcings.


How big are the Work Units?

Compared to SETI@Home 's Work Units, the Models are very big. Even on a fast Pentium 4 it can take around 3 weeks for a Slab Model, 8 weeks for a sulphur cycle model, and 20 weeks for a Transient Coupled Model.

You doing both a CPDN unit and a BBC unit will take up your computer for a long time. Why not do either, instead of both? Why not look at the FAQs on either site, instead of needing to ask afterwards? On both sites it'll tell you that these units take a long time, increasingly so if you do them with other projects!

I give you one link to check what I wrote in: the BOINC WIKI. Good luck.

---

Thanks for your response. I knew the work units were long but not THAT long. I've decided not run either Climate Prediction or BBC on the P4. Hate to drop the WU but I just got a HP laptop with a 64 bit processor and it looks like it's gonna handle those and the other prrojects ok. The P4 will do the others too. Thanks again.

---

I have a related question to the previous one. Which projects have the smallest downloads for WU? I am on dial up and a slow one at that. I am not in a position to leave the connection on for hours, which is what I am finding necessary for Rosetta.

Thank you to any who can help,

Dave

---

I have a related question to the previous one. Which projects have the smallest downloads for WU? I am on dial up and a slow one at that. I am not in a position to leave the connection on for hours, which is what I am finding necessary for Rosetta.

Thank you to any who can help,

Dave

Dave,

I would suggest Einstein@Home. E@H does involve a rather large (~7Mb) download, but once that is on your harddrive, it will be "sliced" into literally 100s of WUs, maybe 2 months of work, with ongoing upload/download only of tiny parameters/results in the interim. When that large datafile is exhausted of WUs, (in about 2 months, as I said) it will then need to fetch another of similar size.

Hope this fills your bill. L:-)

Respects,

Michael R.

---

"The arc of history is long, but it bends toward Justice"

I have a related question to the previous one. Which projects have the smallest downloads for WU? I am on dial up and a slow one at that. I am not in a position to leave the connection on for hours, which is what I am finding necessary for Rosetta.

There is a special feature in Rosetta, for people with dialup or slow links:

see FAQ adjustable Work Unit runtime parameter

Basically you can crunch multiple "models" on the same WU for much longer than the default 2hrs/WU. I personally set it to 8hr/WU, but slow-link users can use up to 4days/WU (i.e. 4 CPU-days). If you set it 8hrs/WU, your download traffic will be reduced to 1/4th of the current one.

PS: I think thr max WU-runtime nowadays is 12hr, since the project has reduced WU-TTL (time-to-live or maxtime) while they're debugging the 1% issue.

---

How-To: Join Distributed Computing projects that benefit humanity

I think thr max WU-runtime nowadays is 12hr,

The max is presently 24hrs until that bug is nailed. Each WU is 2-3MB, regardless of how long you chose to crunch it. The results are generally 300K or less.

So, you probably had seen the R@H default of 2hr WUs. But you can set the preference in the Rosetta preferences to up to 24hrs, thus using about a tenth of the bandwidth you may have observed.

Once the rare 1% bug is nailed, they'll up the limit to 4 days again. They're just trying to avoid anyone spinning for 4 days on a WU that's not getting anywhere. So, crunching for 4days per WU would cut network bandwidth by 75% AGAIN! But you'd still have the 3MB download when you do get a new WU. But if you're modem runs 56kb that should still be <15 min.

There's a nice chart in the wiki that might help you chose the projects that will work for you.

---