Forum > Discussion Forum
Multibeam has arrived - please upgrade!
Simon:
Hi Folks,
over at the main SETI@Home project, Multibeam apps have been released.
This marks a major turning point for the project, as we're switching from data gathered on the (now no longer operative) linefeed receiver at Arecibo to the newer ALFA Multibeam receiver (that can record 14 signals at the same time the old did one).
The updated apps also bring another change: the default credit multiplier was adjusted. It used to be 3.35, now it's 2.85. The reasoning behind this adjustment is the following - since a lot of optimized code from the lunatics apps was incorporated into the new MB stock applications, the processing speed improved significantly. Earlier, Eric Korpela wanted to increase the credit multiplier upon switching to MB; after the new code was added, the apps were so much quicker that instead it had to be reduced - to stay at approximately the same credits/hr as the old one.
This has created a bit of resentment among the power crunchers; after all, their bonus over the average user just got gutted. In contrast, all average users now process significantly more WUs, though they will continue to receive similar credit/time as before.
It all balances out in the end; at least, it should, IF:
* Most people do update their optimized apps if they use any
* There does not remain a "hard core" of crunchers refusing to update and skewing credit claims for everyone
Meaning: if you don't update your science app, you will overclaim compared to the average cruncher. Anyone care to remember what ensued the last time this happened? "Big Bada-Boom", as the fifth element would say...
So what happens if you say "ah well, screw it, it's not as if they could do anything about it"?
Well, wrong, they can and will. Namely, they (the S@H project) will reduce the credit multiplier even more to balance out the overclaimers, punishing EVERYONE for mistakes a few made. Next step will probably be, all KWSN apps up to 2.2 will be officially unwelcome at the main project.
I would ask you to consider this and make the right decision - another point to mention is that our optimization community will be much less motivated if people turn out to value credits more than fairness and scientific value. In fact, some of them would probably not continue to work on further optimizations.
So, I'd like to request that everyone update their science apps ASAP, please (I'm uploading them as this is posted).
Regards,
Simon.
Crunch3r:
I addition to what Simon posted i'd like to inform you as well that the new apps (2.4) , also have an improved support for Windows Vista.
While the "older 2.2B" apps have had some issues regarding Vista compatibility and could crash on suspend/resume, resulting in ZERO credit.
However we've fixed that in our new releases and that shouldn't happen any more. If you still experience issues please report them here on the message board.
(Most probably there are going to be some additional fixes for the 32 bit Windows app. IF we notice or get notified that there are issues.)
Missing platforms ... HPUX on PARISC, IA64 and Solaris on SPARC.
Those will be release shortly (haven't had the time to compile them and of course WILL be faster that any previous released apps ;) )
So the only thing left to say.... Happy crunching using the new multibeam optimized apps.
Have fun. ;)
nutsalot:
Thanks Guys. ;D
My farm is now completely running the Chicken 2.4 Apps and this is the only way to go.
Keep up the good work.
KWSN - Sir Nutsalot
Simon:
Stats block / download counters will get updated/added tomorrow :)
Cheers,
Simon.
Crunch3r:
Ok here's Erics response.
(Joe is BCC'd on this, since I don't know if the email I have for him is public knowledge.)
Damn, I remember writing the code in one of the constructors in seti_header.cpp, but it's definitely not there now. That's the problem with developing on multiple machines simultaneously, sometimes a change can get lost. It looks like the 5.27 application is constant at 2.85, and we'll need to do one more release to change it.
If you want yours to do it right and not need to do a later release, the function seti_analyze() in analyzeFuncs.cpp is probably a good place to add an "if (swi.analysis_cfg.credit_rate != 0) LOAD_STORE_ADJUSTMENT=swi.analysis_cfg.credit_rate;" Like around line 189.
Whatever you do, I'll do the same.
Eric
Navigation
[0] Message Index
[#] Next page
Go to full version