Read the threads on here you will see that the BOINC server software is going to be updated before any more work is released. With a bit of lot, not too long after that.

Does anyone have any idea when the upgrade will take place? This week? Next week? Before the Sun turns into a red giant and swallows that Earth?

There is a risk here that if the work drought goes on long enough, so many people may drift away to other projects, that when the researchers do provide more work there won�t be enough computers available to get it run in a timely fashion.

---

There were just under 37,000 computers attached a few weeks ago. Now there are just under 17,000 computers. Still a bit more than the number of models usually released in the big batches.

My guess is that it'll be OK by Christmas. Just as there was a saying in 1914 in the UK, that the war in Europe would be over by Christmas. And they were right; it was over by Christmas, 1918.

---

Backups: Here

Number of tasks in progress is going up! I presume that means some tasks have been released, even if they do go too quickly to see them as available.

If they are releasing tasks (presumably reissues of old failed WU�s ) I haven�t been getting any of them. My computers run 24/7 and allow new tasks is set. Nothing is suspended so I don�t see why I don�t catch at least one of those new/old tasks.

---

Don't know how many were in the batch I was referring to then but number of tasks in progress has gone up by over 4,000 between when I looked at it yesterday and today.

Let's see - 17,000 computers, 4,000 data sets.
Carry the first number you don't think of, multiply by the temperature.

Ahhh. I think that the problem is that there are more computers than models. But I could be wrong.

Has any one heard of a word spelt patience?
Or ultra-marathon running? That should give one something to do while one waits for work.

---

Backups: Here

Finding the i5 laptop was struggling to cope with just two or three CM3's, the problem was identified as a failing hard drive, which was replaced yesterday.

With the limited number of cpdn tasks I had decided that the 4 cores would be back-filled with LHC Sixtrack science tasks. So today I turn on the revived laptop - there was just enough time to attach to LHC before boinc picked up another CM3 task from cpdn to fill the fourth core. It's now got a full complement of four CM3s fighting in boinc for air-time from 16 Sixtrack tasks.

I can only surmise that the virtue of 'Patience' was mis-heard by the laptop, XP and boinc manager. They applied 'Pertinaceous' instead.

---

Patience is the watchword here however. I could let my dual core atom try for some cm3 tasks but given the time it takes to complete regional models I suspect I am better off leaving things as they are! The I3 machine has with the times it is switched off taken into account still got a couple of days to go before it is out of CPDN work. If it runs out it will get attached to WCG like the atom.

The atom does like it's new SSD hard disk though.

I now have a cm3 running in high priority. When some regional tasks come along, my atom netbook will be back in action for CPDN. In the meantime it is taking the best part of 24 hours for each task it runs. It now has a screenful ofWCG tasks to get rid of.

It looks like the only work for now, (and for some time), are the RAPID models.

And it occurs to me that it's not possible to be attached to this project 24/7 as with other projects.
If it takes one minute to contact the scheduler and get a reply, then for another hour and a few minutes, the computer will just sit there waiting for the timer to expire. So computers after work and not getting any, are only connected about 23 minutes each day.

---

Backups: Here

Good point, well expressed, Les.


A few of my machines managed to snag a task from this last batch. Lucky. (Of course, that will displace some WCG work for the MIT Clean Energy project but, no biggie, these boxes were built to support CPDN, not fill-in projects.)

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

Wonder of wonders, I managed to snag 3 of the Rapid WU�s. Unfortunately, 2 of them when to my slower machine were they will take about 170 hours longer to crunch. Such is life.

---

Glad to hear that you got some Jim.

---

Backups: Here

The home XP file server is the same 'Pertinaceous' self as the XP laptop - acquiring four CM3s that are fighting for air-time from the LHC Sixtrack cohort.

The home Linux server has been recommissioned for SWMBO and her applications. It'll be off-cpdn for the foreseeable future. The office will have to be kept warm by the eight remaining cpu cores running cpdn.

---

Me somehow caught several Rapid-Rapit things --
will keep my boxes busy for many days.
Hope the server software upgrade goes well.
Take care all - and keep on crunching.

Thx

E

---

Interestingly, my dual core atom netbook won't download Rapit models as boinc won't let it anyway.

Tasks won't finish in time: BOINC runs 73.1% of the time; computation is enabled 100% of that

So No attempting records for the longest period of cpu in action on a model there then and that machine will just have to be patient and wait for more regional models. Still plenty of WCG crunching to keep it happy.

The Rapit models do have a short deadline of only 3 months, unlike the Regional models were the deadlines in nearly a year.

I had four tasks running on my four cores, until they all crashed... Bye bye CPDN.

Task ID Werkeenheid ID
15462521 8409130
15454013 8402208
15453805 8406283
15453417 8406273

On the two iMacs I had, every single workunit crashed upon reboot. And now after waiting for so long I had new work for my Win7 laptop and it crashed too.
There are other, less frustrating projects available on BOINC.

Have you looked at the various threads on this subject?
Antivrus programs can put an exclusive lock on files making them unavail able to BOINC when it wants to write to them. This can cause them to crash. Also it is recommended that you suspend the models and use the file > exit dialogue before shutting down. Also suspend the models if you are going to do any processor intensive work with the computer. Some have even suggested it is best not to run this type of model except on computers that are running 24/7. Unless you are able to carry out some or all of these measures the rapit models are going to be very prone to crashes. Also exclude your BOINC data directory from any antivirus scans

Dave