When I query my account from BOINC Mgr (6.6.20) Projects tab for SETI@home/Your Results, I see over 100 wu as "In Progress". My machines are both 8-core machines, and have about 30 or so wu in queue. And I process more than that every day. So there are about 30 or so listed as "In Progress" that I know nothing about, and am confused about why they are "In Progress". (They are the ones more than a day old).
How can I find out why they are there? And what can I do about them? They are obviously holding up credit for the other users that I am paired with on them.
Some of them may be due to a power outage I had a few days ago...
What info do you need from me to track them down?
Thanks,
Jon Ravin

---

These may be ghost WUs that are sent and not received by your machine, there is little that you can do and just have to wait until the dates are overdue when they will be sent out again.

---

Actually, it turned out to be my bad (with one exception) - or, as Roseanne Rosannadanna used to say, "Nevermind".

On May 31 and June 1 I switched my machines to the SSE3 64bit Optimized MB App (which increased my throughput by about 75%, by the way). At the time, I lost all of the WU I had in my queues. They just disappeared... (I hadn't realized that would happen). The WU from those 2 dates in my "In Progress" list are (I assume) those missing WU. There is also one dated May 21; maybe that's a "ghost".

Is there any way of returning the lost WU to my queues? Or at least marking them as available in the database, since they are not going to get finished until they are distributed to other users late this month, if left untouched?

---

The only way that I know of is to detach the host from SETI, then re-attach. You'll probably want to run your current cache down to nothing first - no point in causing a resend for work which you do have available to crunch.

I'm planning to do that this afternoon to release the ~150 tasks which the faulty BOINC v6.6.34 gobbled up - I'll let you know how I get on.

Thanks for the suggestion. Please let me know if it works!

---

I have just checked one of your pc's (4912909) and you have a total of 531 results (Details), 37 (In progress), 313 (Pending), 153 (Valid) and 7 (Error). As of 11:21 a.m. Eastern time.

The only work units you see under BOINC will be the work units that are either waiting to be processed and ones that have been processed but not reported.

The ones "In Process" are ones that you're pc has yet to do,"Pending" are the ones you have completed but your wing man has yet to do. "Valid" are the ones that have been verified by the SETI server.

The "Your Results" button in the BOINC Mgr (6.6.20) is showing all the results from all 3 of your pc's that are attached to SETI.

Hope this gives you a bit of clarification into things.

---

Thanks for the suggestion. Please let me know if it works!

Yes, it worked - you can see the results on host 3755243.

Notes:

1) If you use any optimised applications, BACK UP YOUR PROJECT FOLDER. It gets deleted when you detach. Best order is complete last task --> report completed tasks (using project update button) --> back up project directory --> detach --> restore project directory --> re-attach.

2) It's b****y difficult to get three CPU cores and a CUDA card to run out of work at the same time!

3) And it's best not to try to do it on a weekend when the servers are playing up particularly badly....

4) As you can see, I got my old Host ID back (no special action on my part). But you'll have to look for the 'client detached' results yourself (tasks issued 4 June and before), because none of the filters will find them.

5) Work estimates, cache size etc. will be screwy for a little while. The first CUDA task after the re-attach was a shorty: estimated over an hour, completed in 7m:30s as usual.

I have just checked one of your pc's (4912909) and you have a total of 531 results (Details), 37 (In progress), 313 (Pending), 153 (Valid) and 7 (Error). As of 11:21 a.m. Eastern time.

The only work units you see under BOINC will be the work units that are either waiting to be processed and ones that have been processed but not reported.

The ones "In Process" are ones that you're pc has yet to do,"Pending" are the ones you have completed but your wing man has yet to do. "Valid" are the ones that have been verified by the SETI server.

The "Your Results" button in the BOINC Mgr (6.6.20) is showing all the results from all 3 of your pc's that are attached to SETI.

Hope this gives you a bit of clarification into things.

Ray - thanks; I had already figured most of this out. There are some "In Progress" ones that are from 1 June and 31 May that are the ones I am having a problem with, and were the ones I originally asked about that were blown away by changing to the optimized app = apparently BOINC or SETI discards the in queue or not completed WUs when changing to the Opt. apps.
Jon

---

...
There are some "In Progress" ones that are from 1 June and 31 May that are the ones I am having a problem with, and were the ones I originally asked about that were blown away by changing to the optimized app = apparently BOINC or SETI discards the in queue or not completed WUs when changing to the Opt. apps.
Jon

It's a matter of matching the app version in the upgrade to the version chosen to do the work when it was downloaded. And an "app version" for BOINC 6.6.x actually includes 4 different criteria; the name, number, platform, and plan_class. Your transition was from stock 6.03 (which is a 32 bit application) to the 64 bit optimized version, there has been some uncertainty about how to handle the effective platform change.

For most users upgrading from stock to an optimized app there shouldn't be a loss of work, but not all transitions have been exhaustively tested. Each test would involve transitioning back to stock first and that's at least a nuisance.

                                                               Joe

I was working through my first AstroPulse assignment and about 4 hours from completion when I upgraded my hard drives and was unable to restore the image I'd created to the new drive. As a result I lost the AstroPulse work and several Multi-Beam tasks waiting to run and will not be able to return them. Will a failure to return the AstroPulse work unit by the deadline disqualify me from running them in the future because of a perceived inability to process the data in a timely manner? It appeared that one core in my X4 processor could crunch a work unit in about 48 CPU hours so once the pipeline was filled I could probably return about one or so complete units each day.

---

Will a failure to return the AstroPulse work unit by the deadline disqualify me from running them in the future because of a perceived inability to process the data in a timely manner?

No.

---

I was working through my first AstroPulse assignment and about 4 hours from completion when I upgraded my hard drives and was unable to restore the image I'd created to the new drive. As a result I lost the AstroPulse work and several Multi-Beam tasks waiting to run and will not be able to return them. Will a failure to return the AstroPulse work unit by the deadline disqualify me from running them in the future because of a perceived inability to process the data in a timely manner? It appeared that one core in my X4 processor could crunch a work unit in about 48 CPU hours so once the pipeline was filled I could probably return about one or so complete units each day.

You have the phenom 9500. If you use the optimized app for SSE3 astropulse you'll be finishing AP WU's in about 24-27 hours

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope