Seti Beta
Message boards :
Number crunching :
Seti Beta
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 . . . 10 · Next
| Author | Message |
|---|---|
|
Heffed Send message Joined: 19 Mar 02 Posts: 1856 Credit: 40,736 RAC: 0 
|
yeah... I attach to everything. Not quite... I'm attached to 16 projects. :) ID: 124318 ·  |
 Raven  Send message Joined: 28 Aug 02 Posts: 373 Credit: 99,071 RAC: 0 
|
#96 in Astropulse. #11 in Orbit. This isn't the same as OSRA, is it? [EDIT Hehe, I'm user #161, a new record low for me, and I'm User of the Hour again!] 
ID: 124324 · |
Jord  Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 
|
From this post: Orbit@home is a project based on BOINC and ORSA, monitoring the orbit of all the asteroids passing near the Earth. Every time a new asteroid is discovered or re-observed, the orbit of the asteroid is updated and propagated in future to check for possible impacts with the Earth. As bigger and better telescopes are built, the number of orbits to update every day increases, so more computing power is needed in order to do it. It is at this point that the distributed computing philosophy enters and helps doing the work. The basic idea is the following: each different client can work with the data relative to a single asteroid, because there is no correlation between asteroids (excluding extremely rare cases, like asteroid-asteroid impact or gravitational perturbation; both these cases can be handled in an improved version of orbit@home). If the number of clients available is greater than the number of orbits to update (times a redundancy factor), it is possible in principle to update all the orbits in the same time needed by a single computer to update a single orbit. This is what makes the orbit@home project so appealing. Yet since it doesn't have an application yet, you don't need to stay attached to it. It does have a scheduler now, but that one immediately times out to 24 hour waits. ID: 124327 · |
ric  Send message Joined: 16 Jun 03 Posts: 482 Credit: 666,047 RAC: 0 
|
Its getting more and more difficult to keep up with all the BOINC projects. Here is a list of all the projects that I know of: + *LHC *LHC-ALPHA ID: 124339 · |
|
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 
 |
Its getting more and more difficult to keep up with all the BOINC projects. Here is a list of all the projects that I know of: Well, would guess most of the listed projects have also a small alpha-test-project... Anyway, Folding@home officially announced 1. April of the existence of the FAH/BOINC client and mentioned a more open beta test will be available later. ID: 124347 · |
Ulrich Metzner  Send message Joined: 3 Jul 02 Posts: 1256 Credit: 13,565,513 RAC: 13 
|
[EDIT Hehe, I'm user #161, a new record low for me, and I'm User of the Hour again!] Hehe, i'm user #97 @orbit :P And i'm user #242 @folding, but they urged me to keep out, cause i stepped in to early. Although they didn't contact me until today... Aloha, Uli ID: 124354 · |
|
Ulrich Metzner Send message Joined: 3 Jul 02 Posts: 1256 Credit: 13,565,513 RAC: 13
|
BTW: Anyone had a succesful result on an AMD cpu? I always get something similar to: [core_client_version]4.19[/core_client_version] [message] - exit code -1073741819 (0xc0000005)[/message] [active_task_state]1[/active_task_state] [signal]0[/signal] [stderr_txt] ***UNHANDLED EXCEPTION**** Reason: Access Violation (0xc0000005) at address 0x7C920C27 read attempt to address 0x0099FCDD [/stderr_txt] Grmbl... :/ Aloha, Uli ID: 124380 · |
Kajunfisher  Send message Joined: 29 Mar 05 Posts: 1407 Credit: 126,476 RAC: 0
|
I have :-) http://setiweb.ssl.berkeley.edu/beta/results.php?userid=157 No matter where you go, there you are... 
ID: 124382 · |
Pascal, K G  Send message Joined: 3 Apr 99 Posts: 2343 Credit: 150,491 RAC: 0
|
From the Wiki ***UNHANDLED EXCEPTION**** Reason: Access Violation (0xc0000005) at address '(address)' read attempt to address '(address)' From BOINCWiki Message Type: Error Message Actually, we geeks call this a "Fatal Error", this means that the whole world comes to an end … This error can be the result of a programming error in the code for: The BOINC Client Software The Science Applications Any other program running on the computer The Operating System On the other hand, it could be because it is Tuesday. Semper Eadem So long Paul, it has been a hell of a ride. Park your ego's, fire up the computers, Science YES, Credits No. ID: 124393 · |
Celtic Wolf  Send message Joined: 3 Apr 99 Posts: 3278 Credit: 595,676 RAC: 0
|
From the Wiki Ahhhh now I see the problem The computer thought it was Tuesday when in fact it's Thurday. It doesn't know how to handle the loss of Wednesday.. I'd rather speak my mind because it hurts too much to bite my tongue. American Spirit BBQ Proudly Serving those that courageously defend freedom. ID: 124397 · |
The Pirate  Send message Joined: 14 Apr 00 Posts: 191 Credit: 4,929,008 RAC: 0
|
BTW: Anyone had a succesful result on an AMD cpu? I have one completed and ready to report but nothing has shown up at the S@H Beta site yet.  
ID: 124418 · |
|
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3
|
ID: 124421 · |
Dominique  Send message Joined: 3 Mar 05 Posts: 1628 Credit: 74,745 RAC: 0
|
BTW: Anyone had a succesful result on an AMD cpu? 2 after a reset. ID: 124422 · |
|
Heffed Send message Joined: 19 Mar 02 Posts: 1856 Credit: 40,736 RAC: 0
|
ID: 124431 · |
|
Angus Send message Joined: 26 May 99 Posts: 459 Credit: 91,013 RAC: 0 
|
I've finished a couple at least on an AMD XP2600+ Computer ID 169 
ID: 124484 · |
|
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13
|
.....@Home They clearly states they DON'T WANT a link to their page at this time... ID: 124499 · |
|
Heffed Send message Joined: 19 Mar 02 Posts: 1856 Credit: 40,736 RAC: 0
|
.....@Home Actually, from info posted on the project forum regarding emails from the project head, they've said it's OK to mention the project as it's no longer secret, just not front page stuff. Account creation was limited. ID: 124500 · |
|
Ulrich Metzner Send message Joined: 3 Jul 02 Posts: 1256 Credit: 13,565,513 RAC: 13
|
Ahhhh now I see the problem The computer thought it was Tuesday when in fact it's Thurday. It doesn't know how to handle the loss of Wednesday.. Ok :) But in reality i think it was my fault, cause i looked shortly at the graphics when it was suspended. After it resumed it crashed out and died. The buggy graphics code from 4.10 may be back :/ Aloha, Uli ID: 124505 · |
Mike   Send message Joined: 17 Feb 01 Posts: 34559 Credit: 79,922,639 RAC: 80
 |
Ahhhh now I see the problem The computer thought it was Tuesday when in fact it's Thurday. It doesn't know how to handle the loss of Wednesday.. Yes, i cannot view graphics like 4.10. greetz Mike With each crime and every kindness we birth our future. ID: 124507 · |
Pepo  Send message Joined: 5 Aug 99 Posts: 308 Credit: 418,019 RAC: 0 
|
I've just realized that the EnhancedSetiBeta client's crunching thread (on Windose) has already its base/dynamic priority at 1. The standard client's prio was at 4 (or 2? Not running now...) Seti Classic (driven by SETI Dirver at prio 1 too) is usually sleeping on my computer and if there is some problem with work units, it jumps in. Now they are sharing the processor fifty-fifty (actually ~43-43). I wondered why is the SetiBeta progressing so slowly... Peter ID: 124531 · |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.