Lookin' Up (May 23 2007)

Author	Message
Grant (SSSF) Volunteer tester Send message Joined: 19 Aug 99 Posts: 13854 Credit: 208,696,464 RAC: 304	Message 574830 - Posted: 24 May 2007, 8:25:39 UTC - in response to Message 574829. Or have i missed somthing AFAIK- the new system is using HDDs to record the data & will require a new client to process it. "Multibeam data recorder- .... Since the raw data will be organized in a different manner, we will be developing a new SETI@home application in order to analyze data in this new format." From here. Grant Darwin NT ID: 574830 ·

kittyman Volunteer tester Send message Joined: 9 Jul 00 Posts: 51478 Credit: 1,018,363,574 RAC: 1,004	Message 574831 - Posted: 24 May 2007, 8:31:04 UTC Last modified: 24 May 2007, 8:31:28 UTC Dunno...the response I got on Simon's site a while back indicated that the current Chicken apps would crunch Multibeam data (codename MultiChicken). "Time is simply the mechanism that keeps everything from happening all at once." ID: 574831 ·

Richard Haselgrove Volunteer tester Send message Joined: 4 Jul 99 Posts: 14679 Credit: 200,643,578 RAC: 874	Message 574833 - Posted: 24 May 2007, 9:04:55 UTC The app is indeed very similar. But 'H Elzinga' was asking about *splitters. My take on that is: The newly recorded data, of which there is plenty in cold storage (even though the Arecibo telescope is switched off and partially dismantled for refurbishment) will need completely new splitters. It would be crazy not to run them under Linux, so any remaining development effort will go to new splitters/Linux. The old* splitters only run under Solaris. Because there is so little classic data left, it is not worth converting the old splitters to run under Linux - that's why every Solaris-compatible pocket calculator in the lab has been diverted from its regular work, and assigned to fill 10-day optimised caches instead. ID: 574833 ·

Grant (SSSF) Volunteer tester Send message Joined: 19 Aug 99 Posts: 13854 Credit: 208,696,464 RAC: 304	Message 574835 - Posted: 24 May 2007, 10:01:31 UTC - in response to Message 574833. But 'H Elzinga' was asking about *splitters*. Doh! Grant Darwin NT ID: 574835 ·

W-K 666 Volunteer tester Send message Joined: 18 May 99 Posts: 19400 Credit: 40,757,560 RAC: 67	Message 574839 - Posted: 24 May 2007, 10:39:12 UTC - in response to Message 574831. Dunno...the response I got on Simon's site a while back indicated that the current Chicken apps would crunch Multibeam data (codename MultiChicken). That is correct but it needs to collect beam/polarisation data also, and it is also shown on graphics screen too. For those that look at it. It will also have some bug fixes, including I hope Joe's win98 and multicore fixes. But although there will be 14 beams, each beams sweep is smaller and therefore there will only be 10* more work. As each unit takes less time. Andy ID: 574839 ·

Francesco Forti Send message Joined: 24 May 00 Posts: 334 Credit: 204,421,005 RAC: 15	Message 574851 - Posted: 24 May 2007, 12:26:15 UTC - in response to Message 574810. In theese hosts I don't have any app_info file and in this moment I can't say anything about my far hosts that are still using app_info. If I'll see them working, I'll tell you. Bye, Franz Ok, now, some hours later I can see that one of my "Far Host" (app_info denoted) have received one RU at: 24 May 2007 7:32:51 UTC and have sent the result at: 24 May 2007 10:01:21 UTC so I can say "It is working good". So I think that gosts/app_info crysis is finished. Bye, Franz ID: 574851 ·

Lee Gresham Send message Joined: 12 Aug 03 Posts: 159 Credit: 130,116,228 RAC: 0	Message 574871 - Posted: 24 May 2007, 14:30:17 UTC Need more info on the function of "app_info.xml". I have 15 machines running Seti and cannot currently find this file on any. I did find it on 1 last week. 2 of these computers have Seti installed within the last 30 minutes and appear to be crunching seti data but don't contain app_info. What gives? Delta-V ID: 574871 ·

