Welcome to MilkyWay@home

Posts by w1hue

21) Message boards : Number crunching : Why am I getting this message? (Message 64723)
Posted 22 Jun 2016 by w1hue
Post:
I do not have "... N-Body Simulation" checked in my preferences, so why do I keep seeing this message in my BOINC log:

(date/time stamp) | Milkyway@Home | Message from server: Your app_info.xml file doesn't have a usable version of MilkyWay@Home N-Body Simulation.

??

Since I don't do 'em, of course there isn't any entry in my app_info.xml file . . .
22) Message boards : News : Running Modfit on MilkyWay@home (Message 64700)
Posted 21 Jun 2016 by w1hue
Post:
My XP machine has kissed the project goodbye, but I have an AMD64 machine running Win10 with a GT-730 still getting tasks. But -- I have it setup to run muntiple WUs (2, actually) at a time and I need to get the new executable as all milkey@home WUs are ending in error now. Modified fit tasks running OK -- can I use the same executable that is running those?
23) Message boards : News : Running Modfit on MilkyWay@home (Message 64685)
Posted 20 Jun 2016 by w1hue
Post:
Additionally, this means some extremely old systems may no longer be supported on the MilkyWay@home project. These include Windows 32-bit systems

I guess that means that I can kiss this project goodbye! :-(
24) Message boards : Number crunching : GPU Requirements (Message 57990)
Posted 24 Apr 2013 by w1hue
Post:
If you go into the Boinc Manager, the icon down by the clock, you can look under the Tasks tab and see how much cpu and gpu percentage Boinc is using, the more cpu percentage Boinc is using the more advantageous it is to leave a cpu core free. ...

Gee, I didn't know that ... I must be stupid or something.

25) Message boards : Number crunching : GPU Requirements (Message 57974)
Posted 23 Apr 2013 by w1hue
Post:
Are you crunching a cpu project using those cpu's at the same time?

Yes.

If so change the setting so one cpu is left free, per gpu, then set MW to run two units at once again and see if it helps. When you also run a cpu project on the same cpu you use to fee a gpu it can slow down both projects. Since the gpu projects crank out much more work it might make sense to drop one cpu core from the cpu projects and give more to the gpu projects.

Since I saw very little advantage run-time wise (per WU) running two units in the gpu as opposed to one, I believe that I am better off in the overall scheme of things in just running one gpu WU and not slowing down the cpu while crunching other projects. I only have a dual core machine and my (single) gpu a is a GT 520 which I chose for its low power consumption over a speedier power hog.
26) Message boards : Number crunching : GPU Requirements (Message 57739)
Posted 30 Mar 2013 by w1hue
Post:
There seems to be some question at to whether or not a GT 520 card will work on this project. Just for the record, I have been using one for the past year or so and it crunches Milkyway@home WUs just fine -- also Einstein@Home and SETI@Home. I tried running two WUs at a time in it for awhile, but decided I wasn't gaining much and apparently slowing down CPU jobs because of the extra CPU effort needed to keep two WUs running in the GPU. Not sure why that is, but it sure appeared to be the case! (The machine has s dual core AMD cpu and I have my computing preferences set to use 100% of available CPUs.)
27) Message boards : Number crunching : Need Help with app_info for NVIDIA GPU (Message 55588)
Posted 20 Sep 2012 by w1hue
Post:
SUCCESS!

I reset the milkyway project and restarted BOINC -- it downloaded WUs and has been happily crunching two WUs at a time in my GT 520 for the past couple of hours! And I am still running BOINC 7.0.28. Doing a scan of past posts regarding BOINC 7.0.25+, it appears that those experiencing errors were running higher end cards and/or a 64bit OS. I am running 32bit WinXP.

Just for the record, here is my app_info file that is working:

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.02_windows_intelx86__opencl_nvidia.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>102</version_num>
<flops>2.0e10</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>cuda</plan_class>
<coproc>
<type>NVIDIA</type>
<count>0.5</count>
</coproc>
<cmdline></cmdline>
<file_ref>
<file_name>milkyway_separation_1.02_windows_intelx86__opencl_nvidia.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

