There are no more tasks in the queue ready to send.

Hopefully this is just temporary.

Yes, there is new application with improved accuracy output so the current tasks has to be finished. New units are also shorter. There are many new tasks so I will split the batch to parts.

It looks like, that some fellow crunchers have misunderstood the situation and suspended their work for A@H.
Friends, please finish your WUs. As Kyong has written, the old tasks have to be finished before the new tasks will be send out.

Even my Bulldozer CPU needs "just" 40 hours for a WU. Even with switching between projects i can not believe that finishing a A@H Wu lasts over 5-7 days, so i'm speculating that some of you have suspended work for A@H.
If thats true, and if the project really has to wait for this old version WUs to be finished, we will get new work in the beginning of september (Deadline+Crunchingtime for resendet WUs).

So please, if i guessed right, finish your actual workunits.

Thanks Cyklodenis. New batch of workunits is already waiting. There are about 27000 new workunits so they will probably released in smaller groups.

After a quick look through the tasks that I have in the pending state (albeit: 'inconclusive')....

For the last computer sent for each of the tasks:
... The deadline date is in the range of Aug 21th - Aug 27th
... The 'time since sent' is not yet up to the 'average turnaround time'

Only about 350 have cleared in the last 7 days.
This may be a long wait.

Thats the point, friend.
Because of that i've posted the message above. I hope that everybody finishes his WUs as usual, but i'm afraid that some of us have suspended work (not only work fetch).

We are not many actually. Because of that i think everybody here should feel a little bit responsible for the further progress of the project.

In order to prevent this problem in the future I will try to fix the new workunits to the specific app version. If there are some changes in output it will be no problem to replace application for new workunits.
The other reason is due to 64bit version of the app. It is almost ready but problem is that 64bit version produces another number at the last decimal position than 32bit version. So there may be again output change in the apps.

Is it possible to send every WU 2 or 3 times?
So you will get at least 1 WU back in time.

Kyong, I think there are few computers running now, with multiple tasks in cache. Can you abort all the distributed tasks that have not started yet, and resubmit them to other computers, so we can finish them faster?

Nice idea, i am on standby.

I will try, going to look at it.

Yes, that would be the best way to handle it. Or I can do them <joking>. Since POGS ran out of work this morning I have 80 CPU threads looking for work. Hahaha
Best of luck on the new project.

---

Please limit resends to only one per computer, otherwise we will never finish this batch. See this computer, that got 12 resends a few days ago...

In reviewing the numbers, it seems that there are 55 WU still out, and there have been just 4 users report in the last 24 hours.

This probably means that there are just a very few users that have WUs on their machines.

In particular (and I am not in any way trying to target anyone), I found two machines have 8 and 9 still out; and these machines have 5 days and 13 days of average turn around time, respectively; and with deadlines of Sept 5th - 12th.
That is one-third of the total.

If the machines with a number of WUs can redistributed those that they won't get to in a timely manner (a day or two), then aborting them would help us all to finish the current series.

Unfortunately, part of the problem is the number of 'inconclusive' results for each WU, myself having only two thirds finish was valid. This has meant that there has been a large quantity of re-processing done. Some of the WUs that I have run were in their 6/7/8 iteration. It follows that even if the currently captured WUs are redistributed, there is no guarantee that the WU's next host will be able to produce a valid result and clear it from the queue.


So, this will go on for a while longer.

Here is hoping for a successful conclusion to this situation.
But there may come a time where intervention may be necessary.


----
I apologize in advance if I offended anyone.

Down to 3 users and 19 tasks.
We can wait or you can kill the tasks, shorten the deadline and re-issue them for us to complete pronto.

Now down to 2 and 19.

Now down to 1 and 17.
There's nowhere to hide. :P
I hope they are crunching them.

That stat on the server page is informative.
I have 1 re-send which is at 55% at 16 hrs, but no other tasks from this project.
So that means I must be the 1 user in the last 24 hours.
But I account for only 1 of the 17 tasks in progress.

So who has the other 16?

Perhaps they may have detached the project and that's why their client has not contacted the server in the last 24hrs? (or maybe a laptop that is turned off?)

at 2 and 15
I still have 1 in progress.

Finished mine but it looks like it just went right on out again
http://asteroidsathome.net/boinc/workunit.php?wuid=8172
multiple error and inconclusive results.
If there are a few WUs like this, it would explain why they are taking so long to finish.