Welcome to MilkyWay@home

Posts by JohnMD

1) Questions and Answers : Getting started : Project download error (Message 68335)
Posted 22 Mar 2019 by ProfileJohnMD
Several days BOINC Manager can't download milkyway_1.46_windows_x86_64__opencl_ati_101.exe. Speed = 0.0KBps always. Status - active. Reload or refreash project not helped. Other projects has no such problems.Firewall - off (exeption had same result)

22.03.2019 0:06:46 | Milkyway@Home | Temporarily failed download of milkyway_1.46_windows_x86_64__opencl_ati_101.exe: connect() failed
22.03.2019 0:06:48 | Milkyway@Home | Started download of milkyway_1.46_windows_x86_64__opencl_ati_101.exe
22.03.2019 0:06:50 | | Project communication failed: attempting access to reference site
22.03.2019 0:06:51 | | Internet access OK - project servers may be temporarily down.

In task list for all Milkyway@Home status = downloading data

You have hidden your machine(s) so don't expect hardware help.
2) Message boards : News : New Server Update (Message 68325)
Posted 21 Mar 2019 by ProfileJohnMD
I think I found the issue with the credit assignment. It seems that the newest BOINC server version no longer supports how we would set the credit per workunit. Should be a pretty easy fix, I am working on an implementation now.



Is it supposed to be about 100 points lower then before? I'm seeing a static value of 133.62 while the old ones varied slightly depending on task length at 227.17 and 243.61. Run times seem the same.

I got "old" credit for one of my WUs -
But all the others are still getting "new" credit
3) Message boards : News : Changing Workunit Priority to 1 from 0 (Message 67201)
Posted 4 Mar 2018 by ProfileJohnMD
Hey EG,

This is very strange. I'm not sure what's going on here, but I will look into it.


The phrase "Use Reliable Host" might explain it all. New hosts and reawakened old hosts have zero history and therefore no reliability.
The object of the exercise is "Don't Use Unreliable Host" - can you find a parameter for that instead ?
I too would like to rejoin...
4) Message boards : News : Running Modfit on MilkyWay@home (Message 64759)
Posted 26 Jun 2016 by ProfileJohnMD
Hi Jake,
Have you any idea how many 32-bit Intel Core 2 machines there are out here ?
Many upgraded to Windows 10.
I would hardly call them
extremely old systems

If it's XP you can't support, so filter on NT 6 or higher instead of 64-bit.
Do-it-yourself solutions are NOT the aim of BOINC.
5) Message boards : Number crunching : SSE4.1 slower than SSE3 ? (Message 64360)
Posted 5 Mar 2016 by ProfileJohnMD
Is it possible to force SSE3 on cpu with SSE4.x capability ?
6) Message boards : Number crunching : app 'milkyway_nbody', plan class 'mt' doesn't match any app (Message 64352)
Posted 28 Feb 2016 by ProfileJohnMD
This "app_version" used to work. Can someone tell me how to find the new version ?
Thanks in advance
7) Message boards : Number crunching : Guidence from Project Team Requested (Message 4229)
Posted 17 Jul 2008 by ProfileJohnMD
After seeing some of the times, I'm thinking that the "medium" length ones will probably work out the best for everyone, so figure on timings roughly around what you're getting with the 373... series.

As for the rest, I got my times wrong and Travis is flying back today, so tonight or tomorrow we should have some of the timing issues fixed.

It sounds like you know pretty well how many cycles are required for each unit. Whether they last 12 minutes or 12 hours on my P4 doesn't bother me as long as these cycles get translated into realistic (say, factor 2 ?) runtime estimates.

One thing that does bother me is that the project can apparently choose unit sizes quite arbitrarily - are they getting 60 times the science from 12-hour units compared with 12-minute ones ?

©2019 Astroinformatics Group