21) Message boards : News : Windows 32-bit Application Release (Message 64972) Posted 3 Aug 2016 by Wisesooth Post: Did anyone tweak the 64-bit software affecting Windows 10 Intel systems? If not, Microsoft did a number on themselves. I tried a Windows Solitaire Collection challenge while BOINC was running in the background. Solitaire app randomly aborted. When I suspended BOINC masnager, it still happened. When I changed my account preferences and disabled BOINC use of the GPU, it still happened. When I restarted the machine without bringing up BOINC manager, Solitaire behaved itself. I exited solitaire gracefully and launched the BOINC manager. I usually pick on a game to test compatibility because this is where people get careless with getmains and freemains. Some even try to do recursive calls. Hope this helps you.

22) Message boards : News : MilkyWay@home Linux 32-bit Version 1.37 (Message 64830) Posted 7 Jul 2016 by Wisesooth Post: The feeder server is down. All of my tasks are ready to report. What's happening?

23) Message boards : News : Nbody Release 1.60 (Message 64539) Posted 7 May 2016 by Wisesooth Post: Hello Sid, Reference UID 1028971 Task 1584882935 sent 4 May 20:16:12 UTC Reported/expired 6 May 4:40:20 UTC on my machine 683929 Task consumed run time 90:487:50 CPU: 337,941.60 This is a 4 month old machine with an Intel i5-6000 3.30 GHz CPU and 8 GB RAM on board. Hope this helps you. Wisesooth PS: I did some design work on your GO button. Did Heidi share it with you?

24) Message boards : News : Nbody Release 1.54 (Message 64104) Posted 16 Nov 2015 by Wisesooth Post: Sounds familiar. I fat fingered my mouse when it happened to hover over "Send no more work" button when I first started. Check if you have something wrong in your global preferences. If you are on the BOINC Basic window, click on ADVANCED. Next, click on the PROJECTS button at the top. It will show a list of projects you chose to run. Click on the Milkyway project to highlight it. A pane will show on your left. Go to the Milkyway home page (the bottom button). Once you are there, scroll down until you see PROFILES and launch that. Look on the bottom of the next screen and select "My Account." (NOTE: I did not design this.) You will see two preference buttons. You want to open "Preferences for this project." The next screen shows a list of task types you gave permissions to download. They have check boxes on the left of each task type. If none of them are checked, that is your problem. Look for a tiny "edit" button and select it. Now you can check the boxes for the task types you want to run. Click on SAVE and close the page. That should get you back to the PROJECT window. Click on UPDATE (the top button). When it finishes doing its thing, click on the TASKS pane. Hopefully, you will see Milkyway tasks flowing into your list. Hope this helps you, and thank you for crunching for milkyway. A fellow cruncher,

25) Message boards : News : Nbody Release 1.54 (Message 64102) Posted 16 Nov 2015 by Wisesooth Post: I do not know if this has anything to do with nBody, but Cortana and Start menu have failed twice recently in Windows 10 while running BOINC. System logged me off and back in again when I pressed Microsoft's "fixit" button. BOINC did not like that at all. Milkyway tasks restarted from last checkpoint. Looks to me like Cortana is misbehaving when BOINC is running. I have no Cortana mischief in other Windows 10 systems. Thought you might like to know. BTW Sidd, I started to work on a cool GO button for you. See Heidi for details.

26) Message boards : News : New Release- Nbody version 1.52 (Message 63988) Posted 11 Oct 2015 by Wisesooth Post: Just upgraded my liquid-cooled Intel i7 to Windows version 10. Noticed two errors on my stats within an hour or two, even though I suspended the tasks without leaving their state in cache before I started. Windows the new Win 10 OS called shutdown() for some strange reason (probably an update requiring restart). It did not bring BOINC down gracefully. Checkpoint did not recover the task successfully after I resumed activity. Thought you might like to know.

27) Message boards : News : New Release- Nbody version 1.52 (Message 63929) Posted 13 Sep 2015 by Wisesooth Post: I run Milkyway@home on two machines: an i7 Intel liquid-cooled screamer, and a mini-ITX PC with an Intel i5. Most of the time the N-Body tasks finish quickly. However, I found two very long-run tasks; one on each machine. Task 1252250516 WU 922273871 CPU i7 RT 6719.88 CPU-Time 40511.71 Task 1253332518 WU 923062623 CPU i5 RT 5528.59 CPU-time 20362.66 Both finished and await consensus. Remember, you asked.

