Posts by Corgi

1) Message boards : Number crunching : Help us solve the 1% bug! (Message 13233)
Posted 8 Apr 2006 by Corgi
PS: AFAIK, the only info needed when reporting a stuck WU, is just WU number e.g. #11819500 in this case (or just its name). If you just abort it, the project will also know the random-seed (it shows in stderr.txt output in resultid)

I believe they would like to know the exact percentage complete that the WU was stuck at.

yes, we need to know this. the name of the work unit is also helpful as we can then see at a glance whether particular types of work units are having the most problems.

Heh, I'd rather be providing too much than too little. Would you remind me where I can find the ID # and date for any suspect workunits again, please?
2) Message boards : Number crunching : Help us solve the 1% bug! (Message 13146)
Posted 7 Apr 2006 by Corgi
I've got another one. Here's a copy of all the text on the BOINC display, plus the URL of a screenshot of the same. When I ran the test from the command prompt, it stopped at exactly the same point -- 39 min+ so far at time of this posting.

FA_RLXpt_hom006_1ptq__361_426_1 (left in memory)
1.042% Complete
CPU time: 9 hr 13 min 58 sec

Corgi - Total credit: 1064.71 - RAC: 16.7777

Stage: Full atom relax
Model: 1 Step: 314653
Accepted RMSD: 10.78
Accepted Energy: -51.5163

Rosetta@home v4.83 [URL]

Screenshot: (39.6Kb)
PC ID: 23940 'Sothis'
GenuineIntel Intel(R) Pentium(R) M processor 1500MHz
Microsoft Windows XP Home Edition, Service Pack 2, (05.01.2600.00)

©2022 University of Washington