Posts by Steveplanetary

1) Message boards : Number crunching : All my units erroring out... (Message 51985) Posted 16 Dec 2011 by Steveplanetary Post: That sounds very interesting. Please keep us posted.
2) Message boards : Number crunching : All my units erroring out... (Message 51964) Posted 13 Dec 2011 by Steveplanetary Post: I have the same problem with Windows 7 x64 Home Premium on a 2nd gen. Intel Core i5 quad. Not only do all the nbody v.84s error out, but the longest initial time on them was 60 seconds. That's WAY shorter than they used to be. These workunits should finish quickly. It looks like you aren't getting errors anymore. No. No errors, Matt. Are these short WUs for testing purposes?
3) Message boards : Number crunching : All my units erroring out... (Message 51944) Posted 13 Dec 2011 by Steveplanetary Post: These are the only out of the ordinary messages: 12/11/2011 10:33:37 AM \| Milkyway@home \| [error] State file error: missing application file milkyway_nbody_0.80_windows_x86_64__mt 12/11/2011 10:33:37 AM \| Milkyway@home \| [error] No app version found for app milkyway_nbody platform windows_x86_64 ver 80 classmt; discarding nbody-Plum_Embedded_185113_0
4) Message boards : Number crunching : All my units erroring out... (Message 51943) Posted 13 Dec 2011 by Steveplanetary Post: I ran many n-body V.80 this morning along with milky@home 0.88's. ( all passed with flying colors ) This last download included n-body V.84 and more 0.88's. All the new n-body V.84 failed!!!!! I'd send all the pages of the reasons why but that's redundant because those that have preceaded me have the same problem. Is there anything I can do to solve this problem? I have the same problem with Windows 7 x64 Home Premium on a 2nd gen. Intel Core i5 quad. Not only do all the nbody v.84s error out, but the longest initial time on them was 60 seconds. That's WAY shorter than they used to be.
5) Message boards : Number crunching : Results not uploading? (Message 51818) Posted 3 Dec 2011 by Steveplanetary Post: Thanks. That makes a lot of sense.
6) Message boards : Number crunching : Results not uploading? (Message 51816) Posted 3 Dec 2011 by Steveplanetary Post: Thank you both for the explanation. Steve
7) Message boards : Number crunching : Results not uploading? (Message 51814) Posted 3 Dec 2011 by Steveplanetary Post: So if I understood correctly, that's just the way M@H does it. I also thought I read that this is a time saving measure. But if that is the case there is still something I don't understand...doesn't it take the same length of time to send results back whether or not there is a printout?
8) Message boards : Number crunching : Results not uploading? (Message 51812) Posted 3 Dec 2011 by Steveplanetary Post: I have pasted 40 lines from my Event Log below. Most of them are from Einstein@Home because they illustrate the difference between E@H and M@H. I draw your attention to the lines in bold. The last two bold E@H lines indicate the resuming and completion of WU ending in 1264_1. These are followed by lines showing upload of the results from that WU. The bold M@H lines also indicate the starting or resuming of WUs, along with lines indicating their completion, but there are no lines indicating upload of results. Would somebody, perhaps a moderator or administrator, please tell us the reason for the difference? TIA 12/3/2011 2:29:41 AM \| Milkyway@home \| Resuming task nbody-rebuild-clr_327415_3 using milkyway_nbody version 66 12/3/2011 2:50:44 AM \| Milkyway@home \| Sending scheduler request: To fetch work. 12/3/2011 2:50:44 AM \| Milkyway@home \| Reporting 1 completed tasks, requesting new tasks for NVIDIA GPU 12/3/2011 2:50:47 AM \| Milkyway@home \| Scheduler request completed: got 1 new tasks 12/3/2011 2:56:51 AM \| Milkyway@home \| Computation for task ps_separation_82_2s_coadd_1_5836_0 finished 12/3/2011 2:56:51 AM \| Einstein@Home \| Restarting task p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1 using einsteinbinary_BRP4 version 100 12/3/2011 3:33:31 AM \| Einstein@Home \| Resuming task LATeah0069S_864.0_196250_0.0_0 using hsgamma_FGRP1 version 23 12/3/2011 3:33:31 AM \| Einstein@Home \| Resuming task h1_0411.95_S6GC1__1344_S6BucketA_1 using einstein_S6Bucket version 101 12/3/2011 3:33:31 AM \| Einstein@Home \| Resuming task LATeah0069S_864.0_453600_0.0_0 using hsgamma_FGRP1 version 23 12/3/2011 3:33:31 AM \| Einstein@Home \| Resuming task LATeah0069S_928.0_104650_0.0_1 using hsgamma_FGRP1 version 23 12/3/2011 3:51:38 AM \| Milkyway@home \| Sending scheduler request: To fetch work. 12/3/2011 3:51:38 AM \| Milkyway@home \| Reporting 1 completed tasks, requesting new tasks for NVIDIA GPU 12/3/2011 3:51:40 AM \| Milkyway@home \| Scheduler request completed: got 1 new tasks 12/3/2011 3:57:04 AM \| Milkyway@home \| Starting task ps_separation_82_2s_mix0_2_978029_1 using milkyway version 82 12/3/2011 4:34:05 AM \| Milkyway@home \| Resuming task nbody-rebuild-clr_327415_3 using milkyway_nbody version 66 12/3/2011 4:48:46 AM \| Milkyway@home \| Computation for task nbody-rebuild-clr_327415_3 finished 12/3/2011 4:48:46 AM \| Einstein@Home \| Resuming task LATeah0069S_864.0_196250_0.0_0 using hsgamma_FGRP1 version 23 12/3/2011 4:48:46 AM \| Einstein@Home \| Resuming task h1_0411.95_S6GC1__1344_S6BucketA_1 using einstein_S6Bucket version 101 12/3/2011 4:48:46 AM \| Milkyway@home \| Starting task ps_separation_82_2s_mix1_2_1014840_1 using milkyway version 88 12/3/2011 4:48:46 AM \| Milkyway@home \| Starting task ps_separation_82_2s_mix3_2_952042_1 using milkyway version 88 12/3/2011 4:58:09 AM \| Milkyway@home \| Computation for task ps_separation_82_2s_mix0_2_978029_1 finished 12/3/2011 4:58:09 AM \| Einstein@Home \| Restarting task p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1 using einsteinbinary_BRP4 version 100 12/3/2011 5:00:54 AM \| Einstein@Home \| Computation for task p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1 finished 12/3/2011 5:00:54 AM \| Einstein@Home \| Starting task p2030.20100913.G48.73+01.03.S.b4s0g0.00000_1704_1 using einsteinbinary_BRP4 version 100 12/3/2011 5:00:57 AM \| Einstein@Home \| Started upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_0 12/3/2011 5:00:57 AM \| Einstein@Home \| Started upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_1 12/3/2011 5:00:59 AM \| Einstein@Home \| Finished upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_0 12/3/2011 5:00:59 AM \| Einstein@Home \| Finished upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_1 12/3/2011 5:00:59 AM \| Einstein@Home \| Started upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_2 12/3/2011 5:00:59 AM \| Einstein@Home \| Started upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_3 12/3/2011 5:01:01 AM \| Einstein@Home \| Finished upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_2 12/3/2011 5:01:01 AM \| Einstein@Home \| Finished upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_3 12/3/2011 5:01:01 AM \| Einstein@Home \| Started upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_4 12/3/2011 5:01:01 AM \| Einstein@Home \| Started upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_5 12/3/2011 5:01:03 AM \| Einstein@Home \| Finished upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_4 12/3/2011 5:01:03 AM \| Einstein@Home \| Finished upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_5 12/3/2011 5:01:03 AM \| Einstein@Home \| Started upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_6 12/3/2011 5:01:03 AM \| Einstein@Home \| Started upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_7 12/3/2011 5:01:05 AM \| Einstein@Home \| Finished upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_6 12/3/2011 5:01:05 AM \| Einstein@Home \| Finished upload of p2030.20100913.G44.55+00.20.S.b5s0g0.00000_1264_1_7
9) Message boards : Number crunching : N-body core interactions? (Message 51754) Posted 21 Nov 2011 by Steveplanetary Post: Here are some questions from a newb who is not a computer scientist. I have a quad core computer, so of course when I am crunching a N-body simulation, it makes sense that there would be at least one thread per core. And on the 2nd page of the Add Project window, MW is shown as having multicore support, as well as Nvidia GPU support. My questions are these: Are the 4 parts of the task that are using all 4 cores of my processor talking to each other, sharing data? Does one core do a calculation that is passed on to another core to be used in another calculation? Or do the cores just pass on the results of their calculations to the application, which then sorts it all out? And is there just one thread per core, or more? Any information along these lines would be greatly appreciated. Steve