Seti for BOINC "officially active"

[Rattledagger]

If you activated your old "classic" account, you should already be part of the correct team...

As for credit, only then 3 users has crunched a wu and got comparable results will credit be given. The credit will be to discard top & bottom and average the rest... so in most cases the middle claimed credit is granted credit. So then you've crunched 1 you must wait for the 2 others also.

Oh, and uploading of results is a 2-part-process, there 1st upload result afterwards reporting back to the scheduling-server. To minimize traffic on the scheduling server means this only happens then asking for more work, and is then you hit your min-cache-day-setting or a result nearly reach it's deadline.

 

[silverpig]

Hmmm, the stats for BOINC are messed up.

Both the original seti page, as well as smoke's page, as well as all of my stats say I have ~6240 work units completed, but my stats on the BOINC page say I have completed just 5895 seti classic units... Oh well.

 

[Rattledagger]

Originally posted by: silverpig
Hmmm, the stats for BOINC are messed up.

Both the original seti page, as well as smoke's page, as well as all of my stats say I have ~6240 work units completed, but my stats on the BOINC page say I have completed just 5895 seti classic units... Oh well.

As already written earlier in this thread, the BOINC-stats was pulled 14. May 2004.

edit:

We have released a new version of SETI@home based on BOINC, a general-purpose platform for distributed computing projects. We encourage you to switch to the new SETI@home. If you have problems with the new version, you can uninstall it and reinstall the old 'Classic' version of SETI@home. The schedule is:

On 14 May 2004 we made a 'snapshot' of SETI@home Classic user information (accounts, teams, profiles) and used it to initialize the new SETI@home database.
On June 22 2004 we made SETI@home/BOINC available for general use. There will be a 'transition period' during which you can run either SETI@home Classic or SETI@home/BOINC. During this transition period, SETI@home Classic accounts and team changes can be made, but they will not be carried over.
Once SETI@home/BOINC is running smoothly and versions are available for most platforms, we will turn off the data server for SETI@home Classic. At this point you will need to switch to SETI@home/BOINC.

The rest is at http://setiboinc.ssl.berkeley.edu/sah/transition.php

 

[Wolfsraider]

The full readme file can be viewed here

Hope it helps

mike

 

[Robor]

I keep getting a red "I" over my BOINC icon in the taskbar. I don't see a newer BOINC client to download. Here's a copy/paste of my clients message window...