jason_gee Volunteer developer Volunteer tester Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0	Message 574874 - Posted: 24 May 2007, 14:41:04 UTC - in response to Message 574871. Need more info on the function of "app_info.xml". I have 15 machines running Seti and cannot currently find this file on any. I did find it on 1 last week. 2 of these computers have Seti installed within the last 30 minutes and appear to be crunching seti data but don't contain app_info. What gives? Your computers are hidden so I cannot check, however I suspect you are using the stock science application. These do not use the 'Anonymous Platform' and do not use or need an app_info.xml file. "Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions. ID: 574874 ·

Lee Gresham Send message Joined: 12 Aug 03 Posts: 159 Credit: 130,116,228 RAC: 0	Message 574883 - Posted: 24 May 2007, 15:20:51 UTC - in response to Message 574874. Thanks Jason. I tried an optimized version last week and I guess thats where the app_info came from. Most machines now are running standard Seti 5.816. Some are running beta 5.10 and 5.11. I am going to unhide for awhile. Lee Delta-V ID: 574883 ·

jason_gee Volunteer developer Volunteer tester Send message Joined: 24 Nov 06 Posts: 7489 Credit: 91,093,184 RAC: 0	Message 574895 - Posted: 24 May 2007, 16:02:31 UTC - in response to Message 574883. Thanks Jason. I tried an optimized version last week and I guess thats where the app_info came from. Most machines now are running standard Seti 5.816. Some are running beta 5.10 and 5.11. I am going to unhide for awhile. Lee I missed the unhide, but did that sortof answer your questions? "Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions. ID: 574895 ·

Bounce Send message Joined: 3 Apr 99 Posts: 66 Credit: 5,604,569 RAC: 0	Message 574896 - Posted: 24 May 2007, 16:03:57 UTC - in response to Message 574833. Last modified: 24 May 2007, 16:06:22 UTC The old splitters only run under Solaris. Because there is so little classic data left, it is not worth converting the old splitters to run under Linux isn't it great to step back and look at how far we've come? when the SETI@H project began how big of a "problem" was "not having enough data" to crunch? thanks for the on going effort, LabBoiz! it's appreciated by even those who whine a lot. ID: 574896 ·

IrishFBall32 Volunteer tester Send message Joined: 28 May 04 Posts: 11 Credit: 16,993,631 RAC: 0	Message 574914 - Posted: 24 May 2007, 17:16:36 UTC WUs are flowing nicely both up and down now, Even on the chicken apps... good work guys... now if only those 'pocket calculators' running as splitters could keep up :) ID: 574914 ·

Lee Gresham Send message Joined: 12 Aug 03 Posts: 159 Credit: 130,116,228 RAC: 0	Message 574922 - Posted: 24 May 2007, 17:46:24 UTC - in response to Message 574895. Thanks Jason. I tried an optimized version last week and I guess thats where the app_info came from. Most machines now are running standard Seti 5.816. Some are running beta 5.10 and 5.11. I am going to unhide for awhile. Lee I missed the unhide, but did that sortof answer your questions? That took care of the current question. I did unhide and left it that way but it Seti project hasn't changed it yet. I'll just wait and see. Thanks Delta-V ID: 574922 ·

goetz Send message Joined: 28 Dec 00 Posts: 2 Credit: 1,497,442 RAC: 0	Message 574928 - Posted: 24 May 2007, 17:51:53 UTC - in response to Message 574583. You guys have done really good work and since today morning everything seems to work again, even with the chicken optimized crunchers. I hope you have time to relax a bit now! Cheers! ID: 574928 ·

