Welcome to MilkyWay@home

Posts by swiftmallard

21) Message boards : Number crunching : Problems with latest Windows 10 update (Message 64206)
Posted 1 Jan 2016 by swiftmallard
Post:
I am having a different problem after switching to Windows 10 and BOINC 7.6.22 BOINC manager shows my WUs completing in just a few seconds and all erroring out. I've made no other changes. Anyone have any ideas what I need to do?
22) Message boards : Number crunching : Problem with running two milkyway work units (Message 64136)
Posted 30 Nov 2015 by swiftmallard
Post:
I had the same issue and solved it by running a CPU project as well as GPU.
23) Message boards : Number crunching : Using the MW ATi application, Q & A (Message 63917)
Posted 10 Sep 2015 by swiftmallard
Post:
Problem detected.
Driver 14.6 RC, OS Win7 x 64 SP1, Radeon 7790.
No works.
What problem?

Other drivers can not install, you need this version!

According to your Tasks page, you have not tried any work units.
24) Message boards : Application Code Discussion : MilkyWay Screen Saver (Message 63822)
Posted 21 Jul 2015 by swiftmallard
Post:
I just started the MilkyWay project and it's awesome! I also run the SETI project, and that screen saver runs in the background. I would like to also run the MW screen saver, but it does not run, even though I am processing both. I'd like to have the two screen savers alternate between themselves if that's possible.
Thanks for the help.

There is no Milky Way screen Saver. That would require computing power the project would rather use for science rather than for show.
25) Message boards : News : server issues (Message 63737)
Posted 17 Jun 2015 by swiftmallard
Post:
Seem to have a lot of 'validation inconclusive' nvidia opencl units - about 50 over the last couple of days since the wu's started coming in again. Not sure whether that's an anomaly, but it seems unusual enough to let you guys know ...


This is normal. The results are simply waiting to be confirmed by other crunchers.


Ermm...pretty much the whole batch shows as 'validate errors'. In fact everything back to the server dropout shows as a validation error. All but two out of 188 tasks show as validation errors. That seems much less normal ...

To be fair, I put a new card in a week or so back - a new Asus GTX 750. But that model ran fine on another machine and is handling SETI with no problems.

Comments?


You asked about "validation inconclusive". Validate errors are a different thing and can be caused by any number of issues. Sit tight and one of the crunchers who know far more about nvidia than I will be able to assist you.
26) Message boards : News : server issues (Message 63731)
Posted 16 Jun 2015 by swiftmallard
Post:
Seem to have a lot of 'validation inconclusive' nvidia opencl units - about 50 over the last couple of days since the wu's started coming in again. Not sure whether that's an anomaly, but it seems unusual enough to let you guys know ...

This is normal. The results are simply waiting to be confirmed by other crunchers.
27) Message boards : Number crunching : max. gpu temperature for permanent mw crunching (Message 63539)
Posted 8 May 2015 by swiftmallard
Post:
Turn your memory speed down when crunching MW, it is not needed and only serves to create heat.
28) Message boards : Number crunching : Problem with N-Body Simulation 1.48 never finishing (Message 63424)
Posted 20 Apr 2015 by swiftmallard
Post:
Just make certain that box is not checked and save your preferences. You will then not receive n-body work. Then abort any you have and you'll be good to go.
29) Message boards : Number crunching : Problem with N-Body Simulation 1.48 never finishing (Message 63421)
Posted 20 Apr 2015 by swiftmallard
Post:
...
I went to the website and changed the preferences to not run the N-Body simulations (unchecked), but im still getting them in the work queue.

If no work for selected applications is available, accept work from other applications? Uncheck the box.
30) Message boards : Number crunching : All Milkyway@Home 1.02 tasks ending in computation error on HD6950. (Message 63412)
Posted 20 Apr 2015 by swiftmallard
Post:
Device doesn't support double precision

Here is problem #1
Milky Way requires double precision capable cards.
31) Message boards : Number crunching : nbody simulation 1.48 (mt) continue to run when completed (Message 63408)
Posted 19 Apr 2015 by swiftmallard
Post:
In your preferences, make certain these boxes are not checked:

MilkyWay@Home N-Body Simulation