--- - 2004-06-23 12:38:54 - Starting BOINC client version 3.18 for windows_intelx86
SETI@home - 2004-06-23 12:38:55 - Project prefs: no separate prefs for home; using your defaults
SETI@home - 2004-06-23 12:38:55 - Project prefs: no separate prefs for home; using your defaults
SETI@home - 2004-06-23 12:38:55 - Host ID is 6299
SETI@home - 2004-06-23 12:38:55 - Host ID is 3805
--- - 2004-06-23 12:38:55 - General prefs: from SETI@home (last modified 2004-06-23 02:05:32)
--- - 2004-06-23 12:38:55 - General prefs: no separate prefs for home; using your defaults
SETI@home - 2004-06-23 12:38:55 - Restarting computation for result 11se03aa.2459.881.698572.43_2 using setiathome version 3.08
SETI@home - 2004-06-23 12:38:59 - Deferring communication with project for 56 minutes and 13 seconds
--- - 2004-06-23 12:39:00 - Suspending computation and network activity - user is active
--- - 2004-06-23 12:45:04 - Resuming computation and network activity
--- - 2004-06-23 12:45:07 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 12:45:07 - Requesting 177754 seconds of work
SETI@home - 2004-06-23 12:45:07 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 12:45:11 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 12:45:11 - Message from server: No work available (your core client is out of date - please upgrade)
SETI@home - 2004-06-23 12:45:11 - Project prefs: no separate prefs for home; using your defaults
SETI@home - 2004-06-23 12:45:11 - No work from project
SETI@home - 2004-06-23 12:45:11 - Deferring communication with project for 42 minutes and 7 seconds
--- - 2004-06-23 12:48:54 - Suspending computation and network activity - user is active
--- - 2004-06-23 13:11:36 - Resuming computation and network activity
--- - 2004-06-23 13:12:11 - Suspending computation and network activity - user is active
--- - 2004-06-23 13:15:05 - Resuming computation and network activity
--- - 2004-06-23 13:15:24 - Suspending computation and network activity - user is active
--- - 2004-06-23 13:28:56 - Resuming computation and network activity
--- - 2004-06-23 13:28:56 - Cache low-water mark hit; requesting more work
--- - 2004-06-23 13:28:59 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 13:28:59 - Requesting 177344 seconds of work
SETI@home - 2004-06-23 13:28:59 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 13:29:02 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 13:29:02 - Message from server: No work available (your core client is out of date - please upgrade)
SETI@home - 2004-06-23 13:29:02 - No work from project
SETI@home - 2004-06-23 13:29:02 - Deferring communication with project for 1 minutes and 0 seconds
--- - 2004-06-23 13:30:03 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 13:30:03 - Requesting 177375 seconds of work
SETI@home - 2004-06-23 13:30:03 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 13:30:06 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 13:30:06 - Message from server: Not sending work - last RPC too recent: 64 sec
SETI@home - 2004-06-23 13:30:06 - No work from project
SETI@home - 2004-06-23 13:30:06 - Deferring communication with project for 10 minutes and 0 seconds
--- - 2004-06-23 13:34:14 - Suspending computation and network activity - user is active
--- - 2004-06-23 13:37:41 - Resuming computation and network activity
--- - 2004-06-23 13:37:41 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 13:37:41 - Requesting 177450 seconds of work
SETI@home - 2004-06-23 13:37:41 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 13:37:44 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 13:37:44 - Message from server: No work available (your core client is out of date - please upgrade)
SETI@home - 2004-06-23 13:37:44 - Project prefs: no separate prefs for home; using your defaults
SETI@home - 2004-06-23 13:37:44 - No work from project
SETI@home - 2004-06-23 13:37:44 - Deferring communication with project for 3 hours, 48 minutes, and 14 seconds
--- - 2004-06-23 13:39:09 - Suspending computation and network activity - user is active
--- - 2004-06-23 13:45:26 - Resuming computation and network activity
--- - 2004-06-23 13:45:26 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 13:45:26 - Requesting 177405 seconds of work
SETI@home - 2004-06-23 13:45:26 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 13:45:30 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 13:45:30 - Message from server: No work available (your core client is out of date - please upgrade)
SETI@home - 2004-06-23 13:45:30 - No work from project
SETI@home - 2004-06-23 13:45:30 - Deferring communication with project for 1 minutes and 0 seconds
--- - 2004-06-23 13:46:31 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 13:46:31 - Requesting 177442 seconds of work
SETI@home - 2004-06-23 13:46:31 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 13:46:34 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 13:46:34 - Message from server: Not sending work - last RPC too recent: 65 sec
SETI@home - 2004-06-23 13:46:34 - No work from project
SETI@home - 2004-06-23 13:46:34 - Deferring communication with project for 10 minutes and 0 seconds
--- - 2004-06-23 13:54:07 - Suspending computation and network activity - user is active
--- - 2004-06-23 14:07:08 - Resuming computation and network activity
--- - 2004-06-23 14:07:08 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 14:07:08 - Requesting 177480 seconds of work
SETI@home - 2004-06-23 14:07:08 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 14:07:12 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 14:07:12 - Message from server: No work available (your core client is out of date - please upgrade)
SETI@home - 2004-06-23 14:07:12 - No work from project
SETI@home - 2004-06-23 14:07:12 - Deferring communication with project for 1 minutes and 24 seconds
--- - 2004-06-23 14:08:37 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 14:08:37 - Requesting 177520 seconds of work
SETI@home - 2004-06-23 14:08:37 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 14:08:40 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 14:08:40 - Message from server: Not sending work - last RPC too recent: 89 sec
SETI@home - 2004-06-23 14:08:40 - No work from project
SETI@home - 2004-06-23 14:08:40 - Deferring communication with project for 10 minutes and 0 seconds
--- - 2004-06-23 14:14:34 - Suspending computation and network activity - user is active
--- - 2004-06-23 14:17:56 - Resuming computation and network activity
--- - 2004-06-23 14:18:41 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 14:18:41 - Requesting 177667 seconds of work
SETI@home - 2004-06-23 14:18:41 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 14:18:44 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 14:18:44 - Message from server: No work available (your core client is out of date - please upgrade)
SETI@home - 2004-06-23 14:18:44 - No work from project
SETI@home - 2004-06-23 14:18:44 - Deferring communication with project for 4 minutes and 43 seconds
--- - 2004-06-23 14:18:45 - Suspending computation and network activity - user is active
--- - 2004-06-23 14:21:16 - Resuming computation and network activity
--- - 2004-06-23 14:22:22 - Suspending computation and network activity - user is active
--- - 2004-06-23 14:24:23 - Resuming computation and network activity
--- - 2004-06-23 14:24:23 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 14:24:23 - Requesting 177636 seconds of work
SETI@home - 2004-06-23 14:24:23 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 14:24:26 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 14:24:26 - Message from server: Not sending work - last RPC too recent: 342 sec
SETI@home - 2004-06-23 14:24:26 - No work from project
SETI@home - 2004-06-23 14:24:26 - Deferring communication with project for 41 minutes and 21 seconds
--- - 2004-06-23 14:26:48 - Suspending computation and network activity - user is active
--- - 2004-06-23 14:37:22 - Resuming computation and network activity
SETI@home - 2004-06-23 14:37:44 - Deferring communication with project for 2 hours, 48 minutes, and 14 seconds
--- - 2004-06-23 15:05:48 - Cache low-water mark hit; requesting more work
SETI@home - 2004-06-23 15:05:48 - Requesting 178298 seconds of work
SETI@home - 2004-06-23 15:05:48 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-06-23 15:05:51 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - 2004-06-23 15:05:51 - Message from server: No work available (your core client is out of date - please upgrade)
SETI@home - 2004-06-23 15:05:51 - No work from project
SETI@home - 2004-06-23 15:05:51 - Deferring communication with project for 1 hours, 20 minutes, and 27 seconds
SETI@home - 2004-06-23 15:37:44 - Deferring communication with project for 1 hours, 48 minutes, and 14 seconds

 

