New Apps based on Code Revision 2.0 'Ni!' have been released

[Simon]

Hi folks,

read up at http://setiathome.berkeley.edu/forum_thread.php?id=31810&nowrap=true#457400 about the new release, please It's 4:41 AM and I'm too tired to type it again.

The post title says it all - check the Downloads section for the new apps!

[BenHer]

You da 'sleepy' man Simon. 

[Dirk Sadowski]

Hello, or sweet dreams now Simon!

Thanx for the new apps!

The apps are now faster, too?

Greetings!

[pepperammi]

Done a complete test/comparison run for the new Rev2 apps.
SSE, SSE2 Generic, SSE2 Intel and SSE3 Intel on my Pentium D 830 @ 3.2 Ghz. I've done them with the added -bench command if maybe there's any extra info for you. All working perfectly and looks like the adaptive optimisation I think you called it working perfectly too. All strongly similar

Fantastic work everybody

Only thing I notice is the stderr output is still saying "(R-1.3" In boinc. This could be just because it was started with the previous app though.

[EDIT] added cleared up times and stderr output

[Dirk Sadowski]

Hello!

I had crunched a WU 2/3 with Crunch3rs... then the rest 1/3 with Simons app.
I stopped the crunching one times... (because of the doubled entry in "stderr_txt"...)

Now I cannot see that Simon and the other good guys had made the app.
This is what the optimizers wanted or is this an error?
It was running an my AMD K7 Athlon 600Mhz.
(SaH_5.15_KWSN_MMX_Ben-Joe_2.0_A)

Greetings!


--------------------------------------------------------
Windows optimized S@H Enhanced application by Crunch3r
Version info: Windows MMX V5.12 by Crunch3r

Work Unit Info:
...............
WU true angle range is : 0.4265

ChirpData--[unrolled]: 29520293 (chosen)
  GetPeak--[hand_opt]: 3512 (chosen)
        f_sum--[unroll4]: 72519 (chosen)
GetChiSq--[hoisted+abs(]: 24435 (chosen)
Bench Time: 9.92 seconds
work_len=1048576
ChirpData--[unrolled]: 29284930 (chosen)
  GetPeak--[hand_opt]: 3107 (chosen)
        f_sum--[unroll4]: 72231 (chosen)
GetChiSq--[hoisted+abs(]: 24403 (chosen)
Bench Time: 9.94 seconds
work_len=1048576

Spikes Pulses Triplets Gaussians Flops
     0       0       0           0      16119038856279
--------------------------------------------------------

[BenHer]

Dirk,

The simon app does not display any "tag" information on WUs when it is started beyond about 1% of WU crunching. 

This way, when other projects, or shutting down the computer, and restarting cause the program to be loaded a 2nd or 3rd time for the same WU, it wont have a series of "Crunched by KWSN" or similar in the stderr.txt file.

Any new WU started by it will have the tag lines.

[rgathright]

I am seeing good results so far on my Xeon 5120.  Thanks!   

[Simon]

You da 'sleepy' man Simon. 

Yeah, good thing I could take half a day off today cause I definitely couldn't have survived on 3 hours sleep.

I did get some fellow KWSN members to test the apps I couldn't test myself (MMX+SSE only) yesterday, so I got the whole bunch uploaded and released after all. Ni!

Regards,
Simon.

[BenHer]

Rgathright - link to your computer info on seti please.

Also - 5120 is a Core duo DP xeon (woodcrest).  And during our testing we found that Simon's older 1.3 was faster than the new release on his woodcrest.

Please confirm.

[Simon]

Ben's correct,

the 1.3 and 1.41 Core 2 / SSSE3 apps are actually quicker (at least, they were in our testing) than the 2.0-based ones.

So we're of course interested how it's working out for you

Please post a host link to this computer to satisfy our curiosity.

Regards,
Simon.

[rgathright]

http://setiathome.berkeley.edu/show_host_detail.php?hostid=2722436

 I am getting some strange WU times...
2:28:28 67% for 09jn03aa.22751.29217.786080.3.203
2:27:53 63% for 09jn03aa.22751.29217.786080.3.198

I hope these are just really long WU's.

I used an old version of "kwsn-test" (7/5/2006) and saw a gain of 40 seconds on this computer vs the other results.

[Dirk Sadowski]

Hello!

After the installation of the new app...
I got now new work...

In the overview in Boinc I have now WUs for S@H V5.17...
(Before V5.15 with Crunch3rs V5.12)

In the "app_info.xml" of the new Simon- app: "5.12, 5.13, 5.14, 5.15 and 5.17"
I thought S@H V5.17 is now only for S@H- beta...

I let run now V5.17 WUs for main, but they are for beta?


Greetings! 


EDIT:
When it's an error...
The new app is ready to cruch S@H V5.17- main- WUs?

[Simon]

Hi Dirk,

I added 5.17 to the default app_info.xml files because otherwise people have lots of trouble when they run SETI Beta and normal SETI alongside. BOINC 5.4.x has a problem otherwise for them.

No matter what BOINC says, the app itself is based on 5.15 code, albeit heavily modified.

Also nochmal auf Deutsch - ist nur weil einige Leute ziemliche Probleme haben, die gleichzeitig SETI Beta und normales SETI crunchen. 5.4.x BOINC Versionen haben da jedenfalls ohne den 5.17er Eintrag grob 100e WUs mit Fehlern wieder rausgeworfen.

Egal was BOINC sagt, die App selber ist ne 5.15er, obwohl stark modifiziert.

HTH,
Simon.

[Dirk Sadowski]

Hello Simon,

thanx for reply!

And many thanx to you and your guys for the good work!


So if in main S@H V5.17 will come, your app cannot crunch them...?
Or, I cannot download new WUs from the server?

So, if I let run only main, then I can modify my app_info.xml?

Greetings!

[Simon]

The problem with modifying your app_info.xml when you have already downloaded WUs BOINC thinks are for 5.17 is that it will not find the entry and error them out.

So before you edit your file, please run your cache dry with "no new tasks" "keine neuen aufgaben zulassen".

When you have crunched all WUs, then shut down BOINC and edit/remove the entry. Then start it up and it will be fine.

HTH,
Simon.

Left to themselves, things tend to go from bad to worse.

- Murphy's Law