cyan Send message Joined: 12 Jul 99 Posts: 1 Credit: 1,328,191 RAC: 0	Message 574933 - Posted: 24 May 2007, 18:00:07 UTC Last modified: 24 May 2007, 18:01:47 UTC The problem of the Time-out persists, at least for me, increased, if it fits. Tonight I have received 200 ghost wu, that added to the other fifty previous ones. This time has not been, like in the previous ones, product of a HTML error, but 20 ghost wu by each Time-out. And all it with the file app_info deactivated. On the other hand, in two days I have only obtained a valid connection to reporting task finished and uploaded. My machine is iMac C2D. Peculiarly my other two machines (PowerPC), although, and after with great difficulty and numerous Time-out, have been staying more or less correct, although for one of them download new units isnÂ´t possible. All this with regard to the little movement of the forum today. It is that the others no longer have these problems? (Sorry for my AltaVista-english) ID: 574933 ·

William Roeder Volunteer tester Send message Joined: 19 May 99 Posts: 69 Credit: 523,414 RAC: 0	Message 574951 - Posted: 24 May 2007, 19:37:12 UTC - in response to Message 574933. Tonight I have received 200 ghost wu, that added to the other fifty previous ones. This time has not been, like in the previous ones, product of a HTML error, but 20 ghost wu by each Time-out. And all it with the file app_info deactivated. I was able to download more work switched to a modified app.xml (no 5.17) the Chicken app started but I couldn't get more work deleted the app.xml and no I'm getting more work and crunching optimized. ID: 574951 ·

Blurf Volunteer tester Send message Joined: 2 Sep 06 Posts: 8964 Credit: 12,678,685 RAC: 0	Message 574960 - Posted: 24 May 2007, 19:52:29 UTC Receiving lots of valid WU's on all my machines...with chicken app on. ID: 574960 ·