28) Message boards : News : Fix for stderr.txt Truncation and Validation Errors (Message 63889) Posted 25 Aug 2015 by Wisesooth Post: Still running 7.4.42 but upgraded to Msoft V-10 on two PCs. Both use i5 Intel processors. One runs 32-bit; the other 64-bit OS. The 32-bit machine runs only seti@home. The 64-bit machine runs only milkyway@home. Both machines are running without problems. Thought you might like some good news for a change.

29) Message boards : News : Nbody Status Update (Message 63845) Posted 31 Jul 2015 by Wisesooth Post: You mentioned about compiling nbody on an XP machine. Last I recalled, XP was only 32 bit. You seem to be doing a lot of floating point arithmetic. Are you doing double-precision? If so, wouldn't a 64-bit compiled version have to use different code and at least a 64-bit compiler? Am I missing something?

30) Message boards : News : Nbody Status Update (Message 63797) Posted 13 Jul 2015 by Wisesooth Post: Hello Sid, Great detective work. However, I might have a "heads up" for you to think about. Microsoft is planting Version 10 on PCs round the world in waves starting sometime around August 2015. I am fairly sure that folks running Windows 8 will gladly update to get rid of the painful "anomalies" in version 8 and 8.1. Eventually, Windows 7 users will convert to 10 once they see that version 10 is reliable. This migration is bound to affect grid computing projects. I do not know if Windows 10 will require new driver upgrades for chipsets and other motherboard internals, but you may want to consider that a scary thought. Microsoft is not talking about it, even when asked. If you have connections, ask. It might affect your code. Windows anything causes weird stuff to happen with multithreaded apps because it causes timing issues. Watch your back.

31) Message boards : News : server issues (Message 63739) Posted 17 Jun 2015 by Wisesooth Post: Thanks for the info, Jake. You asked about server issues at our end following the scheduled power outage. Earlier today, I saw that user update requests were not handling tasks ready to report. I checked the "server status" button and found that about 7 or server tasks were down with errors. All of them seemed to be related to a database corruption with MySQL. I suspect that you may have corrupted indexes. I know little about the "secret sauce" that lubricates the grid, but I had some past experience with MySQL that were not very pretty. The servers may think they are running, but not be aware that they are running in circles. Seti@home had a similar problem months ago. They had to rebuild their database from scratch. Hope this is helpful.

32) Message boards : News : server issues (Message 63683) Posted 7 Jun 2015 by Wisesooth Post: Something else seems strange. I am getting responses that some of my results (14) are inconclusive. I see no errors for my other BOINC project and all results are verified correct. Also, the cobblestones on my profile do not match what BOINC charts on my machine. According to BOINC, I have 2.02 billion cobblestones. yet my profile shows slightly less than 2.0 billion. That is a 2 percent difference. Now the count for this post in the signature area shows slightly over 2 billion. Thought you might like to know.

33) Message boards : News : Windows Users-please abort Nbody tasks (Message 63675) Posted 5 Jun 2015 by Wisesooth Post: Does anyone have any idea about the impact of Windows 10 on BOINC and milkyway project?

34) Message boards : News : Windows Users-please abort Nbody tasks (Message 63621) Posted 20 May 2015 by Wisesooth Post: Thanks for the correction. I couldn't find the original quote. I used one from the lamestream media. Big mistake!

35) Message boards : News : Windows Users-please abort Nbody tasks (Message 63619) Posted 19 May 2015 by Wisesooth Post: The author of Sherlock Holmes once wrote, "When all possibilities are impossible, what remains is possible." Statisticians concerned about software quality ponder and try to contain what they call "degrees of freedom." Grid computing offers degrees of freedom on steroids. There are different varieties and flavors of machines, operating systems, versions of same, different processors tuned to optimize different things, different versions of CMOS, stepping levels, and driver issues. How does one design and code software to defend against all of these possibilities, especially in a heuristic simulation mode? That seems to be a daunting challenge. In addition to the above, anti-virus software sometimes behaves like an electronic version of Lupus when it spots a task that looks like a resource hog. Ditto for high-priority load balancing software provided with high-performance motherboards. If these do not bring BOINC to its knees, automatic updates requiring automatic restart trash cache memory, RAM, and even corrupt general registers so apps cannot close during a warm restart. Please cut Sid some slack.