[Rattledagger]

Originally posted by: Robor
I keep getting a red "I" over my BOINC icon in the taskbar. I don't see a newer BOINC client to download. Here's a copy/paste of my clients message window...

--- - 2004-06-23 12:38:54 - Starting BOINC client version 3.18 for windows_intelx86

snip

http://setiboinc.ssl.berkeley.edu/sah/download.php

and see on the Windows/x86 - line.

Oh, neither beta nor alpha has v3.19 for download.

 

[RaySun2Be]

I downloaded and installed the SETI BOINC Windows client this morning. It looks like it is the BOINC Bete Version 3.19, M1.

The 1st result took about 4hrs, 28 minutes, which is about an hour slower than what the 3.03 SETI1 CLI client was running, timewise.

 

[Robor]

Originally posted by: Rattledagger
http://setiboinc.ssl.berkeley.edu/sah/download.php

and see on the Windows/x86 - line.

Oh, neither beta nor alpha has v3.19 for download.

Hmmm... I dunno how I managed to install that other client. I uninstalled it and installed 3.19. Appears to be working now.

Thanks once again Rattledagger!

 

[nickdakick]

Originally posted by: RaySun2Be
I downloaded and installed the SETI BOINC Windows client this morning. It looks like it is the BOINC Bete Version 3.19, M1.

The 1st result took about 4hrs, 28 minutes, which is about an hour slower than what the 3.03 SETI1 CLI client was running, timewise.

3 hours ~15 min which is exactly the time I had with 3.03 cli. No Probs here.

 

[SirUlli]

Originally posted by: Coolkid

How long is left for S@H1 then?

