17/05/2006 5:56:13 PM|SETI@home|Unparsed line in app_info.xml:

Yes - what everyone said about removing the whitespace. Unfortunately, for whatever reason, this messaging system doesn't support the UBB standard CODE directive - so only PRE was available. Using "reply" as mentioned works well.

Darkstar's app_info.xml is already almost out of date. One of my machines has downloaded several enhanced 5.19 tasks. Shouldn't be tooo difficult to modify, though.

That was the real point in posting it formatted with the many versions shown - once someone sees the flow, it's reasonably easy to replicate.

The latest released version is 5.15, this hopefully fixes a Win9x timer bug.

5.13 and 5.14 were only released in Beta.

True for the clients - however, some of the work units did actually escape into the wild (true at least for 5.13's). I may be mistaken, but I believe that only the application versions have been changing recently, with the work units actually the same. I do what I can with the information at hand - if only certain versions of work units are intended to be processed on the non-beta side of the house, it would be useful if that information were easily accessible (without need of slogging through the beta forums, etc.).

True for the clients - however, some of the work units did actually escape into the wild (true at least for 5.13's). I may be mistaken, but I believe that only the application versions have been changing recently, with the work units actually the same. I do what I can with the information at hand - if only certain versions of work units are intended to be processed on the non-beta side of the house, it would be useful if that information were easily accessible (without need of slogging through the beta forums, etc.).

There are no 5.13 work units, there are only setiathome_enhanced work units. The _apparent_ requirement for some specific version above 5.12 is a flaw in the BOINC core client which picks up the Beta version of setiathome_enhanced when this main project sends work units to a host using an app_info.xml.

                                               Joe

I tried the Crunch3r SSE2 and SSE3 versions on a Linux FC4 box with P4 3.0E SSE3 and it just dies. Exits error code 2 according to boinc manager. Old version of BOINC mind you (4.32) but I would not thought that would cause the client to drop like that. Anyone else know of this problem.

---

I tried the Crunch3r SSE2 and SSE3 versions on a Linux FC4 box with P4 3.0E SSE3 and it just dies. Exits error code 2 according to boinc manager. Old version of BOINC mind you (4.32) but I would not thought that would cause the client to drop like that. Anyone else know of this problem.

Hi. Did crunch3r's app write anything uselful to stderr.txt before it died?

Regards Hans

---

Hans hi.
No sorry nothing available. Wish there was. Just the exit error 2 message to show for it.
Regards
Ian

---

Hans hi.
No sorry nothing available. Wish there was. Just the exit error 2 message to show for it.
Regards
Ian

Have you had a look at the reade files included in the archive ?

Most likely it's a library dependency issue...

P.S.

It would help much if you could unhide your computers ;)

---

Join BOINC United now!

Hello =)

I just installed this new Enhanced app.. finally.. i was waiting about 3-4 days without work wondering why i'm not getting this new Enhanced app... and it turned out that i had modified app_info :P so today...

installed boinc 5.4.9 and cruncher's SSE3 app =) everything works ok! =)
my time will be about 2:40 so not that bad i guess... =] GW Crunch3r =)

---

Hi all,

I want to thank crunch3r again for the work he did. Previously with the non enhanced version of seti i also used his appl and got upto 2000 credits a day.

I changed to the enhanced verion now of crunch3r but unfortunately everything dropped like hell. I obtain less then 600 credits now.

computation times are upto 50000 seconds. Credits arround 60 to 80 per wu.
The boinc client I use is 5.3.12.tx36, but this should not interfere with the computation time which is my main concern.

I'm running seti on 4 linux machines.
2 Athlon XP, 1 P4 and one Celeron.

The only thing i did was dropping the content of the archives in the project directory and adjusting the app_info.xml file.
Did I overlook something?

---

"Several billion trillion tons of superhot
exploding hydrogen nuclei rose slowly above
the horizon and managed to look small, cold
and slightly damp."

