...
I'm bemused by the October 1 reply deadline, by the way.
...
It makes me wonder whether the variable deadline function has not been calibrated for Multibeam to anywhere close to the previous work.

...
These 0.405 angle range WUs are estimated quite long. The curve for the 0.226 through 1.127 angle ranges where Gaussian searches are performed is much steeper than needed. Near 1.127 the estimates are far less generous.

                                                               Joe

Well it is done now with a little under 6500 seconds processing time on a Core 2 running at 3 GHz:
my first finished multibeam result
sterr_out says:
WU true angle range is : 0.004766

I vaguely recall some oddities down very near zero, but the mismatch between estimate (as reflected in the deadline) and reality seems very large here.

---

Howdy,

If that --> 03mr07aa.15818.24612.4.4.97 is a MB WU then i finished one too.

CPU time 9761.125

Optimized SETI@Home Enhanced application
Optimizers: Ben Herndon, Josef Segur, Alex Kan, Simon Zadra
   Version: Windows SSE3 64-bit based on S@H V5.15  'Noo? No - Ni!'
  Revision: R-2.4|xP|FFT:IPP_SSE3|Ben-Joe
     CPUID:               Intel(R) Pentium(R) D CPU 3.00GHz 
     Speed: 2 x 3436 MHz 
     Cache: L1=64K L2=2048K
  Features: MMX SSE SSE2 SSE3 x86_64 
 
Work Unit Info
True angle range:  0.405744

Spikes Pulses Triplets Gaussians Flops
   1      0       0        0     16411746821007

Quite a "monster" while looking at cpu time.

---

Join BOINC United now!

... Revision: R-2.4|xP|FFT:IPP_SSE3|Ben-Joe ...

????

---

"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.

... Revision: R-2.4|xP|FFT:IPP_SSE3|Ben-Joe ...

????

???? -> MultiBeam Chicken app.

---

Join BOINC United now!

Well it is done now with a little under 6500 seconds processing time on a Core 2 running at 3 GHz:
my first finished multibeam result
sterr_out says:
WU true angle range is : 0.004766

I vaguely recall some oddities down very near zero, but the mismatch between estimate (as reflected in the deadline) and reality seems very large here.

Arrrggghhh, I seem to have posted a link to the wrong result. My actual AR was .405690. Worse, the allowed edit time is past, so I can't fix my original post. Sorry.

the actual multibeam, this time

---

Any word on when Chicken App 2.4 will be up for general release?

---

Any word on when Chicken App 2.4 will be up for general release?

