I have a computer that was off line for a couple of weeks. Now that it is back up it is running jobs that are past deadline. There are 9 of them "Ready to start". each is about 90 mins long. Are these jobs "lost"? If so why do they still run? Should I take any action to keep them from running? If left they should all finish before midnight tonight, New Year's Eve.

Thanks

---

I have a computer that was off line for a couple of weeks. Now that it is back up it is running jobs that are past deadline. There are 9 of them "Ready to start". each is about 90 mins long. Are these jobs "lost"? If so why do they still run? Should I take any action to keep them from running? If left they should all finish before midnight tonight, New Year's Eve.

Thanks

How far are they past deadline? If they are too far past deadline, you might not recieve credit for them. If you feel it's not worth the risk of losing credit, go into the Tasks section an click "Abort" on the appropriate tasks that you believe you won't get credit for.
How long until your New Years? Because I know I'm already in 2009. :)

---

- Luke.

The work units are 2 and 3 days past deadline.
As of this writing my local time is 9:55 am 12/31/2008.

Happy New Year NZ

---

That´s right!!!
I guess you are the first SETI@home cruncher who is already in 2009!!!
Happy new year !!

---

The work units are 2 and 3 days past deadline.
As of this writing my local time is 9:55 am 12/31/2008.

Happy New Year NZ

I would go with an abort in this case. 3 days is a ample amount of time for a workunit to get re-issued and turned around...

Happy New Year Mark. (& Dirk ;)

---

- Luke.

The work units are 2 and 3 days past deadline.
As of this writing my local time is 9:55 am 12/31/2008.

Happy New Year NZ

I would go with an abort in this case. 3 days is a ample amount of time for a workunit to get re-issued and turned around...

Happy New Year Mark. (& Dirk ;)

I do not think I would abort them....

If I am not mistaken, if you report the work late, but the wingman they were reissued to has not reported yet and the WU closed out....I believe you will still get the credit....

I would just let them complete....

Mind you....my rigs do not have much experience in reporting work late...LOL.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

The work units are 2 and 3 days past deadline.
As of this writing my local time is 9:55 am 12/31/2008.

Happy New Year NZ

I would go with an abort in this case. 3 days is a ample amount of time for a workunit to get re-issued and turned around...

Happy New Year Mark. (& Dirk ;)

I do not think I would abort them....

If I am not mistaken, if you report the work late, but the wingman they were reissued to has not reported yet and the WU closed out....I believe you will still get the credit....

I would just let them complete....

Sure? He still could get credit but have a read of this: BOINC Wiki You May Not Get Credit. Consider Aborting it.

It could go either way, if we could kindly see the computer with the overdue Workunits?...

---

- Luke.

I am somewhat confused now. When I look at the computer itself with Seti Manager I see the Past Due work units. When I look at the computer through Seti it does not show the work units. http://setiathome.berkeley.edu/results.php?hostid=3820109
Does that mean that Seti has already dropped them from my computer?

---

I am somewhat confused now. When I look at the computer itself with Seti Manager I see the Past Due work units. When I look at the computer through Seti it does not show the work units. http://setiathome.berkeley.edu/results.php?hostid=3820109
Does that mean that Seti has already dropped them from my computer?

You have aborted them on the BOINC client... It takes a number of hours/days or so from it to vanish from the website pages and servers though. Due to such things as Server Validation, completion of the workunits by Wingmen, etc.

---

- Luke.

No they are still on the client, but not on the server website. I am thinking the best thing here is to abort on the client.

---

No they are still on the client, but not on the server website. I am thinking the best thing here is to abort on the client.

Oops... looks like I had it the wrong way round. I would, but some here would probably disagree.

---

- Luke.

Heck, they are short units and will be done before the day is over so rather than fuss I decided to let them be. Not a big deal in the big picture.

Thanks for the replies.

Happy New Year Everyone

---

instead of speculating please just take a look to see which if any WU's were completed by a 3rd party. Theres a good chance the New Wingman may get the WU completed first so you won't get anything for your efforts.

---

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

I have a computer that was off line for a couple of weeks. Now that it is back up it is running jobs that are past deadline. There are 9 of them "Ready to start". each is about 90 mins long. Are these jobs "lost"? If so why do they still run? Should I take any action to keep them from running? If left they should all finish before midnight tonight, New Year's Eve.

Thanks

If they are "ready to start" there is no down-side to aborting them. If you crunch fast enough you have a fair chance of getting credit, but a third cruncher has already been assigned, and that particular work unit will wait for them to crunch anyway.

---

my point is this. check the PD WU's on your page. Make sure that the 3rd wingman hasnt sent in the work already. If you crunch it and its already been done you lose.

---

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

my point is this. check the PD WU's on your page. Make sure that the 3rd wingman hasnt sent in the work already. If you crunch it and its already been done you lose.

Your point is completely valid.

Mine is that if the result has already been assigned to a third cruncher, and he hasn't even started crunching, he'll be able to get new work that isn't going to be crunched 3 times.

Once assigned, the third cruncher is going to get a fair time to finish, even if his result turns out to not be strictly needed.

---

umm if the 3rd person only has a 1 day or less cache setup their is a very high chance the work will already be done. I keep a large cache on hand. I have no Idea what the 3rd person has but I suggest looking at each WU before they start so you dont wind up wasting time. If they are reported then dump it.

---

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

umm if the 3rd person only has a 1 day or less cache setup their is a very high chance the work will already be done. I keep a large cache on hand. I have no Idea what the 3rd person has but I suggest looking at each WU before they start so you dont wind up wasting time. If they are reported then dump it.

If the work unit has been assigned, it is in one of three states on the third machine:

1) Not started, perhaps buried in a large cache.

2) Started/running

3) Done, waiting to be reported.

In all three cases, if you abort a work unit that you have not started, you have zero time invested, and you know that third result is pending out there someplace.

For all three cases, Mark has a chance of beating the assimilator. He says they're short, so he's got a good chance of getting credit (even "late" work will get credit most of the time).

It's just that there is no real upside: if he aborts the ones he hasn't started, he gets zero credit for zero compute time, and he'll get new work, with a near 100% chance of getting credit.

---