• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

new seti@home v3.03

E

EmperorNero

Golden Member
not sure if this has been posted or not, but...get it here.

edit: oops, I had an old link on my clipboard and thought it was seti's d/l site 😱

anyway, go to sukhoi's link to get to the real site.
 
But is there a 3.03 CLI? The file name for the CLI is still the same! And the GUI didn't have the problem with the VLARs! Only the CLI!

:frown:
 
Looking forward to the CLI. I just hope it fixes the low angle WU problem. I'm not looking forward to 29 CLI client installs though. Just stopping the client, replacing the .exe and restarting it will take a couple of hours. Ah, the cost of maintaining a fleet. 🙂

Rob
 


<< Added a mechanism by which the server can tell the client that it is obsolete and the client will remember that. This will prevent obsolete clients from continually contacting the server >>



Also...WU times will increase, but it is in the benefit of science. Just read the page in Ass1's link for info about blocking old clients and fixes.
 
The next obvious question is, are they going to block the 3.0 GUI/CLi clients as well? Can they?
 


<< Changed the alias of the server host. Both the old and new names will be in effect for a while. At some point, we will turn off the old name. The reason is that when we set our server to reject requests from older versions of the client, some of our really old clients (1.x)and some (otherwise great!) third party buffering programs don't have the correct logic to recognize what is happening, and they will keep retrying. By continually contacting our server, they will waste precious bandwidth. Once we turn off the old server name, they will no longer be able to reach the server. >>



are setiQ and setiDriver going to be blocked!?!?!?!?!?!?!?!
ack ack ack ack

🙁 🙁
 
I think only WU's submitted/processed by older clients will be blocked. Therefore, if an old client processes a WU, and SetiQ tries to send it in, it will be rejected. Also, that particular reference was that they are changing the server address so that the old clients won't even be able to TRY to submit WU's. This will probably mean that we'll need a new version of SetiQ/SetiDriver with the new server address, but that shouldn't be too difficult for the respective programmers to change... 🙂
 
Installed 3.03 GUI last night...

30% done after 9.5 hours on a K6-2-400..

This machine noormally completes after around 17 hours...

I know processing time isn't linear any more but it's looking slow !!!!

We'll see


Col
 
Does anybody know what the new server alias is? In SETI Gate (which I am trying to test), this can be set manually and I'd like to test it with the new server alias...

JHutch
 
It might be...

sagan.ssl.berkeley.edu


sounds interesting to me....
It looks like I might be blocked from uploading through work so an alternative address would be sweet...

Col
 
Fardringle and Orange Kid - Mike Ober (Seti Driver) wrote this today on alt.sci.seti:



<< SETI Driver will pick this change up when the 3.03 CLI client is added via the &quot;New Client&quot; button. I suspect a lot of the other caching programs will pick this change up as well. Only those programs that act as a SETI Proxy should need to be updated. >>



So it appears that Seti Driver would be okay. Setiqueue is another issue altogether...
 
Hi Guys,

I e-mail Ken Reneris asking if he was going to update SetiQ.
He usually replies pretty quickly so I'll keep you posted....

cheers,

Col.

p.s.

47% complete at 16hours 20 minutes on the AMD400 GUI 3.03
It would normally be finishing around now !!!!!!!!!!!!!!!!!!!
 
They said they were reducing traffic by adding more science to the WUs. If they take that much longer, I wonder if they'll credit us two WUs for work from V3.03? They should.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top