28) Message boards : Number crunching : Need Help with app_info for NVIDIA GPU (Message 55587)
Posted 19 Sep 2012 by w1hue
Post:
Remember that you NEED to use Boinc version 7.0.25 for Nvidia cards to work here, as anything higher from there up up thru 7.0.31 will NOT work!

That's strange -- my 7.0.28 works fine with SETI. If that is really the case, I'll just wait for 7.0.32 to be released and try again. Too much hassle to down-grade.

BTW -- your app_info fine looks about the same as mine, except your <class_plan> is cuda and mine is cuda_fermi.
29) Message boards : Number crunching : Need Help with app_info for NVIDIA GPU (Message 55582)
Posted 19 Sep 2012 by w1hue
Post:
Well, I found part of the problem: I left this out of the app_info file:

<file_ref>
<file_name>milkyway_separation_1.02_windows_intelx86__opencl_nvidia.exe</file_name>
<main_program/>
</file_ref>

At least the .exe file no longer gets deleted from the milkyway directory! However, I can't get it to download WUs!

Even with all other GPU projects suspended, I get this when I "update":

9/18/2012 8:52:36 PM | Milkyway@Home | Sending scheduler request: Requested by user.
9/18/2012 8:52:36 PM | Milkyway@Home | Not reporting or requesting tasks
9/18/2012 8:52:39 PM | Milkyway@Home | Scheduler request completed


Here's my current app_info file contents:
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.02_windows_intelx86__opencl_nvidia.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>102</version_num>
<flops>4.0e10</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>cuda_fermi</plan_class>
<coproc>
<type>nvidia</type>
<count>0.5</count>
</coproc>
<cmdline></cmdline>
<file_ref>
<file_name>milkyway_separation_1.02_windows_intelx86__opencl_nvidia.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

Now What??
30) Message boards : Number crunching : Need Help with app_info for NVIDIA GPU (Message 55581)
Posted 18 Sep 2012 by w1hue
Post:
I've been futzing for the past hour or so trying got get an app_info.xml file configured so that I can run two Milkyway WUs at a time in my NVIDIA GT 520 GPU (it runs single Milkyway WUs and multiple SETI WUs just fine).

Here's my most recent attempt for the Milkyway app_info.xml file:

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.02_windows_intelx86__opencl_nvidia.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>102</version_num>
<flops>4.0e10</flops>
<avg_ncpus>0.05</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>cuda_fermi</plan_class>
<coproc>
<type>NVIDIA</type>
<count>0.5</count>
</coproc>
<cmdline></cmdline>
</app_version>
</app_info>

This is essentially the same as one I found in a search of the message boards that apparently worked. When I restart BOINC after installing the file, the file milkyway_separation_1.02_windows_intelx86__opencl_nvidia.exe gets deleted (it was definitely there before BOINC restarted!

Here's an excerpt from the log file:

9/18/2012 4:21:50 PM | | NVIDIA GPU 0: GeForce GT 520 (driver version 285.58, CUDA version 4.10, compute capability 2.1, 1024MB, 989MB available, 182 GFLOPS peak)
9/18/2012 4:21:50 PM | | OpenCL: NVIDIA GPU 0: GeForce GT 520 (driver version 285.58, device version OpenCL 1.1 CUDA, 1024MB, 989MB available)
9/18/2012 4:21:50 PM | Milkyway@Home | Found app_info.xml; using anonymous platform
9/18/2012 4:21:50 PM | SETI@home | Found app_info.xml; using anonymous platform
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] No application found for task: windows_intelx86 102 opencl_nvidia; discarding
9/18/2012 4:21:50 PM | Milkyway@Home | [error] State file error: result de_separation_09_2s_sample_2_1341007502_45150216_0 not found for task