Sorry, never mind...

Hi all,

I want to thank crunch3r again for the work he did. Previously with the non enhanced version of seti i also used his appl and got upto 2000 credits a day.

I changed to the enhanced verion now of crunch3r but unfortunately everything dropped like hell. I obtain less then 600 credits now.

computation times are upto 50000 seconds. Credits arround 60 to 80 per wu.
The boinc client I use is 5.3.12.tx36, but this should not interfere with the computation time which is my main concern.

I'm running seti on 4 linux machines.
2 Athlon XP, 1 P4 and one Celeron.

The only thing i did was dropping the content of the archives in the project directory and adjusting the app_info.xml file.
Did I overlook something?

First, the difference you see in crunch times is normal for seti enhanced. Since the new applications do a much more detailed search through the data it takes a lot longer for you to crunch a work unit. You will also see a much greater variation in crunch times. Some wu's will crunch in almost the same times as a standard wu. while others can take much, much longer. This is due to the "angle range" of the work unit. The credits you will get crunching the new wu's are given now according to the amount of processing actually done to the wu so the "short" or high angle range work units will give less credits while the "long" or average to low angle range work units will give more credits due to the larger amount of processing that these work units receive. So no, you seem to have done everything right, the differences you see are just in the way the new application crunches wu's.

/edit/ BTW, your crunch times with Crunch3r's optimized application will help your crunch times, but you won't notice as much difference as you did with optimized applications under standard seti. This is due to the fact that the standard seti application wasn't optimized. The new enhanced application has already been highly optimized, thanks to contributions from Crunch3r, TMR, Joe Segur, and others too numerous to mention. The only "optimizations" that a specific optimized application has is that they make use of certain instruction sets available in various processors, such as mmx, sse, sse2, sse3, etc. So the differences between the stock application and the optimized app will not be nearly as much as it was in standard seti.

---

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.

Athlon64 3.200+ not overclocked

Seti Enhanced WUs about 3:30

with the BOINC Client 5.5...

http://calbe.dw70.de/boincw.html

for Info

22.05.2006 19:45:01||Running CPU benchmarks
22.05.2006 19:46:00||Benchmark results:
22.05.2006 19:46:00|| Number of CPUs: 1
22.05.2006 19:46:00|| 3028 floating point MIPS (Whetstone) per CPU
22.05.2006 19:46:00|| 11394 integer MIPS (Dhrystone) per CPU
22.05.2006 19:46:00||Finished CPU benchmarks

... :)

btw thanks Crunch3r fore the good Work.

Greetings from Germany NRW
Ulli

Hi Crunch3r,

After many attemps and alot of WU's aborted which I'm very sorry about, I'm pleeding for like yourself to direct me to the correct Optimizing files using your Crunch3r APP's?? I'm currently crunching 5.15 WU's using Enhanced...
Any help here would be very greatful...PLEASE!!

Can people view my comp to get an idea?

Thanks Stargate

---

why am I getting computation errors? I upgraded to 5.4.9 enhanced. used crunch3r's 5.5 opt client in the boinc folder and put his 5.12 opt app in the seti folder then changed the .xml What did I do wrong?

---

why am I getting computation errors? I upgraded to 5.4.9 enhanced. used crunch3r's 5.5 opt client in the boinc folder and put his 5.12 opt app in the seti folder then changed the .xml What did I do wrong?

Checking your computers it looks like it still can't find the correct application. Check your app_info.xml file and make sure both lines where it says the filename to use is exactly the filename you have installed.

---

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.

Hi Crunch3r,

After many attemps and alot of WU's aborted which I'm very sorry about, I'm pleeding for like yourself to direct me to the correct Optimizing files using your Crunch3r APP's?? I'm currently crunching 5.15 WU's using Enhanced...
Any help here would be very greatful...PLEASE!!

Can people view my comp to get an idea?

Thanks Stargate

Skippy, this is for you too.

