Posts by Alinator

41) Message boards : News : Separation Modified Fit Release (Message 58999) Posted 20 Jun 2013 by Alinator Post: Yes, and if you're running an app_info (to keep nBody under better control for example) you'll need to edit the <name> element for MWSMF as well.
42) Message boards : News : Separation Modified Fit Release (Message 58995) Posted 20 Jun 2013 by Alinator Post: Confirmed. I have a couple now on one of my hosts, so now the next adventure begins! ;-) <edit> I take it giving it a unique name did the trick?
43) Message boards : News : Separation Modified Fit Release (Message 58989) Posted 20 Jun 2013 by Alinator Post: OK, what's the story here? There doesn't seem to be any of the MWSMF in the field. The server status page shows 500 ready and zero sent and has been that way for over 24 hours.
44) Message boards : Number crunching : Calculation error on all received WUs (Message 58987) Posted 20 Jun 2013 by Alinator Post: Hmmmm.... Well, I'll keep my fingers crossed for Steffen on that. It sure would be a lot easier than any of the other options. ;-)
45) Message boards : Number crunching : Calculation error on all received WUs (Message 58985) Posted 20 Jun 2013 by Alinator Post: OK, as I mentioned in the other message, from looking at your host details the problem here seems to be project switched from sending your host work targeted for the AMD specific CAL based application (MilkyWay@Home 0.82 i686-pc-linux-gnu (ati14)) to the openCL version (MilkyWay@Home 1.02 i686-pc-linux-gnu (opencl_amd_ati)). Unfortunately, development of openCL for AMD GPU's has been far less than seamless and determining a given host's exact capabilities can be complex, convoluted, and confusing (CCC, pun intended)! When you add in the BOINC mechanisms for getting the right application to the right target host, it can get to be a real nightmare scenario given the almost limitless number of possible combinations in the field. :-( So what to do about it in your case? The first thing to try would be to update to the latest driver (assuming you're not on it already) and see if that fixes the signal 11 the tasks are faulting out on. If you're already using the latest driver, you could try rolling back to an earlier version to see if the project picks up on that and switches back to sending work targeted to the CAL based application. If neither of those options work, then the only other alternative is to go to the anonymous platform. This means you would have to make up an app_info.xml filo and install it as well as the correct application file(s) manually in the MilkyWay directory. HTH
46) Message boards : News : Separation Modified Fit Release (Message 58977) Posted 19 Jun 2013 by Alinator Post: I don't know if this belongs here but every work unit I get is calcualted until 100% and then results in 'calculation error'. All of those are either de_separation or ps_separation. Application is Milkyway@home 1.02 (opencl_amd_ati). I tried it ~1 week ago with one batch of workunits and I tried it again today. This is one of the results: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=504866748 I guess this is the problem Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' Error reading astronomy parameters from file 'astronomy_parameters.txt' Trying old parameters file but I can't find such a file on my PC (I tried sudo updatedb && locate astronomy_parameters.txt with no result) This isn't the application being discussed in this thread, and it would be better to post this in Number Crunching. Anyway, the 'error' message in the stderr isn't the problem in this case, the problem is the project started sending you work for the openCL version rather than the CAL based one. My guess would be most likely a driver version issue.
47) Message boards : Number crunching : MW Separation Modified Fit (Message 58973) Posted 19 Jun 2013 by Alinator Post: Has anybody actually gotten a task for either the CPU or the GPU yet? The server status page shows 500 task ready to send with none in progress, and it hasn't seemed to change at all since they appeared.
48) Message boards : News : N-Body 1.18 (Message 58966) Posted 18 Jun 2013 by Alinator Post: Bad 1.18 task here
49) Message boards : Number crunching : new app_config.xml for the new applications? (Message 58961) Posted 18 Jun 2013 by Alinator Post: You only need to do it once. As long as the app_config.xml file is in your project folder, it will work even when the app name changes. Be aware that if you reset the project or detach/reattach then you would need to insert the file again. Agreed. I only recently started taking BOINC v7 seriously, so I haven't fully explored all the possibilities app_config brings to the table. ;-)
50) Message boards : News : update for users not getting CPU workunits (Message 58960) Posted 18 Jun 2013 by Alinator Post: Rick - part of the volunteer process is helping the team through times of problems, as well as when the project is running smoothly. It's possible that you haven't got any work units because of a problem that affects others as well - so it's important for you to stick around to help the devs correlate symptoms and work towards a fix. If you'd like to participate in other astronomy-related BOINC projects whilst you're waiting, take a look at theSkyNetPOGS. The part I found amusing was if you take a look, his host was back in the game about 6 hours before he posted. ;-)
51) Message boards : News : Separation Modified Fit Release (Message 58953) Posted 18 Jun 2013 by Alinator Post: There aren't currently any work units up yet. I will be pushing out the newest version today as well as some work units. The new separation should be labeled Milkyway Separation Modified Fit. As far as when we will have a 32bit Windows application, I am not sure. It is the next thing on my list to do after getting this released and stable. Jake W. Hmmmm... When I look at the projects application page, the Modified Fit part doesn't show up in section title line. Likewise, it's missing from the text on the app selection line on the project specific preferences. Not a big deal, but I think we've had enough confusion lately. I imagine you'd like to minimize that going forward. ;-)
52) Message boards : Number crunching : new app_config.xml for the new applications? (Message 58950) Posted 18 Jun 2013 by Alinator Post: It depends. If you are currently running 'stock', no you shouldn't have to do anything other than make sure your project prefs allow it. If you run on the anonymous platform, then yes you will have to modify your app_info to run it.
53) Message boards : News : update for users not getting CPU workunits (Message 58942) Posted 18 Jun 2013 by Alinator Post: No CPU tasks for many days. All GPU tasks OK. Tons of 'em. Instead I'm running SETI (V7 & V6) CPU tasks, OK. Running BOINC 6.12.34. Please, please don't ask me to update/upgrade anything ... my stuff just works, OK! Best Regards, Ray FWIW if I click "Update" MW@H seems not to even try to get CPU tasks!!!??? Give it some time. If you wait, they will come. ;-)
54) Message boards : News : update for users not getting CPU workunits (Message 58937) Posted 17 Jun 2013 by Alinator Post: You may have to wait a bit to get some. With all the hosts that were cut off from MW_Sep recently they may have some trouble keeping up with demand in the short term.
55) Message boards : News : update for users not getting CPU workunits (Message 58935) Posted 17 Jun 2013 by Alinator Post: TADA!!!! Guess they were working on the problem all along! ;-) <edit> Confirmed, one of my hosts W/O the workaround just drew MW_sep work.
56) Message boards : News : update for users not getting CPU workunits (Message 58933) Posted 17 Jun 2013 by Alinator Post: We're talking about the CPU MW Separation tasks in this thread, not nBody.
57) Message boards : News : Separation Modified Fit Release (Message 58932) Posted 17 Jun 2013 by Alinator Post: ... Since the depreciation fiasco there has been no work for my 32bit cpu machine. I did post a workaround for that in NC.
58) Message boards : News : Separation Modified Fit Release (Message 58924) Posted 17 Jun 2013 by Alinator Post: Then I suggest you give it a unique 'friendly_name' so we can tell the difference in the project specific prefs and the other BOINC generated info pages. Preferably before you actually roll it out.
59) Message boards : Number crunching : CPU MW Workaround for GPU-less Winboxes (Message 58896) Posted 15 Jun 2013 by Alinator Post: Notes: 3.) If modifying the app_info file for 64 bit hosts, the file name must be changed in both locations.
60) Message boards : News : update for users not getting CPU workunits (Message 58895) Posted 15 Jun 2013 by Alinator Post: Workarround does not work on: <snip hardware specs> sorry Hmmmm..... First, since this was about the workaround it would have been better to post this in the NC thread rather than here in the News forum. Second, you have your hosts hidden, so that makes it kind of hard for me to make any observations about the problem might be. Anyway, I have a couple of questions: 1.) By not working, did you mean your hosts would not download and run a CPU MW task (NOT nBody and/or GPU anything) from the project? Here is the host I used to test the workaround on and it does work exactly as I intended it to work. 2.) I noted that all three of the hosts you listed are multi-cored, GPU equiped machines. Given your RAC I have to assume you are running them with all computing resources enabled. So the question is what were you expecting from a workaround that was specifically tailored for single (or at most dual) cored hosts without any GPU capacity?

Previous 20 · Next 20