Posts by kashi
|
1)
(Message 5082)
Posted 3 Dec 2016 by kashi Post: Hi cliff, A complex app_info.xml like that is beyond the ability of most GPU crunchers. Some of the theoretical possible configurations also exceed the available BOINC command options. Running 3 separate GPU projects concurrently on the one box is already quite an achievement. I don't have a computer with 2 or more graphics cards any more so I can't experiment myself. Had an overclocked HD 5970 and HD 5870 and reached 149th world ranking but they really sucked the juice. When electricity tariffs increased greatly here was forced to reduce the amount of GPU crunching I do. Now even have one box that doesn't have a separate graphics card. Not jelly though, still like to see others enjoying going to town with multiple powerful graphics cards. |
|
2)
(Message 5079)
Posted 2 Dec 2016 by kashi Post: I see. You had me confused when you said BOINC wouldn't accept an app_config.xml with the correct app name of "period_search" as shown in client_state.xml. I had a look at your configuration and realised you have 3 Nvidia cards and are running them on different projects. This is a complication that may cause a simple app_config.xml file to not work as expected. For this it may be necessary to experiment with also using the <coproc> option in app_config.xml file in combination with an app_info.xml file. I don't know exactly what you are trying to achieve but <exclude_gpu> and <ignore_nvidia_dev> are other options available to give fine grain control when multiple Nvidia cards are being used. I had related problems years ago when running multiple graphics cards caused by the cards being enumerated differently by BOINC and the individual projects. There was no app_config.xml back then only app_info.xml. Thankfully I only need to deal with one card now. Hopefully you won't find the challenge too frustrating. Good luck with it. |
|
3)
(Message 5077)
Posted 1 Dec 2016 by kashi Post: You ask for an app_info.xml file and then refer to an app_config.xml file. They are different. If you get them mixed up it will cause you confusion. For example an app_info.xml file requires BOINC to be stopped and restarted before it works, whereas an app_config.xml file can be activated by clicking "Read config files" option in BOINC Manager. An incorrectly configured app_info.xml file will immediately delete an existing cache of tasks as soon as BOINC is restarted. |
|
4)
(Message 1887)
Posted 6 Oct 2013 by kashi Post: I think DPAD possibly refers to Distributed Particle Accelerator Design now more commonly known as Muon. There is original Stephen Brook Muon and a yoyo@home BOINC wrapper Muon. |
|
5)
(Message 1745)
Posted 11 Sep 2013 by kashi Post: No it's not just you. The same thing happened about 3 weeks ago. The administrator will need to fix the validator and you will then need to wait until the 3rd task iteration is returned. |
|
6)
(Message 1561)
Posted 22 Aug 2013 by kashi Post: Thank you. |
|
7)
(Message 1555)
Posted 22 Aug 2013 by kashi Post: Validator is not working correctly. All my tasks completed recently where wingman has also reported completed task are status "Completed, validation inconclusive". It is not just my computer, my wingmen all have numbers of "validation inconclusive" tasks too. All my pending tasks that were completed and reported recently by wingmen are also "validation inconclusive". Last task that validated successfully was reported by my computer about 6 hours ago. |