Later today. Probably close towards 12 pm MET. (that's CET +1h)

[EDIT]

And i urge everyone that is using 2.2b to upgrade ASAP, when the download of "MB chicken 2.4" is available for public.

Otherwise you might get no credit and/or run into compatibility issues.

---

Join BOINC United now!

Any word on when Chicken App 2.4 will be up for general release?

Later today. Probably close towards 12 pm MET. (that's CET +1h)

[EDIT]

And i urge everyone that is using 2.2b to upgrade ASAP, when the download of "MB chicken 2.4" is available for public.

Otherwise you might get no credit and/or run into compatibility issues.

Listened...

I donwload the 2.2B last week, and the success was spectacular...!

I will stand by to upgrade to the 2.4 MB version.

Good work, folks!!!

---

Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

What is the upgrade process for those going from 2.2B to to 2.4?

---

What is the upgrade process for those going from 2.2B to to 2.4?

You got 2 options.

First, let you cache run dry and drop the new app and app_info.xml like you did the first time. (SAFE method)

Second, stop boinc rename the new MB app matching the "old" 2.2 app name and replace the old one with the newly renamed one. restart boinc (UNSAFE method)

HTH

---

Join BOINC United now!

What is the upgrade process for those going from 2.2B to to 2.4?

You got 2 options.

First, let you cache run dry and drop the new app and app_info.xml like you did the first time. (SAFE method)

Second, stop boinc rename the new MB app matching the "old" 2.2 app name and replace the old one with the newly renamed one. restart boinc (UNSAFE method)

HTH

Ok, am I correct that 'The New & Improved Hot & Tastey Chicken Soup' is targeted for release today?

Also, by 'droping the new app and app_info.xml' file in the directory, do I need to take the old 2.2B's out or will the 2.4 take care of that? [If memory serves me correctly, there were 3 files with 2.2B to install]

If so, I guess I should set my 'puters to no new downloads so I can clear out backlog.

---

Ok, am I correct that 'The New & Improved Hot & Tastey Chicken Soup' is targeted for release today?

Early christmas... new apps are beeing released now....

---

Join BOINC United now!

Early christmas... new apps are beeing released now....

Humm... the ap_info.xml included in the distribution zip for the 32-bit Windows Core2 SSE3 variant of 2.4 mentions versions 512, 513, 514, 515, and 517.

It does not, however, mention version 527, the currently distributed one.

Possibly not the intended outcome?

---

Early christmas... new apps are beeing released now....

I downloaded the new app for core2 and took a look in the new app_info.xml file. It contains entries for <version_num> from 512 to 517.

Ehh... Shouldn't there be an entry for 527 as well??

This is the contents of the file in question:

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>KWSN_2.4_SSE3-Core2_MB.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>512</version_num>
<file_ref>
<file_name>KWSN_2.4_SSE3-Core2_MB.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>513</version_num>
<file_ref>
<file_name>KWSN_2.4_SSE3-Core2_MB.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>514</version_num>
<file_ref>
<file_name>KWSN_2.4_SSE3-Core2_MB.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>515</version_num>
<file_ref>
<file_name>KWSN_2.4_SSE3-Core2_MB.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>517</version_num>
<file_ref>
<file_name>KWSN_2.4_SSE3-Core2_MB.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

---

Early christmas... new apps are beeing released now....

Humm... the ap_info.xml included in the distribution zip for the 32-bit Windows Core2 SSE3 variant of 2.4 mentions versions 512, 513, 514, 515, and 517.

It does not, however, mention version 527, the currently distributed one.

Possibly not the intended outcome?

That's not an issue. More important is that the apps are now compatible with MB and that's not a matter of version numbers.

Of course, you can change it to 527 but it won't affect crunching at all.


HTH

---

Join BOINC United now!

Few I thought I was going to be the only one whose machine returned to 517. As long as it's not going to effect the results.

That's not an issue. More important is that the apps are now compatible with MB and that's not a matter of version numbers.

Of course, you can change it to 527 but it won't affect crunching at all.

Well one diference is that if one follows the install instructions provided with the distribution, upon restarting boincmgr, one's current queue of results is discarded with "no ap version for result:windows_intelx86 527" errors.

On my second such host, I first edited the provided ap_info.xml to delete the antiqie version entries, and provide a 527 entry. On that host one in-process result resumed, and a queued never yet started result started up instead of being discarded.

Assuming the versions are compatible for in-process results, this seems preferable (though not so risk-free as your "safe" suggestion), and might by its ease and low loss of work help encourage a swift switch.

---

Any word on when Chicken App 2.4 will be up for general release?

Later today. Probably close towards 12 pm MET. (that's CET +1h)

[EDIT]

And i urge everyone that is using 2.2b to upgrade ASAP, when the download of "MB chicken 2.4" is available for public.

Otherwise you might get no credit and/or run into compatibility issues.

As always Crunch3r, thanks for the good information.

One question tho'. . . I seem to be getting a mixture of old and new (MB) wu's. Can I assume that the new 2.4 chicken app will run the older ones and still return valid science?
Best Regards,
Gus

Can I assume that the new 2.4 chicken app will run the older ones and still return valid science?
Best Regards,
Gus

Yes, the new 2.4 apps can handle "older" WUs as well as Multi Beam Wus. No need to worry, it's all valid sience.

HTH

---

Join BOINC United now!

Thanks for the hard work guys, go spread your wings and fly from the Coup, you deserve it!