My seti stats are so screwed up!

[sash1]

mine stats

I dun even think I have to DESCRIBE the problem, it's pretty obvious...

So what's up? My SETI drive was acting weird for a few days (now it's fine tho), saying the Est. time was 200 some odd days, even though it only ended up taking I think 5 hours or sumpin, I dunno exactly. So what seems to be the problem?

~Aunix

UPDATE: I just hit the BIGGEST "Fat Wu" evar! This one is going to take 1412 days! WAHOO!

Good thing this time I be ready: Thanks Smokeball

 

[titanmiller]

Did you change your clock while seti was running?

 

[sash1]

Originally posted by: titanmiller
Did you change your clock while seti was running?

Nope

 

[Smoke]

Describe for us how you have installed SETI and also details about your computer.

 

[jatwell]

Well, it looks like you registered on the 18th and have only submitted 4 WU's so far. It just takes that amount of time to the present and the number of WU's to find the average.

Have is ever showed up more than 4 WU's? If so, I wonder why you're losing them...

 

[Assimilator1]

Her average WU time is w-a-y too high.

Out of curosity AunixM3 do you flush SETI to a SETIQ proxy or direct to S@H?

 

[Ken g6]

Her system. If that's an overclock, it's not much of one. You're sure you (or any other program) didn't change your clock?

 

[sash1]

here is what my seti looks like

And I'd just like to clear up a few things: if I'm a girl... then I guess Adul must be too.

~Aunix

 

[onebadv6]

are you using the gui client? I had a freind using setispy and was wondering why his units were taking so long. Turned out he downloaded the gui client and was using setispy to run it. Ran completly in the background like the command line but without the speed.

 

[sash1]

Originally posted by: onebadv6
are you using the gui client? I had a freind using setispy and was wondering why his units were taking so long. Turned out he downloaded the gui client and was using setispy to run it. Ran completly in the background like the command line but without the speed.

No I'm using the CLI. (I followed method 2 here)

~Aunix

 

[Smoke]

Looks like the SetiDriver is setup perfectly to me.

And this chart shows you are starting to crunch faster too.

And this page shows your History.

Don't understand what happened with that one WU with the AR of 0.598 taking 8d:4:57! :Q

You are averaging around 9 hours for the rest. Let's hope that keeps up and no more of those 8 hour jobs show up.

[Edit: I just noticed you are running a 1700+ XP. You should be averaging around 3:30!

Do a CTRL/ALT/DEL and see what "Processes" are using up your CPU. Seti should be around 99 (%).

 

[Assimilator1]

onebadv6
Look at his screenshot ,there's no GUI running

I got to admit I'm baffled by this though ,I once managed to get SETIQ to show a WU as taking 21days when somehow the clock set itself back over a year (dont ask where 21days came from! ) ,it did show the WU as pending from over a year ago

Aunix
Are you sure WUs are only taking about 5hrs?
I assume you don't have your PC on 24/7?

[edit]nm I was too busy PMing Smokeball so I hadn't seen his post

 

[Smoke]

"He' is not any of those people ... those are members of TeAm Smokeball.

Here is where you will see "AunixM3" listed along with other users of the TS SetiQueue!

 

[Assimilator1]

Doh! ,I keep forgetting about the different q's within SETIQ!

Btw I thought Adul was a girl!

 

[sash1]

Originally posted by: Smokeball
[Edit: I just noticed you are running a 1700+ XP. You should be averaging around 3:30!

Do a CTRL/ALT/DEL and see what "Processes" are using up your CPU. Seti should be around 99 (%).

Actually, I'm still using my Duron 950, my sig is what is en route from newegg currently, I'm just too excited I guess.

~Aunix

 

[Assimilator1]

Hows the latest WU panning out?

 

[Smoke]

Completed Ra, Dec AR Client Cpu Time
2003 Mar 01 09:11am 5.042,28.59 0.385 ptd-24-198-167-37.maine.rr.com 8:09

2003 Feb 28 05:48pm 23.175,15.59 0.432 ptd-24-198-167-37.maine.rr.com 9:49

2003 Feb 27 02:42pm 13.58,24.56 0.598 ptd-24-198-167-37.maine.rr.com 8d 4:57

2003 Feb 25 02:52pm 20.984,18.01 0.417 ptd-24-198-167-37.maine.rr.com 9:13

2003 Feb 20 12:04pm 13.611,24.72 0.61 ptd-24-198-167-37.maine.rr.com 8:57

2003 Feb 19 01:37pm 20.435,8.27 0.61 ptd-24-198-167-37.maine.rr.com 8:32


Fastest WU yet!

 

[Assimilator1]

Thats about right for an old Duron

Btw AunixM3 ,don't know if its worth the hassle seeing as your upgrading soon but you could speed SETI up considerable by raising the FSB & lowering the multiplier.My brothers Duron 800 does WUs in about 8.5 hrs on 8x100 CAS3 ,when run at 6x133 CAS2 it does WUs in just over 7hrs

 

[Smoke]

I think this WU: "2003 Feb 27 02:42pm 13.58,24.56 0.598 ptd-24-198-167-37.maine.rr.com 8d 4:57" was one of those FAT Work Units I've written about before.

I have had similar episodes with some of my mini-team mates. We'd try this and we'd try that and no matter what we did it seemed there was a completed WU that would just not TRANSMIT and SetiDriver would not start the next WU because of it.

Sometimes a shutdown and restart would kick the "fat wu" through but many times it had no effect.

I have found that the best solution, when you have a "stuck or fat wu", is to delete the whole SETI FOLDER and do a complete new SETI INSTALL. The time you waste trying to figure out what's wrong could be put into producing WUs and you'll end up many WUs ahead.

That's my opinion anyway.

And I know, here come the FAT WU jokes.

Was FAT WU one of the characters in Hawaii Five-0? lol

 

[Assimilator1]

Interesting ,I don't believe that has happened to me .......yet!

Hawai 5 0? I know the program but

 

[Smoke]

The character in Hawaii Five-0 was named, "Wo Fat". LOL

 

[Spacehead]

I had a similar problem before too. I happened to check on a WU that was only about 6%-8% processed & the estimated times was several hundred hours. So i found which WU it was & deleted it.
I had SETI Driver start the next one & it ran normally, as did the next several.
I was about to delete the flakey WU from the recycle bin & then thought i'd try running it again, just to see what happened. It then processed normally.

 

[Assimilator1]

Wierd!

SB
hehe

 

[sash1]

LOL! Bump, see my update

 

[Assimilator1]

So whats your average WU time now?