36) Message boards : News : New Nbody Version 1.50 (Message 63574) Posted 14 May 2015 by Wisesooth Post: I have a task simulation of version 1.50 running on an i5 Intel with an Asus motherboard. The motherboard utility lets me monitor processor stats. It is using all four threads, but at a fraction of their capacity. The BOINC timer gets to 100% or 99.98% and stays there. I let the latest 1.50 simulation run for 19 hours. Another machine uses an i7 Intel processor. It has been running a 1.50 simulation for 11 hours. This machine also runs SETI so it shares a thread to run a GPU task while any milkyway task is running. The milkyway task ties up all 8 threads, but uses only four at a fraction of their capacity. One thread occasionally peaks at around 60% while the other three run as low as 2%. This machine is a liquid cooled screamer. It is barely above idle. Hard drive and network activity is less than moderate or nil. It seems to be contemplating its wait states. I cannot run a single simulation task to completion. I have no choice but to abort ALL simulations of any version. I have no problems with SETI or single-thread milkyway tasks. My machines speed up to capacity crunch mode as soon as I abort the simulation task. I hope this info helps. PS: The author of Sherlock Holmes once wrote something like this. When all alternatives are impossible, what remains is possible.

37) Message boards : News : New Nbody version 1.48 (Message 63329) Posted 7 Apr 2015 by Wisesooth Post: I had to abort n-body tasks after they ran anywhere from 25 hours to three days at 100% before I aborted them. 100% is not just a number; it also is a clue. If the task is in a long loop while using multiple-core threads, the cause may be a persistent timing issue. This anomaly occurs when a task uses multiple processor threads to calculate a heuristic solution. Boinc uses machines of all kinds of capabilities. Most of them are not designed for intense scientific computation. Statisticians talk about "degrees of freedom." Grid computing by its very nature introduces potential instability in multi-core tasks. I currently am having no problems with n-body 1 tasks. I am having problems with n-body 2 tasks.

38) Message boards : News : MilkyWay@home Server Maintenance (Message 63298) Posted 29 Mar 2015 by Wisesooth Post: I am still getting what looks like a program loop (possibly thread timing loop) in the orphan sim 2 simulation tasks. The last one ran 35 hours using 8 threads on an Intel i7 before I aborted it. This was a 48MT task. Thought you might like to know.

39) Message boards : News : New Nbody version 1.46 (Message 63238) Posted 15 Mar 2015 by Wisesooth Post: One of my machines is essentially dedicated to milkyway@home. Every instance of n-body 1.46 is failing with a computation error within seconds of start. This machine has an i5 Intel processor but uses a 32-bit Windows OS. Although the i5 has 64-bit instruction support, 32-bit Windows does not know what to do with 64-bit anything. Could this be the reason why I am getting the computation errors? The Milkyway@home 7.0 stuff works fine. The n-body simulation stuff does not work at all. My 64-bit screamer (liquid-cooled i7) runs both milkyway and seti tasks. I receive no n-body 146 stuff; only n-body 1.48. Although these tasks run to completion and report, the server reports a significant amount of "inconclusive", "invalid" and "error" rejections. I receive no errors or "invalids" from seti tasks. Processor core temps are well below the limit that would create excessive heat or overclocking instability. Seti seems to be using deterministic algorithms. Milkyway seems to be using heuristic algorithms. If there is a randomizer in the code, I smell "Monte Carlo" in the hypotenuse. Heuristic algorithms do not produce answers that absolutely match. They produce answers that are statistically close (well, most of the time). Could this explain the anomalies that are unique to milkyway tasks?

40) Message boards : News : New Nbody version 1.46 (Message 63102) Posted 5 Feb 2015 by Wisesooth Post: This is a "heads up." I occasional encounter a hung task while crunching n-body simulations using all 8 threads of my liquid-cooled Intel i7. It reaches either 100% or 99.999% and stays there until I manually abort it. The last abort was ps_nbody_12_20_orphin_sim_3_1422013803_27545_1. The prior instance lasted 2-1/2 days before I discovered it. Hope this helps.

Previous 20 · Next 20

©2024 Astroinformatics Group