1)
Message boards :
Number crunching :
do you NOT overclock? (and crunch 24/7)
(Message 63962)
Posted 5 Nov 2009 by Robert Everly Post: New i5/750 build. Not overclocked (yet). Little over 1000ppd, 50/50 split between here and Einstein. 2 cores each. So it would be around 2000ppd if all 4 cores were here. Einstein is around 1500ppd (3000ppd if solo project). Both are close to leveling off, but not quite yet. http://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=1168293 |
2)
Message boards :
Rosetta@home Science :
Energy vs rmsd plots
(Message 29355)
Posted 15 Oct 2006 by Robert Everly Post: Would it be possible to view these same plots for teams? |
3)
Message boards :
Rosetta@home Science :
DISCUSSION of Rosetta@home Journal (2)
(Message 18869)
Posted 18 Jun 2006 by Robert Everly Post: Are there other suggestions for feedback we could give? Certificates, etc. we could think about if people would like this, but we would certainly need this to be at least in part handled by a volunteer group as we are swamped with CASP. Printable certificates would be cool. I'm sure someone that knows some PHP (not me) could modify the Seti certificates for use here. Would be neat to have them available for milestones and top predictions. The seti certificates are located in the repository Here. They are Cert1, Cert2 & Cert3. |
4)
Message boards :
Number crunching :
There is nothing in my Team page. Why?
(Message 18818)
Posted 16 Jun 2006 by Robert Everly Post: Blank for me at first. Switching to most any other encoding from Unicode will display the page. Something is strange with the page. |
5)
Message boards :
Number crunching :
Report Problems with Rosetta Version 5.22
(Message 18758)
Posted 16 Jun 2006 by Robert Everly Post: Here's one that went crazy. resultid 23976562 On this host hostid 214416 This host does nothing but crunch. Another host did complete the WU sucessfully. <core_client_version>5.4.9</core_client_version> <message> - exit code -1073741819 (0xc0000005) </message> <stderr_txt> X_NB neighbors increase MAX_NB in param.cc allatom: 1434 res: 95 atom: 1 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1434 res: 95 atom: 1 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1434 res: 95 atom: 1 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1434 res: 95 atom: 1 has more than MAX_NB neighbors *snipped a lot of lines* allatom: 1567 res: 103 atom: 4 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1567 res: 103 atom: 4 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1550 res: 103 atom: 5 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1550 res: 103 atom: 5 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1550 res: 103 atom: 5 has more than MAX_NB neighbors increase MAX_NB in param.cc allatom: 1550 res: 103 atom: 5 has more than MAX_NB neighbors Unhandled Exception Detected... - Unhandled Exception Record - Reason: Access Violation (0xc0000005) at address 0x0061B538 read attempt to address 0x790C3DE3 Engaging BOINC Windows Runtime Debugger... |
6)
Message boards :
Rosetta@home Science :
Rosetta AP article!
(Message 17732)
Posted 6 Jun 2006 by Robert Everly Post: Noticed the CNN.COM article didn't provide a link to the project. So I sent a request to the editor. You can too at this link http://www.cnn.com/feedback/dotcom/ |
7)
Message boards :
Number crunching :
Rosetta in the news!
(Message 17727)
Posted 6 Jun 2006 by Robert Everly Post: Indirectly Rosetta made the local news here in Cleveland, OH. In there little tech segment on Fox 8 they were talking about something and had the CNN.COM page on the screen. On the CNN page was the picture of Dr. Baker & a computer running Rosetta. The image was large enough to see the graphics and the news people told the views to go to CNN to read more about whatever they were talking about. |
8)
Message boards :
Number crunching :
Is this for real???
(Message 17391)
Posted 30 May 2006 by Robert Everly Post: What about those high credit claims? |
9)
Message boards :
Number crunching :
Just a heads up for you folks.
(Message 17279)
Posted 28 May 2006 by Robert Everly Post: A question for members of the teams vying for dominance--Rom is currently working on an a benchmark internal to the rosetta code that will ultimately used in calculating credits. would you like to see this on rosetta@home sooner or later? Sooner. Absolutely without question. Just make it fair. |
10)
Message boards :
Rosetta@home Science :
Comments/questions on Rosetta@home journal
(Message 16278)
Posted 14 May 2006 by Robert Everly Post: Today (Friday) we have closed accepting server predictions for the first Roger that. Crunching on. :) |
11)
Message boards :
Rosetta@home Science :
Comments/questions on Rosetta@home journal
(Message 16249)
Posted 14 May 2006 by Robert Everly Post: Today (Friday) we have closed accepting server predictions for the first What should be done with T0283 WUs that are still on our machines? Also. should the deadlines for the CASP7 WUs be just a bit ealier than the real deadlines. Back to the T0283. One of them I still got running has a deadline of May 27. But if the CASP deadline was May 12, will those results be of any benefit? |
12)
Message boards :
Number crunching :
Loss of credit?
(Message 16122)
Posted 13 May 2006 by Robert Everly Post: To Chaplin. From what I see every thing looks ok. But thats just my perspective. With your current batch of WUs, your get .247 credits per 1000 seconds of crunching. By comparison, my recent Dell addition a P4 2.8 is getting .151c/1000sec. This is the box here. Its sole purpose in life is to run Bonic projects. You can double that amount since I have HT turned on, so if its running two rosey WUs, I'm getting the the neighborhood of .302c/1000sec. The only thing that stands out to me is that your laptop only shows 1 cpu. Does it support HT? And if it does, have you turned it off? |
13)
Message boards :
Number crunching :
CASP 7 WU names
(Message 15997)
Posted 12 May 2006 by Robert Everly Post: Can we get a listing of the WU names for the CASP 7 proteins. I want to keep an eye out for them. |
14)
Message boards :
Number crunching :
Report Problems with Rosetta Version 5.07
(Message 15590)
Posted 5 May 2006 by Robert Everly Post: Two 5.07s died here. resultid=19196099 died with <core_client_version>5.4.3</core_client_version> <message>Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> # random seed: 1535558 # cpu_run_time_pref: 21600 # cpu_run_time_pref: 21600 # cpu_run_time_pref: 21600 # cpu_run_time_pref: 21600 # cpu_run_time_pref: 21600 ERROR:: Exit at: .dock_structure.cc line:401 </stderr_txt> and resultid=19101907 died with <core_client_version>5.4.3</core_client_version> <message>Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> # random seed: 3953224 # cpu_run_time_pref: 21600 # cpu_run_time_pref: 21600 # cpu_run_time_pref: 21600 ERROR:: Exit at: .hbonds.cc line:293 </stderr_txt> These are my first errors in a long time, so keep up the good work. |
15)
Message boards :
Number crunching :
CASP6 graphics
(Message 15214)
Posted 1 May 2006 by Robert Everly Post:
If the native structure is unknown, perhaps you should put a "?" or a smiley or something in the native box. Anything will do. |
16)
Message boards :
Number crunching :
To Do List Request
(Message 15168)
Posted 1 May 2006 by Robert Everly Post: Could we get the individual results for proteins updated. The ones found off the home page here: http://boinc.bakerlab.org/rosetta/rah_results.php Results |
17)
Message boards :
Number crunching :
Report stuck & aborted WU here please - II
(Message 13606)
Posted 13 Apr 2006 by Robert Everly Post: Very good news. Keep up the good work everyone! |
18)
Message boards :
Number crunching :
Report stuck & aborted WU here please - II
(Message 13557)
Posted 12 Apr 2006 by Robert Everly Post: Just got my first stuck WU. Yay me :( Anyway its. http://boinc.bakerlab.org/rosetta/workunit.php?wuid=13923483 It's currently at 8+49 CPU time. Stuck at 1.042% It has exceeded both the default run time and my run time setting. I have suspended the WU. Bonic 5.2.13. Please advise as to what to do with this WU. |
19)
Message boards :
Number crunching :
Cancelled work?
(Message 12683)
Posted 25 Mar 2006 by Robert Everly Post: Thanks for the credits, but what happened? Validator go nuts or was the work acutally cancelled? |
20)
Message boards :
Number crunching :
Cancelled work?
(Message 12650)
Posted 25 Mar 2006 by Robert Everly Post: I'm a bit confused here. This WU was cancelled by the project, but completed fine on my end. Showing up in my results list with a credit status of pending, but with errors "cancelled" Also the max # of error/total/success results are 2, 3, 1, and I'm the only one that has run it. So...??? Has some work be cancelled? http://boinc.bakerlab.org/rosetta/workunit.php?wuid=11987704 |
©2024 University of Washington
https://www.bakerlab.org