Welcome to MilkyWay@home

Posts by ylixia

1) Message boards : News : New N-Body Runs (Message 61903)
Posted 16 Jun 2014 by Profile ylixia
Nearly all of the xx_nbody_06_10_orphan_sim_x runs I've had recently have ended up with errors so no, it's probably not you :)
2) Message boards : Number crunching : Ever longer N-Bodies (Message 61900)
Posted 15 Jun 2014 by Profile ylixia
Ok, so it's not just me - these runs seem to be causing a lot of errors.

3) Message boards : Number crunching : Ever longer N-Bodies (Message 61899)
Posted 15 Jun 2014 by Profile ylixia
There seems to be an issue (for me at least) with "..nbody_06_10_orphan_sim.." N-Body WUs.

They start off with a fairly low estimated time left of maybe an hour or less, but then this keeps increasing instead of decreasing. For example, I have one now which was originally down for completion in 1h28m but is still only 21.7% done after 22h13m.

Other N-Body WUs seem to be fine.
4) Message boards : Number crunching : Updated GPU Requirements (Currently not supporting GPU tasks) (Message 60644)
Posted 23 Dec 2013 by Profile ylixia
From Matthew Arsenault:
R7xx is sketchy, since support was dropped from the driver (and I just removed support for it from the backend), so you need to use an old version of it. Anything newer than that should be fine.

Err, is the model number a typo? As the R700 series includes the HD 48xx & 47xx which do have DP & you list as supported (bar the 4730 which I guess is just an omission?), or are you referring to OpenCL support?

No I think he means the new R7 series.
5) Message boards : Number crunching : Feature request: Run CPU versions of applications for which GPU versions are available - yes/no (Message 60486)
Posted 29 Nov 2013 by Profile ylixia
Maybe this has been discussed before, if so, my apologies. However, a quick forum search returned nothing. Is there any chance you could implement a switch like "Run CPU versions of applications for which GPU versions are available - yes / no"? This switch is available at Einstein@home and it allows to opt into every application while only crunching those applications on CPU where no GPU version is available.

Currently I want to crunch again some MilkyWay@Home N-Body Simulation on CPU, but I have to opt out from MilkyWay@Home and Milkyway@Home Separation (Modified Fit) otherwise I'll get CPU workunits for such applications, too (which I do not want for obvious reasons). I am aware that I could use an app_info.xml, but this is a rather complicated approach if you only want to choose the standard apps you're running. Like "shooting with cannons at sparrows", as a german saying goes. ;) For allocating GPU resources I am using an app_config.xml currently.

Go to MilkyWay@Home preferences here on the site and change the options as below:

Run only the selected applications
MilkyWay@Home: no
MilkyWay@Home N-Body Simulation: yes
Milkyway@Home Separation: no
Milkyway@Home Separation (Modified Fit): no

If no work for selected applications is available, accept work from other applications?

When asking for CPU apps your PC will get just N-Body as asked for. When asking for GPU apps your PC will ask for N-Body, get told "no there aren't any" and then the 'accept work from other applications' option will kick in.

©2024 Astroinformatics Group