Message boards :
Number crunching :
Astropulse Errors II-Optimized version 5.03!
Message board moderation
Author | Message |
---|---|
Blurf Send message Joined: 2 Sep 06 Posts: 8962 Credit: 12,678,685 RAC: 0 |
This thread is to post errors and address concerns regarding the new Optimised AP v5.03 Astropulse application. Please do not open new threads but post errors and commentary here. Please, upgrade your Optimized AP version to ap_5.03 and Current Opt. App of r112! Thanks! |
JarrettH Send message Joined: 14 Nov 02 Posts: 97 Credit: 25,385,250 RAC: 95 |
This is sort of broad, but it feels like I haven't received any SETI work for a couple weeks since using the optimized AP 5.03. My work queue is for 10 days and since crunching takes about 15hr per unit, AP units fill this queue. Is there some error in here preventing me from getting SETI work? I definitely remember prior to using the new optimized AP that I would receive work for SETI also. <app_info> <app> <name>setiathome_enhanced</name> </app> <file_info> <name>AK_v8_win_SSSE3x.exe</name> <executable/> </file_info> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>528</version_num> <file_ref> <file_name>AK_v8_win_SSSE3x.exe</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>setiathome_enhanced</app_name> <version_num>603</version_num> <file_ref> <file_name>AK_v8_win_SSSE3x.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>astropulse</name> </app> <file_info> <name>ap_5.00r103_SSE3.exe</name> <executable/> </file_info> <app_version> <app_name>astropulse</app_name> <version_num>500</version_num> <file_ref> <file_name>ap_5.00r103_SSE3.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>astropulse_v5</name> </app> <file_info> <name>ap_5.03r112_SSE3.exe</name> <executable/> </file_info> <app_version> <app_name>astropulse_v5</app_name> <version_num>503</version_num> <file_ref> <file_name>ap_5.03r112_SSE3.exe</file_name> <main_program/> </file_ref> </app_version> </app_info> My SETI app is "AK_v8_win_SSSE3x.exe" Using a Core 2 Duo E6600 and BOINC 6.4.5 |
FaaRsiDe Send message Joined: 20 Feb 00 Posts: 6 Credit: 50,080,582 RAC: 393 |
JarrettH... I do not believe you are receiving no SAH workunits due to your optimized-AP. I am running stock AP app and SAH 6.4.5 and have received NO SAH workunits either for approx. one week. My belief is that something is up with the overall project and scheduling/transmission of SAH workunits. I could be wrong, but have no other explanation, and have not yet received any response from the project regarding this. FaaRsiDe |
Josef W. Segur Send message Joined: 30 Oct 99 Posts: 4504 Credit: 1,414,761 RAC: 0 |
It's my distinct impression that difficulty getting MB work is an issue with BOINC 6.4.x and later. I'm using an older version of BOINC which simply asks for enough work to fill xxxx seconds rather than having separate requests by resource. My project preferences are set to ask for MB work but allow other work, and I've had no difficulty getting MB work. Since the beginning of March, there was one work request when the Scheduler said it didn't have any, and one where it delivered an AP_v5 WU because it didn't have any MB. All others got MB work, though with the way I manage my dial-up connection that only amounts to about 50 work requests. Joe |
Byron S Goodgame Send message Joined: 16 Jan 06 Posts: 1145 Credit: 3,936,993 RAC: 0 |
|
dnolan Send message Joined: 30 Aug 01 Posts: 1228 Credit: 47,779,411 RAC: 32 |
It's my distinct impression that difficulty getting MB work is an issue with BOINC 6.4.x and later. I'm using an older version of BOINC which simply asks for enough work to fill xxxx seconds rather than having separate requests by resource. My project preferences are set to ask for MB work but allow other work, and I've had no difficulty getting MB work. Since the beginning of March, there was one work request when the Scheduler said it didn't have any, and one where it delivered an AP_v5 WU because it didn't have any MB. All others got MB work, though with the way I manage my dial-up connection that only amounts to about 50 work requests.Joe Joe, not that it's a PROBLEM, per-se, but I don't use any 6.x.xx versions of Boinc, and as per this post, I don't really get much in the way of MB. The hosts referenced are all using 5.10.45, except one 5.10.28. -Dave |
Cosmic_Ocean Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 |
It's my distinct impression that difficulty getting MB work is an issue with BOINC 6.4.x and later. I'm using an older version of BOINC which simply asks for enough work to fill xxxx seconds rather than having separate requests by resource. My project preferences are set to ask for MB work but allow other work, and I've had no difficulty getting MB work. Since the beginning of March, there was one work request when the Scheduler said it didn't have any, and one where it delivered an AP_v5 WU because it didn't have any MB. All others got MB work, though with the way I manage my dial-up connection that only amounts to about 50 work requests.Joe I think it's not just limited to 6.4.x +.. I run 6.2.19 and have all four checkboxes selected (MB, AP, AP_v5, allow for others) and only get ap_v5..nothing else..whether 100 seconds are requested, or 2M seconds are requested. If I go to a venue that only allows MB and no others, I get 1-20 MBs per request without any problems. I'm thinking server-side is to blame. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
arkayn Send message Joined: 14 May 99 Posts: 4438 Credit: 55,006,323 RAC: 0 |
|
Cosmic_Ocean Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 |
Yeah, I did that a few times and decided it was too much of a hassle. I'll just crunch away with ap_v5. I get more credits/second with that anyway. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
arkayn Send message Joined: 14 May 99 Posts: 4438 Credit: 55,006,323 RAC: 0 |
|
SATAN Send message Joined: 27 Aug 06 Posts: 835 Credit: 2,129,006 RAC: 0 |
The last time I tried to crunch with the optimised packages, I noticed there is something missing from the downloaded files. If you compare the app_info_xml and the other downloaded files things do not match up. I can't find what it is off hand, but it stops the client asking for MB units. I found this with 6.2.19 and anything later. Will have a look around tomorrow and see if I can find the problem again. |
Cosmic_Ocean Send message Joined: 23 Dec 00 Posts: 3027 Credit: 13,516,867 RAC: 13 |
I built my app_info by hand by looking at the app_infos for ak_v8 and the two different AP's. I know the apps were installed correctly and it all works fine, because I can do all three kinds of work without problems. I don't think the order of the <app> declarations matter, but mine goes MB, AP, AP_v5, and I only have the latest version specified for all three (v5 only has one version..right? 5.03). Like I said, if I turn AP off with a venue change, or run the cache dry and change the app_info to MB-only, I have no problem getting work that way, but with the presence of an ap_v5 app, that's all the server sends. Linux laptop: record uptime: 1511d 20h 19m (ended due to the power brick giving-up) |
W5GA, W5TAT, W8QR, K6XT Send message Joined: 25 Sep 99 Posts: 42 Credit: 23,144,377 RAC: 6 |
Same here. No SETI since I turned on AP in SETI prefs. Today I tried turning off both AP (5 and 5r3) in SETI prefs but so far still will not download any SETI. I use the Lunatics enhanced V10, BOINC 6.4.5. Will BOINC not download any SETI apps until I complete all AP now in my cache? |
W5GA, W5TAT, W8QR, K6XT Send message Joined: 25 Sep 99 Posts: 42 Credit: 23,144,377 RAC: 6 |
R. Haselgrove told me on another list that there are still old V5 AP units to be cleaned up by 5.00. So I've kept both AP 5.00 and 5.03 in app_info. He said the older units are mostly already crunched by others so if I crunch one of these I'm the wingman, get nearly instant credit. Art |
SoNic Send message Joined: 24 Dec 00 Posts: 140 Credit: 2,963,627 RAC: 0 |
I cannot process this kind of units because every time that I select in options to process them, I do receive ONLY this kind of units, rendering useless my GPU/CUDA. A change in the policy is needed to prevent hogging of the Boinc by those units. If you want to process this kind of units, leave the original SETI units to live too... |
MadMaC Send message Joined: 4 Apr 01 Posts: 201 Credit: 47,158,217 RAC: 0 |
Have you looked at your app_info file If you used the one that came with the download, you will only get 5.03 wu's. You need to merge it with your existing app_info file so that you continue to get MB units as well as astropulse. There are plenty of people more qualified than me who can help you with that.. |
ENTERPRISE Send message Joined: 10 Mar 01 Posts: 12 Credit: 358,790 RAC: 0 |
I think I am having the same problem. I run AP V5, and it runs like dialup. It used to zip right along. Now messege says over 300 hrs. to complete. Enterprise with team Bill2001 |
elgar Send message Joined: 21 May 99 Posts: 69 Credit: 2,687,478 RAC: 0 |
I started getting AP units then realized I hadn't updated the location on my 'home' settings not to accept them. Dozens of AP's were in the queue and no CUDA, so I aborted the transfer and changed the settings. Only 2 got through but I'm still processing CUDA at the same time. Why would BOINC try and shove dozen's of APs and no CUDA work units on somebody at 100hrs+? Anyway, computer location solves it but it still seems like a bad default behaviour on BOINC's part. |
Fred J. Verster Send message Joined: 21 Apr 04 Posts: 3252 Credit: 31,903,643 RAC: 0 |
Hi, apart from having little MB WU's to crunch and a lot of AP V5.03, my hosts do have work. My fastest host is now crunching EINSTEIN, although 64 results have passed? Has received, since yesterday, a new load of AP (V5.03) WU's. All have BOINC versions from 6.5.4 and up (except Crunch3r's 6.0.1 on my Laptop). Seen no real error's, only my pending has risen from 32K to 69K! |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
The easiest solution to prevent AP's from hitting your machine is to go to your personal seti page click on seti preferences. then unclick ap, ap v5.0 and accept work from other apps. Also look into the combo Optimized apps this will allow you to run AP WU's and Cuda at the same time. THe opt ap for AP 5.03 drastically reduces the completion time on the WU's In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
©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.