Posts by b1llyb0y

1) Message boards : Number crunching : Waiting for a team answer to this question (Message 73871) Posted 20 Sep 2012 by b1llyb0y Post: I understand where you are coming from, after all I am a long time folder myself. I believe you are missing the point, a project such as Rosetta is a massive under taking and I am almost 100% sure they are under staffed. Its not that they dont give a damn, its they dont have enough time in the day to get everything done. I run a small business and this is the case for me everyday, just imagine how the staff feel at Rosetta. What I am essentially wanting to say, is its not as clear cut as "they are not responding so they dont care." At the end of the day its your choice whether you stay or go, but you should put yourself in their shoes for a few days then you will understand (even if only by imagination). If you are doing it for the points, you are doing it for the wrong reasons. If he was doing it only for the points, he probably wasn't here, there are projects paying a lot more. The credits are a measure for the amount of job done for the project, watching them means also watching that my machines are doing useful job for the project. If I am going to burn electricity all the time for this project, I just want to know that my machine is processing things correctly. Its a mental thing the points. If my machine is going to crunch for x hrs or whatever then I mentally want to see that I am getting the right amount of credit for it. And the above comment about not wanting to do anything about problems like I have found here with version 7 and not putting out a notice or a thread about this problem or even bothering to reply to something about this problem shows that the team really does not give a damn. Of course if I leave then there will be plenty others to take my place. Key thing is, why waste my resources on a malfunctioning non news no reply project? It is really bizarre how the guys at Einstein can put notices on their page when they find something interesting or have a task malfunction badly or a IT problem and also send out notifications when they have made a big discovery and this project does none of the above. never has, never will. Pretty sad really.
2) Message boards : Number crunching : Waiting for a team answer to this question (Message 73860) Posted 19 Sep 2012 by b1llyb0y Post: If you are doing it for the points, you are doing it for the wrong reasons. Let's see if anyone from the team is paying attention. The question is: Why are all the hyb_******* tasks only giving a fixed credit of 20? This is messing with my RAC and is starting to annoy me. Why can't you guys make them give credit more like a real task instead of some toy task? I am into the science for you guys, but at the same time it makes me feel like I am wasting CPU time on such ridiculous amounts of credit.
3) Message boards : Number crunching : Alot of Errors on Frizzled Workunits (Message 73567) Posted 4 Aug 2012 by b1llyb0y Post: I have not gotten errors on my Mac yet with those work units, but your version of Boinc is out dated .. It is now at 7.0.31. Looking at my tasks, almost all Workunits I get that start with Frizzled have errors. Its not just me either, as the other computer that has crunched the same workunit also got a client error. Anyone else getting this, and is this a problem with the Workunit. Running the latest BOINC 6 for Mac BTW.
4) Message boards : Rosetta@home Science : 10 reasons I crunch R@H and you should too (Message 73383) Posted 7 Jul 2012 by b1llyb0y Post: What a load of rubbish, there are over 5 million work units according to my last count. 10 reasons I left Rosetta: 1-10 Never any work!!
5) Message boards : Number crunching : Rosetta@Home Version 3.24 (Message 72666) Posted 5 Apr 2012 by b1llyb0y Post: Maybe you could solve the problem by not sending those particular work units to Mac's? Unfortunately, it probably isn't going to get resolved in the foreseeable future. The problem is there's a complex interaction between the Rosetta@home code base and a compiler bug which means that trying to compile with full optimizations just doesn't work (the compiler gets stuck in an infinite loop). While the bug has been fixed in the latest versions of the compiler, using them means that we lose compatibility with all but the most recent MacOS versions. We've been banging on this multiple ways, and have tried numerous settings on multiple machines (you name it, we've probably tried it), and haven't been able to come up with anything which simultaneously allows compiling with optimizations and support for the full range of MacOS versions currently being used. We've made the decision to provide a working, albeit slower, R@h to all Mac users, rather than forcing everyone to update to the latest OS version. It sucks, but unfortunately it's the position we're stuck with for the foreseeable future. [/quote]
6) Message boards : Rosetta@home Science : DISCUSSION of Rosetta@home Journal (5) (Message 72639) Posted 2 Apr 2012 by b1llyb0y Post: I completely agree, whilst I understand the researchers and scientists are very busy doing their job it would be great to get feedback more often, it would also encourage more folks to join. Folding@Home is doing a pretty good job in keeping their crunchers happy with info, Rosetta should be doing the same ..
7) Message boards : Number crunching : Mac OS X Lion 10.7.3 + BOINC 7.0.18 = Compute error? (Message 72408) Posted 28 Feb 2012 by b1llyb0y Post: I am part of the boinc alpha test, and can say that 7.0.15 had compute errors, 7.0.18 has resolved it for me so far. That being said, If you are not a part of the alpha testing you should not be using it .. switch to a public release OR become part of the alpha testing team. Recently rosetta@home tasks began to give me "Compute error". Probably it is somehow connected with recent rosetta@home application updates. Now I have no other choice but to abort the incoming tasks.