Going to 3.03

[ElFenix]

i got an email message today asking why i was using an obsolete client and asked why said client was connecting all the time. apparently SetiDriver was having a field day filling WUs. so, i'm switching slowly to 3.03.

 

[Sukhoi]

What client were you using? They better not e-mail me about using the 3.0 CLI for a while.

 

[BadThad]

No kidding? :Q

 

[ElFenix]

i was using the 3.0

 

[Assimilator1]

Whoops! ,just as well I'm switching clients in a few days!

 

[Orange Kid]

3.03 is suck!!!!!!!!!!
what used to take 8ish hours is now taking 17hrs.
thats got to help with bandwidth!!!!!!!!!!!
what a poor excuse

sorry for the rant im not in a happy mood

 

[blade47]

Times on my P3-500e @ 620mhz went from just over 5hrs to around 8.5hrs so I'm not too disappointed.

 

[Assimilator1]

Orange Kid
Its not just for bandwdith ,they have refined the search

Cheer up mate ,in a few months time it'll seem normal!

 

[ElFenix]

damn... 8:30 for a p3 700... tsk tsk... guess the pro will stay rc5... lucky for me i can't get to some of my 3.0 clients right now.

 

[CurtOien]

Sounds like a good excuse to buy some more power.

 

[Viztech]

A couple of people posted about the same thing at ARS Technica

I just fired up 3.03 Cli on the 2K box. Oh well...

viz

 

[networkman]

I repeat an earlier post I made in which I stated that I had serious questions about the new 3.03 client.

In fact, I'll venture to say that the new client really doesn't do anything new in the way of science, it just slows things down. With slower times, WUs don't get requested or submitted as often and the bandwidth goes down!

Go ahead someone, show me I'm wrong! :|

 

[Jalapeno]

I'm new to SETI, but I have to agree with Networkman. V3.03 seems to benefit only the guys running SETI at UC Berkeley.
I switched to the command line DOS version as soon as Assimilator1 (thanks again!) provided me with it and I intend to use it as long as I can! Heck, I'm doing units at a rate of 3hrs. 45mins. right now...

Assimilator1, could you, if you please, send me the "SETI Q" thing? I've got a bunch of NT machines at work I'd like to start crunching!

I really like the efforts and the results Team AnandTech is producing, but I have founded my own little group for now (a measly 460 units returned...), but we are growing. Maybe I can convince my guys to join AnandTech down the road...

 

[Assimilator1]

NWM

In fact, I'll venture to say that the new client really doesn't do anything new in the way of science

While it seems that v3.03 does have some 'issues' its certainly not true that it doesn't do any extra 'science' ,I quote from the SETI site.

Added additional science coverage. We now do a thorough search out to a chirp rate of +- 20 Hz/second. The cost of the additional coverage is that clients will take longer to process a workunit.

Originally it was +-10Hz.
I'm not saying that it isnt't odd that WU times are so rigidly fix to the angle range ,but to say ALL the increase in WU time is purely down to a 'fudge' is just not right

Jalapeno

No problems,I'll send it to your E mail

 

[snow patrol]

with 3.03 it's taking about 11 Hours on a P3 667. Is that too slow?

 

[BadThad]

argggg....I rec'd my email today. The pressure is on! I'm gonna switch over this week, my goal of 8000 wu's was reached.

Networkman

You're correct. It's nothing new, just expanded coverage. I will have to understand the definition of "chip rate" to further evaluate the my opinion of "increased science". Nonetheless, I still believe the project is fun and worth-while. I don't really care what they do, data is data. Bring the crunching on...LOL. After all, CPU cycles are a terrible thing to waste.

 

[Assimilator1]

The chirp rate refers to the frequency shift due to the doppler effect (eg moving objects).

Nonetheless, I still believe the project is fun and worth-while

Totally agree

(even if you did just beat me again in a race! )