log in
1) Message boards : Number crunching : Download bandwidth error message from server. (Message 4000)
Posted 27 Feb 2017 by Profile Nathan Neitman
We still are lead to believe that the issue stems from everyone downloading the updated Python app, subsequently consuming our bandwidth. There is not a whole that can be done on our end, other than wait out everyone downloading the update.

The problem should sort itself out in the next couple days after everyone gets the newest update, and everyone can get back to crunching like normal.

Thanks for contributing and happy crunching,
2) Message boards : Number crunching : Last few WU's giving less credit? (Message 3871)
Posted 19 Aug 2016 by Profile Nathan Neitman

You should see your credit received for the work you are doing returned to normal now.

Thanks for your support and happy crunching,
Nathan Neitman
3) Message boards : Number crunching : Latest MM WU's Not Obeying Use at Most CPU Time (Message 3848)
Posted 2 Aug 2016 by Profile Nathan Neitman
There was a mistake on our end when we told you the BOINC version, we actually have the same version as you running on our test box (7.2.42 x64). So, the issue appears not to be the BOINC client version.

So, to rehash Brandon's previous post: BOINC does not throttle how much your CPU is used similar to how you would throttle a car's engine by how hard you press the gas pedal, but instead limits usage by restricting how long the BOINC process runs for (Or to go with the example how long you press the pedal).

A possible case for why you're seeing the 100% CPU usage via Psensor is that pretty much all monitoring software works via snapshots of utilization. The utilization amount is decided by your OS based on how many operations it has queued up (really how busy it is going to be). At that moment of the snapshot you may see that BOINC could be well over your desired CPU usage, but if you have a graph over time instead of the snapshot you will see that the usage should be close to what you set (allowing some variance because the snapshots could potentially have an interval that falls in line with when the CPU is busy with BOINC processing).

A possible solution would be for you to dial back your CPU time setting to something like 40% or so, and seeing if that produces more favorable temperatures. If not, you should dial it back further.

P.S. Thank you for making me aware of pSensor, it looks really cool! :)

Cheers and happy crunching,
4) Message boards : Number crunching : Linux machines giving up on downloads (Message 3821)
Posted 18 Jul 2016 by Profile Nathan Neitman

To begin diagnosing your issue, we will need you to please enable "http_debug" in your event logging. This will allow us to begin seeing why your work units are not being uploaded properly.

Thanks for supporting us and happy crunching,

5) Message boards : Science : Results Publishing (Message 3508)
Posted 10 Jul 2015 by Profile Nathan Neitman
Here you go Doktorn, this page has a general project overview for the projects with a list of the jobs that have been ran for each project: https://mindmodeling.org/research_project.php?project=all

We're currently working to create a more streamline and transparent system for reporting the science that is occurring both behind and in front of the curtain of MindModeling! But, until then you can use this page as general overview of each project.


Main page · Your account · Message boards

Copyright © 2018 MindModeling.org