thankyou all for answering my questions i may have been crunching for 8 years but I am still totally ignorant of the techie side to the project when when it come to crunching work unit

so again thankyou for the simple answers makes thing so much clearer

and if this makes sense i have not had enough beer :)

This is a good place for questions, even dumb ones. Someone here will know the answer and help you. It may not be the answer you're looking for, but it will generally be truthful. If it isn't "dead-on" someone else will correct that user in minutes. LOL

fire away, ask all you want.

tony

PS, I'll have that beer for you.

thankyou all for answering my questions i may have been crunching for 8 years but I am still totally ignorant of the techie side to the project when when it come to crunching work unit

so again thankyou for the simple answers makes thing so much clearer

and if this makes sense i have not had enough beer :)

---

Sapiens dominabitur astris.
The wise shall exercise dominion over the stars.

Here's the result ID for the ONLY one on your results page that is client error -aborted:

Result ID 561478377
Name 29no99ab.14352.6880.965922.3.79_0
Workunit 137744611
Created 29 Jun 2007 13:05:42 UTC
Sent 29 Jun 2007 23:16:02 UTC
Received 30 Jun 2007 12:06:03 UTC
Server state Over
Outcome Client error
Client state Aborted
Exit status -221 (0xffffff23)
Computer ID 2663263
Report deadline 8 Jul 2007 11:47:02 UTC
CPU time 0
stderr out <core_client_version>5.10.7</core_client_version>


Validate state Invalid
Claimed credit 0
Granted credit 0
application version 5.17


Notice CPU time ZERO and the exit status -221?

That means it didn't run any time at all, or atleast didn't report any time. the -221 means the seti backend already has that wu in the master science database and doesn't need you to crunch it. Crunching it (spending time on it) would be a waste of your time and energy (money). It aborted it so you could move on to more scientifically useful work. All and all a good thing.

IMO they could find a better word then error though. LOL

The problem is my machine crunches them. Then when the are uploaded and i update it say's in my results client error work aborted

which means i am crunching work unit for no reason and wasting crunching time

---

Sapiens dominabitur astris.
The wise shall exercise dominion over the stars.

Why am now getting a lot of aborted work unit when they complete?

They are actually being aborted before they start because the server has already received 2 or more results to form a quorum and therefore it need not be crunched by your pc.

This sticky thread....Aborted By Project has more information about this.

---

Why am now getting a lot of aborted work unit when they complete?

---

Sapiens dominabitur astris.
The wise shall exercise dominion over the stars.

thankyou very much for your help I did try to use one the apps suggested further down in thread but followed the instruction but nothing happened well i think nothing happened

all Boinc is say's i am using SETI 5.15 enhanced this is bit confusing if as some said eraly i am not

and thanks for the non Techie answers

What BOINC says is determined by what you tell it in the app-info.xml file you installed when you installed the optimized application. What anyone else sees when they check an actual result crunched by your computer is shown in the result file. The app-info.xml file "must" call it seti enhanced because that is the only type of work units we have. The actual version number reported doesn't have to match as long as the system recognizes it as a valid version for this type work unit. You could build an application and name it anything you want but if it were listed in the app-info.xml file as for use as a seti enhanced 5.15 that is what BOINC will call it. And that is what it will ask for work units for. Right now we don't have a minimum version as long as it is listed as SETI enhanced, but sometime in the future we may limit it to a certain version or above. If for instance you are still reporting the 5.15 version but we come out with a new type work unit that version 5.30 is required to crunch, you would not get work until you upgraded to report that you were using an app capable of crunching the new 5.30 wus.
During the transition from standard SETI to SETI Enhanced, people would have to list two versions in their files. One for the earlier 4.xx version work units and another for the new 5.xx enhanced work units. They would also have to keep copies of both applications on their computer. If they got a 4.xx version work unit it would crunch it with the older application, but if they got a new enhanced application then it would be crunched by the 5.xx enhanced app.

Hope this explains a little of what you are seeing without rambling on too much!

---

Jim

Some people plan their life out and look back at the wealth they've had.
Others live life day by day and look back at the wealth of experiences and enjoyment they've had.

Yep, looking at one of your results:

<stderr_txt>
Optimized SETI@Home Enhanced application
Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
Version: Windows SSE2-generic 32-bit based on S@H V5.15 'Noo? No - Ni!'
Revision: 2.2B|xW|FFT:IPP_SSE2|Ben-Joe
CPUID: AMD Athlon 64 'Winchester'
CPUs: 1, cores: 1, threads: 1 cache: L1=64K, L2=512K, L3=0K
Features: MMX, 3DNow!, 3DNow!+, SSE, SSE2,
speed: 1802 MHz -- read MB/s: L1=9891, L2=5070, RAM=2719

Work Unit Info
True angle range: 0.909612

Spikes Pulses Triplets Gaussians Flops
3 0 3 4 7532992067517

</stderr_txt>

