Posts by SandJ

1) Message boards : Number crunching : Congratulations Stefan on doing Task 2000000000 (Message 66237) Posted 22 Mar 2017 by SandJ Post: I just noticed the task numbers have rolled round 2,000,000,000 and wondered what happened to that task. Task number 2000000000 was done by user Stefan on computer (14 seconds per work unit - wow!) for work unit.
2) Message boards : News : New N-Body Release (Message 57642) Posted 25 Mar 2013 by SandJ Post: Just extending the deadline wouldn't take care of the problem for a number of reasons. <snip> Helpful, thank you. Don't get me wrong here, I see your point on this matter and agree with it in principle Here we go... However, don't forget this was announced ahead of time as a Beta run for the application so you really have to be willing to eat the lost time for tasks which go down the can for whatever the reason. I wasn't expecting beta runs on a project I joined about 5 years ago! Mind you, it seems most of the projects are either claiming to be Alpha or Beta status regardless of their age or stability. On just one data packet, that 'lost time' was about 3 months of processor time. A seriously big ouch when multiplied across all the affected data packets. Anyway, I see the one remaining one of these data packets I had has now been credited as a wingman managed to get it finished (in just under 22 days) (although someone is still crunching it) so I'll slope off happy.
3) Message boards : News : New N-Body Release (Message 57541) Posted 18 Mar 2013 by SandJ Post: Given the problems we saw early on, I think it's time to cut bait on these (especially if they're being 'forced' to run single threaded by the BOINC version you're running). That would be rather annoying for those of us with "Completed, validation inconclusive" packets with wingmen who keep running out of time. If the deadline were extended, they would mostly finish and the credits then get allocated. If these 1.06 runs are to be culled, can it be done such that we get the credits for the time we've contributed, to prevent some serious disappointment?
4) Message boards : Number crunching : Lots of "Completed, validation inconclusive" errors (Message 57540) Posted 18 Mar 2013 by SandJ Post: This work unit I completed successfully a month ago is still "Completed, validation inconclusive". The most recent attempt by another wingman did indeed run out of time and it has been issued yet again, this time to a slower machine so it will also probably run out of time. *Extending the deadline for the MilkyWay@Home N-Body Simulation v1.06* jobs might actually see these being completed**, instead of wastefully started, re-started and re-started. They need to be permitted to use something like 21 days.
5) Message boards : Number crunching : Lots of "Completed, validation inconclusive" errors (Message 57413) Posted 4 Mar 2013 by SandJ Post: Thank you for the explanations and I see there has been discussion about long N-Body packets elsewhere. I am now watching work unit 291524669 every day. The most recent attempt has timed out and it has now been farmed out to a slightly slower machine than the last one. So far this work unit has used up some 46 days of processor time. Previously, I would have whinged about this. With hindsight I see the benefit of distributed processing: having a few PCs ut on the internet tied up with such a work unit is far better than an entire processor of a research team being tied up for 46 days. Anyway, I do hope this packet finally gets validated. At my average of 775 credits per run time hour, it is worth between 140k and 244k credits. At my average of 5,800 credits per CPU hour, this work unit is worth 2.5 million credits. :-D I know that if I get nothing for what was 18 days of CPU time over 7.6 elapsed days, I won't be happy! I wonder if it is worth extending the deadline by another week or two for these long N-Body packets so they can be validated? Please.
6) Message boards : News : New N-Body Release (Message 57282) Posted 19 Feb 2013 by SandJ Post: Shall I let it run, even after the Deadline ??? Will that help the science - to validate this WU id 291600433 ? :o) It will take at least two times 1 milion 800 thousand seconds in total ... on my core i7 720QM 1.6 GHz ! ... even though: I let it run alone sometimes (TurboBoosts to 2.8 GHz). Ah, so I am not alone in having a mega-second WU. I had one: http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3148&nowrap=true#57268 I seem to be getting a succession of "Completed, validation inconclusive" results. Task Work unit Computer Sent Time reported or deadline Status Run time CPU time Credit Application 399803703 291524669 462901 10 Feb 2013 \| 12:36:32 UTC 18 Feb 2013 \| 3:52:29 UTC Completed, validation inconclusive 659,757.00 1,561,110.00 pending MilkyWay@Home N-Body Simulation v1.06 (opencl_nvidia) I don't know if I ever got any credits for that. :-(
7) Message boards : Number crunching : Lots of "Completed, validation inconclusive" errors (Message 57268) Posted 18 Feb 2013 by SandJ Post: I seem to be getting a succession of "Completed, validation inconclusive" results. Task Work unit Computer Sent Time reported or deadline Status Run time CPU time Credit Application 399362675 308407768 462901 9 Feb 2013 \| 21:42:33 UTC 10 Feb 2013 \| 1:19:10 UTC Completed, validation inconclusive 962.17 164.17 pending MilkyWay@Home v1.02 (opencl_nvidia) 399362671 308311940 462901 9 Feb 2013 \| 21:42:33 UTC 10 Feb 2013 \| 1:19:10 UTC Completed, validation inconclusive 956.65 171.08 pending MilkyWay@Home v1.02 (opencl_nvidia) 399148819 308257986 462901 9 Feb 2013 \| 14:37:56 UTC 9 Feb 2013 \| 21:42:33 UTC Completed, validation inconclusive 956.90 167.38 pending MilkyWay@Home v1.02 (opencl_nvidia) 399803703 291524669 462901 10 Feb 2013 \| 12:36:32 UTC 18 Feb 2013 \| 3:52:29 UTC Completed, validation inconclusive 659,757.00 1,561,110.00 pending MilkyWay@Home N-Body Simulation v1.06 (opencl_nvidia) 399803697 303617765 462901 10 Feb 2013 \| 12:36:32 UTC 18 Feb 2013 \| 3:53:39 UTC Completed, validation inconclusive 88.47 88.47 pending MilkyWay@Home N-Body Simulation v1.06 (opencl_nvidia) 399803696 297188080 462901 10 Feb 2013 \| 12:36:32 UTC 18 Feb 2013 \| 3:53:39 UTC Completed, validation inconclusive 15.13 14.08 pending MilkyWay@Home N-Body Simulation v1.06 (opencl_nvidia) The ones taking 900 seconds are tolerable, but the one that claims to have taken 18 DAYS of CPU time is VERY annoying. Is it just me, or a general problem?
8) Questions and Answers : Windows : "Process creation failed: A device attached to the system is not functioning" (Message 27645) Posted 13 Jul 2009 by SandJ Post: I would recommend the optimized app anyways: http://zslip.com/milkyway.htm Much faster. So I'll need to find out which version to use (v0.16 or v0.19), then whether it's SSE, SSE 2, SSE 3, SSSE 3, SSE 4.1, SSE 4.2 or x87. Then how to install it. I can't be bothered. I'll just detach from the project. It'd be a lot easier if one could just attach to this project in the ame way as other projects.
9) Questions and Answers : Windows : "Process creation failed: A device attached to the system is not functioning" (Message 27571) Posted 12 Jul 2009 by SandJ Post: Does detatching delete the old files? If not then try resetting MW. No difference: 11/07/2009 10:45:34\|Milkyway@home\|Resetting project 11/07/2009 10:45:50\|Milkyway@home\|Sending scheduler request to http://milkyway.rpi.edu/cgi/cgi 11/07/2009 10:45:50\|Milkyway@home\|Reason: Requested by user 11/07/2009 10:45:50\|Milkyway@home\|Requesting 43200 seconds of new work 11/07/2009 10:45:55\|Milkyway@home\|Scheduler request succeeded 11/07/2009 10:45:55\|Milkyway@home\|Message from server: No work sent 11/07/2009 10:45:55\|Milkyway@home\|Message from server: (reached daily quota of 1 results) 11/07/2009 10:45:55\|Milkyway@home\|Message from server: (Project has no jobs available) 11/07/2009 10:49:28\|Milkyway@home\|Resetting project 11/07/2009 10:49:28\|Milkyway@home\|Detaching from project 11/07/2009 10:50:53\|\|Attaching to http://milkyway.cs.rpi.edu/milkyway/ 11/07/2009 10:50:55\|http://milkyway.cs.rpi.edu/milkyway/\|Scheduler list download succeeded 11/07/2009 10:50:55\|http://milkyway.cs.rpi.edu/milkyway/\|Sending scheduler request to http://milkyway.rpi.edu/cgi/cgi 11/07/2009 10:50:55\|http://milkyway.cs.rpi.edu/milkyway/\|Reason: Requested by user 11/07/2009 10:50:55\|http://milkyway.cs.rpi.edu/milkyway/\|Requesting 43200 seconds of new work 11/07/2009 10:50:59\|http://milkyway.cs.rpi.edu/milkyway/\|Scheduler request succeeded 11/07/2009 10:50:59\|Milkyway@home\|Message from server: No work sent 11/07/2009 10:50:59\|Milkyway@home\|Message from server: (reached daily quota of 1 results) 11/07/2009 10:50:59\|Milkyway@home\|Message from server: (Project has no jobs available) 11/07/2009 10:50:59\|Milkyway@home\|Successfully attached to Milkyway@home 11/07/2009 10:51:42\|Milkyway@home\|Sending scheduler request to http://milkyway.rpi.edu/cgi/cgi 11/07/2009 10:51:42\|Milkyway@home\|Reason: Requested by user 11/07/2009 10:51:42\|Milkyway@home\|Requesting 43200 seconds of new work 11/07/2009 10:51:47\|Milkyway@home\|Scheduler request succeeded 11/07/2009 10:51:47\|Milkyway@home\|Message from server: Not sending work - last request too recent: 44 sec 11/07/2009 10:52:29\|Milkyway@home\|Already attached 11/07/2009 10:52:53\|Milkyway@home\|Sending scheduler request to http://milkyway.rpi.edu/cgi/cgi 11/07/2009 10:52:53\|Milkyway@home\|Reason: To fetch work 11/07/2009 10:52:53\|Milkyway@home\|Requesting 43200 seconds of new work 11/07/2009 10:53:04\|Milkyway@home\|Scheduler request succeeded 11/07/2009 10:53:04\|Milkyway@home\|Message from server: No work sent 11/07/2009 10:53:04\|Milkyway@home\|Message from server: (reached daily quota of 1 results) 11/07/2009 10:53:04\|Milkyway@home\|Message from server: (Project has no jobs available) 11/07/2009 10:53:04\|Milkyway@home\|No work from project 12/07/2009 05:51:55\|Milkyway@home\|Sending scheduler request to http://milkyway.rpi.edu/cgi/cgi 12/07/2009 05:51:55\|Milkyway@home\|Reason: To fetch work 12/07/2009 05:51:55\|Milkyway@home\|Requesting 43200 seconds of new work 12/07/2009 05:52:00\|Milkyway@home\|Scheduler request succeeded 12/07/2009 05:52:03\|Milkyway@home\|Started download of file milkyway_0.19_windows_intelx86.exe 12/07/2009 05:52:03\|Milkyway@home\|Started download of file parameter_212F5_2s.txt 12/07/2009 05:52:06\|Milkyway@home\|Finished download of file parameter_212F5_2s.txt 12/07/2009 05:52:06\|Milkyway@home\|Throughput 7249 bytes/sec 12/07/2009 05:52:06\|Milkyway@home\|Started download of file stars212F5 12/07/2009 05:52:13\|Milkyway@home\|Finished download of file milkyway_0.19_windows_intelx86.exe 12/07/2009 05:52:13\|Milkyway@home\|Throughput 30499 bytes/sec 12/07/2009 05:52:13\|Milkyway@home\|Started download of file ps_sgr_212F5_2s_hiw_search_parameters_16891112_1247374001 12/07/2009 05:52:14\|Milkyway@home\|Finished download of file ps_sgr_212F5_2s_hiw_search_parameters_16891112_1247374001 12/07/2009 05:52:14\|Milkyway@home\|Throughput 1360 bytes/sec 12/07/2009 05:52:31\|Milkyway@home\|Finished download of file stars212F5 12/07/2009 05:52:31\|Milkyway@home\|Throughput 92364 bytes/sec 12/07/2009 05:52:32\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 12/07/2009 05:52:33\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 12/07/2009 05:52:33\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 12/07/2009 05:52:33\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 12/07/2009 05:52:33\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 12/07/2009 05:52:33\|Milkyway@home\|Unrecoverable error for result ps_sgr_212F5_2s_hiw_16891112_1247374001_1 (CreateProcess() failed - A device attached to the system is not functioning. (0x1f)) 12/07/2009 05:52:33\|Milkyway@home\|Deferring scheduler requests for 1 minutes and 0 seconds 12/07/2009 05:52:33\|\|Rescheduling CPU: start failed 12/07/2009 05:52:33\|Milkyway@home\|Computation for task ps_sgr_212F5_2s_hiw_16891112_1247374001_1 finished 12/07/2009 05:52:33\|Leiden Classical\|Resuming task wu_80398718_1245057971_41860_0 using trajtou-cu111 version 540 12/07/2009 05:53:34\|Milkyway@home\|Sending scheduler request to http://milkyway.rpi.edu/cgi/cgi 12/07/2009 05:53:34\|Milkyway@home\|Reason: To fetch work 12/07/2009 05:53:34\|Milkyway@home\|Requesting 43200 seconds of new work, and reporting 1 completed tasks 12/07/2009 05:53:40\|Milkyway@home\|Scheduler request succeeded 12/07/2009 05:53:40\|Milkyway@home\|Message from server: No work sent 12/07/2009 05:53:40\|Milkyway@home\|Message from server: (reached daily quota of 1 results) 12/07/2009 05:53:40\|Milkyway@home\|Message from server: (Project has no jobs available) 12/07/2009 05:53:40\|Milkyway@home\|No work from project I would recommend the optimized app anyways: http://zslip.com/milkyway.htm Much faster. I shall try that next...
10) Questions and Answers : Windows : "Process creation failed: A device attached to the system is not functioning" (Message 27527) Posted 11 Jul 2009 by SandJ Post: Has this happened to any other wus? Could be a fluke. Every work unit since about January.
11) Questions and Answers : Windows : "Process creation failed: A device attached to the system is not functioning" (Message 27502) Posted 11 Jul 2009 by SandJ Post: ME is after 98 so it should run MW. Are you using an optimized app? Have you restarted your pc? I am using whatever version is downloaded automatically. My PC has been restarted many times since this problem started. I have just detached and re-attached. I'll see what that does...
12) Questions and Answers : Windows : "Process creation failed: A device attached to the system is not functioning" (Message 27467) Posted 10 Jul 2009 by SandJ Post: I suspect the 'Applictions' page at http://milkyway.cs.rpi.edu/milkyway/apps.php should say something like "XP or later" instead of "Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 0.19" but I don't really know. I wonder if anyone reads these Q&As or is it just me, talking to myself?
13) Questions and Answers : Windows : "Process creation failed: A device attached to the system is not functioning" (Message 27448) Posted 10 Jul 2009 by SandJ Post: Having searched for the same message on other BOINC projects, I think I may be getting this because it is a Windows ME machine. "This probably has something to do with an API function recently introduced into your code, which unfortunately is not supported under Win98..."
14) Questions and Answers : Windows : "Process creation failed: A device attached to the system is not functioning" (Message 27093) Posted 5 Jul 2009 by SandJ Post: Since about January my Windows ME machine has been failing on this project with compute errors. This is the message: 05/07/2009 05:11:41\|Milkyway@home\|Sending scheduler request to http://milkyway.rpi.edu/cgi/cgi 05/07/2009 05:11:41\|Milkyway@home\|Reason: To fetch work 05/07/2009 05:11:41\|Milkyway@home\|Requesting 43200 seconds of new work 05/07/2009 05:11:46\|Milkyway@home\|Scheduler request succeeded 05/07/2009 05:11:47\|Milkyway@home\|Started download of file parameter_222F5_3s.txt 05/07/2009 05:11:47\|Milkyway@home\|Started download of file stars222F5 05/07/2009 05:11:50\|Milkyway@home\|Finished download of file parameter_222F5_3s.txt 05/07/2009 05:11:50\|Milkyway@home\|Throughput 9845 bytes/sec 05/07/2009 05:11:50\|Milkyway@home\|Started download of file ps_sgr_222F5_3s_hiw_search_parameters_11674371_1246766915 05/07/2009 05:11:51\|Milkyway@home\|Finished download of file ps_sgr_222F5_3s_hiw_search_parameters_11674371_1246766915 05/07/2009 05:11:51\|Milkyway@home\|Throughput 1086 bytes/sec 05/07/2009 05:12:16\|Milkyway@home\|Finished download of file stars222F5 05/07/2009 05:12:16\|Milkyway@home\|Throughput 112883 bytes/sec 05/07/2009 05:12:18\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 05/07/2009 05:12:18\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 05/07/2009 05:12:19\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 05/07/2009 05:12:19\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 05/07/2009 05:12:19\|Milkyway@home\|Process creation failed: A device attached to the system is not functioning. (0x1f) 05/07/2009 05:12:20\|Milkyway@home\|Unrecoverable error for result ps_sgr_222F5_3s_hiw_11674371_1246766915_0 (CreateProcess() failed - A device attached to the system is not functioning. (0x1f)) 05/07/2009 05:12:20\|Milkyway@home\|Deferring scheduler requests for 1 minutes and 0 seconds 05/07/2009 05:12:20\|\|Rescheduling CPU: start failed 05/07/2009 05:12:20\|Milkyway@home\|Computation for task ps_sgr_222F5_3s_hiw_11674371_1246766915_0 finished 05/07/2009 05:13:18\|Milkyway@home\|Sending scheduler request to http://milkyway.rpi.edu/cgi/cgi 05/07/2009 05:13:18\|Milkyway@home\|Reason: To fetch work 05/07/2009 05:13:18\|Milkyway@home\|Requesting 43200 seconds of new work, and reporting 1 completed tasks 05/07/2009 05:13:23\|Milkyway@home\|Scheduler request succeeded 05/07/2009 05:13:23\|Milkyway@home\|Message from server: No work sent 05/07/2009 05:13:23\|Milkyway@home\|Message from server: (reached daily quota of 1 results) 05/07/2009 05:13:23\|Milkyway@home\|Message from server: (Project has no jobs available) 05/07/2009 05:13:23\|Milkyway@home\|No work from project 05/07/2009 05:14:41\|\|Rescheduling CPU: application exited
15) Questions and Answers : Windows : Work Units with Computation Error (Message 1751) Posted 24 Feb 2008 by SandJ Post: I have just come back from a few days away to see the PC had stopped processing with a popup error. I too have now set this project to "No new tasks" until it is fixed.
16) Questions and Answers : Windows : Work Units with Computation Error (Message 1346) Posted 4 Jan 2008 by SandJ Post: are the windows popup messages still happening? Yes.
17) Questions and Answers : Windows : ASTRONOMY_1.13_WINDOWS_INTELX86.EX error (Message 1305) Posted 3 Jan 2008 by SandJ Post: I have had the following dialogue box a few times since I started working on this project: ------------------------------------------ Astronomy_1 Astronomy_1 has caused an error in ASTRONOMY_1.13_WINDOWS_INTELX86.EX Astronomy_1 will now close. If you continue to experience problems, ------------------------------------------ I am running Windows ME.