You are still getting the "can't find app" errors. Make sure both places in the app_info.xml file has the exact filename of the application you have downloaded. now copy them to another directory temporarily for safekeeping. Since you have now started crunching with 5.15 you will have to set the project to "no new tasks" or "no new work" and crunch your cache down. Then shut down the boinc manager and the boinc client. Now copy your application and the app_info.xml files back into your seti project directory. Now set the project to start receiving work and let it download one wu. Set it for "no new work/tasks" again and see if it crunches that wu correctly. If so, set it to allow new work and turn it loose. If not, you have just lost one wu which is nothing to cry over. Recheck everything and try again.

---

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.

I have one crunching now. It preempted 2 wu's on the way to the one its running now. Like it looked for the fastest wu first. hmmm. Its been crunching for 21 minutes now. Thanks for your help!

---

Hi Jim,

Regarding the previous post you made answering my question.

I must say that i do not trust it anymore.

A lot of people are saying they are crunching in 3 hours or so. Mine are getting close to 15 hours. With the previous seti it took me less then an hour for one. I do not trust a crunchtime of more then 10 hours.

Also I hardly receive any credits. It is these days dropping to below 300 credits a day. I am comming from 1800.

---

"Several billion trillion tons of superhot
exploding hydrogen nuclei rose slowly above
the horizon and managed to look small, cold
and slightly damp."

Hi Jim,

Regarding the previous post you made answering my question.

I must say that i do not trust it anymore.

A lot of people are saying they are crunching in 3 hours or so. Mine are getting close to 15 hours. With the previous seti it took me less then an hour for one. I do not trust a crunchtime of more then 10 hours.

Also I hardly receive any credits. It is these days dropping to below 300 credits a day. I am comming from 1800.

Hi Klaas,
I'm not familiar with your computer's memory and cache, but it has been found that the l1 cache on the computer affects your crunch times more than any other single factor. However if you are looking at the "estimated time remaining" when running a wu, these times will be way off for the new wu's. From the wu's I've seen that you have reported I haven't seen any that were over approximately 6 1/2 hours. As a reference, I have a p3 500mhz that crunches in anywhere from 20 something to over 60 hours per wu. When I first start a wu, the "estimated time remaining" can be well over 120 hours for the lower AR work units.
Yes, everybody that has been running optimized clients and applications is seeing a drop in credits. This is due to the fact that the new enhanced application coounts credits in a different way (fpops instead of benchmarks) that specialized clients such as trux's calibrating client has no control over. Instead the credits are granted at a rate that is meant to be the same as granted in all other projects. In other words if your computers can earn 300 cr/day on Seti, then they can earn 300/day on Einstein or Climate Preditction, or any other project running boinc. In the near future other projects are going to be releasing applications thatt count credits in the same way as ours, and that will level the playing field not only across this project, but across all projects that use the fpops counting method.

---

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.

After a few days of running Crunch3r's 5.12 app on my Linux Ubuntu 5.10 box (Athlon64 3000+ Venice, SSE3), and crunching a few workunits with the same angle range with both the SSE3 and later the SSE2 app, I found that on average a 0.5459 AR workunit needs some 17200 seconds with the SSE3 app, and only 15900 with the SSE2 app.

I think it is worth experimenting with. :)

Greetings,
Sander

---

After a few days of running Crunch3r's 5.12 app on my Linux Ubuntu 5.10 box (Athlon64 3000+ Venice, SSE3), and crunching a few workunits with the same angle range with both the SSE3 and later the SSE2 app, I found that on average a 0.5459 AR workunit needs some 17200 seconds with the SSE3 app, and only 15900 with the SSE2 app.

I think it is worth experimenting with. :)

Greetings,
Sander

Hi Sander,

this is quite interesting Maybe i should make the Quick reference wu available for download, so that you or others who like to test the app. can get quickly a result for different optimized applications.

Just let me know ;)

---

Join BOINC United now!