So it looks like your good to go!

---

thankyou very much for your help I did try to use one the apps suggested further down in thread but followed the instruction but nothing happened well i think nothing happened

all Boinc is say's i am using SETI 5.15 enhanced this is bit confusing if as some said eraly i am not

and thanks for the non Techie answers

LOL DUDE :D your latest results show over 50% reduction in processing time for the similar angle range results. ( i.e. they used to take over twice as long :D )
Congratulations!

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

thankyou very much for your help I did try to use one the apps suggested further down in thread but followed the instruction but nothing happened well i think nothing happened

all Boinc is say's i am using SETI 5.15 enhanced this is bit confusing if as some said eraly i am not

and thanks for the non Techie answers

---

Sapiens dominabitur astris.
The wise shall exercise dominion over the stars.

The angle range issue is explained in detail in the Enhanced FAQ.

---

if any one can explain this i would be grateful and no techie speak please

I'll try being non-techie....;-)

Credit is awarded based on the number of computations, also known as Floating Point Operations or FLOPS it takes to complete a given workunit. It doesn't matter how long it takes......what matters is the amount of effort that the processor had to put in to compute the result.

For example, if I ask you to perform a series of additions I can bet that you'll be able to perform them faster than a similar set of divisions on a given sample of data....

t could be done this way starting from any arbitrary number.

As an example consider if you had to perform a series of maths operations where the end result was the number 50.

10 plus 15 equals 25 plus 11 equals 36 plus 14 equals 50

I'm sure that it would be very easy to add these numbers together. However consider the following...

225 divided by 3 equals 75 divided by 6 equals 12.5 multiplied by 4 equals 50

I'm sure in this case the first division would take that much longer and so would the second operation...This is just an analogy, but I hope you understand what I mean.....

That said, different workunits have been recorded at different angle ranges by the Arecibo dish. Some angle ranges have easier computation than others....so it is often the case that the mid-range workunits take longer in time than the ones that give you 60 or more credits.

These variations in credit have been graphed before and it's been found that there is a sort of negative sweetspot in the orientation of the telescope when the signal was recorded.

I believe that these workunits that give lesser credit per hour because they take longer are generally fewer and occasionally we all have the bad luck to be assigned these.

But don't worry about, your pc is working fine and this situation is more or less normal.

---

Another thing to mention is, that you probably have received (and successfully crunched) some of the 58.7 killer WUs which show up every now and then. They take about 50 - 100% more time to crunch but only grants about 58.70 (in your case 58.69) Credits.

Fortunately they are not handed out very often... ;-)

HTH
Andy

I have upgraded to seti enhanced

if any one can explain this i would be grateful and no techie speak please

Hi Shadow:

You are using the standard Seti application. You may want to upgrade the application to the new optimized application by Chicken.

Franz

If you're not using faster cooking Chicken Soup you're running on slow cooking beef stew :)

---

@Shadow,
As Franz said try the optimised application for your cpu. The linked post, if you haven't found it is Post #519083.
There are options for with and without graphics. These apps are stable and validate with no problems and can be 50% faster.

Andy

I have upgraded to seti enhanced

if any one can explain this i would be grateful and no techie speak please

Hi Shadow:

You are using the standard Seti application. You may want to upgrade the application to the new optimized application by Chicken.

Franz

I have upgraded to seti enhanced

Because some work units were taking 9hrs to crunch but i was only getting credit for about 6 hrs crunching Also, under this version some work unit have been aborted by the software and to top it all just had a work unit crunch for 14hrs and only got credit for 6hrs or there abouts

As much as like BOINC I wish I got some consistency in credit when crunching. To crunch a work unit for 14hrs and only get credit for Approx 6hrs is a bit disheartening.

if any one can explain this i would be grateful and no techie speak please

I just looked at your last 5 results. On all received the credit that your computer claimed. Only one of them shows that your computer worked longer than the other computers who claimed the same amount of credit. Check out your own results and you can see that some of the other computers that worked on the same units actually worked nearly twice as long and in one case more than twice as long to get the same credit that you did. Remember that you get credit for the actual amount of processing your computer does. If you are using it for other things then it is not processing the work unit full time. For example, the time that I am spending responding to this post is using processing time that would otherwise be used to process work units.
Some one can probably give you a better explanation as to how the credit is computed, but you seem to be getting appropriate credit from what I could see.

---

I have upgraded to seti enhanced

Because some work units were taking 9hrs to crunch but i was only getting credit for about 6 hrs crunching Also, under this version some work unit have been aborted by the software and to top it all just had a work unit crunch for 14hrs and only got credit for 6hrs or there abouts

As much as like BOINC I wish I got some consistency in credit when crunching. To crunch a work unit for 14hrs and only get credit for Approx 6hrs is a bit disheartening.

if any one can explain this i would be grateful and no techie speak please

---

Sapiens dominabitur astris.
The wise shall exercise dominion over the stars.