Strange Action by BOINC/SETI? Please ignore - poster is a dunce
Message boards :
Number crunching :
Strange Action by BOINC/SETI? Please ignore - poster is a dunce
Message board moderation
| Author | Message |
|---|---|
Cruncher-American    Send message Joined: 25 Mar 02 Posts: 1513 Credit: 370,893,186 RAC: 340 
|
I updated my system with GTX 680 from cuda42 to cuda50, and made all the necessary changes in app_info. When restarted, all seems fine except that the application in the Tasks tab is still showing as setiathome_v7 7.00 Cuda42, not cuda50. (The executables in the project folder are the cuda50 ones, though, and Task Manager shows they are being executed here). Is this just an artifact of the way BOINC works? Also, I got this from a request for more WUs: 7/25/2013 12:28:49 PM | SETI@home | No tasks sent 7/25/2013 12:28:49 PM | SETI@home | No tasks are available for SETI@home Enhanced 7/25/2013 12:28:49 PM | SETI@home | No tasks are available for SETI@home v7 7/25/2013 12:28:49 PM | SETI@home | No tasks are available for AstroPulse v6 7/25/2013 12:28:49 PM | SETI@home | This computer has reached a limit on tasks in progress 7/25/2013 12:28:49 PM | SETI@home | Project has no tasks available 7/25/2013 12:29:21 PM | SETI@home | Computation for task 16ja09ab.2617.6207.9.12.203_1 finished 7/25/2013 12:29:21 PM | SETI@home | Starting task 16ja09ab.2617.8252.9.12.232_0 using setiathome_v7 version 700 (cuda42) in slot 2 7/25/2013 12:29:23 PM | SETI@home | Started upload of 16ja09ab.2617.6207.9.12.203_1_0 7/25/2013 12:29:27 PM | SETI@home | Finished upload of 16ja09ab.2617.6207.9.12.203_1_0 7/25/2013 12:32:21 PM | SETI@home | Computation for task 17au08ae.4969.7025.8.12.3_0 finished 7/25/2013 12:32:21 PM | SETI@home | Starting task 12au09ab.23204.9883.13.12.59_0 using setiathome_v7 version 700 (cuda42) in slot 1 7/25/2013 12:32:23 PM | SETI@home | Started upload of 17au08ae.4969.7025.8.12.3_0_0 7/25/2013 12:32:26 PM | SETI@home | Finished upload of 17au08ae.4969.7025.8.12.3_0_0 7/25/2013 12:33:55 PM | SETI@home | Sending scheduler request: To fetch work. 7/25/2013 12:33:55 PM | SETI@home | Reporting 2 completed tasks 7/25/2013 12:33:55 PM | SETI@home | Requesting new tasks for CPU and NVIDIA 7/25/2013 12:33:57 PM | SETI@home | Scheduler request completed: got 0 new tasks 7/25/2013 12:33:57 PM | SETI@home | No tasks sent 7/25/2013 12:33:57 PM | SETI@home | No tasks are available for SETI@home Enhanced 7/25/2013 12:33:57 PM | SETI@home | No tasks are available for AstroPulse v6 7/25/2013 12:33:57 PM | SETI@home | This computer has reached a limit on tasks in progress 7/25/2013 12:34:56 PM | SETI@home | General prefs: from SETI@home (last modified 05-Apr-2011 20:47:52) Why didn't it ask for more setiathome7 the second time, considering the 2 reported WUs were setiathome7? EDIT: NEVERMIND. The next request got 3 more v7 cudas (OK) and labels them as cuda50 in the task list. Gotta learn some patience, Jon /EDIT ID: 1394767 ·  |
|
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 
|
I updated my system with GTX 680 from cuda42 to cuda50, and made all the necessary changes in app_info. When restarted, all seems fine except that the application in the Tasks tab is still showing as setiathome_v7 7.00 Cuda42, not cuda50. (The executables in the project folder are the cuda50 ones, though, and Task Manager shows they are being executed here). Is this just an artifact of the way BOINC works? That'll be because those tasks were Branded in your client_state.xml as Cuda42 Wu's, if you're got the app_version entries in the right order then fresh work will be branded Cuda5 Also, I got this from a request for more WUs: Probably means there were v7 tasks available to send, but they were VLARs, and VLARs aren't sent to GPUs, so no work sent. Claggy ID: 1394772 · |
|
Cruncher-American Send message Joined: 25 Mar 02 Posts: 1513 Credit: 370,893,186 RAC: 340
|
Thanks, Claggy, I had forgotten (or never known) that client_state.xml has that info in it. Now at least I'll be able to find out about how long it takes my machine to blow through 100 v7 WUs on the GTX680. ID: 1394773 · |
 William  Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
Ignore? what's that? Labels are assigned when a WU is first received - it's a tag in client_state.xml. When you run anonymous, the tag comes from whatever is specified in the first app_version for that type of work. In Lunatics installer created app_infos the extra entries are designed to pick up work in progress - and each entry specifies the app choosen by the user as the one to run WUs tagged that way with. So one app - several tags. If you had made the mistake of having just one entry specifing cuda50 alongside the cuda 50 app you'd have lost all cuda42 marked work (well until it gets resent at least). You could also have swapped apps by keeping the cuda42 tag and just changing the app entries. Then you would still be running the cuda50 app but the work would be tagged 42. Having the tag reflect what app is running was a deliberate installer design decision. As you discovered this only applies to new work. A person who won't read has no advantage over one who can't read. (Mark Twain) ID: 1394776 · |
|
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4
|
I updated my system with GTX 680 from cuda42 to cuda50, and made all the necessary changes in app_info. Rather than doing all that, and risking mucking up, just rerun the Lunatics Installer, and select a different Cuda app, the order of app_version sections will whatever you selected, then the others. Claggy ID: 1394780 · |
|
William Send message Joined: 14 Feb 13 Posts: 2037 Credit: 17,689,662 RAC: 0 |
I updated my system with GTX 680 from cuda42 to cuda50, and made all the necessary changes in app_info. I suspect he did rerun the installer and meant the extra changes to count etc. A person who won't read has no advantage over one who can't read. (Mark Twain) ID: 1394784 · |
|
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4
|
I updated my system with GTX 680 from cuda42 to cuda50, and made all the necessary changes in app_info. He hinted that he was going to edit his app_info in this thread: How Does BOINC Chose Which CUDA App to Run? Claggy ID: 1394786 · |
kittyman  Send message Joined: 9 Jul 00 Posts: 51469 Credit: 1,018,363,574 RAC: 1,004
|
LOL....... The kitties have hinted at a few thingys too. What worked and what did not is a matter of Seti history. "Freedom is just Chaos, with better lighting." Alan Dean Foster 
ID: 1394795 · |
|
Cruncher-American Send message Joined: 25 Mar 02 Posts: 1513 Credit: 370,893,186 RAC: 340
|
Well, as the OP, I can quell the Great Update Debate above by telling you all that Claggy was sort of correct. I did run the Lunatics installer, carefully choosing cuda50. I then also edited app_info to fix 1) count (from 1 -> 0.33) and (for AP) avg_ncpu & max_ncpu -> 1.0. Claggs, you win the Grand Prize of 37.45567 credits (subject to Credit New, of course). ID: 1394821 · |
©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.