If no work for selected applications is available, accept work from other applications
32) Message boards : Number crunching : Milkyway@home separation(modified fit) 1.36 coming up as invalid (Message 63402)
Posted 19 Apr 2015 by swiftmallard
Post:
Almost all the work units are coming up invalid on my computer or validation inconclusive. I have 4 GTX 780ti and two GTX Titans all on one motherboard. Any ideas? Thanks

All your invalid work units are the Modified Fit variety. Simply stop running them.
33) Message boards : Number crunching : server sending tasks NOT selected (Message 63373)
Posted 13 Apr 2015 by swiftmallard
Post:
I recently noticed an increase in invalid results for modified fit WU's so I altered my project setting to deselect modified fit WU.

However after doing an update, I found I had received 4 of those tasks. Dispite them being set to off/no in MW@H config settings.

Is this a minor glitch, or will it persist in sending me unselected tasks?
[edit]
And now I have even more modified fit WU..

Just below the application selection boxes is this:
If no work for selected applications is available, accept work from other applications?

Yours should be unchecked.
34) Message boards : Number crunching : One Task = Status: Running(8 CPUs), Other tasks "Waiting To Run" (Message 63369)
Posted 12 Apr 2015 by swiftmallard
Post:
Hi,

Still trying to understand the various elements of MW@H

We all are.

Is it normal for 1 Task, per my Title to be the only running Task/WU..??

For n-body units, as you have here, yes. I suggest you uncheck n-body work in your preferences, that will make things settle out.

It appears the WU's of Type "Milkyway@Home N-Body Simulation.. " do this, on 3 PC's
When it starts the other 7 change to "waiting to run"


That's because n-body units require the entire CPU to run, whether the n-body app actually appears to be using all cores or not is irrelevant. Again, go to your preferences and uncheck the n-body and uncheck the send work for other applications box.

[/quote]
35) Message boards : Cafe MilkyWay : LPTPW Mark II (Message 63348)
Posted 10 Apr 2015 by swiftmallard
Post:
Woz, because I am now.
36) Message boards : Number crunching : upgraded my gpu how to max it out? (Message 63343)
Posted 10 Apr 2015 by swiftmallard
Post:
when I was running SLI it let me have a WU working on each of the GPUs so that I could put out two at a time.

That is not the same as crunching two WU per card.
37) Message boards : Number crunching : Problem with N-Body Simulation 1.48 never finishing (Message 63321)
Posted 6 Apr 2015 by swiftmallard
Post:
How do I stop my computer from downloading the N-body Simulation 1.48? I have set my preferences to NO on N-body (all categories) but I keep getting these files and they do not want to finish, they just keep running with a Remaining Time of ---. The only ways that I have found to stop the processing of these files is to either re-boot or abort it.

Make certain this box is not checked in your preferences:
If no work for selected applications is available, accept work from other applications?
38) Message boards : Number crunching : Completed, validation inconclusive, credit pending (Message 63301)
Posted 30 Mar 2015 by swiftmallard
Post:
Work units are sent to more than one cruncher to process. After you return results that are somewhere near what the project expects them to be, you are now waiting for another cruncher to return the same results you did, plus or minus an acceptable margin of error. Validation inconclusive WUs are the units waiting for another cruncher to report results.
39) Message boards : Number crunching : strongest performing milkyway@home AMD card (Message 63119)
Posted 7 Feb 2015 by swiftmallard
Post:
You might wish to read through this thread:
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3551&postid=61794#61794
40) Message boards : News : New Modfit Runs (Message 63085)
Posted 1 Feb 2015 by swiftmallard
Post:
What would you recommend to set for CPU usage for the GPU projects? Do they each really need a whole CPU core, or can the GPUs share a single core between them?

My experience is that leaving a core free to feed the GPU adds so little output that it's not worth doing, I prefer to run a single CPU project on all cores and a single GPU project on the card. I run as few projects as possible at any one time to eliminate any issues with Boinc wanting to switch between them, KISS at work.

It seems to me that your measurement of optimization of the overall output includes receiving the maximum credit from a given project, a nice objective goal. But many major crunchers will tell you that the easiest way achieve this is to:
A. keep it simple
B. set it and forget it

You've done what you can. Let it run for a year and come back to see where you are. I have no doubt you will be well pleased.


Previous 20 · Next 20

©2020 Astroinformatics Group