Once SETI@home/BOINC is running smoothly and versions are available for most platforms, we will turn off the data server for SETI@home Classic. At this point you will need to switch to SETI@home/BOINC.

Linky

Sir Ulli

 

[Freewolf]

Originally posted by: SirUlli

Originally posted by: Coolkid

How long is left for S@H1 then?

Once SETI@home/BOINC is running smoothly and versions are available for most platforms, we will turn off the data server for SETI@home Classic. At this point you will need to switch to SETI@home/BOINC.

Linky

Sir Ulli

I doubt very much that I will be switching any of my machines to it.

 

[amdxborg]

Originally posted by: SirUlli

Originally posted by: Coolkid

How long is left for S@H1 then?

Once SETI@home/BOINC is running smoothly and versions are available for most platforms, we will turn off the data server for SETI@home Classic. At this point you will need to switch to SETI@home/BOINC.

Linky

Sir Ulli

Still don't know how long that will be...

 

[SirUlli]

Originally posted by: amdxborg

Originally posted by: SirUlli

Originally posted by: Coolkid

How long is left for S@H1 then?

Once SETI@home/BOINC is running smoothly and versions are available for most platforms, we will turn off the data server for SETI@home Classic. At this point you will need to switch to SETI@home/BOINC.

Linky

Sir Ulli

Still don't know how long that will be...

the only man who kwow this is David Anderson, but i think you have time, this year i think nothink will change, or the BOINC TEAM make a big update.

Sir Ulli

 

[amdxborg]

Thanx Sir Ulli! I now have hope!

 

[Zuke]

Now I wonder how many folks will switch back to another project or lend help to another project now that Seti 1 is done or almost done....

 

[soni]

Anyone noticed that the seti client under boinc still doesnt run at idle priority
I have made a post about it under the window client.

The linux client runs nicely at nice 19

 

[jdiddy]

Im 58 days off of 25,000 but if they took a snapshot on May 14 then my final Seti1 total will be stuck at the number that I had on that day?? Grrrr neeed more crunchers.

 

[Rattledagger]

Most likely they will not update the credits showing as "classic" under your boinc-account, since "On 14 May 2004 we made a 'snapshot' of SETI@home Classic user information (accounts, teams, profiles) and used it to initialize the new SETI@home database." & "During this transition period, SETI@home Classic accounts and team changes can be made, but they will not be carried over." For me a "snapshot" is something that shouldn't change over time...
Of course your final score in "classic" should most likely be accessible for a long time on the "old" site...

Soni, priorities & limiting cpu-usage is M2-tasks. But running at 2 compared to classic at 4 is already an improvement.

 

[soni]

Thanks Ratledagger, but why 2, when they should use 1

 

[Rattledagger]

Well, seti@home using 4, genome@home used 4, some other DC-programs also probably uses 4, so my guess they set 2 and has done most of the time since squishing bugs. Programming the separate gui and fixing any problems popping up is their main priority now, but the little "nice to have" things like process affinity will also probably slowly be incorportated.

 

[silverpig]

I've got it running under windows fine now. I'm doing a custom compile on my gentoo box with some fairly aggressive optimizations... we'll see how it goes

 

[SlangNRox]

I'm giving boinc another try.

 

[CyGoR]

I also planned on trying boinc, but with no succes.. Like robor posted (his messages log..) above, I get the same thing. Just downloaded the newest (v3.19 M1) but it doesn't work..

SETI@home - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
SETI@home - Message from server: No work available

Both on my Windows pc as on my Apple....
Any ideas?

[edit]
It worked! After a few attempts it finally downloaded enough for a few days of work.. Let's see if the A64 is any good at this project
[/edit]

 

[lane42]

From the BONIC site,

June 24, 2004
To handle increased demand for more workunits, we are bringing another splitter online as quickly as possible. We are also working on increasing overall system performance. The overall system is experiencing twice the maximum load beta generated and is climbing. We are working to resolve the issues as quickly as possible.

 

[Unforgiven]

as of 8:30 am pst.....

SETI@home is temporarily shut down for maintenance. Please try again later.

good start to the project i see :laugh: