Welcome to MilkyWay@home

Posts by Keith Myers

1) Message boards : Number crunching : Not receiving enough with WUs (Message 70876)
Posted 5 days ago by ProfileKeith Myers
Post:
Well then, your next choice would be to spoof the gpu count to increase the number of tasks allotted. Edit the coproc_info.xml file to clone the original card entry multiple times then lock the file afterwards so BOINC can not update or change your new values.
2) Message boards : Number crunching : Not receiving enough with WUs (Message 70874)
Posted 5 days ago by ProfileKeith Myers
Post:
Number of tasks requested depends on the BOINC settings for "days of work" and "additional days of work" with the maximum being 10/10.
But the project limits the total amount of tasks carried by a host to ngpus X 300. So for your two cards you will be allotted 600 tasks maximum to be carried daily in your cache.
3) Message boards : News : New Separation Runs 6/9/2021 (Message 70872)
Posted 7 days ago by ProfileKeith Myers
Post:
All my tasks, invalid, valid or errored show the lua error. Just as Tom stated, the printed error is innocuous and has no bearing on the real reason for invalid or errored tasks.
4) Message boards : News : New Separation Runs 6/9/2021 (Message 70866)
Posted 8 days ago by ProfileKeith Myers
Post:
I've had nary a problem with these new stripe 84/85 runs. Much better than previous attempts.
Good job!
5) Message boards : Number crunching : possible problem with one of my computers (Message 70863)
Posted 10 days ago by ProfileKeith Myers
Post:
Your gpu does not support double-precision. Too old. From all the stderr.txt outputs of your failed tasks.

Device doesn't support double precision

MW@home requires a gpu that can do double-precision floating point operations.

Best to deselect any gpu app and only use the cpu for that host. If necessary move it to another venue/location than your other hosts to set cpu only tasks.
6) Questions and Answers : Getting started : Credits Not Showing up in GP (Message 70854)
Posted 13 days ago by ProfileKeith Myers
Post:
The 3 pools all award accumulated credit at varying intervals because of their different staking frequencies. Apparently Pool-1 took 3 days to payout in the last interval. Lots of posts about missing payments in the GRC forums. So you just have to be patient.
Also, you really should be asking these kind of questions over in the GRC forums/communication channels.
7) Message boards : Number crunching : Do Windows machines prefer other Windows for validation? (Message 70841)
Posted 21 days ago by ProfileKeith Myers
Post:
This is common on projects with multiple app platforms. The applications produce slightly different results and the validators don't have sufficient tolerance settings to allow validating different platforms against one another.
8) Questions and Answers : Getting started : Credits Not Showing up in GP (Message 70839)
Posted 25 days ago by ProfileKeith Myers
Post:
MW@home does not require stats authorization for 3rd parties. So that isn't the issue.
Common solution I see posted all the time for the GRC pools is doing a sync or whatever. Not sure as I don't do the pools.
9) Message boards : News : Where MilkyWay@home Was The Last Few Days (Message 70803)
Posted 19 May 2021 by ProfileKeith Myers
Post:

Thanks for the info, but what is RPI??? lol


Rensselaer Polytechnic Institute
10) Message boards : Number crunching : I gotta remember... (Message 70794)
Posted 17 May 2021 by ProfileKeith Myers
Post:
Is your Mint Update Manager actually a wrapper around Synaptic? Confused why your error message says it is ready to launch Synaptic.

In Ubuntu the Update Manager is a standalone application and the same for Synaptic. They are not related and neither invokes the other.

What happens when you use Synaptic to do the update and get your firmware update via that application instead of using the Update Manager?
11) Questions and Answers : Unix/Linux : MW stopped using my nvidia GPU (Message 70776)
Posted 5 May 2021 by ProfileKeith Myers
Post:
Post the output from the Event Log when requesting work with the sched_ops_debug flag set. How many seconds of gpu work are you requesting?
Also post the startup of the Event Log after starting BOINC to be sure the gpu is detected.
When those are posted and nothing is self-evident, go back and set work_fetch_debug to show why BOINC is not requesting MW work.
12) Message boards : Number crunching : This task has been stuck with validacion error since end of january (Message 70775)
Posted 5 May 2021 by ProfileKeith Myers
Post:
Absolutely no impact to users. Simply an annoyance for OCD types. Wait till summer to purge the database.
13) Questions and Answers : Unix/Linux : MW stopped using my nvidia GPU (Message 70767)
Posted 4 May 2021 by ProfileKeith Myers
Post:
With Windows drivers, always reinstall the drivers directly downloaded from Nvidia.

Always check that you have the OpenCL component of the drivers installed with clinfo. Available for both Linux and Windows.
14) Message boards : News : The Last Couple Days (Message 70759)
Posted 30 Apr 2021 by ProfileKeith Myers
Post:
Welcome to the project and forums. Search on n-body tasks stalling and you will find countless posts going back years on the problem. Mostly occurs on Windows and one of the things you can try is to stop and restart BOINC.

The other thing is to write up an app_config.xml file to restrict the n-body tasks to only use 2-4 cpus instead of their default of using all cpus concurrently.

Also if running any virus scanners, don't scan the BOINC folder or sub-folders as they can restrict writing necessary files and checkpoints for BOINC.
15) Message boards : Number crunching : I gotta remember... (Message 70743)
Posted 15 Apr 2021 by ProfileKeith Myers
Post:
Hi Siran, I alway forget you are using Mint. I dislike the Update Managers because they install updates behind the scenes and you don't know what they are installing normally.

I like to know beforehand what is going to be installed so I don't get bit in the arse.
16) Message boards : Number crunching : I gotta remember... (Message 70733)
Posted 13 Apr 2021 by ProfileKeith Myers
Post:
After doing a sudo apt update, you should follow that up with a apt list --upgradable to print out in the terminal just what packages are going to be installed when you do the sudo apt upgrade.

That way you can see if any of them are the video drivers or kernel updates that will require a reboot to be enabled. Just CYA with an extra step.
17) Message boards : MilkyWay@home Science : The Milky Way Has Shells (Message 70712)
Posted 3 Apr 2021 by ProfileKeith Myers
Post:
NP
18) Message boards : MilkyWay@home Science : The Milky Way Has Shells (Message 70709)
Posted 1 Apr 2021 by ProfileKeith Myers
Post:
Hey Everyone,

Dr. Heidi Newberg (the head of the MilkyWay@home project) recently made a video explaining our group's recent work. Did you know that our Milky Way Galaxy has shells? These were formed from a head-on collision between the Milky Way and another galaxy roughly 3 billion years ago! Hear about it in a short YouTube video here: https://www.youtube.com/watch?v=BC3NeNbO_qg&t=5s

While this result didn't benefit directly from the workunits that our volunteers crunch, it is still work that utilizes the MilkyWay@home software to perform new, interesting science about our Galaxy!

Best,
Tom

Thanks Tom, made the link clickable.
19) Message boards : Number crunching : Work units Unable to handle request. (Message 70705)
Posted 30 Mar 2021 by ProfileKeith Myers
Post:
Thanks for your comment, Tom. Good to know you have a plan to handle the problem.
20) Message boards : Number crunching : Work units Unable to handle request. (Message 70703)
Posted 27 Mar 2021 by ProfileKeith Myers
Post:
That would have to be a LOT of new work to wrap around to the beginning to cause such an issue. Also I'm sure that the admins will note the lost work unit ID's and make an exclusion table when the database wraps around to those values.

Or they could do as I suggest and simply wipe the database and start fresh anew.


Next 20

©2021 Astroinformatics Group