"Flwrite" <lostwithout@home.com> wrote in message
news:MK-dnR6_VuH6KGPdRVn-pQ@adelphia.com...

Hey Stratcat...

You're shaking up my braincells.  You wrote:

If you runn 2 concurrent CLI's, there's a switch to tick on SetiDriver
called "create Setilog.csv", which it will, upon completion of the WU.

I only crunch one WU at a time.  When I first started with SETI Driver, I
turned on the SETILog.csv function.  It saves a lot of information in

Excel

format.  But it was too much information for me.  I think there were only
two or three columns that I cared about, and the rest I didn't understand.

(Interesting that it offers special functionality for multiple

processes -- 

double crunching.)

So I started my own spreadsheet, and I update it with my latest SETI stats
when I have a free minute.  It's nice to get a little practice on Excel.

Hehe..I've been exercising BOTH of my remaining brain cells! ;-)

Yeah, there's another utility progy call "SetiWatch", which will auto-import
the .csv file from SetiDriver. I'm running P4C hyper-threaded cpu's, so I
run two concurrent CLI clients, which gives me a substantially greater
output than a single client. Unfortuanately, SetiSpy only can monitor a
single WU at a time, so it can sometimes miss a unit in it's log, when
running in my usual configuration. That's why I added SetiWatch to the
'usual' SetiSpy/SetiDriver combo. Plus SetiWatch gives some nice 'lifetime'
totals & averages, though you could do 'em yourself, as you said, using
M$Excel.

SetiDriver's .csv file creation can be turned on or off, anytime you choose,
not just upon the initial installation, FWIW

Sorry about the typos all over those three posts. I only had a couple
quick minutes to fire 'em off, & run.
-- 
Strat