From MilkyWay News Archive: (http://milkyway.cs.rpi.edu/milkyway/all_news.php#163)
26 Mar 09:
Sorry for the recent lack of communication, but we've been working on quite a few things behind the scenes here.
First, my new laptop just came in the mail, so I'll be able to seriously start working on a CUDA version of the milkyway application. We'll be developing this for OS X, Linux and Windows.
Second, we're going to be doing a few server-side changes to how things are run, which should significantly help with workunit reporting and work availability. We'll be splitting MilkyWay@Home into two separate applications/backends, Milkyway regular and Milkyway GPU. This will allow us to keep current workunit sizes for non-GPU applications, while farming a lot more work out to the GPUs (so they need to contact the server less frequently). We'll be doing different optimization methods on the regular Milkway and the GPU Milkyway so they'll both be doing equally valid research. In the next day or two I'll be posting the code that the application will be using for the GPU version. After testing to make sure that it's working correctly we'll swap to only awarding credit to the GPU applications for GPU milkyway (that way our servers wont be as bogged down, which will mean better work availability). Also, before a credit firestorm erupts again, we have no plans to award less credit/work to the GPU applications, so you don't need to worry about that.
edit: changed title to Project News
WOW! how great are those news!!
:mwalk: :mwalk: :mwalk:
milkyway on cuda, BRING IT ON!!
Sounds good, especially the CUDA part!
From Milkyway News Artchive: (http://milkyway.cs.rpi.edu/milkyway/all_news.php#166)
There might be some downtime this afternoon as we should be meeting with labstaff to get the MilkywayGPU@Home project up and running. I'll also be posting CPU code for the GPU application this afternoon so the people who have made the GPU application for the ATI cards can get their hands on it and modify it so it works with ATI cards. We should have the CUDA code out sometime this week.
From Milkyway News Archive: (http://milkyway.cs.rpi.edu/milkyway/all_news.php#170)
19 May 09:
The reason we went down today a few times was that there were power outages on campus while they were doing things to the electrical system. Hopefully things should be up and running smoothly now.
FromMilkyWay News Archive: (http://milkyway.cs.rpi.edu/milkyway/all_news.php#172)
20 May 09:
Looks like the power is going to be out until tomorrow morning with another outage tomorrow afternoon. I'll post more information as we know about it.
FromMilkyWay News Archive:
20 May 09:
Looks like I've finally gotten the CUDA application working. I'm in the process of cleaning up the code, and it should be available for you to play around with tonight. It's my first crack at a CUDA application, so it's a bit rough, but currently it's crunching the current stripe 82 WUs in around a minute using a GeForce 9600M GT. I'm sure there's quite a bit more optimization we can to do get it running even faster, as this is the first version and not optimized at all. Part of the reason this has taken so long was that I was doing quite a bit of testing comparing double and single precision math on the GPU. I've come up with some schemes that will allow us to use older graphics cards which don't support double precision math (like the GeForce I've been using); which should let a lot more of our users be able to use the GPU application. More news later when I post the code.--Travis
whats the go with milky and their cuda app??
aparently its out, but none of my cuda systems are picking any wus.. anything i have to do manually, or will it start crunching the gpu-wus automatically?
Only the code is released so far, not any work units yet.
It is going to be run as a separate project from MilkyWay@Home on CPU and you will have to attach to it. The url to attach in BOINC is the same as the separate website: http://milkyway.cs.rpi.edu/milkyway_gpu/
After the official MilkyWay GPU application is released, then support for the current third party ATI only GPU application will be removed for the CPU project.
From the MilkyWay news feed:
Monday, 8 June 2009 10:00 AM
Project News: 3 stream searches and the ATI GPU fix
We are once again attempting 3 stream searches. If you are getting errors relating to the search ps_sgr_235_3s_4 you can get a fixed version of the code here ( http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=886#24282 (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=886#24282) ) compliments of Cluster Physik
From the MilkyWay news feed:
June 9, 2009
Power Outage & Work Availability Update
There was just a power outage which took out the server, it should be back up and running now. I also did an update to the feeder which has it running more frequently. I think this should improve the work availability. Let us know how things are working.
Visual Search Progress
I made a little update to the search progress forum thread. You can now see how the searches are progressing here.
From the MilkyWay news feed:
Search Progess on the Main Page
Wednesday, 10 June 2009 10:00 AM
If you look below the news, the plots describing the progress of the different searches we're running is now on the main page. They're updated every five minutes.
Nathan Cole's PhD Thesis
Wednesday, 10 June 2009 10:00 AM
Nate finished up his PhD thesis and we've made it available here (http://wcl.cs.rpi.edu/papers/cole-phd-thesis.pdf). Its also in our publications section. Thanks everyone for your help!
Busy news day for MilkyWay today! :faint:
From the MilkyWay news feed:
Science Sticky Thread Started
June 11, 2009
We have started a thread (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=902) in the science forums relating to the astrophysics portion of the project for those who are interested.
New Search Accuracy and Runs
June 11, 2009
A few more optimizations to the search process have been made, so we're running some of the old stripes again to get better fits. The new runs are ps_new_11_1, for example.
CUDA Code for Milkway@Home
June 11, 2009
Since it looks like the server is handling things fine (no work shortages), I've put out the CUDA code for milkyway@home. If this works and the server holds up we won't need milkywayGPU@home. The code can be downloaded in the usual code release directory. (http://milkyway.cs.rpi.edu/milkyway/download/code_release/) I've also added two CUDA binaries for intel versions of OS X, single and double precision if anyone would like to test them out. They're also in the code release directory. If anyone would like to test the code for linux and windows that would be appreciated. I've started a new forum thread about this here. (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=906)
Short Workunits
June 11, 2009
Matts searches had the wrong sized integral so they were crunching much faster than expected. We've stopped these so there shouldn't be any new short workunits.
Cuda Update
June 11, 2009
I noticed a problem in the binaries and code I put on the code download page. I removed them to do some fixes, but they should be available tonight or at the latest tomorrow morning.
Camping!
June 11, 2009
Travis here. I'm going to be camping until Sunday so don't break anything while I'm gone. Hopefully Matt and John will keep the server running and filled with work for you guys :) I'm still having a few problems with the CUDA application for regular milkyway, so it'll probably be out Monday or Tuesday after I get back.
From the MilkyWay@Home news feed:
Explanation of Milkyway@Home Astronomy Progress
Monday, 15 June 2009 10:00 AM
John has made the following post (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=902#24982) in the science section. It's an in depth explanantion of the current astronomy work being done here and quite readable and easy to understand (even I can get it). I recommend it if you'd like to know a bit more about what's going on here on the astronomy end of things.
--Travis
From the MilkyWay@Home news feed:
Project News: RAC minimum on the Cafe
Monday, 22 June 2009, 10:00:00 AM
Do to some rather unsavory activity in the Cafe, it now has a minimum RAC of 5 to enable posting messages.--Travis
Looks like Milkyway is off the air at the moment.
http://downforeveryoneorjustme.com/milkyway.cs.rpi.edu returns a fail.
Yeh - it's a bugger.
I had Milky, and GenLife as backups to Einstein - and they all fell over today.
All back up now though :dance:
From the MilkyWay@Home news feed:
Project News: Updating Server Daemons Tonight
Tuesday, 21 July 2009 10:00 AM
I'll be updating the server daemons tonight with better result verification and updated particle swarm and genetic searches. There will probably be some downtime while I get everything up and running correctly. We've also been examining some issues we're having with our fitness calculation, so we'll be releasing a new application and its code to deal with that as well. It also seems we're having some excessive credit issues again so things are going to have to be tweaked (have fun flaming our forums :P).
From the MilkyWay@Home news feed:
Project News: Started a Genetic Search
Tuesday, 21 July 2009 10:00 AM
I'm testing a genetic search right now with the new verification. Let me know how things are working. Work should be flowing now
From the MilkyWay@Home news feed:
Project News: Server Crash
Wednesday, 29 July 2009 10:00 AM
Our database crashed or got corrupted this morning and it's looking we lost a lot of user accounts and credits. For now if you lost your account just make a new one. We're looking into this right now and are trying to restore all that we can.--Travis
From the MilkyWay@Home news feed:
Project News: Server Crash Update
Wednesday, 29 July 2009 10:00 AM
Looks like labstaff is in the process of restoring the lost data right now. Hopefully we didn't lose too much after the restore is done.
From the MilkyWay@Home news feed:
Project News: Server Database Restored
Wednesday, 29 July 2009 10:00 AM
We restored the server to this mornings backup. Let us know if you're still having any problems.
From the MilkyWay@Home news feed:
Project News: Updated User Stats
Wednesday, 29 July 2009 10:00 AM
Since some users are still reporting missing credit, I've re-run the stats export which should hopefully update their credit to what it should be after the restore. This might take a little while to show up correctly, but let me know if this has fixed your missing credit, if you're still missing credit. The only credit that you should be missing would be from 4am this morning til around 2pm this afternoon.
2009-07-30: MilkyWay@home - Project News: CUDA App Alpha Preview
An alpha version of the CUDA App has been released for community preview, please see the following forum post (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=906&nowrap=true#28652).
edit: added the link
From the MilkyWay@Home news feed:
Assimilator Down
Saturday, 8 August 2009 10:00 AM
We're having a small problem with the assimilator, it should be back up and running shortly.
Milkyway@Home Now Accepting Donations
August 12, 2009
Professor Newberg has gone through all the steps to allow MilkyWay@Home to actually accept donations and has written a letter of request, which I've posted here. The letter discusses the progress we've made in both scientific computing and astronomy, as well as our current funding situation. You can directly access the page to make donations here.
From the MilkyWay@Home news feed:
Server Side Software Upgrade
Thursday, 20 August 2009 10:00 AM
A planned BOINC server side software upgrade will take place on August 21 at 4:00pm EDT (America/New_York).
Quote from: BF on August 21, 2009, 01:17:13 PM
From the MilkyWay@Home news feed:
Server Side Software Upgrade
Thursday, 20 August 2009 10:00 AM
A planned BOINC server side software upgrade will take place on August 21 at 4:00pm EDT (America/New_York).
Sounds like another outage in the making. :rofl: :rofl: :rofl:
Quote from: Dataman on August 21, 2009, 01:21:54 PM
Sounds like another outage in the making. :rofl: :rofl: :rofl:
SHHHHHHH!!!! They might hear you biggrin
Not officially reported yet but I just noticed the following has recently appeared as a MilkyWay application:
Linux running on an AMD x86_64 or Intel EM64T CPU 0.19 (cuda) 22 Aug 2009 0:25:54 UTC
Edit: Oops didn't realise this has already been reported on the forum by one of the staff and is said to be giving segfault errors.
From the MilkyWay@Home news feed:
Project News: CUDA Application Released
Wednesday, 26 August 2009 10:00 AM
The CUDA application has been released on BOINC, please see this thread (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1083#29742) for more information. The Milkyway@Home team appreciates your patience in reaching this milestone. This code has been implemented and tested on the GeForce GTX 285 donated by NVIDIA to the Milkyway@Home research team.
Please take note of the hardware and driver requirements of the CUDA application!
From the MilkyWay@Home boards:
The CUDA application for 32 bit Windows has been deployed on BOINC. In terms of hardware a NVIDIA GPU supporting Compute Capability 1.3 is required. The following GPUs: GeForce GTX 295, 285, 280, 260, Tesla S1070, C1060, Quadro Plex 2200 D2, Quadro FX 5800, 4800 are known to have CUDA 1.3 support. The GPUs also need to have 256 MB of Video RAM and NVIDIA Driver 190.xx or higher needs to be installed. If these prerequisites are not met the CUDA application will not be downloaded through BOINC.
The requirements are horrible. :faint: Few, I think, will run them under these conditions. I am going to wait and see how it sorts out before running any. ???
GTX 275 should support Compute Capability 1.3, although it is not listed in the nVidia documentation for some reason. CUDA-Z (http://cuda-z.sourceforge.net/) would probably show a GTX 275 has Compute Capability 1.3.
Quote from: kashi on August 27, 2009, 11:08:11 AM
GTX 275 should support Compute Capability 1.3, although it is not listed in the nVidia documentation for some reason. CUDA-Z (http://cuda-z.sourceforge.net/) would probably show a GTX 275 has Compute Capability 1.3.
I'm sure you are correct as the 260 meets them. From the subsequent posts in their thread, it looks like another app that "eats" your machine. I hope we are not entering an era where you have to give the app the entire machine to run it. :cry2: Ok for farms but very unfriendly to the casual cruncher who wants to run several sciences. :thumbdown: But as I said, I'll just see how is sorts over the next few days.
You regular Milkywayers would know, but their server is currently down for maintenance and not issuing work. Just thought I should mention it leading into the long weekend (for those who get it biggrin)
FYI: Milkyway is now the most active BOINC project followed by Collatz, SETI, WCG, Einstein & GPUGrid. I never thought I'd see the day SETI and WCG would be knocked out of 1st & 2nd respectively.
It's got to be the credit rate.... at just under 4 minutes for 314 credits (4840 cr/ hr - 116K + a day !) why WOULDN'T anyone crunch there ?!?!
I have a problem though... I get work easily for my two ATI cards, yet my GTX 275 keeps getting the "no work sent" message..... is there an optimised app for cuda cards ?
MW is down due to "Snowmageddon". They have a blizzard going on. I switched to GPUGrid.
Seems to be back again - some sort of hardware issue rather than the snow.
From Milkyway news:
Server outage
I'm taking the server down tonight (and probably most of the tomorrow). I've made some big changes in the assimilator and validator which should help me implement new features and debug them in the future (mainly I rewrote them in Java so I don't have to worry about memory leaks or segmentation faults). I'll be debugging them over the next couple days so expect some outages. Most notably, validation will be much stricter now; considering even though I've asked nicely we still see a lot of people trying to scam the system (scripts and single precision GPU clients for example). It's kind of sad that a few bad users have to ruin things for everyone (and make our work that much more difficult), but I guess thats the way things have to be. On another note, we've had two papers accepted recently, one to the Distributed Applications and Interoperable Systems (DAIS 2010) conference (http://discotec.project.cwi.nl/index.php/DAIS:Main (http://discotec.project.cwi.nl/index.php/DAIS:Main)), and another to the World Congress on Evolutionary Computation (CEC 2010) http://www.wcci2010.org/topics/ieee-cec-2010 (http://www.wcci2010.org/topics/ieee-cec-2010). I'll be making these available after the validator/assimilator upgrades.
2 Apr 2010 2:36:58 UTC
And in light of those adjustments, I am now getting wus sitting in pending and also being invalidated...... fur some unknown reason.
The exception that proves the rule?: :pcwhack: Love it when I am invalidated for wus with too many successful results LMAO
Might take them a while to fix this, if you don't wish to have perhaps half your completed work marked invalid then it may be time to give Collatz a go. Or DNETC if it works alright for you.
I don't know how this happened, I would have thought they would have been checking at least a small sample of the returned results against their computers at Rensselaer Polytechnic. I could understand them not catching the relatively small number that had been done by a rogue NVIDIA single precision app but missing the massive number being returned by 58xx and 5970 cards seems surprising.
Yep, as I predicted above it's 58xx and 5970 that are the fly in the ointment. This red wine is great stuff, it must make you psychic. :rofl:
WEG
I still reckon it's the other cards what is wrong cause ATI fixed a little bug in latest cards WEG
Anyways, am now having a run at DNETC...... 4800+ crs for 24-25 mins work ain't nowt to sneeze at.
The 5xxx bug is fixed and delivered in the stock ATI app. But DNETC has no doubt been given a great boost!
2010-12-03: MilkyWay@home - OpenCL for Nvidia available for testing
The OpenCL application for Nvidia GPUs is ready for testing for Windows and Linux x86_64. I'm particularly interested in the performance / responsiveness tradeoff on mid-low range GPUs.
Many thanks to cncguru for donating his GTX 480. If I hadn't had it, it would be about 30% slower than it is.
http://milkyway.cs.rpi.edu/milkyway/download/test/milkyway_separation_0.48_x86_64-pc-linux-gnu__cuda_opencl.tar.gz
http://milkyway.cs.rpi.edu/milkyway/download/test/milkyway_separation_0.48_windows_intelx86__cuda_opencl.zip
Extract these to the project directory. On Windows this is something like C:\ProgramData\BOINC\projects\milkyway.cs.rpi.edu_milkyway
On Ubuntu for me, this is /var/lib/boinc-client/projects/milkyway.cs.rpi.edu_milkyway
2011-01-24: MilkyWay@home - bypassing server set cache limits
While we appreciate everyone wanting to crunch more MilkyWay@Home by increasing their cache limits; this is part of the reason why we've had so many server problems lately with an unresponsive validator. Mainly, our machine/database is not fast enough to keep up with the additional amount of workunits this is causing in the database. So if anyone is modifying their BOINC client to artificially increase their cache we're asking you to stop so the project will be more stable (until we can further improve our hardware). A few of the really offending clients (who have cached 1k+ workunits) are being banned as they haven't responded to us, and they're hurting everyones ability to crunch the project as a whole.
So in short, we need you guys to work with us as we're working with limited hardware that can't handle more than 500k+ workunits at a time -- our cache is low partially for this reason. Second, as we've said in a bunch of previous threads in the past, due to the nature of the science we're doing at the project we need a low cache because this really improves the quality of the work you guys report.
As you (hopefully) know by now, we search for structure and try to optimize parameters to fit that structure within the Milky Way galaxy. And lately we've been also doing N-Body simulation of the formation of those structures. What your workunits are doing is trying to find the optimal set of parameters for those N-Body simulations to end up best representing our sky survey data or to fit those different structures (like dwarf galaxy tidal streams) from that data.
To do this, we use strategies which mimic evolution. The server keeps track of a population of good potential solutions to these problems, and then generates workunits by mutating some solutions, and using others to create offspring. You guys crunch the data and return the result -- if it's a good one we insert it into the population which improves as a whole. Over time, we get very very good solutions which aren't really possible using other deterministic approaches.
If people have large caches, that means the work they're crunching can come from very old versions of those populations which have since evolved quite a bit away from where they were when the user filled up their cache. When they return the results there's a lower chance for the results to improve the population of results we're currently working with.
So that's why our cache is so low, and we'd really appreciate it if you worked with us on this. There are other great BOINC projects out there which can help fill in missing crunch time when we go down, and the BOINC client can definitely handle running more than one at a time. So it might not be too bad to explore some of the other great research going on out there. :)
Thanks again for your time and understanding,
--Travis
IOW - quality, not quantity?
Yet another Milkyway problem. :pcwhack: I seems it never ends with them.
2011-02-10: MilkyWay@home - Issues with the Milkyway@home Support Server
The Computer Science account server at RPI has crashed, making it hard for us to access the Milkyway@home server. The staff is working hard to restore it.
We have to wait this one out. In the meantime, the Milkyway@home server may start doing crazy things - please bear with us until we regain access. Thanks!
-Matthew
Some interesting images of who crunches MW. From their website:
http://milkyway.cs.rpi.edu/milkyway/
Milkyway now (finally) has badges.. :thumbsup:
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3423&postid=60567 (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3423&postid=60567)
and
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3463#60878 (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3463#60878)
Thankfully they are clear and distinct, unlike NFS badges which are the same colour for all 3 apps, so require my nose to the monitor to see what they are. :jester:
Milkyway@Home has published a newsletter with highlights from the 2014/2015 academic year.
It is located at ...
http://milkyway.cs.rpi.edu/milkyway/fundraising_docs/MilkyWayNews.pdf (http://milkyway.cs.rpi.edu/milkyway/fundraising_docs/MilkyWayNews.pdf)
Booo...... They must be having server issues as noone's getting any work :( :thumbdown:
Oh well. good excuse to boost my SETI numbers I guess.
Anyone here know anything about app_info.xml files?
Because I'm running a newer AMD card, they don't work anymore as standard. I was given a app_info.xml file which I copied into my BOINC directory to get things working again but it has now stopped working again.
I've asked the question over on the message boards but no help so far. This is what I'm currently using -
<app_info>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</name>
<executable />
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.567833</max_ncpus>
<plan_class>opencl_ati</plan_class>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64__opencl_amd_ati.exe</file_name>
<main_program/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1.0000</count>
</coproc>
</app_version>
<file_info>
<name>milkyway_separation_1.20_windows_x86_64.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>120</version_num>
<file_ref>
<file_name>milkyway_separation_1.20_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
^^ This now produces invalid or inconclusive WU's.
Got me stumped.
Thx
Flying blind here because I don't have the same hardware to test but there are 2 things quickly apparent. Firstly you are using an old version 1.20 application which is no longer supported. Secondly you have configured to run 2 tasks at once, which can cause problems sometimes. Assuming you don't want to do any MilkyWay CPU tasks then you could try the following:
Clean out all unsupported BOINC MilkyWay files by detaching and reattaching.
Stop BOINC, copy app_info.xml below plus copy 2 program files you've downloaded into Milkyway project folder.
Start BOINC again.
Download these 2 and save them somewhere in case BOINC has a hissy fit and deletes them. This will allow you to try again if need be without having to download again.
http://milkyway.cs.rpi.edu/milkyway/download/milkyway_1.36_windows_x86_64__opencl_ati_101.exe
http://milkyway.cs.rpi.edu/milkyway/download/milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe
Following app_info file will use 1 CPU core to support running 1 GPU task. For now, set computing preferences to use 100% of CPU time. Using less has sometimes caused problems. You can try changing it again if/when you get your GPU crunching MilkyWay properly.
<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_1.36_windows_x86_64__opencl_ati_101.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>milkyway_1.36_windows_x86_64__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway_separation__modified_fit</name>
<user_friendly_name>Milkyway Sep. (Mod. Fit)</user_friendly_name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<cmdline></cmdline>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
This app_info was extracted from one posted on MilkyWay. Hopefully it will work for you. If it's not a configuration issue it may be a driver incompatibility.
As always, should you or any of your Crunching Force be caught or killed, Dingo will disavow any knowledge of your actions. This tape will self-destruct in five seconds. Good luck, chooka. :boom:
HAHAHA Thank you very much Kashi!
I managed to get it working again now. Yes, I run 2 tasks at the same time which uses 100% of my GPU. Running 1 task at a time underutilised the card.
All seems good now. :thumbsup:
:AUS:
Glad to hear you got it working again. Well done. v:
Eureka! MW has ordered a new server (hopefully with sufficient storage).
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4383#68034
I agree DM!
Do you know why the server/database goes down usually every 24hrs? It's bloody annoying.
Lets hope it fixes things :thumbsup:
Quote from: chooka03 on March 06, 2019, 12:04:52 PM
I agree DM!
Do you know why the server/database goes down usually every 24hrs? It's bloody annoying.
Lets hope it fixes things :thumbsup:
I think they bring them down early in the AM (eastern time) to run a cleanup job otherwise they run out of space. They were down all weekend because of some power upgrade at the university. They have been up since then.
:bloodshot
If you are running MW, check your invalids. Since the last outage the invalids are about 8-10%. I have set the project to "no new tasks" until they resolve it.
EDIT: Also they received their new server today so expect some downtime over the next few days.
MilkyWay@home was featured in an Astrobites article earlier this month ...
A supercomputer made of idle CPUs rewinds stellar streams (https://astrobites.org/2021/03/04/milkywayathome/)
The project has published a new paper:
https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4839#71760
Well there goes another GPU project!
Guess that's the end of Milkyway for me. I don't bother with CPU work.
Separation Project Coming To An End
Dear Volunteers,
We are beginning to sunset the Separation project (note that this is different from the N-Body project, which still needs your help!!!). Thanks to your computational contributions, we have completed the goals that we set out to accomplish with this the project, so we are going to shut down the Separation project in the near future. We are planning on submitting a paper containing the final results of the Separation project to an academic journal in the near future. It is possible that the reviewer may request revisions that involve re-running Separation data, in which case we might bring it back for a short time, but until that happens we do not need your computer time for this. We would like to sincerely thank you for all the time and effort that you spent helping us complete this substantial task. We owe the success of the project to you all.
With this announcement comes a few updates to MilkyWay@home: MilkyWay@home will continue to exist, but only as the Nbody project. Because of the complexity of running Nbody tree codes on GPUs, there is little speed-up from running Nbody on a GPU compared to an equivalent CPU. Although we did beta-test a full GPU Nbody application, we have decided not to deploy it due to concerns over maintaining its support; among other issues, supporting GPU Nbody would require changing the GPU code every time the CPU code is updated, and making sure every change is tested and works identically on both platforms. Since we are actively working on extensions of the Nbody code that include such things as the effects of the Large Magellanic Cloud's gravity and the consequences of self-interacting dark matter on the formation of tidal streams, this parallel support would be difficult. So, when Separation shuts down, we will be ending GPU support for MilkyWay@home. This will have the greatest impact on people who crunch lots of Separation work units on high-end GPUs; these users can expect to earn a much lower amount of credit per time than they did before. If you contribute only CPU cycles, your ability to earn credit will be unaffected. We still want as many people to contribute CPU time to MilkyWay@home as possible! However, we understand that if your goal is to use GPUs to obtain a large amount of credit quickly, there are more efficient ways to do this and other projects that can better use your resources.
We would appreciate your input on this because we expect that it will probably take some time for GPU-oriented users to swap that hardware over to different projects. How long would you like us to wait before we shut down Separation?
Again, thank you so much for letting us use your processors! They have not only increased our knowledge of the Milky Way galaxy that we live in, but they have also contributed to five PhD theses and trained dozens of undergraduate students to build and maintain large and complex computing systems. These students and I thank you for your contributions. We will be posting the results of the final Separation project results probably later this year, after they have gone through the peer review process (which takes about six months on average, with wide variability).
Best,
Tom & Prof. Newberg
Quote[Milkyway@home] Commenting on Recent Issues with the server
Hello everyone,
I wanted to apologize for the recent server issues. The migration brought unforeseen challenges, particularly with DNS changes. As a newcomer to server management and BOINC projects, I've been on a steep learning curve to transition this project to a new server.
As mentioned in a previous post, and reiterated here, we have set up a temporary DNS entry for milkyway-new that now points to the server. The changes will take some time to become effective (I don't have a specific timeline, but I'm closely monitoring the process). This update will allow for downloading older work units linked to milkyway-new and uploading completed ones.
I'm immensely grateful to all the volunteers who have suggested fixes and assisted others with client-side issues. Your contributions have significantly accelerated problem-solving during this server migration. I can't thank you enough for your support.
To those who have voiced frustrations, I apologize for any shortcomings in my expertise. I recognize the value of the computing time you generously volunteer and understand your desire for acknowledgment of your contributions. I encourage you to continue sharing your concerns, as long as they are respectful. Destructive or derogatory comments don't contribute constructively to our project. We aim to foster a positive environment at MilkyWay@home for everyone passionate about science and distributed computing, free from unnecessary negativity.
One common concern has been the need for better communication. Despite my efforts to preemptively share updates, it appears more is needed. I would like to improve in this area. I'm considering regular updates (weekly, bi-weekly, or monthly) and would appreciate your thoughts on this. Please share your ideas in the comments on how I could improve communication.
On a related note, we are excited to announce that we're currently developing a new version of the n-body code. This upgrade will allow for the fitting of additional parameters, such as orbit parameters, along with other minor improvements. We anticipate implementing these changes in the coming weeks.
Additionally, we are making plans to reintroduce support for Mac users. More details will be provided as soon as we have further information.
Once again, I apologize for the recent issues with MilkyWay@home and am very thankful for your patience.
Best regards,
Kevin
View article (https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=5064)· Wed, 29 Nov 2023 22:02:25 +0000
Quote[Milkyway@home] Admin Updates
Hello everyone,
This thread will be used as a place for project admins to post updates.
If you have a comment or a question, you should post those in the appropriate threads.
There is also an Admin Updates Discussion thread (https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=5068)for further discussion on the updates.
Thank you,
Kevin
View article (https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=5069) · Fri, 15 Dec 2023 19:56:07 +0000