SETI GUI v3.07 is out with some fixes that might improve your wu output if you use the gui that is.

[lobadobadingdong]

If you've been using 3.03, there are some larger WU's that the client can't send out, here is a link to berkely's page I found about this.

here's what it says:

Some workunits produce large (> 60KB) result files. Previous versions can't send these files, so users don't get credit (and, since our server doesn't get results, it keeps sending the work units over and over). This was only partially fixed in version 3.06, but is now fully functional.

I have just found a problem, the 3.07 only has links to the gui version, and not the cli version of the client. Can anyone find a cli for this?
I and many others use the cli version, I think sending in these "fat wu's to berkely should still be done instead of them floating from one client to another looking for a gui user to crunch it.

 

[Baldy18]

I'm pretty sure that version 3.07 of the GUI has been out for a while now. No version 3.07 is in the works for the CLI client.

It won't really improve output since these "bloated" WUs are usually discarded by the client within the first few minutes of processing.

 

[lobadobadingdong]

So in other words, by discarding the "fat" WU's we get more work done faster anyway. But 3.07 gui returns info to berkely that hasn't been getting sent that they keep re-distrubuting over and over, because the work never gets done.

btw how do read the setilog.csv file to find out the actual work times per wu?

 

[Confused]

Originally posted by: lobadobadingdong
btw how do read the setilog.csv file to find out the actual work times per wu?

Column AQ is the CPU time in seconds


Confused

 

[Baldy18]

I use the SETIWatch program to read the log file.

 

[lobadobadingdong]

thanks for help, where do you get the seti watch program?

 

[Confused]

Originally posted by: lobadobadingdong
thanks for help, where do you get the seti watch program?

SETIWatch



Confused

 

[Assimilator1]

CLi v3.03 didn't suffer from the same problem as GUI v3.03 had!