There's never any real idea about when work will appear, it just does when those behind the scenes are ready to do so.

Now if only there were a way to take some tasks off my machine with work in the queue to ones with spare cpus. They could be transferred back before reporting to get around the problem with the project having them allocated to a particular machine id.

This wouldn't work with tasks from my machine with most in the queue unfortunately as it is running Linux and my others are using Windows version of BOINC under WINE.

Hopefully there will be some more WU’s released soon. My computers are getting short of work.

---

Mine too, one still has work in the hopper but the other two have three units between them for six cores, though I am better off than some as on the team I joined I have rocketed up to third in the work average stakes which means I am ahead of people with a lot more speed and cores than I have. I guess it just means that they ran out of work more quickly because of their faster processors.

I'm treating the lack of work as a good opportunity to clear out all the dead wood files in projects. I'm systematically Removing CPDN and then rejoining the project to create clean starts. Over the years of continuous running and with occasional fails, I know there is rubbish in there but I'm not certain which are the good files and which the bad.

Over the years of continuous running and with occasional fails, I know there is rubbish in there but I'm not certain which are the good files and which the bad

Hmm, perhaps I should do that too. All the cleaning out I normally do is looking for task folders left by crashed work units and deleting them manually.

And now there seems to be some work units pouring into the hopper.

Yes, I just snagged some. Hopefully this is the end of the work drought.

---

Not sure if the one I got from batch 468 is going to take 128 days though! Will check on it in an hour or two and work out how long it will really take!

Estimating somewhere between 20-25 days at the moment. Tomorrow will check again in case my arithmetic is faulty.

Estimated time to complete the hadam3p_eu 3 month tasks from batch 469 would seem to be somewhere in the neighborhood of 21 hours on my Win7 2.6 GHz machine with 8 Gb of RAM.

---

The eu ones look like they will take about 38 hours on my 2.1GHz laptop.

I notice all the tasks have fallen out of the big hole in the bottom of the hopper already.

Compute rate on my machine is about 0.5% per hour. Estimated size is 5,222,246 Gflops. These runs are for cafr region. See Ian's post in New Region thread.

About 21 hours on my Windows 10 PC with A10-6700 CPU which AMD says has four cores but the Windows Task Manager says it has 2 cores and 4 logical processors, so it runs only 2 BOINC tasks at the same time, plus a GPU task, either Einstein@home or SETI@home.Speedup of GPU tasks is impressive.
Tullio

---

I have a large bunch of completed work units waiting for validation some for months. They have a quorum of 1, and another work unit failed before it was assigned to me. I have not gotten new work units in about a month, though my client asks for them from time to time. 64-bit Linux machine with a 4-core processor and 8 GBytes of RAM.

Could the server be waiting to validate all these work units before sending me any more?

---

The BOINC validation process consists of comparing the results returned by two computers to see if they're the same.
This doesn't work with cpdn, because slight changes about the way different manufacturers code the floating point maths chips means that results from the same starting values will be slightly different for each result.
And there are other slight differences between what each compiler for different OSs generates.

The reason that none of us is getting work, is because there hasn't been much lately.
You can see the amount of work available on the Server Status page, linked from the front page of the project. (Top right hand corner.)

The BOINC validation process consists of comparing the results returned by two computers to see if they're the same.
This doesn't work with cpdn, because slight changes about the way different manufacturers code the floating point maths chips means that results from the same starting values will be slightly different for each result.
And there are other slight differences between what each compiler for different OSs generates.

I understand that. But why, then do I see:

Workunit 10556865
Jean-David Beyer · log out
name wah2_eu25_1e77_209612_13_401_010556865
application Weather At Home 2 (wah2)
created 12 May 2016, 18:45:19 UTC
minimum quorum 1
initial replication 1
max # of error/total/success tasks 3, 2, 1
validation Pending
Task
click for details Computer Sent Time reported
or deadline
explain Status Run time
(sec) CPU time
(sec) Credit Application
19793559 1256552 4 Jul 2016, 19:39:49 UTC 19 Jul 2016, 0:28:47 UTC Completed, waiting for validation 1,143,372.43 1,077,273.00 pending Weather At Home 2 (wah2) v8.12
i686-pc-linux-gnu
19643226 1242972 28 Jun 2016, 4:55:40 UTC 4 Jul 2016, 19:29:30 UTC Error while computing 0.00

if it requires a quorum of only 1? Mine is the Completed one.

---

"Validation" is a "BOINC" thing - it, like several other "Boinc" parts, just aren't used on this project. But they're built-in, so they have to appear somewhere.

All checking of results is done by the researchers, using various statistic methods.

The "quorum" size, along with the next 2 items, is for the part of the software that determines how many times the researchers want an individual task to get sent.

All checking of results is done by the researchers, using various statistic methods.

So the validation is done by humans (perhaps aided by machines). So they are way behind in validating my results. I am not paranoid enough to imagine I am the only one whose results are being (temporarily) ignored.

---

What's in the "Validation" column, and (also one of the credit columns), is put there by BOINC.
And there it stays. Forever.

IGNORE IT! IT'S JUST AN UNUSED BOINC VALUE.