Brian Silvers Send message Joined: 11 Jun 99 Posts: 1681 Credit: 492,052 RAC: 0	Message 574974 - Posted: 24 May 2007, 19:58:12 UTC - in response to Message 574960. Receiving lots of valid WU's on all my machines...with chicken app on. Receiving lots of error messages from scheduler. It's almost to the point where it's not worth bothering. 5/24/2007 3:27:56 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:27:56 PM\|SETI@home\|Reason: To report completed tasks 5/24/2007 3:27:56 PM\|SETI@home\|Reporting 1 tasks 5/24/2007 3:33:01 PM\|\|Project communication failed: attempting access to reference site 5/24/2007 3:33:02 PM\|\|Access to reference site succeeded - project servers may be temporarily down. 5/24/2007 3:33:02 PM\|SETI@home\|Scheduler request failed: a timeout was reached 5/24/2007 3:33:02 PM\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds 5/24/2007 3:34:02 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:34:02 PM\|SETI@home\|Reason: To report completed tasks 5/24/2007 3:34:02 PM\|SETI@home\|Reporting 1 tasks 5/24/2007 3:34:27 PM\|SETI@home\|Scheduler request succeeded 5/24/2007 3:34:27 PM\|SETI@home\|Message from server: Completed result 17mr05aa.29088.2529.804838.3.201_1 refused: result already reported as success 5/24/2007 3:36:17 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:36:17 PM\|SETI@home\|Reason: To fetch work 5/24/2007 3:36:17 PM\|SETI@home\|Requesting 126268 seconds of new work 5/24/2007 3:36:42 PM\|SETI@home\|Scheduler request succeeded 5/24/2007 3:36:42 PM\|SETI@home\|No work from project 5/24/2007 3:36:42 PM\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds 5/24/2007 3:37:42 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:37:42 PM\|SETI@home\|Reason: To fetch work 5/24/2007 3:37:42 PM\|SETI@home\|Requesting 126268 seconds of new work 5/24/2007 3:38:57 PM\|SETI@home\|Scheduler request failed: HTTP internal server error 5/24/2007 3:38:57 PM\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds 5/24/2007 3:39:57 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:39:57 PM\|SETI@home\|Reason: To fetch work 5/24/2007 3:39:57 PM\|SETI@home\|Requesting 126269 seconds of new work 5/24/2007 3:41:37 PM\|\|Project communication failed: attempting access to reference site 5/24/2007 3:41:39 PM\|\|Access to reference site succeeded - project servers may be temporarily down. 5/24/2007 3:41:42 PM\|SETI@home\|Scheduler request failed: server returned nothing (no headers, no data) 5/24/2007 3:41:42 PM\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds 5/24/2007 3:42:42 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:42:42 PM\|SETI@home\|Reason: To fetch work 5/24/2007 3:42:42 PM\|SETI@home\|Requesting 126269 seconds of new work 5/24/2007 3:44:07 PM\|SETI@home\|Scheduler request failed: HTTP internal server error 5/24/2007 3:44:07 PM\|SETI@home\|Deferring scheduler requests for 1 minutes and 0 seconds 5/24/2007 3:45:07 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:45:07 PM\|SETI@home\|Reason: To fetch work 5/24/2007 3:45:07 PM\|SETI@home\|Requesting 126269 seconds of new work 5/24/2007 3:46:32 PM\|SETI@home\|Scheduler request failed: HTTP internal server error 5/24/2007 3:46:32 PM\|SETI@home\|Deferring scheduler requests for 1 minutes and 24 seconds 5/24/2007 3:47:57 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:47:57 PM\|SETI@home\|Reason: To fetch work 5/24/2007 3:47:57 PM\|SETI@home\|Requesting 126270 seconds of new work 5/24/2007 3:48:22 PM\|SETI@home\|Scheduler request succeeded 5/24/2007 3:48:22 PM\|SETI@home\|No work from project 5/24/2007 3:48:22 PM\|SETI@home\|Deferring scheduler requests for 2 minutes and 42 seconds 5/24/2007 3:51:07 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:51:07 PM\|SETI@home\|Reason: To fetch work 5/24/2007 3:51:07 PM\|SETI@home\|Requesting 126270 seconds of new work 5/24/2007 3:54:17 PM\|\|Project communication failed: attempting access to reference site 5/24/2007 3:54:17 PM\|SETI@home\|Scheduler request failed: server returned nothing (no headers, no data) 5/24/2007 3:54:17 PM\|SETI@home\|Deferring scheduler requests for 2 minutes and 4 seconds 5/24/2007 3:54:18 PM\|\|Access to reference site succeeded - project servers may be temporarily down. 5/24/2007 3:56:22 PM\|SETI@home\|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi 5/24/2007 3:56:22 PM\|SETI@home\|Reason: To fetch work 5/24/2007 3:56:22 PM\|SETI@home\|Requesting 126271 seconds of new work 5/24/2007 3:57:48 PM\|\|Project communication failed: attempting access to reference site 5/24/2007 3:57:49 PM\|\|Access to reference site succeeded - project servers may be temporarily down. 5/24/2007 3:57:52 PM\|SETI@home\|Scheduler request failed: server returned nothing (no headers, no data) 5/24/2007 3:57:52 PM\|SETI@home\|Deferring scheduler requests for 29 minutes and 18 seconds ID: 574974 ·

GreggyBee Volunteer tester Send message Joined: 9 Mar 01 Posts: 203 Credit: 1,600,521 RAC: 0	Message 574977 - Posted: 24 May 2007, 20:02:53 UTC Uploading and downloading fine, with Chicken running; even Beta seems to be accepting uploads, although the server's supposedly disabled. Well done guys, The Sun also rises... ID: 574977 ·

Henk Haneveld Volunteer tester Send message Joined: 16 May 99 Posts: 154 Credit: 1,577,293 RAC: 1	Message 574989 - Posted: 24 May 2007, 20:32:13 UTC Confirmed, the 5 minute timeout problem is still there and creating Ghosts ID: 574989 ·

©2024 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.