HELP!!
31) Message boards : Number crunching : Suddenly most results invalid (Message 51448)
Posted 20 Oct 2011 by w1hue
Post:
If you look at the top computers you may notice that almost all of them regularly post invalid tasks. This is VERY unusual compared to other projects and may indicate either a problem with 0.82 or a validator problem. The former CP apps did not exhibit this behavior.

I'm pretty much at the bottom of the heap with my three CPU-only (well, one has a GPU, but not gudnuf for this project...) computers, so I doubt that my participation will be missed. After all the WU's submitted by one machine over ~30 period and the majority from the other two machines got marked as "invalid", I decided to quite wasting my machines's time and removed the project. All three have no problems with several other BOINC projects.
32) Message boards : Number crunching : Why are finished tasks deleted so fast? (Message 51138)
Posted 20 Sep 2011 by w1hue
Post:
It was an easy fix to keep server load down at times in the past couple years and was left this way. I don't think it is needed as much now but it is still in place.

It would REALLY be nice if they stuck around long enough to see! At least a day or two.
33) Message boards : Number crunching : Doing work, not getting any credit (Message 51126)
Posted 19 Sep 2011 by w1hue
Post:
Since no one has come up with any viable ideas, I have suspended milkyway work on my three machines. All of the pending WU's (except one from a detatched machine that the system apparently thinks is still attached...) have now gone away with no credits being given. Not worth my or the project's time to work on WUs that apparently result in invalid results... Maybe after Travis finishes diddling with the validator I'll give the project another try. In the meantime, I'll let the machines crunch for cosmology@home (along with seti@home, einstein@home and LHC@home)
34) Message boards : Number crunching : Doing work, not getting any credit (Message 51049)
Posted 14 Sep 2011 by w1hue
Post:

It means your computer 285024 is not producing valid results.

If that's the case, then I guess it hasn't been producing any valid results for the past six weeks or so ... but it was previously, so what's changed??

Since it isn't doing anything useful for the project, I'll detatch it and let it work on projects for which it can do useful work.

My other two machines are starting to get 'validation errors' as well, so guess I might as well detatch them as well.
35) Message boards : Number crunching : Doing work, not getting any credit (Message 51029)
Posted 13 Sep 2011 by w1hue
Post:
You have 3 machines on your profile.

Can you post some links to WU's that are the issue please?


I would if I knew where to find them... The machine ID is shown in my original post.

Saturday I reset the project, but that didn't seem to do any good. This morning I detached, rebooted the machine, and reattached. I'm waiting to see if I get any credit for the WU now in progress.
36) Message boards : Number crunching : Doing work, not getting any credit (Message 51024)
Posted 12 Sep 2011 by w1hue
Post:
HELLO.... Anyone out there??
37) Message boards : Number crunching : Doing work, not getting any credit (Message 50992)
Posted 8 Sep 2011 by w1hue
Post:
One of my machines (ID 285024) has not received any credits in over a month, even tho it has crunched at least 15 WU's. After a completed WU is reported it shows up as "Completed, validation inconclusive" and is sent out to another user. After a few days it then "goes away" with no indication (at least, not anyplace that I can find) as to its status. What's going on here??? That machine is crunching WUs for other projects and receiving credit OK.
38) Message boards : News : number of unvalidated results climbing (Message 43281)
Posted 29 Oct 2010 by w1hue
Post:
Looks like I just lost another 20 or so hours of work...
39) Message boards : News : a fix for the output file issue (Message 42955)
Posted 19 Oct 2010 by w1hue
Post:
My credits have not changed for about ten days during which time I completed at least three WUs with over 60 hrs CPU time, my pending credits list shows 0, and my task list is blank. So, guess not... at least not as far as getting credit for the "lost WUs" is concerned. Oh well, life is a bitch, then you die. (Just kidding!!) I'll un-suspend the project and see what happens with new WUs.
40) Message boards : News : a fix for the output file issue (Message 42921)
Posted 18 Oct 2010 by w1hue
Post:
Does this fix the problem of not getting credit for completed WUs that show "computation error"?


Previous 20 · Next 20

©2024 Astroinformatics Group