Posts by Alan Barnes

1) Message boards : News : Clearing the Queue (Message 66705) Posted 19 Oct 2017 by Alan Barnes Post: But that doesn't entirely explain why some "Didn't need" WUs which were cancelled attracted credit whilst others didn't. AB
2) Message boards : News : Clearing the Queue (Message 66701) Posted 19 Oct 2017 by Alan Barnes Post: I have noticed that recently a number of completed work-units (MilkyWay@Homev1.46) have been marked as "Didn't need", only some of which have been allocated credit. Please explain! Also I obtained a number of "Completed, can't validate" results. Again I suppose this is due to the recent Transitioner problems etc. Alan Barnes
3) Message boards : News : Bad Runs Put Up Over The Weekend (Message 66637) Posted 17 Sep 2017 by Alan Barnes Post: Same here although very few completing at all and none on Linux Ubuntu 14.04. Alan
4) Message boards : Number crunching : N-Body long processing time (Message 62206) Posted 22 Aug 2014 by Alan Barnes Post: I too am experiencing problems with N-body simulation v1.42 -- a job ran for almost 17 hours on 2 CPUs reached 100% and then promptly crashed with a computation error. 805862330 596473367 12 Aug 2014, 14:32:47 UTC 22 Aug 2014, 21:41:18 UTC Error while computing 60,819.13 103,158.20 --- MilkyWay@Home N-Body Simulation v1.42 (mt) It was running on GenuineIntel Pentium(R) Dual-Core CPU T4500 @ 2.30GHz [Family 6 Model 23 Stepping 10] (2 processors) We are not amused!! Alan Barnes
5) Questions and Answers : Wish list : Credit for N-body Simulation (Message 61713) Posted 11 May 2014 by Alan Barnes Post: Why is the credit gained for running the N-Body Simulation so miserly? It uses two CPUs on my machine and runs for about 2 hours (elapsed time) and yet the credit gained is considerably less than processes running for a shorter time on only one CPU. Alan Barnes For example: 739342477 553083608 10 May 2014, 23:33:18 UTC 11 May 2014, 9:08:28 UTC Completed and validated 4,686.24 4,617.28 106.88 MilkyWay@Home v1.01 739341968 553054361 10 May 2014, 23:33:18 UTC 11 May 2014, 9:08:28 UTC Completed and validated 9,567.88 9,400.50 213.76 Milkyway@Home Separation (Modified Fit) v1.30 739341961 553083233 10 May 2014, 23:33:18 UTC 11 May 2014, 9:08:28 UTC Completed and validated 4,648.01 4,534.58 106.88 Milkyway@Home Separation (Modified Fit) v1.30 739335755 553078635 10 May 2014, 23:33:18 UTC 11 May 2014, 9:08:28 UTC Completed and validated 7,613.17 14,580.35 58.87 MilkyWay@Home N-Body Simulation v1.40 (mt) 739335754 553078634 10 May 2014, 23:33:18 UTC 11 May 2014, 9:08:28 UTC Completed and validated 7,143.05 13,678.46 54.64 MilkyWay@Home N-Body Simulation v1.40 (mt)
6) Questions and Answers : Macintosh : Repeated Computational Errors on MacOSX (Message 60500) Posted 1 Dec 2013 by Alan Barnes Post: Further to my earlier post: the tasks all seem terminate with the error message: <core_client_version>7.2.33</core_client_version> <![CDATA[ <message> process got signal 5 </message> <stderr_txt> dyld: unknown required load command 0x80000022 </stderr_txt> ]]> Presumably some update of a system call is incompatible with the older version on my machine. Alan Barnes
7) Questions and Answers : Macintosh : Repeated Computational Errors on MacOSX (Message 60499) Posted 1 Dec 2013 by Alan Barnes Post: I am getting repeated computational errors which cause most (though not all) MilkyWay tasks to terminate soon after launching. I am running an oldish version of MacOSX Version 10.5.8 (Darwin 9.8.0) on a GenuineIntel Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz [x86 Family 6 Model 15 Stepping 11](2 processors). I am running BOINC 7.2.33. I have had similar problems with all tasks from Asteroids@Home. OK the machine is prehistoric, but it does successfully run all Einstein@Home projects. Is there a fix? Or is there a subset of MilkyWay applications that will run on older Macs? Curiously two tasks seem to have run successfully: Task 621272327 to completion consuming nearly 2hrs of CPU time Task 622043280 so far running for 0:49:30 Alan Barnes